Garpa Posted March 16, 2021 Share Posted March 16, 2021 (edited) Hello all, I have a windows server 2019 VM corrupted after the 6.9.1 upgrade. In the log files, it seems my vdisk start in read only mode : -blockdev '{"driver":"file","filename":"/mnt/cache/vm/server/vdisk1.img","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"}' \ In the attached xml I tried to change the loader in loader readonly='no' but no change, I also tried to change the machine type in i440fx-5.1 but again it don't works. When a start the VM I have a Windows BSOD with "UNMOUNTABLE BOOT VOLUME" I read this topic : https://forums.unraid.net/topic/87617-solved-681-cant-start-win-10-vm-after-upgrade/ And I try to make a new VM from scratch and I have attached the existing vdisk but it's the same result. Any idea ? Edit : My vdisk seems to be damaged, when I add the vdisk to another VM the disks can't be read, so I'l searching a wat to restore the vdisk, of course no save of that vdisk Thanks a lot server_new.xml server_old.xml Edited March 16, 2021 by Garpa Quote Link to comment
ktasoul Posted April 5, 2021 Share Posted April 5, 2021 I have the same problem, same message. In my case only black screen in Linux vm. The vm actualy is running fine on VLC. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.