Custom Query (16363 matches)
Results (2278 - 2280 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2332 | worksforme | RedHat 5 64-bit install crashes VirtualBox 2.0.2 | ||
| Description |
I am running 64-bit VirtualBox 2.0.2 on a 64-bit machine running 64-bit Vista Business SP1. I am trying to install RedHat Enterprise 5 Update 2 (actually Oracle Enterprise Linux 5 which is simply a rebadged version of RedHat). Part way through the install, VirtualBox crashes. I have run this a ferw times and each time it fails, but at different points. I have attached the VM settings file, the machine log file and the image (.png) file. |
|||
| #2333 | fixed | Crash when disabling network interface => Fixed in 2.0.4 | ||
| Description |
I have installed Solaris 10 5/08 with the VirtualBox packages virtualbox-ose-kmp-default-2.0.2_2.6.25.16_0.1-12.1 xorg-x11-driver-virtualbox-ose-2.0.2-12.1 virtualbox-ose-2.0.2-12.1 on openSUSE 11.0/64bit. The inital installation I did with a one network configured as NAT. If I change this network now to "Host Interface" the guest Solaris will not start with the message Failed to initialize Host Interface Networking.
VBox status code: -3100 (VERR_HOSTIF_INIT_FAILED).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Console
Interface:
IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}
If I start the guest with "Not attached", I the guest starts. Once the guest is in runlevel 3 and I log into it and the JDK is up and running, I tried to change the configuration network configuration. If I click on "Devices" -> "Network Adapters" -> "Adapter 0" the guest crashes immediately. The only message I receive is in the host log "/var/log/messages" saying ... Sep 27 12:12:45 humpyham kernel: VirtualBox[6562]: segfault at 10 ip 7fd0f1fc03d2 sp 41055b20 error 4 in VBoxDD.so[7fd0f1fac000+75000] Sep 27 12:19:47 humpyham kernel: VirtualBox[7200]: segfault at 10 ip 7f9afb9db3d2 sp 41ba9b20 error 4 in VBoxDD.so[7f9afb9c7000+75000] ... |
|||
| #2334 | wontfix | VBox TAP adapters not listed in RRAS in Windows Server 2008 | ||
| Description |
Installing on Windows Server 2008 Standart and adding virtual box host network adapter (TAP) driver does not add it to "Routing and Remote Access" (RRAS) service. I can't see it in as "available routing interface". Adapter is still listed in "control panel network connections" or ipconfig.exe /all correctly. In windows server 2003 (sp1 and sp2) adapter is listed in RRAS service. I tested it. |
|||

