![]() ![]() i have two interfaces, one natnetwork that i use to reach the internet one host-only that i use to reach the host and between the guests. theoretically i could choose to reach the host from the guests on that network, but i don't want to. I am not having this problem with my "natnetwork" adapters. Symptom is, after a suspend/resume cycle on the host, my guests can still ping each other on their shared host-only network, but they cannot ping the host. i've also tried "disabled" for my windows driver for the virtualbox network interface and then "enabled", with no change. i've tried setting it to "not attached" and then "host-only", without result. it's a host-only adapter not nat or bridged, so i don't think using the lenovo driver for my nic will change anything. I wonder if the root issue is that, from the eyes of VirtualBox, that the network adapter is powering off, and once that happens, it doesn't know how to claw it back. Most people here seem to report issues with sleep. My connectivity is lost until I shut down and restart the VM or if I power down while saving the machine state and power back up. However, if I plug the Surface Pro back into its dock, while the Surface Ethernet Adapter is reconnected to the system, I still get no internet connectivity. ![]() That's understandable as I've disconnected the Surface Ethernet Adapter. If I need to unplug the dock, I lose all network connectivity in my guest OS. My VM is Ubuntu 16.10, and my host is Windows 10 Professional. I have my VM use a bridged adapter on my Surface Ethernet Adapter. I use an Ethernet cable connected to my Surface Dock for all networking needs while in the office. I use a Surface Pro 4 connected to the Surface Dock. I'm running into a not identical but possibly related problem. Can provide logs and assist in any testing support I'd still like to see some time put into fixing it. This bug is painful but is survival-able (the bug where the virtual box host services crash during a accidental shutdown is way worse! :-) Some times, closing the guest - "Save the machine state", reload the save state, then repeat these steps a second time some times works to restore network connectivity (without having to shut down the Virtual Box Manager) I usually have to close the guest and "Save the machine state", close the Virtual Box Manager, then reload the Guest saved state (Haven't had to restart the Host OS) Happens about 80% of the time (20% of the time it works after resume) The host network is being accessed in bridge mode Has occurred with a Windows XP Home Guest running on windows 8/8.1 premium and now windows 10(migrated from 8.1), after suspending/hibernating the Host OS.Ĭurrently Running Oracle Virtual Box 5.0.20 r106931 with latest addons install in the guest. Also experience the guest losing network connectivity issue for quiet some time (Has happen for more than a year - I've been using Virtual box for about 4 years in total) ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |