Custom Query (16363 matches)
Results (175 - 177 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17431 | invalid | vmdk stops working when upgrading 5.1.30 -> 5.2.4 (Error ID: DrvVD_DISKFULL) | ||
| Description |
When upgrading to version 5.2 (all versions up to and including 5.2.4, my virtual disk has stopped working. The machine is paused at startup and yields the error message below (Error ID: DrvVD_DISKFULL). If I resume the machine, it seems to run sluggishly and never boots. I attach a log and my vmdk file (which uses the raw disk). Note that this file has worked perfectly for many versions of VirtualBox up until and including 5.1.30. If I go into settings in VirtualBox manager and look at "Storage", it says: Virtual Size: 476.94 GB Actual Size: 1.86 TB which I find strange... Error message: 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. Host system reported disk full. VM execution is suspended. You can resume after freeing some space. Error ID: DrvVD_DISKFULL Severity: Non-Fatal Error |
|||
| #17821 | duplicate | vmdk stops working when upgrading 5.1.30 -> 5.2.12 (Error ID: DrvVD_DISKFULL) | ||
| Description |
When upgrading to version 5.2 (all versions up to and including 5.2.12, my virtual disk has stopped working. The machine is paused at startup and yields the error message below (Error ID: DrvVD_DISKFULL). If I resume the machine, it seems to run sluggishly and never boots. I attach a log from an attempt to start using version 5.2.4 and my vmdk file (which uses the raw disk). Note that this file has worked perfectly for many versions of VirtualBox up until and including 5.1.30. Also, if I downgrade to 5.1.30 again, my virtual machine with its ram disk works again. If I go into settings in VirtualBox manager and look at "Storage", it says: Virtual Size: 476.94 GB Actual Size: 1.86 TB which I find strange... Here's the error message I get when trying to start the machine using 5.2 versions: 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. Host system reported disk full. VM execution is suspended. You can resume after freeing some space. Error ID: DrvVD_DISKFULL Severity: Non-Fatal Error |
|||
| #12883 | obsolete | vmdk for USB disk works only first time | ||
| Description |
I created a vmdk for an external hard drive. I was able to run a VB session once. At the end of the session, I went throught the shutdown procedure. The next day, I plugged in the hard drive, checked (via gnome-disks) that the drive and its partitions are visible but not mounted on the host. I then started virtualbox, and got the message: One or more virtual hard disks, CD/DVD or floppy disk image files are not currently accessible. As a result, you will not be able to operate virtual machines that use these files until they become accessible later. The Virtual Media Manager flags the vmdk with an error: Could not open the medium '/local/me/.../sda-full.vmdk'. VD: error VERR_ACCESS_DENIED opening image file '/local/me/.../sda-full.vmdk' (VERR_ACCESS_DENIED) The directory and file mentioned in the error message are owned by me and group vboxusers: -rw-rw---- 1 me vboxusers 629 Mar 27 14:08 sda-full.vmdk The device, /dev/sda has permissions: brw-rw-rw- 1 root disk 8, 0 Mar 21 22:42 /dev/sda brw-rw-rw- 1 root disk 8, 1 Mar 21 22:42 /dev/sda1 brw-rw-rw- 1 root disk 8, 2 Mar 21 22:42 /dev/sda2 I created the vmdk with the command: % sudo VBoxManage internalcommands createrawvmdk -filename ~/VirtualBox\ VMs/Project/sda-full.vmdk -rawdisk /dev/sdc % chown me ~/VirtualBox\ VMs/Project/sda-full.vmdk My host is Ubuntu 13.10, the guest is Redhat 8.0. |
|||

