VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2278 - 2280 of 16363)

Ticket Resolution Summary Owner Reporter
#15705 fixed problem generating ovf file using packer jhkrischel
Description

With virtualbox 5.1, the OVF file created during a packer build has a sparse Network section: `

<Network>

<Adapter slot="0" enabled="true" MACAddress="0800276F4FE5" type="82540EM">

<NAT/>

</Adapter> <Adapter slot="1" type="82540EM"/> <Adapter slot="2" type="82540EM"/> <Adapter slot="3" type="82540EM"/> <Adapter slot="4" type="82540EM"/> <Adapter slot="5" type="82540EM"/> <Adapter slot="6" type="82540EM"/> <Adapter slot="7" type="82540EM"/>

</Network>

`

In comparison, with virtualbox 5.0.26, a packer build will create network settings that are proper:

`

<Network>

<Adapter slot="0" enabled="true" MACAddress="080027967E30" cable="true" speed="0" type="82540EM">

<DisabledModes/> <NAT>

<DNS pass-domain="true" use-proxy="false" use-host-resolver="false"/> <Alias logging="false" proxy-only="false" use-same-ports="false"/>

</NAT>

</Adapter> <Adapter slot="1" enabled="false" MACAddress="080027FB4F38" cable="true" speed="0" type="82540EM">

<DisabledModes>

<NAT>

<DNS pass-domain="true" use-proxy="false" use-host-resolver="false"/> <Alias logging="false" proxy-only="false" use-same-ports="false"/>

</NAT>

</DisabledModes>

</Adapter> <Adapter slot="2" enabled="false" MACAddress="0800279D475E" cable="true" speed="0" type="82540EM">

<DisabledModes>

<NAT>

<DNS pass-domain="true" use-proxy="false" use-host-resolver="false"/> <Alias logging="false" proxy-only="false" use-same-ports="false"/>

</NAT>

</DisabledModes>

</Adapter> <Adapter slot="3" enabled="false" MACAddress="080027E05792" cable="true" speed="0" type="82540EM">

<DisabledModes>

<NAT>

<DNS pass-domain="true" use-proxy="false" use-host-resolver="false"/> <Alias logging="false" proxy-only="false" use-same-ports="false"/>

</NAT>

</DisabledModes>

</Adapter> <Adapter slot="4" enabled="false" MACAddress="080027849293" cable="true" speed="0" type="82540EM">

<DisabledModes>

<NAT>

<DNS pass-domain="true" use-proxy="false" use-host-resolver="false"/> <Alias logging="false" proxy-only="false" use-same-ports="false"/>

</NAT>

</DisabledModes>

</Adapter> <Adapter slot="5" enabled="false" MACAddress="0800275A2598" cable="true" speed="0" type="82540EM">

<DisabledModes>

<NAT>

<DNS pass-domain="true" use-proxy="false" use-host-resolver="false"/> <Alias logging="false" proxy-only="false" use-same-ports="false"/>

</NAT>

</DisabledModes>

</Adapter> <Adapter slot="6" enabled="false" MACAddress="0800272AFF8A" cable="true" speed="0" type="82540EM">

<DisabledModes>

<NAT>

<DNS pass-domain="true" use-proxy="false" use-host-resolver="false"/> <Alias logging="false" proxy-only="false" use-same-ports="false"/>

</NAT>

</DisabledModes>

</Adapter> <Adapter slot="7" enabled="false" MACAddress="080027E80098" cable="true" speed="0" type="82540EM">

<DisabledModes>

<NAT>

<DNS pass-domain="true" use-proxy="false" use-host-resolver="false"/> <Alias logging="false" proxy-only="false" use-same-ports="false"/>

</NAT>

</DisabledModes>

</Adapter>

</Network>

`

There might be other virtualbox 5.1 issues beyond that, but I ran into that when my packer created vagrant boxes were created with no cables connected.

#15704 fixed Vboxvideo ignores DPI settings of the X11-server -> fixed in 5.1.2, possibly earlier vminko
Description

Steps to reproduce:

  1. Configure the X11-server to use a special DPI setting via the "-dpi" parameter. For example, on Gentoo you need to edit /etc/X11/xinit/xserverrc:

exec /usr/bin/X -nolisten tcp -dpi 144 "$@"

  1. Start X11-server and check the actual DPI:

xdpyinfo | grep resolution

Expected result: The actual DPI setting is 144x144 dots per inch

Actual result: The actual DPI setting is 96x96 dots per inch

Problem description: The DPI=96 is hard-coded in the vboxvideo driver (in vboxvideo.c). It's better to keep the DPI value given by the X11-server. The proposed fix to this bug is attached.

#15703 fixed VM terminates, host error "The memory could not be read" wadewh
Description

Host Win10 64 bit Guest Win10 32 bit

Start guest In the guest, start notepad. Type several characters by using alt-numeric key pad combinations. e.g. ALT 072 ALT 071 After a few characters the guest terminates and the host reports the error in the attached image.

The error is not specific to notepad. My initial discovery was in a different editor.

Verified to be present in v5.1.3 also. Tested in 5.0.20 and did not appear to be a problem in that version.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy