kleinemeise Posted April 11 Share Posted April 11 Hello dear Unraid Community, I currently want to switch from Proxmox and Synolgy to Unraid. But currently I have the following problem: The VMs I created do not start or do not recognize the vdisks as hard drives: I first tested one imported from Proxmox via vma.py (https://forums.unraid.net/topic/120576-guide-import-vm-from-proxmox-backup-to-unraid/) Then I created another new VM using Debian ISO --> that worked too. The VM then ran without any problems. Until I briefly changed the “Primary vDisk Location” for testing. Now the new Debian VM doesn't start either. What am I doing wrong? Does anyone have a tip for me? I think I'm still missing something Quote Link to comment
JorgeB Posted April 11 Share Posted April 11 Point to the existing vDisk in the "Primary vDisk location" Quote Link to comment
kleinemeise Posted April 11 Author Share Posted April 11 17 minutes ago, JorgeB said: Point to the existing vDisk in the "Primary vDisk location" the vDisk is existing --> Quote Link to comment
JorgeB Posted April 11 Share Posted April 11 But is was auto, does is still not start in manual? Quote Link to comment
kleinemeise Posted April 11 Author Share Posted April 11 yes - it doesn't start with manual either. The XML code also looks good or not? 😕 <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Debian-Test</name> <uuid>793c38fc-e160-31e7-d5d8-fbcba5ba4d25</uuid> <metadata> <vmtemplate xmlns="unraid" name="Debian" icon="debian.png" os="debian"/> </metadata> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>1</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> </cputune> <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.fd</loader> <nvram>/etc/libvirt/qemu/nvram/793c38fc-e160-31e7-d5d8-fbcba5ba4d25_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='1' threads='1'/> <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='raw' cache='writeback'/> <source file='/mnt/user/domains/Debian-Test/vdisk1.img'/> <target dev='hdc' bus='sata'/> <serial>vdisk1</serial> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <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'/> <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'/> <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'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <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'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:06:a8:6c'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='de'> <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'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </memballoon> </devices> </domain> Quote Link to comment
kleinemeise Posted April 11 Author Share Posted April 11 with gparted i can start the vm and i can see my vdisk - but a boot is not possible: Quote Link to comment
JorgeB Posted April 11 Share Posted April 11 XML looks OK to me, try typing exit in the UEFI shell, then select the boot menu option. Quote Link to comment
JonathanM Posted April 11 Share Posted April 11 4 hours ago, kleinemeise said: <driver name='qemu' type='raw' cache='writeback'/> try changing raw to qcow2 Quote Link to comment
kleinemeise Posted April 11 Author Share Posted April 11 when i changed raw to qcon2 i get the following message: internal error: process exited while connecting to monitor: 2024-04-11T14:17:42.985421Z qemu-system-x86_64: -blockdev {"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-1-storage","backing":null}: Image is not in qcow2 format Quote Link to comment
JonathanM Posted April 11 Share Posted April 11 Try creating a new VM, but point the primary vdisk to the existing file. Quote Link to comment
Tagtraum Posted April 11 Share Posted April 11 I stumbled upon the same problem today as well (although the timing is probably a coincidence), also while creating a debian VM. First occurence was when renaming the VM after succesfully installing and booting into debian. This moved the .img file to a different folder within the "domains" share, while at the same time changing the folder values in the VM config. Afterwards, same UEFI shell as in the first post. I played around a little bit, it seems as if the VM works as intended, until the vdisk file path in the config is changed. Even if it is changed back to the same value as it was originally. I also tried using /mnt/user or /mnt/cache paths. I currently have a working debian VM (because I never changed the file path after installation), however, if I create a second VM pointing to the same vdisk file, it again shows the UEFI shell on boot. Quote Link to comment
kleinemeise Posted April 12 Author Share Posted April 12 Another example: I create a new VM and cleanly install Debian. I save the path to the image. Then I create a new VM and manually set the path to the image before. The VM doesn't start afterwards - same error 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.