SimonF

Yes

See this post. I can look to provide something you can put into a user script but when qemu gets update through releases it will drop support 6 is already deprecated.

We added a change to make sure the support version is not decreated. Currently we are running 10.2.2 and these are deprecated. We did have users with 4.x and that support dropped. Qemu 11 is out now and if we update to that 5.x are likely to go.

Hence why 8.0 was selected.

root@computenode:~# qemu-system-x86_64 -machine help | grep pc-q35
pc-q35-9.2 Standard PC (Q35 + ICH9, 2009)
pc-q35-9.1 Standard PC (Q35 + ICH9, 2009)
pc-q35-9.0 Standard PC (Q35 + ICH9, 2009)
pc-q35-8.2 Standard PC (Q35 + ICH9, 2009)
pc-q35-8.1 Standard PC (Q35 + ICH9, 2009)
pc-q35-8.0 Standard PC (Q35 + ICH9, 2009)
pc-q35-7.2 Standard PC (Q35 + ICH9, 2009) (deprecated)
pc-q35-7.1 Standard PC (Q35 + ICH9, 2009) (deprecated)
pc-q35-7.0 Standard PC (Q35 + ICH9, 2009) (deprecated)
pc-q35-6.2 Standard PC (Q35 + ICH9, 2009) (deprecated)
pc-q35-6.1 Standard PC (Q35 + ICH9, 2009) (deprecated)
pc-q35-6.0 Standard PC (Q35 + ICH9, 2009) (deprecated)
pc-q35-5.2 Standard PC (Q35 + ICH9, 2009) (deprecated)
pc-q35-5.1 Standard PC (Q35 + ICH9, 2009) (deprecated)
pc-q35-5.0 Standard PC (Q35 + ICH9, 2009) (deprecated)
q35 Standard PC (Q35 + ICH9, 2009) (alias of pc-q35-10.2)
pc-q35-10.2 Standard PC (Q35 + ICH9, 2009)
pc-q35-10.1 Standard PC (Q35 + ICH9, 2009)
pc-q35-10.0 Standard PC (Q35 + ICH9, 2009)

The values are changed when libvirt start. https://github.com/unraid/webgui/pull/2625/changes

@Woodpusherghd @emexso

I have made some updates to the API which the dashboard uses. This a plugin that will install the changes, once you have tested you can remove or keep it in place until a release ships with the API changes.

https://preview.dl.unraid.net/unraid-api/tag/PR2011/dynamix.unraid.net.plg

Before you applied it here, on 7.3 it is called boot parameters in settings. And you can set to raw mode to make the edits. But I would do via system drivers



tools->system drivers click the pencil to edit, change the vlaue and press the disk to save.


For your gpu in the i915 driver add
options i915 force_probe=!7d67

in XE driver
options xe force_probe=7d67

Once you have updated these it will required a reboot.

You need to enable boot for the nvmes m2-keym1 and m3 https://youtu.be/yh8Ao5ryOeE?si=3bYHcHgiK-B9w3xy

I have MSI z890 with 245K I needed this driver for my board. Nuvoton NCT6687 Driver its in ca

You need to stop the i915 driver binding to the device and get xe to load for it.

From lspcu you can find the info required for the force_probe.
lspci -nn | grep VGA

00:02.0 VGA compatible controller [0300]: Intel Corporation Arrow Lake-S [Intel Graphics] [8086:7d67] (rev 06)
04:00.0 VGA compatible controller [0300]: Intel Corporation DG2 [Arc A770] [8086:56a0] (rev 08)
0e:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU106 [GeForce RTX 2060 Rev. A] [10de:1f08] (rev a1)
80:14.5 Non-VGA unclassified device [0000]: Intel Corporation Device [8086:7f2f] (rev 10)

in my case 56a0 for the A770

For the i915 driver you need to do

options i915 force_probe=!56a0 note ! in front of the model.

and for XE

options xe force_probe=56a0

You can add them to modprobe files via system drivers in tools as below, but change to match your device.

