Custom Query (16363 matches)
Results (634 - 636 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #6230 | duplicate | upgrade from 3.1.2 to 3.1.4 breaks all VirtualBox adapters | ||
| Description |
After upgrading vb 3.1.2 to 3.1.4 i lost all my virtualbox network-adapters after ending setup you end up with a unknow device in the network section of device manager. if you start vb you don't have a host-only adapter and if you try to create it's ending with message "Failed to create the host-only network adapter".i try to install it normal and as administrator but no luck. un-installing and installing version 3.1.2 does also not work anymore i can't create network adapters. i remove a real adapter on my system and install it again and this works good. if i try to manually install the driver for the unknown device i can pick the wright driver from the list but on install it fails with message "not enough system resources to proceed" ( translated from dutch ). i have a very detailed log from the install. is there a workaround to fix this ? i can't run any version of vb anymore. host os is windows seven hp greetings Erwin |
|||
| #3215 | fixed | upgrade 2.1.0 to 2.1.2 breaks tap interfaces => Fixed in SVN | ||
| Description |
After upgrading from 2.1.0 to 2.1.2 a setup using host interface networking on tap interfaces with proxy-arp and routing (see the article at http://www.savvyadmin.com/virtualbox-host-interface-networking-with-nat/) fails: guests can no longer ping each other. Outgoing traffic (leaving the linux host) works ok. Could this be related with the bugfix for bug #3056? |
|||
| #12787 | obsolete | upg 4.3.6 -> 4.3.8 modifies VM settings | ||
| Description |
Host : XP Pro SP3 Downloaded and installed the newer 4.3.8-92456. A few remarks about this:
Bug 1: VB complains about the Intel Wireless Wifi 4965 AGN card connected to the 2nd NAT (access by bridge), and powers off the VM. Disconnected the 2nd NAT. Restart. Bug 2: After 2 or 3 failed attempts, loading XP in safe mode with F8. Some drivers load, then the VM shuts down unexpectedly.
Somewhere in the log, there are a few lines like this one: After I reverted to 4.3.6, the second crash kept on happening. I decided to verify the VM's settings. I discovered the new 4.3.8 modified the .vdi storage:
In short, 4.3.8 may not like the settings of your VMs! Don't know whether this behavior can be reproduced as I do *not* want to damage my VMs. Please excuse me if this report is bad, it's the first time I fill a bug report. |
|||

