March 6, 20215 yr I wanted to move a VM to an unassigned device to reduce space and the i/o in the cache drives. The VM was booting fine prior to the move, but when moving the img and changing the config to point to the new location, the VM will never boot and get me straight to the interactive shell. Here is the XML of the VM https://pastebin.com/16FnWW7j The BIOS seems to find the drive, but is not detecting it well If I change the drive from virtio to sata, the bios seems to be able to see that it is a drive, but never boot on it I am not sure what to do and I don't want to create a new VM from scratch and reconfigure everything. Thanks
May 14, 20215 yr Have you solved this? I'm having a similar problem. Moved vdisks from cache to the array, pointed the new location and now it's not working anymore. Just boots asking for new install (both on win10 vm and Manjaro VM)
May 14, 20215 yr On 3/6/2021 at 4:57 AM, vinid223 said: I wanted to move a VM to an unassigned device to reduce space and the i/o in the cache drives. The VM was booting fine prior to the move, but when moving the img and changing the config to point to the new location, the VM will never boot and get me straight to the interactive shell. Here is the XML of the VM https://pastebin.com/16FnWW7j The BIOS seems to find the drive, but is not detecting it well If I change the drive from virtio to sata, the bios seems to be able to see that it is a drive, but never boot on it I am not sure what to do and I don't want to create a new VM from scratch and reconfigure everything. Thanks May worth a try, change this: <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/RandomStorage/domains/GitlabRunner - Ubuntu/vdisk1.img' index='1'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> To this, according to redhat instructions: <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/RandomStorage/domains/GitlabRunner - Ubuntu/vdisk1.img' index='1'/> <target dev='vda' bus='virtio'/> <boot order='1'/> </disk>
May 14, 20215 yr I'm attaching my XML also: https://pastebin.com/XBkLt0VL I noticed that the capacity and allocation for all of the vm's is now incorrect!? I made all of the with 40~50G. (All of them are qcow2)
May 14, 20215 yr Author 4 hours ago, gperpetuo said: Have you solved this? I'm having a similar problem. Moved vdisks from cache to the array, pointed the new location and now it's not working anymore. Just boots asking for new install (both on win10 vm and Manjaro VM) I was not able to find a fix. It was not a big deal so I just created a new VM. Ghost82 solution might be worth a try. Let me know if it works
November 20, 20214 yr Solution On 5/14/2021 at 11:01 PM, vinid223 said: I was not able to find a fix. It was not a big deal so I just created a new VM. Ghost82 solution might be worth a try. Let me know if it works I had the same issue after moving vDisk from cache to array. The problem for me was when I point the vDisk path to the new location the type of vDisk changed from "qcow2" to "raw". So after I change this back to qcow2 everything works perfectly.
February 21, 20224 yr On 11/20/2021 at 10:26 AM, aarontry said: I had the same issue after moving vDisk from cache to array. The problem for me was when I point the vDisk path to the new location the type of vDisk changed from "qcow2" to "raw". So after I change this back to qcow2 everything works perfectly. OMG Thank you sooo much!! I had the very same issue and your trick solved it!
October 8, 20223 yr On 11/20/2021 at 10:26 AM, aarontry said: I had the same issue after moving vDisk from cache to array. The problem for me was when I point the vDisk path to the new location the type of vDisk changed from "qcow2" to "raw". So after I change this back to qcow2 everything works perfectly. Omg thank you so much, have had this happen multiple times, just made a new VM every time, but this just fixed it!
December 3, 20223 yr +1 for this, fixed my issue as well. this feels like a bug that should be fixed.
December 18, 20223 yr Helped me solve my issue which was that <boot order='1'/> was not defined on my disk. Good reminder to make a backup of the XML! Edited December 18, 20223 yr by adalfonso
January 18, 20233 yr On 11/20/2021 at 4:26 AM, aarontry said: I had the same issue after moving vDisk from cache to array. The problem for me was when I point the vDisk path to the new location the type of vDisk changed from "qcow2" to "raw". So after I change this back to qcow2 everything works perfectly. Thanks! I pointed my VM at a array backup to test and ran into this. This *seems* like a bug, who/how does this get reported? At least offer a warning that disk type has/will change & option to set? Issue is in the snip <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/domains/ZEUS/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </disk> Edited January 18, 20233 yr by dja
February 28, 20233 yr On 11/20/2021 at 4:26 AM, aarontry said: I had the same issue after moving vDisk from cache to array. The problem for me was when I point the vDisk path to the new location the type of vDisk changed from "qcow2" to "raw". So after I change this back to qcow2 everything works perfectly. This saved me. Wow, nice find. Future people, if this works for you, please reply so that this stays on top of Google.
April 30, 20233 yr On 2/28/2023 at 10:09 AM, flyize said: This saved me. Wow, nice find. Future people, if this works for you, please reply so that this stays on top of Google. Same issue, same fix. Lost 2 hours restoring backups trying to figure out why moving the vdisk was problematic. Unraid should really add a "type" field for people using the UI rather than the XML, it would make it so obvious. Unsure why they wouldn't support the creation of other types (such as qcow2) of vDisks anyways.
July 11, 20232 yr Another thanks for the solution to this, I think the fix would be very easy to implement if it gets noticed by the devs
January 18, 20242 yr Hey guys, having the same Problem with my Homeassistant qcow2 file. Changing the raw to qcow2 in the xml did not work for me. Can anyone point me to the solution, XML added. Spoiler <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='10'> <name>HASS.io</name> <uuid>92177873-08c4-edfe-29cf-d63e1f13625e</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='12'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='13'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-7.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/92177873-08c4-edfe-29cf-d63e1f13625e_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='2' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/application_data/domains/Hassio/haos_ova-11.1.qcow2' index='1'/> <backingStore/> <target dev='hdc' bus='sata'/> <serial>vdisk1</serial> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:42:20:b1'/> <source bridge='br0'/> <target dev='vnet9'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-10-HASS.io/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='2'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> <alias name='tpm0'/> </tpm> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x10c4'/> <product id='0xea60'/> <address bus='6' device='3'/> </source> <alias name='hostdev0'/> <address type='usb' bus='0' port='1'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> Thanks a lot
February 3, 20242 yr On 1/18/2024 at 2:45 PM, Halcyon_81 said: Hey guys, having the same Problem with my Homeassistant qcow2 file. Changing the raw to qcow2 in the xml did not work for me. Can anyone point me to the solution, XML added. Reveal hidden contents <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='10'> <name>HASS.io</name> <uuid>92177873-08c4-edfe-29cf-d63e1f13625e</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='12'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='13'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-7.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/92177873-08c4-edfe-29cf-d63e1f13625e_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='2' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/application_data/domains/Hassio/haos_ova-11.1.qcow2' index='1'/> <backingStore/> <target dev='hdc' bus='sata'/> <serial>vdisk1</serial> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:42:20:b1'/> <source bridge='br0'/> <target dev='vnet9'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-10-HASS.io/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='2'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> <alias name='tpm0'/> </tpm> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x10c4'/> <product id='0xea60'/> <address bus='6' device='3'/> </source> <alias name='hostdev0'/> <address type='usb' bus='0' port='1'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> Thanks a lot @Halcyon_81, were you able to get it going? I’m experiencing the exact thing. Moved some drives around, now I can’t get HA to boot.
February 13, 20242 yr On 11/20/2021 at 11:26 AM, aarontry said: I had the same issue after moving vDisk from cache to array. The problem for me was when I point the vDisk path to the new location the type of vDisk changed from "qcow2" to "raw". So after I change this back to qcow2 everything works perfectly. Thanks!!!! Was about to reinstall my HomeAssistant from scarch, saved me a day or two or retesting everything afterwards. Does anyone know why this happens?
May 6, 20242 yr On 11/20/2021 at 10:26 AM, aarontry said: I had the same issue after moving vDisk from cache to array. The problem for me was when I point the vDisk path to the new location the type of vDisk changed from "qcow2" to "raw". So after I change this back to qcow2 everything works perfectly. 3 years later, this saved my day!
June 2, 20242 yr On 11/20/2021 at 10:26 AM, aarontry said: I had the same issue after moving vDisk from cache to array. The problem for me was when I point the vDisk path to the new location the type of vDisk changed from "qcow2" to "raw". So after I change this back to qcow2 everything works perfectly. I did just registered here minutes ago, just to say: Thank you! This solved my Issue as well. Unraid 6.12.10. I just renamed my VM on the Unraid-GUI while the VM was down, and after booting the VM again, the VM suddenly couldn't find the vDisk anymore. The Unraid-GUI mysteriously loses the Function to change the Disk-Type once it's created. Changing the XML-file also solved my problem: Somehow, the XML-File stated vDisk-Type "raw" all of a sudden. During Creation-Time, I am 100% sure that I changed that to "qcow2". It seems that just renaming the VM caused Unraid to change the Type back to "raw"...
September 24, 20241 yr Thank you!! I was stressing I'd have to recreate home assistant. I couldn't figure out the XML thing I thought I just had to rename the file extension. For other noobs like me, you need to edit the VM and toggle the XML view and change the type as shown by otehrs.
January 7, 20251 yr Another one to say thanks to aarontry for working this out. Still an issue in 2025! Moved my Home Assistant VM from the cache to a new SSD and wouldn't boot (was a QCOW2 disk). I very rarely edit the XML directly, but was able to fix it using this. I do gave an archive of VM backups along with the XML config, so that would have been the next port of call. Not a nice feeling thinking I'd killed it with a simple disk move though!
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.