I am unable to find a way to cleanly stop the VM without it corrupting the ext4 filesystem in disk.img. I am using the default ubuntu setup as built with the makefile. I have tried:
In the VM guest: sudo shutdown -h now
In the VM guest: sudo init 0
From macOS host: vmctl stop ubuntu
All of these leave me with a disk.img that is corrupted. Eventually the corruption builds to the point that the system doesn't start properly. I have the Paragon extfs drivers for macOS, and I can perform the following in macOS:
hdiutil attach -nomount ubuntu/disk.img
After that if I verify the filesystem using the paragon extfs driver it says it needs to be repaired. I can repair it using the paragon extfs driver.
This happens after every shutdown, and from what I understand what I'm doing should exit the VM cleanly.
Can anyone shed light on this or recommend an approach that will prevent the VM from corrupting the ext4 filesystem?
I am unable to find a way to cleanly stop the VM without it corrupting the ext4 filesystem in disk.img. I am using the default ubuntu setup as built with the makefile. I have tried:
All of these leave me with a disk.img that is corrupted. Eventually the corruption builds to the point that the system doesn't start properly. I have the Paragon extfs drivers for macOS, and I can perform the following in macOS:
hdiutil attach -nomount ubuntu/disk.img
After that if I verify the filesystem using the paragon extfs driver it says it needs to be repaired. I can repair it using the paragon extfs driver.
This happens after every shutdown, and from what I understand what I'm doing should exit the VM cleanly.
Can anyone shed light on this or recommend an approach that will prevent the VM from corrupting the ext4 filesystem?
Thanks!