Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[6.12.10] Q35 VM config can get corrupted after changing the graphics card.

  • Minor

There seems to be a issue on 6.12.10 when you create a Q35-7.2 VM and assigning a GPU to it. If you remove the GPU afterwards and change it to a virtual Display, the machine no longer works. This is also vice versa! The VM will not boot at all.

 

After some testing I can conclude this is not always happening. Sometimes there is nothing wrong, and otherwise the VM won't boot.

 

The only way to fix this is to remove the whole VM (or have backups) and create everything again. I have already lost my Windows Key because of hardware changes due to this. A XML copy of previous settings when editing would a nice Feature Request. Then I can just set the old values back. I don't backup my VM's itself. But having a XML backup would be nice.

 

I will do my best to diagnose this issue. This problem is very easy to reproduce. I have already provided the XML variants of the working and non-working configurations (see attachments). I hope someone can see what's going wrong here. I think the XML is incorrectly created after editing.

 

I have attached the XML configs of two identical VMs. One will not boot because I switched the display back to virtual, while the working one was created directly with a virtual display. The VM's XML configurations does not have any Disk or PCI Devices assigned to it to keep it simple.

 

I hope this issue can be looked at.

 

I already did find out this is only affected on Machine Q35 configurations. 1440fx seems unaffected. But I still prefer Q35-7.2 due to many reasons.

 

Steps to reproduce:

- Create a windows 11 VM with decent enough specs (And machine Q35-7.2)

- Use Graphics card "Virtual" during creation

- Don't assign anything else. No Disk and no USB devices. And no installation ISO's. Leave that empty.

- Let the VM boot. The VM will then try to boot within PXE.

- Now stop the VM

- Edit the VM and assign a GPU to the VM (You need a GPU to test)

- Start the VM

- Stop the VM (Probably forcefully because it wont boot because of this issue)

- Edit the VM and remove the GPU and assign the graphics "Virtual" back.

- Start the VM

- The VM is no longer working (Guest has not initialized the display yet)

 

Questions about settings? See my screenshot for the config:

 

Screenshot 2024-07-05 at 04.48.02.pngScreenshot 2024-07-05 at 18.09.37.pngScreenshot 2024-07-05 at 00.15.05.png

 

 

VM - XML - defect.xml VM - XML - working.xml

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.