vamitrou

in ps output i see a huge command with lots of clutter and a bunch of JSON objects attached. I would need the simplest version of it to just launch a VM and boot from the vdisk.

Hi - I am trying to migrate a VM away from Unraid. I have copied the vdisk file already to the remote host (Debian12), but can't get the QEMU working on it. That's what i tried so far, but it either hangs there, or it says "Booting from Hard drive.." # qemu-system-x86_64 \ -machine type=pc-q35-7.2,accel=kvm \ -cpu host,topoext \ -smp 2,sockets=1,cores=2,threads=1 \ -m 2G \ -drive file=~/machine_image.vdisk,format=raw,if=virtio \ -boot order=c \ -enable-kvm \ -nographic \ -bios /usr/share/OVMF/OVMF_CODE.fd \ -serial mon:stdio \ -drive if=pflash,format=raw,readonly=on,file=/usr/share/OVMF/OVMF_VARS.fd Is there a guide for this maybe or someone that knows how to do it? Cheers.

Thanks for the feedback. I tried it myself with 6.12.6 and it works indeed. However, I can see increase in CPU usage and drops my FPS significantly during gaming. Regardless if I load my games from that particular disk or not. WinFSP and VirtioFS were also disabled in some of the tests.

Thanks so much! Indeed, the virtiofs and specifically the memory backing causes this issue. Removing that from my XML resolves the issue. Bug report on qemu: https://gitlab.com/qemu-project/qemu/-/issues/1270

Hi there - It's been weeks already me trying to debug the situation. I have a Windows 11 VM as my daily driver which randomly freezes (mostly when unused). When this happens I can see the assigned CPU cores are maxing out in the Unraid dashboard. I have tried different configurations and it seems that this behavior only occurs when passing through my RTX3070 GPU. I have observed that without passing through the GPU and any PCI or USB device the system works fine. I really have no idea what to look next. Any advise is greatly appreciated. box-diagnostics-20230519-1218.zip

Resurrecting this old thread since I am also interesting to upgrade parity. In theory, if one writes all 0s to the new drive, and then dd the old parity to the new parity, will this make the new disk ready and up to date?