Custom Query (16363 matches)
Results (538 - 540 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #7144 | obsolete | Clipboard sharing stops working when host OS resumes from suspend | ||
| Description |
I suspend my host OS (OS X 10.6.4) while leaving my VirtualBox guest OS (Windows 7) running. Upon resuming from suspend, clipboard sharing no longer works from the guest to the host. However, clipboard sharing still works from the host to the guest. |
|||
| #1353 | wontfix | Problems when discarding snapshots without enough free disk space on the host | ||
| Description |
When the hard disk of the host has not enough free space left to perform discarding an older snapshot, the action aborts with an error when the disk is completely full. The problem is, that the merge of the image to the next is not completed yet. The "old" image is not deleted, but the entry in the xml file (and therefore in the GUI manager) of the virtual machine is gone. So the system is in an invalid state. It seems that the guest still runs normally. |
|||
| #17191 | obsolete | VERR_SVM_NO_SVM with Windows 10 Version 1709 | ||
| Description |
I'm unable to start any VM with "AMD-V is not available (VERR_SVM_NO_SVM)" I've updated to Windows 10 Version 1709 and Virtual Box 5.2.0 because I got Blue Screens with Windows 10 Version 1709 and VirtualBox 5.1.26 (SYSTEM_SERVICE_EXCEPTION in VBoxDrv) All works fine a week ago with Windows 10 Version 1703 and VirtualBox 5.1.26 I've checked Hyper-V (as described in Ticket #14362) after the Windows Update and Hyper-V is not installed. Full message: AMD-V is not available (VERR_SVM_NO_SVM). Fehlercode:E_FAIL (0x80004005) Komponente:ConsoleWrap Interface:IConsole {872da645-4a9b-1727-bee2-5585105b9eed} |
|||

