Custom Query (16363 matches)
Results (475 - 477 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16074 | fixed | stateFile reference in vbox file corrupted upon moving VM | ||
| Description |
When I use the VirtualBox GUI to move a VM having a live snapshot, the stateFile reference in the vbox file gets corrupted:
"Snapshots/filename.sav" becomes "Snapshots/filename.sav/Snapshots/filename.sav".
This quickly results in the VM not starting any more.
VirtualBox versions tested: 5.0.26 and 5.1.6
Host: Windows 7x64
Guest: any
Steps (all done via the VirtualBox GUI (except the vbox file copies via Windows Explorer):
Resulting snapshot tree: "Snapshot 1" -> "Current State (changed)". [Actually the creation of "Current State (changed)" here might be the result of another bug, but that's probably another matter.]
VirtualBox - Error
Failed to open a session for the virtual machine Deb.
Details:
The VM session was closed before any attempt to power it on.
Result Code:
E_FAIL (0x80004005)
Component:
SessionMachine
Interface:
ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
VBox.log provides the following error messages: ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={VM cannot start because the saved state file 'Z:\VM\VirtualBox\Machines\Linux\Deb\Snapshots\2016-10-17T12-48-59-752997200Z.sav\Snapshots\2016-10-17T12-48-59-752997200Z.sav' is invalid (VERR_PATH_NOT_FOUND). Delete the saved state prior to starting the VM}, preserve=false aResultDetail=0
GUI: Aborting startup due to power up issue detected...
Note that Deb2.vbox (which was saved immediately after the VM was moved), already contains the invalid path in the snapshot definition: <Snapshot uuid="{12ae5280-3c84-409c-a9eb-03266b75b4e0}" name="Snapshot 1" timeStamp="2016-10-17T12:48:59Z" stateFile="Snapshots/2016-10-17T12-48-59-752997200Z.sav/Snapshots/2016-10-17T12-48-59-752997200Z.sav">
However, the machine state's stateFile is still correct (which is why the VM can still run successfully): <Machine uuid="{4091a06e-3382-47c8-a46d-3f2efa978a8d}" name="Deb" OSType="Debian_64" stateFile="Snapshots/2016-10-17T12-48-59-752997200Z.sav" currentSnapshot="{12ae5280-3c84-409c-a9eb-03266b75b4e0}" snapshotFolder="Snapshots" lastStateChange="2016-10-17T12:49:25Z">
However, in Deb3.vbox, saved after the first ("successful") run after the move, the machine state has also become corrupted: <Machine uuid="{4091a06e-3382-47c8-a46d-3f2efa978a8d}" name="Deb" OSType="Debian_64" stateFile="Snapshots/2016-10-17T12-48-59-752997200Z.sav/Snapshots/2016-10-17T12-48-59-752997200Z.sav" currentSnapshot="{12ae5280-3c84-409c-a9eb-03266b75b4e0}" snapshotFolder="Snapshots" currentStateModified="false" lastStateChange="2016-10-17T12:48:59Z">
This explains why the VM doesn't start any more.
Things get even worse if I then move the VM back to its original (or any other?) location: stateFile then becomes a quadrupled path: "Snapshots/filename.sav/Snapshots/filename.sav/Snapshots/filename.sav/Snapshots/filename.sav" |
|||
| #4491 | fixed | Copy+Paste in GUI dialog boxes freezes GUI (Windows hosts) | ||
| Description |
VirtualBox.exe very frequently freezes upon Copy+Paste within the "Details of ..." dialog box and in the Settings dialog box (e.g. Details => General => Description). In the latter case I end up with an "Aborted" VM - even though I haven't run it! I'm not sure if I should have reopened the closed/fixed ticket #2065 for this, but that didn't mention the freeze I'm experiencing. This problem seems unrelated to the familiar copy/paste problems between host and guest (e.g. tickets #3303, #3211, #2563 etc.). In any case no running guests are involved here: just VirtualBox.exe. Steps:
The problem seems to be with the copying rather than the pasting: when I copy something to the Windows clipboard from a different application (e.g. Notepad), the Details dialog box always pastes that text correctly. Accordingly, text copied from the Details dialog box (step 3 above) can sometimes be pasted into other applications, sometimes not (although the receiving applications never freeze). N.B. I've encountered this problem in versions before 3.0.2 as well, at least going back to 2.2.0, probably earlier. |
|||
| #3950 | obsolete | Linux guest suffers high system CPU utilization | ||
| Description |
When performing certain kinds of tasks within a Linux guest (in this instance specifically Gentoo) certain types of tasks cause the system CPU utilization to jump to very high levels, typicall >70% and often >90%. This seems most pronounced when doing things within portage that run shell scripts or python scripts. I am using the current guest additions. I have tried HZ at 100 and 1000. With and without apic, with and without smp. I get somewhat better performance with preemption set to server instead of the desktop models. |
|||

