Custom Query (16363 matches)
Results (2026 - 2028 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15500 | obsolete | Changing Win10 Guest Drive letter triggers I/O Error | ||
| Description |
I have a secondary virtual Hard disk in my Windows 10 guest under an Arch Linux Host. The secondary drive comes up as E:\ in my guest, but I would like it to be D:\ With the Virtual CD-ROM drive disabled via VBox (Just to simplify things), in the Windows Guest I use the usual Windows 'Disk Management' tool to change the drive letter. There is a standard Windows message about the danger of changing a letter, then when I click "Yes" Virtual Box instantly throws an I/O error. Here is the contents from clicking 'Copy' in that VBox error window: An error has occurred during virtual machine execution! The error details are shown below. You may try to correct the error and resume the virtual machine execution. The I/O cache encountered an error while updating data in medium "ahci-0-1" (rc=VERR_DISK_FULL). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards. Error ID: BLKCACHE_IOERR Severity: Non-Fatal Error I will also attach full vbox log. No, I do not have any full disks anywhere to be seen. I have to virtually power-off the box to recover. The drive is back on E:\ after restart. Is this use-case expected to work under VBox? I can't see why not... |
|||
| #2252 | duplicate | Changing debug registers via thread context doesn't work | ||
| Description |
Changing debug registers via thread context doesn't work on guest Windows XP, so no level-3 debuggers can't stop at hardware breakpoints. |
|||
| #16545 | fixed | Changing optical device attachment propagates back into previous snapshot(s) | ||
| Description |
5.1.16 on W10 host (64bit). 1) Create a minimal VM, no disk, no DVD image attached. 2) Take a snapshot. 3) Attach an ISO to VM's DVD (current state changed). When viewing the snapshot's properties, you will observe that it has the ISO image attached to it. I think this is an issue with the way the .vbox config file is processed. |
|||

