Custom Query (16363 matches)
Results (235 - 237 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #95 | fixed | Corrupt Video when changing screen properties in WinXP as Guest, Ubuntu Host after installing Guest Additions | ||
| Description |
Description: The video output of the WinXP guest becomes totally messed up. Problem remains after guest reboot. How to reproduce: Right click on WinXP desktop and choose Settings, the try to change either the background color or the wallpaper. As soon as properties are applied the problem occurs and persists. Observation: The guest is obviously running at 1024x768, while the WinXP screen resolution setting shows a contradictary reading of 640x480. Workaround: Don't mess with the guest's screen properties. Booting in VGA mode (F8 while WinXP booting) lets you boot into your system then maybe a system restore might do it. |
|||
| #96 | wontfix | Centos 4.4 guest makes host CPU goes 100 even the guest is idle | ||
| Description |
Running a Centos 4.4 guest under VirtualBox 1.3.6 makes the host CPU goes 100% even after boot. I also have Windows XP and Ubuntu 7.04 guests and they both worked well with host CPU dropping just after the boot. When running Centos 4.4 guests, "top" on host shows 100% busy and "top" on guest shows 99% idle. My host is a Ubuntu 6.10, default Ubuntu kernel, and it has a dual-core CPU. I already tried other Centos kernels, disable ACPI, and reinstalling Guest Addictions but with the same results. The last test was install the Fedora3 kernel (2.6.9-1.667) that is only a bit older but at least install without dependency problems and IT DID GREAT! Host and Guest CPU were minimal after boot just like the other OS's I tested. So it look like a Centos kernel specific problem when running under VirtualBox.
The kernels I tested:
Thanks! Guilherme |
|||
| #97 | duplicate | Network Setup | ||
| Description |
When it comes to virtualising, VirtualBox is the smallest, fastest, best performing software available I have encountered. There is just one problem, the network setup needs work. Whenever I run a virtual machine, I need to access the guest and/or other virtual machines and/or other computers on the local network or internet. I also need to access the virtual machine from the guest or other computers on the network. This can be done by just updating the IP settings on the virtual machine using static IP settings or dynamic (DHCP). My suggestion is to enable one using the VirtualBox interface, to select the guest network card (like Microsoft Virtual PC/Server). You then boot up the virtual machine and set the IP settings static or dynamic. This is the basic setup that I always use and I am sure others also. Currently this is not possible through the interface, and without network connectivity, this excellent software product is useless, because one needs network connectivity 99% of the time when testing. Currently I cannot use it, but I would like to. Thanks. |
|||

