Custom Query (16363 matches)
Results (1042 - 1044 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1794 | fixed | Host hibernation hang after runing Virtual Box with enabled VT-x -> fixed in SVN/2.2 | ||
| Description |
Similar to ticket #1408. Host PC: Notebook HP 9710p, Intel Core 2 duo processor, Windows XP Professional SP3, latest version of Virtual Box (1.6.2). If any guest machine is run with hardware virtualization on (VT-x/AMD-V enabled), the host PC fails to enter hibernation (even after shutting down all of the guest machines and closing Virtual Box). The symptoms are: Start > Shutdown, hibernate, the OS displays "Preparing to hibernate... " message, then the screen goes black and nothing happens. I tried to wait for 15 minutes and nothing happened, only thing to do at this moment is to power off the notebook and power on again. If the guest machines are run using software virtualisation only (VT-x/AMD-V disabled) everything works fine, and the host PC is able to hibernate. Tried with different guest machines, Windows XP SP2, Ubuntu, etc., all behaving the same way. |
|||
| #1795 | fixed | OS X 10.4.6 Install Failed | ||
| Description |
Hi i tried to install 1.6.2 on a Intel mac os 10.4.6 installed like 99% then crased at the end with install failed |
|||
| #1797 | fixed | won't open host network interface => change TAP group setting | ||
| Description |
I have the dreaded "Failed to open host network interface" problem. I'm using Host Interface networking on a Linux host (Debian AMD64, custom 2.6.24 kernel), with a tap device named vbox0 bridged to lan: $ brctl show lan
bridge name bridge id STP enabled interfaces
lan 8000.00161711ac84 no lan0
vbox0
When user andrex tries to start the VM, it fails with the following VBox.log: 00:00:15.216 VirtualBox 1.6.2 r31466 linux.amd64 (May 31 2008 17:30:23) release log
00:00:15.216 Log opened 2008-07-02T15:28:43.546408000Z
00:00:15.230 VRDP: TCP server listening on port 33891.
00:00:15.238 SUP: Loaded VMMR0.r0 (/usr/lib/virtualbox/VMMR0.r0) at 0xffffffff88d44900 -
ModuleInit at ffffffff88d50590 and ModuleTerm at ffffffff88d50560
00:00:15.238 SUP: VMMR0EntryEx located at ffffffff88d50300, VMMR0EntryFast at ffffffff88d505e0 and VMMR0EntryInt at ffffffff88d4fb30
00:00:15.256 Failed to open the host network interface vbox0
00:00:15.256 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005)
aIID={d5a1cbda-f5d7-4824-9afe-d640c94c7dcf} aComponent={Console} aText={Failed
to open the host network interface vbox0} aWarning=false, preserve=false
00:00:15.257 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005)
aIID={d5a1cbda-f5d7-4824-9afe-d640c94c7dcf} aComponent={Console} aText={Failed
to initialize Host Interface Networking.
00:00:15.257 VBox status code: -3100 (VERR_HOSTIF_INIT_FAILED)} aWarning=false,
preserve=false
00:00:15.262 Power up failed (vrc=VERR_HOSTIF_INIT_FAILED, hrc=NS_ERROR_FAILURE
(0X80004005))
00:00:16.862 VRDP: TCP server closed.
andrex is a member of the group vboxusers, which has read/write permission on /dev/net/tun: $ ll /dev/net total 0 crw-rw---- 1 root vboxusers 10, 200 2008-06-15 14:52 tun A few other data points:
Any help would be much appreciated, as I'm currently dead in the water with this VM. NAT networking isn't an option because it doesn't allow me to read Samba shares. Thanks, Andrew. |
|||

