Custom Query (16363 matches)
Results (1096 - 1098 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10170 | fixed | Guest OS temporarily hangs for minutes (ICH9 only) | ||
| Description |
Multiple times in a single session, the guest OS becomes unresponsive for about 1-3 minutes. If I wait long enough, usability is restored. This happens very often, there are again only 5-10 minutes between these temporary freezes. Guest and host are both 64bit Win7. |
|||
| #5685 | duplicate | Windows 7 64-bit guest network connectivity issue | ||
| Description |
Running Windows 7 64-bit host with 8GB RAM and Windows 7 64-bit guest with 2GB RAM on an ASRock P45R2000-Wifi motherboard with an E8500 CPU. It has a P45 North Bridge and an ICH10R South Bridge. The Wifi module is not installed. It has dual NICs which are RealTek RTL8111B/RTL811C, one of which is disabled. The guest NIC is a bridged Intel Pro 1000/MT adapter. In VirtualBox 3.1.0, a 64-bit guest does not acquire a DHCP address, but a 32-bit guest will. Using a static IP address doesn't work either. Changing the guest mode to NAT or Host-only Adapter doesn't help either. The host driver for the NIC is provided by Microsoft, so I also tried installing the latest driver from RealTek, but there was no change. If I roll back to 3.0.12 or 3.0.10, the guest acquires a DHCP address and has a default gateway, but still has no connectivity. Even though it has acquired an IP address, I can't even ping the gateway. A few days ago, I copied the Virtual Disk Image to a portable drive and took it to my home machine which is similar. It has an MSI MS-7519 P45 Neo-F motherboard with a Q9550S CPU with 8GB of RAM, also running Windows 7 64 bit. It has a P45 North Bridge and an ICH10 South Bridge, and also has (a single) Realtek RTL811C NIC. With the same virtual machine settings as my office computer, that configuration runs fine under 3.0.12. I reinstalled 3.1.0 and now my office computer is acquiring a DHCP address, but still can't ping the default gateway. I know it doesn't make any sense. Let me know what other information you need. |
|||
| #9490 | fixed | Linux guest additions text mode video problems after X server starts -> fixed as of 10 Oct 2011 | ||
| Description |
With Linux guest additions version 4.1.0 and 4.1.2, Linux guests have either corrupt video or blank video in text mode consoles after the X server has started. In the kernel boot options, I am using vga=0x317. When booting to runlevel 3, the consoles all work correctly. After running startx or booting in runlevel 5, you can switch to a text console with left control-left alt F1 through F6. Under Fedora 14 as a guest, the screens are completely black. Under SuSE 11.4 as a guest, TTY1 has distorted colors and the fonts are 4 times larger than they should be, and TTY2 through TTY6 are black. When exiting from the X server after startx, the console is unusable. When shutting down or rebooting the guest machine from runlevel 5, you can't read the console shutdown messages. You can switch back to the X server with left alt F7, and the display is fine there. Reverting back to 4.0.x guest additions do not exhibit this problem. I have verified that there are no problems switching back to text mode with version 4.0.8, 4.0.10, and 4.0.12 guest additions under VirtualBox 4.1.2. |
|||

