Custom Query (16363 matches)
Results (2308 - 2310 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10963 | obsolete | [Bridged networking] Guest machine loses connectivity after a while | ||
| Description |
Everything works just fine after boot : the guest has internet access, and anyone on the host's subnet can ping the guest. Here's the list of IP addresses :
Initially, anyone here can ping anyone. Of course it's not limited to ICMP traffic, any IP packet can be exchanged just fine between any of those hosts. And the router doing its job, with anyone on the internet too. Now here's the issue: after waiting a random amount of time (between an hour and a day), the guest partially loses network connectivity. It can actually still send IP traffic to the host, but everything else will fail. Namely, pinging anyone else on the host's subnet will fail, pinging the router will fail, and obviously any internet traffic will fail. So, in terms of IP addresses, 192.168.0.2 can exchange IP traffic with, and only with 192.168.0.3. Traffic between hosts other than the guest still works just fine. Here are some interesting facts :
|
|||
| #10967 | obsolete | Second Display Disapears when using 3D Drivers | ||
| Description |
When running 3D drivers under Windows 7 the second display just dissapears for some reason. I'm not sure where it goes, I have tried searching all desktops and hidden windows, but there is no reference to it anywhere that I can find. No crash report either. |
|||
| #10968 | obsolete | VM crashes when accessed by VNC | ||
| Description |
I am running the latest VirtualBox with the Extension Pack installed. I am running a Mac OS X Server as the guest and have configured Screen Sharing through the system preferences. Each time I try to access the VM remotely via VNC, it crashes almost immediately with the following message: "A critical error has occurred while running the virtual machine and the machine execution has been stopped". This has happened with a different Mac OS X version as well, and occurs regardless of what type of VNC client I use. I tried modifying the VM's parameters like CPU count, RAM size, video memory, 2D/3D acceleration and so on, but nothing has helped. |
|||

