Custom Query (16363 matches)
Results (805 - 807 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #14481 | fixed | std::bad_alloc when starting VBoxHeadless | ||
| Description |
Exact same commands with the same OVA 2.0 import (exported from a 5.0.3 version on Windows 10) for a non-root user gives: terminate called after throwing an instance of 'std::bad_alloc'
while some other OVA files do work properly under the non-root account on CentOS 7 (uname -a gives: Linux server1 3.10.0-229.7.2.el7.x86_64 #1 SMP Tue Jun 23 22:06:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux). /etc/group (partially): root:x:0: vboxusers:x:996:virtualbox virtualbox:x:1001: I do not mind sharing the OVA, but only privately to a person individually (as the OVA does contain private details). |
|||
| #1329 | wontfix | status bar placement | ||
| Description |
If the status bar icons (drive activity, mouse capture etc.) were placed at the top of the window, additional screen real estate could be released hence allowing the guest to run at a higher resolution. |
|||
| #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" |
|||

