My Unraid server recently has experienced several hard shutdown/reboots which seem to be caused by a RDP connection to my Ubuntu Linux VM. After the last time this occurred, my macOS VM will no longer boot. It was running when the server crashed. After the first reboot, the VM was pegged at ~50% CPU usage. After rebooting the server again, the CPU usage is lower, but the VM still hangs on the initial boot screen.

 

Running

qemu-img check vdisk1.qcow2

indicates no errors in the disk image.

 

I've attached my server diagnostics. One thing that stands out in logs/libvirt.txt are these lines:

2025-04-02 08:25:08.529+0000: 13236: error : virFileIsSharedFsFUSE:3503 : unable to canonicalize /mnt/user/domains/macOS/vdisk1.img: No such file or directory
2025-04-02 08:25:08.530+0000: 13236: error : virQEMUFileOpenAs:12154 : Failed to open file '/mnt/user/domains/macOS/vdisk1.img': No such file or directory
2025-04-02 08:25:08.530+0000: 13233: error : virFileIsSharedFsFUSE:3503 : unable to canonicalize /mnt/user/domains/macOS/vdisk1.img: No such file or directory
2025-04-02 08:25:08.531+0000: 13233: error : virQEMUFileOpenAs:12154 : Failed to open file '/mnt/user/domains/macOS/vdisk1.img': No such file or directory
2025-04-02 08:25:08.537+0000: 13236: error : virFileIsSharedFsFUSE:3503 : unable to canonicalize /mnt/user/domains/macOS/vdisk1.img: No such file or directory
2025-04-02 08:25:08.537+0000: 13236: error : virQEMUFileOpenAs:12154 : Failed to open file '/mnt/user/domains/macOS/vdisk1.img': No such file or directory
2025-04-02 08:25:09.848+0000: 13234: error : virFileIsSharedFsFUSE:3503 : unable to canonicalize /mnt/user/domains/macOS/vdisk1.img: No such file or directory
2025-04-02 08:25:09.848+0000: 13234: error : virQEMUFileOpenAs:12154 : Failed to open file '/mnt/user/domains/macOS/vdisk1.img': No such file or directory
2025-04-02 08:25:10.397+0000: 13236: error : virFileIsSharedFsFUSE:3503 : unable to canonicalize /mnt/user/domains/macOS/vdisk1.img: No such file or directory
2025-04-02 08:25:10.397+0000: 13236: error : virQEMUFileOpenAs:12154 : Failed to open file '/mnt/user/domains/macOS/vdisk1.img': No such file or directory
2025-04-02 08:25:10.410+0000: 13234: error : virFileIsSharedFsFUSE:3503 : unable to canonicalize /mnt/user/domains/macOS/vdisk1.img: No such file or directory
2025-04-02 08:25:10.411+0000: 13234: error : virQEMUFileOpenAs:12154 : Failed to open file '/mnt/user/domains/macOS/vdisk1.img': No such file or directory
2025-04-02 08:25:10.411+0000: 13232: error : virFileIsSharedFsFUSE:3503 : unable to canonicalize /mnt/user/domains/macOS/vdisk1.img: No such file or directory
2025-04-02 08:25:10.412+0000: 13232: error : virQEMUFileOpenAs:12154 : Failed to open file '/mnt/user/domains/macOS/vdisk1.img': No such file or directory
2025-04-02 08:25:10.412+0000: 13235: error : virFileIsSharedFsFUSE:3503 : unable to canonicalize /mnt/user/domains/macOS/vdisk1.img: No such file or directory
2025-04-02 08:25:10.413+0000: 13235: error : virQEMUFileOpenAs:12154 : Failed to open file '/mnt/user/domains/macOS/vdisk1.img': No such file or directory
2025-04-02 08:25:10.415+0000: 13236: error : virFileIsSharedFsFUSE:3503 : unable to canonicalize /mnt/user/domains/macOS/vdisk1.img: No such file or directory
2025-04-02 08:25:10.415+0000: 13236: error : virQEMUFileOpenAs:12154 : Failed to open file '/mnt/user/domains/macOS/vdisk1.img': No such file or directory
2025-04-02 08:25:10.417+0000: 13235: error : virFileIsSharedFsFUSE:3503 : unable to canonicalize /mnt/user/domains/macOS/vdisk1.img: No such file or directory
2025-04-02 08:25:10.417+0000: 13235: error : virQEMUFileOpenAs:12154 : Failed to open file '/mnt/user/domains/macOS/vdisk1.img': No such file or directory
2025-04-02 08:25:16.456+0000: 13231: error : virNetSocketReadWire:1781 : End of file while reading data: Input/output error

 

The vdisk for the VM is actually named vdisk1.qcow2. I renamed it when this became the default for qcow2 formatted vdisk files in Unraid 7. Both the filename and the VM XML define it as vdisk1.qcow2. So I don't know where it's getting this old vdisk1.img filename. I tried renaming the file back to vdisk1.img and changing it in the XML, but it continues to log the same error and the VM doesn't boot. (The VM was previously working fine with the vdisk1.qcow2 filename before the hard system reboot.)

 

My next thought would be to delete the VM and recreate it. But I would like to know what the issue is and where the VM state is corrupted.

 

Any idea what the issue is that's preventing the VM from booting and how to fix it?

hobbes-diagnostics-20250402-0243.zip

Edited April 2, 20251 yr by Ancalagon

I was finally able to fix this macOS VM. I'm not sure exactly what combination of things it was that fixed it (some things I eventually undid before it worked). I had to boot into a new macOS VM installation rescue environment and scan the broken VM's disk for errors, which it found and fixed. That may have been the main problem, but it wasn't the only thing required because it still wasn't working afterwards.