You can either re-create the VM and point to the existing VDI or create a full clone (it will take longer) and the delete the original. If it starts you know you have a problem with the original VM. That will simply copy the config files to the right place and link with the same VDI. The conclusion is then that the corruption is at the VM state level and we need to get rid of that.Ĭreate a linked Clone. Unless you power off your VM the "Close" function on your Vm window will ALWAYS save the state of the machine, so "Discarding" the state is only possible when you have two or more states because in that case at a minimum there is always the LAST state. The possibility is that the VM got corrupted at some point during shut down and that created the config corruption, not a VDI corruption at the VM level, not VirtualBox level. There's an actual file permissions issue.There's a problem with the install of Virtual Box.That completely discards two possibilities:
bash: cd: /build/virtualbox-8vePuu/virtualbox-6.1.16-dfsg/: No such file or cd /buildīin dev home lib32 libx32 media opt root sbin sys usrīoot etc lib lib64 lost+found mnt proc run srv tmp varĪnother thing to notice is that for my case other VMs with VDIs in the same location don't have the problem.
cd: /build/virtualbox-8vePuu/virtualbox-6.1.16-dfsg/src/VBox/Devices/Storage/: No such file or cd /build/virtualbox-8vePuu/virtualbox-6.1.16-dfsg/ So what the rc above really means is that it cannot FIND that file, because /build doesn't even exist (nor it seems to be supposed to). VMSetError: /build/virtualbox-8vePuu/virtualbox-6.1.16-dfsg/src/VBox/Devices/Storage/DrvVD.cpp(5228) int drvvdConstruct(PPDMDRVINS, PCFGMNODE, uint32_t) rc=VERR_VD_IMAGE_READ_ONLYīut the problem is the /build directory does not exist at all. In the example below the file under /build/virtualbox.is in read only mode. VMSetError and look for the matching RETURN CODE (rc) I'll take you through the steps for my particular use case but it should give you a general idea on how to look at the problem in order to find the correct solution.Ī.-Have a look at the actual logs of the VM:Ĭlick on the Menu Item, you should see three choices: The number one thing to do instead of guessing is diagnose and the best way to do that when you don't know what the problem is. Let's look at this from a troubleshooting perspective.
0 kommentar(er)
