VirtualBox

Ticket #9913 (new defect)

Opened 2 years ago

Last modified 2 years ago

Windows XP Guest application causes hang of VirtualBox Guest & Windows 7 Host

Reported by: starfire Owned by:
Priority: major Component: other
Version: VirtualBox 4.1.6 Keywords:
Cc: Guest type: Windows
Host type: Windows

Description

I am running Virtualbox 4.0.10 successfully with a Window 7 host and a Windows XP guest.

Any version of Virutalbox newer than the above suffers the following issue:

When starting an application on the guest called "Cisco IP Communicator v7.0.5.4" the guest hangs and does not respond and also the Virtualbox.exe process running on the host hits a constant 25% of CPU (which is one full CPU as I have a quad core system) and cannot be terminated via windows task manager, also of course Virtualbox GUI on the host also fails to respond - the only way to recover from this situation is to reboot the host.

I have tried things like trying a different networking adapter rather than PCnet FAST III, disabling the VTx, nested paging options, switching back to 1 CPU for the guest but it always causes this hang.

Attached are logs from a successful run of the guest on 4.0.10 obviously as it hangs I cannot attach from when a newer version suffers the hang.

I have held off logging a bug until now as I was hoping newer versions may resolve the issue but the fault is still present.

Attachments

Oracle XP-2011-11-16-16-29-01.log Download (75.3 KB) - added by starfire 2 years ago.

Change History

Changed 2 years ago by starfire

comment:1 Changed 2 years ago by Hachiman

Here is the description where you can find logs for hanging VM https://www.virtualbox.org/manual/ch12.html#idp10077472. Does changing network attachment (NAT or bridged) change behavior anyhow?

comment:2 Changed 2 years ago by starfire

Hi, sorry but I can't see anything specific about hangs mentioned there, only collection of logs? - I don't think this would work when Virtualbox is hung as I can't get the GUI to respond but I can reboot and see what it says in the file $HOME/VirtualBox VMs/{machinename}/Logs then I guess.

I will try changing from NAT to bridged to see if that helps.

Thanks.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use