It needs a newer kernel which will be in 7.3. intel_gpu_top will not work as b60 uses xe driver and not i915. They are talking of adding support to top for xe.

Which version is it using, I would recommend setting to prodcution banch rather than Latest as it breaks things for me.

Goto tools->system devices and acknowledge the PCI changes.

Different query for parity and will be the different for pools. Note temps will not show if drives are spun down.

query ExampleQuery {
array {
parities {
temp
}
}
}

On the menu line there is USB which will take you to
Click on the second icon device mapping, first is port mapping. Then it will take you to the settings. Select the VM and enable auto connect at plugin and VM start. The printer will need to be active for it to show in the view.

When you do the block commit it will remove the snapshot. You would also need to update the XML as the path would be wrong.

The snapshotdb may be incorrect also. Can you cat /etc/libvirt/qemu/snapshotdb/VM name/snapshots.db

There is an option in qemu-img to rebase the base image in the overlay file but I have not tried. I would just do the commit and then move etc.

Unraid API only provides data on UPS via the APC integration, NUT is a plugin and not supported by the Unraid API hence no data in the app.

Click on the green padlock on the page selection line on the right. This will then show a spanner in the machine name panel click on it and it should show panels with check boxes to select or deselect.

I have a PR to add along with CPU power usage.

If the last system did not UEFI boot you will need to do the following.

Check the EFI directory on the flash exists. If it is EFI- rename.

Also make sure the FAST BOOT option in the bios is disabled.

Thanks for the report. This is a bug and will look at a fix for 7.2

That is the PCI root bridge the card is 01:00.0 You can bind to vfio in system devices and it will show in PCI other in the VM template. Or use bus 01, slot 00 function 0 in your xml

You need to remove the mappings off the VM template and let usb manager do it. The mapped outside is because it was mapped in the template.

Will only show IPs if you have loaded guest agent.

Click on the name.

Change to no.

Looks like the modprobe are not in place.
Apr  7 14:54:32 Tower kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
Apr  7 14:54:32 Tower kernel: i915 0000:04:00.0: Your graphics device 4908 is not properly supported by i915 in this
Apr  7 14:54:32 Tower kernel: kernel version. To force driver probe anyway, use i915.force_probe=4908
Apr  7 14:54:32 Tower kernel: module parameter or CONFIG_DRM_I915_FORCE_PROBE=4908 configuration option,
Apr  7 14:54:32 Tower kernel: or (recommended) check for kernel updates.
Apr  7 14:54:32 Tower kernel: xe 0000:04:00.0: Your graphics device 4908 is not officially supported
Apr  7 14:54:32 Tower kernel: by xe driver in this kernel version. To force Xe probe,
Apr  7 14:54:32 Tower kernel: use xe.force_probe='4908' and i915.force_probe='!4908'
Apr  7 14:54:32 Tower kernel: module parameters or CONFIG_DRM_XE_FORCE_PROBE='4908' and
Apr  7 14:54:32 Tower kernel: CONFIG_DRM_I915_FORCE_PROBE='!4908' configuration options.
 
You modprobe files on the boot should look like this.
 
root@computenode:~# cat /boot/config/modprobe.d/i915.conf options i915 force_probe=!4908 root@computenode:~# cat /boot/config/modprobe.d/xe.conf options xe force_probe=4908 root@computenode:~#  
 
Something is spamming the logs. Maybe a plugin doing fan control?
 
Apr  7 15:03:36 Tower kernel: pgrep[43970]: segfault at 14 ip 000015333483c74e sp 00007ffcd20cdd20 error 6 in libprocps.so.8.0.2[974e,153334837000+a000] likely on CPU 5 (core 5, socket 0)
Apr  7 15:03:36 Tower kernel: Code: 75 0a 48 83 c4 50 5d 41 5c 41 5d c3 e8 cb af ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 54 55 48 89 f5 53 48 89 fb <c7> 47 14 00 00 00 00 48 85 f6 0f 84 52 01 00 00 48 8b 86 d0 01 00
Apr  7 15:04:01 Tower root: pwm-hdd-fan: set fan to value 143