VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2224 - 2226 of 16363)

Ticket Resolution Summary Owner Reporter
#4020 fixed VM Hangs after saving state Brian Havard
Description

After upgrading from 2.1.4 to 2.2.2 I've had this problem a number of times, though not always (maybe 1 in 4).

After using a VM for a while (doesn't seem to matter what guest OS) I use Host-Q, pick "Save the machine state", watch the progress bar reach 100% and disappear. At this point the VM screen is still greyed and just sits there forever. I can minimize the VM with a Host tap, Alt-F9, and kill the VirtualBox processes. If I kill the VM process last I can later restore the VM successfully, indicating that the save worked.

Host is Ubuntu Jaunty 32 bit.

The last few lines of the log are:

00:06:39.323 Guest Log: VBOXNP: DLL unloaded.
00:06:40.872 Changing the VM state from 'RUNNING' to 'SUSPENDED'.
00:06:42.684 Changing the VM state from 'SUSPENDED' to 'SAVING'.
00:06:46.093 vboxClipboardConvertToUtf8ForX11: VBoxX11ClipboardReadVBoxData returned VERR_TIMEOUT
00:06:47.277 SharedFolders host service: saving state, u32ClientID = 1
00:06:47.704 Changing the VM state from 'SAVING' to 'SUSPENDED'.
00:06:47.715 Console::powerDown(): A request to power off the VM has been issued (mMachineState=9, InUninit=0)
00:06:47.720 SharedFolders host service: disconnected, u32ClientID = 1
00:06:47.720 VBoxX11ClipboardStopX11: stopping the shared clipboard X11 backend
00:11:47.757 VBoxX11ClipboardStopX11: rc=VERR_TIMEOUT
#4022 fixed Windows XP application freezes - continued Franz
Description

I have re-checked the occurrenct of Windows XP (guest) freezes reported previously (ticket # 2823 ), on both 32 and 64 bit Linux host installations, using vbox version 2.2.2: they continue to occur on both systems. As a general rule, the faster the computer, the less freezes. In the same sense, switching off services under Windows translates into faster execution of its applications and less freezes, as does Windows optimizations (registry and hard disk optimization), and not mounting USB disks under Windows but instead accessing them via Linux. I have not seen that switching off any specific service stops windows freezes altogether. Under high load with more than one Windows application open, and frequent disk access, any application may get stuck with the 'xxx not responding' message. In practically all cases, clicking through the file system in a separate window will unblock the application, although it might take several rounds of clicking to permit regular work again. To test if caching might be involved, I tried specific caching software under windows, as well as switching of bidirectional cut and past under vbox/Linux: no significant change was observed.

When looking at vbox log files, I noticed in both installations the same two types of potential errors: one that I do not understand, that comes in blocks of repeats like:

00:00:03.998 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001! 00:00:03.998 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001! 00:00:03.999 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001! 00:00:03.999 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001!

and another one relating to networking when the machine is not connected to the Internet

00:00:18.813 UDP: sendto fails (Network is unreachable) 00:00:19.564 UDP: sendto fails (Network is unreachable) 00:00:20.315 UDP: sendto fails (Network is unreachable) 00:00:21.066 UDP: sendto fails (Network is unreachable) 00:00:21.816 UDP: sendto fails (Network is unreachable)

Imagining that network access failure might be somehow involved in the observed freezes, I switched the network service off under vbox settings and tested again: this results only in less frequent freezes. When checking vbox log files for correlation of above error messages with any freezing event: none observed. It seems that Windows simply looses track of information of the connected file systems (hard disk, external USB drives etc) and that applications then report 'not responding'. As soon as the disk is accessed by any Windows service with file management (such as clicking 'My Computer, a symbolic link to a file system and than clicking through the file system...), it somehow refreshes information and unblocks the application. Windows application with heavy, repeated access to the file system seem to freeze more frequently.

I suspect that tweaking file system timeout parameters at the vbox/Linux level might lead to a solution; so would be probably a more direct use of the Linux file system (e.g., as implemented in Win4Lin). I doubt that changing windows-internal parameters might help, as this type of error is quite specific to vbox emulation, but I will try out any suggestions.

#4027 fixed I can't connect to the internet on Virtualbox Windows XP Billie West
Description

I was able to connect to the internet, then just a few days ago, for some reason, the internet quit working. I am able to connect to the internet fine on the Mac OS X host, just not on Virtual Box. I turned off the Windows firewall and I still cannot connect.

(Windows XP guest on a Mac OS X host)

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy