Describe the issue
When creating a new VM (Ubuntu Server, one that uses QEMU for virtualization) and then trying to start it up, I get a nondescript "Error" dialog with absolutely no context, like this:
This issue was mentioned in issue #3941.
In the replies to the issue, you said that the fix is to set the QEMU flag highmem=on.
The expected behavior after setting the flag is a working VM, but the result is a hard kernel panic.
What can I do to fix this issue?
Configuration
- UTM Version: 3.2.0
- OS Version: 12.4
- Intel or Apple Silicon? Apple SIlicon.
Debug log
This debug log was acquired after UTM gave the "Error" screen that has no context.
debug.log
Upload VM
config.plist:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>ConfigurationVersion</key>
<integer>2</integer>
<key>Debug</key>
<dict>
<key>DebugLog</key>
<true/>
</dict>
<key>Display</key>
<dict>
<key>ConsoleFont</key>
<string>Menlo</string>
<key>ConsoleFontSize</key>
<integer>12</integer>
<key>ConsoleOnly</key>
<false/>
<key>ConsoleTheme</key>
<string>Default</string>
<key>DisplayCard</key>
<string>virtio-ramfb</string>
<key>DisplayDownscaler</key>
<string>linear</string>
<key>DisplayUpscaler</key>
<string>nearest</string>
</dict>
<key>Drives</key>
<array>
<dict>
<key>DriveName</key>
<string>cdrom0</string>
<key>ImageType</key>
<string>cd</string>
<key>InterfaceType</key>
<string>usb</string>
<key>Removable</key>
<true/>
</dict>
<dict>
<key>DriveName</key>
<string>drive0</string>
<key>ImagePath</key>
<string>data.qcow2</string>
<key>ImageType</key>
<string>disk</string>
<key>InterfaceType</key>
<string>virtio</string>
</dict>
<dict>
<key>DriveName</key>
<string>driveDB0577EA-561E-4F83-8A3B-DE8D342D1C3D</string>
<key>ImagePath</key>
<string>efi_vars.fd</string>
<key>ImageType</key>
<string>none</string>
<key>InterfaceType</key>
<string></string>
</dict>
</array>
<key>Info</key>
<dict>
<key>Icon</key>
<string>linux</string>
</dict>
<key>Input</key>
<dict>
<key>InputLegacy</key>
<false/>
</dict>
<key>Networking</key>
<dict>
<key>NetworkCard</key>
<string>virtio-net-pci</string>
<key>NetworkCardMAC</key>
<string>CA:45:64:0A:B0:EE</string>
<key>NetworkMode</key>
<string>shared</string>
</dict>
<key>Printing</key>
<dict/>
<key>Sharing</key>
<dict>
<key>ClipboardSharing</key>
<true/>
<key>DirectoryReadOnly</key>
<false/>
<key>DirectorySharing</key>
<true/>
<key>Usb3Support</key>
<true/>
<key>UsbRedirectMax</key>
<integer>3</integer>
</dict>
<key>Sound</key>
<dict>
<key>SoundCard</key>
<string>intel-hda</string>
<key>SoundEnabled</key>
<true/>
</dict>
<key>System</key>
<dict>
<key>Architecture</key>
<string>aarch64</string>
<key>BootDevice</key>
<string></string>
<key>BootUefi</key>
<true/>
<key>CPU</key>
<string>default</string>
<key>CPUCount</key>
<integer>0</integer>
<key>ForcePS2Controller</key>
<false/>
<key>Memory</key>
<integer>4096</integer>
<key>RngEnabled</key>
<true/>
<key>SystemUUID</key>
<string>1198089C-018C-405E-8555-0FB1A0DD69A8</string>
<key>Target</key>
<string>virt</string>
<key>UseHypervisor</key>
<true/>
</dict>
</dict>
</plist>
Describe the issue
When creating a new VM (Ubuntu Server, one that uses QEMU for virtualization) and then trying to start it up, I get a nondescript "Error" dialog with absolutely no context, like this:
This issue was mentioned in issue #3941.
In the replies to the issue, you said that the fix is to set the QEMU flag
highmem=on.The expected behavior after setting the flag is a working VM, but the result is a hard kernel panic.
What can I do to fix this issue?
Configuration
Debug log
This debug log was acquired after UTM gave the "Error" screen that has no context.
debug.log
Upload VM
config.plist: