Custom Query (16363 matches)
Results (2086 - 2088 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16078 | fixed | NVMe controller not working | ||
| Description |
Create a Windows 10 virtual machine in default configuration (no EFI, 1CPU). Then, after everything is installed and Windows is updated to version 1607, add an NVMe controller and a harddisk. Result: In device manager, the NVMe controller shows up and the proper drivers are used. But it is marked with a yellow exclamation triangle. The NVMe drive is not available and cannot be partitioned. On Linux, the NVMe controller doesn't work after "rmmod nvme; modprobe nvme". Tested with the LiveCD ubuntu-16.10-desktop-amd64.iso. |
|||
| #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" |
|||
| #16069 | fixed | Windows 10 guest aborts | ||
| Description |
I have a Windows 10 guest that was running fine until the Microsoft October updates (released 10/11/2016) that now aborts every couple of hours. I do not see any messages in the vbox.log. The log only appears to have information from just after boot. I did have an issue after updating to Windows 10 1607 with shared folders that I see is fixed in 5.1.7, however, I have not installed 5.1.7 in that I am waiting until the mainstream release of 5.1.8. I am not using shared folders until then. I can provide any additional information requested, but I do not see any submitted bugs that specifically mention my issues. The only thing that has changed on my guest is the Microsoft October updates from 10/11/2016. |
|||

