VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2116 - 2118 of 16363)

Ticket Resolution Summary Owner Reporter
#6429 obsolete Closing Vbox and save the guest state reaches 97-99% and hung forever (I killed it after 10 minutes or so.) ci-zephyurus
Description

Guest: GNU Debian/Linux (32bit) Host: Windows XP SP3 (32bit) VBOX Version: 3.1.4 r57640

When I tried to save the running state by clicking on "[x]" button on the upper right corner of VirtualBox, VBox started to save the state (after I click save the virtual machine state), but after reaching 99%, it didn't proceed any longer. And the remaining time shown was initially about 10 seconds, but then grew longer and longer until I killed it after about 10 minutes of non-activity. (I checked using windows task manager and performance monitor that no CPU was used by Vbox, and no disk I/O was taking place.)

Additional Info: A suspect. VBox driver for clipboard sharing hung?

The reason I wanted to shut down XP host was that somehow for some reason, XP programs began complaining that it could not clear clip buffer(??) and pasting began failing everywhere. Initially I thought the paste problem was only with guest-to-host, and host-to-guest, but as it turned out inter-program pasting between host win XP programs failed(!). So I could not copy a paragraph in ThunderBird browser on win XP host to MS Word program on win XP host.

So I thought something was fishy with win XP host, and decided to reboot XP anyway although the hung Vbox window was still present.

But during the shutdown attempt, a service named (SORRY I FAILED to take note of the name !) *VBOX*Clip*Share* something service could not be stopped. (A dialog popped up that it waited for the service to stop, and obviously it was not stopping. When I hit [terminate], then the dialog disappeared as well as the background hung Vbox(!), too (the greyed out window of Vbox which was staying on the background disappeared, too!)

I noticed there are clipboard related problems:

ticket # 417 Shared clipboard does not work and also affect other programs

seems to be very like the problem I experienced.

The latest ones are: ticket 6150 Bidirectional Clipboard copy stops working eventually, Win client to Fedora host, then both ways. ticket 6091 Paste into windows guest from linux host hangs ticket 5266 Shared Clipboard stops working

But I am not sure if they are related to my particular hung problem.

Log is attached.

#4507 duplicate Closing network connection VB 3.0.0-2 kraki@volny.cz
Description

I have last release of Kubuntu 9.4 on Windows XP SP3. In VB i use Intel desktop NIC. Usually after higher network traffic on hosted OS the network connection on guested OS (Kubuntu) has been unstable. I have about 10 ssh connection to remote system and randomly the connection are closed with:

Read from remote host XXX: Connection reset by peer Connection to XXX closed.

If i go back to version VB 2.2.4 i don't have this problem.

#11289 fixed Closing window (and saving state) via keyboard causes abort on resume => Fixed in SVN CaptainDave
Description

If you press the host window manager's close window key, e.g. Alt+F4 in Fluxbox or Windows+x in spectrwm/scrotwm, you are presented with the save state/shutdown/power off dialog as expected. However, if you choose to save the guest state, on restarting the VM, the progress bar goes to the end and then the VM aborts with a failed assertion regarding !VMCPU_FF_ISSET(pVCpu, VMCPU_FF_INTERRUPT_PIC).

Stopping and saving the state of the guest by closing the window with the mouse, with the host key+q combination, or via "vboxmanage controlvm <VM> savestate" from a terminal all resume properly.

If I had to wager a guess as to what's wrong, it's that the guest expects the modifier key in the close combination, e.g. the Alt in Alt+F4, to be depressed when it resumes, as it certainly was when its state was saved, and it can't handle the unexpected condition.

Please note that bug number 8660 is largely repetitive of this, but the original reporter of that one didn't figure out the (or at least "this") cause of the problem. Plus, it's an old report of an old version.

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