mikeyosm
-
Posts
646 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by mikeyosm
-
-
29 minutes ago, Frank Crawford said:
Folks,
I'm currently maintaining the it87 driver that is now being pulled into your systems, and the current version supports the following chipsets: IT8603E, IT8606E, IT8607E, IT8613E, IT8620E, IT8622E, IT8623E, IT8625E, IT8628E, IT8528E, IT8655E, IT8665E, IT8686E, IT8688E, IT8689E, IT8695E, IT8705F, IT8712F, IT8716F, IT8718F, IT8720F, IT8721F, IT8726F, IT8728F, IT8732F, IT8736F, IT8738E, IT8758E, IT8771E, IT8772E, IT8781F, IT8782F, IT8783E/F, IT8786E, IT8790E, IT8792E, Sis950.
If you are have any of these chipsets, then you don't need to specify the "force_id" option any further. If you do find you need it please contact me and I'll look at adding any missing chipsets, but it will depend on what details I can find.
Unfortunately, for some motherboards, which have multiple chipsets on board, you will need to add the option "ignore_resource_conflict=1" option, in place of the option "acpi_enforce_resources=lax" during the modprobe command, e.g.
for similar reasons, although it only affects the it87 module not others.
Good luck with the use of this module that various people have been improving over the years.
Damn my board had the IT87952E chip - any chance of supporting this one?
-
5 hours ago, song said:
When will "Ventura" be supported? I have upgraded the OpenCORE boot and kext to the latest version. After the installation is completed, the boot appears "five languages" and cannot enter the system!
Me too. Installed Ventura B4 up to the country select screen and then random reboots occur. Using latest 0.8.3 opencore.
-
2 hours ago, mikeyosm said:
it's a fresh install so using opencore v17 as boot picker. Here is my qemu args, please let me know what if anything i need to add/change.... I'm running AMD 3950X - Monterey VM working fine.
old (works with Monterey not Ventura)
<qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+avx2,+aes,+fma,+bmi1,+bmi2,+xsave,+xsaveopt,check'/>
new (still doesnt work with Ventura)
<qemu:arg value='Haswell,vendor=GenuineIntel,+kvm_pv_eoi,+kvm_pv_unhalt,+hypervisor,+invtsc,kvm=on'/>
<qemu:commandline>
<qemu:arg value='-usb'/>
<qemu:arg value='-device'/>
<qemu:arg value='usb-kbd,bus=usb-bus.0'/>
<qemu:arg value='-device'/>
<qemu:arg value='isa-applesmc,osk=ynwa'/>
<qemu:arg value='-smbios'/>
<qemu:arg value='type=2'/>
<qemu:arg value='-cpu'/>
<qemu:arg value='Haswell,vendor=GenuineIntel,+kvm_pv_eoi,+kvm_pv_unhalt,+hypervisor,+invtsc,kvm=on'/>
<qemu:arg value='-global'/>
<qemu:arg value='ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off'/>
</qemu:commandline>UPDATE -
Updated OC boot picker img to 0.8.3 OC release, switched vcpu to 1 core, 1 thread and hey presto, ventura b4 boots to disk image and now is happily installing. I used the same qemu args as Monterey.
UPDATE 2 - Install completed, rebooted got to country picker, crashed and rebooted. Ventura seems to be more of a challenge and I guess needs some opencore/kexts tweaking for this to work reliably in KVM.
-
16 hours ago, ghost82 said:
Ventura is not officially supported.
Anyway, to boot and install it you should upgrade opencore and all the kexts to the latest release version.
Make sure you have also a real haswell or newer cpu, cpus with no avx2 are no more supported.
You may need to change also the emulated cpu from penryn (passthrough or emulated haswell+).
it's a fresh install so using opencore v17 as boot picker. Here is my qemu args, please let me know what if anything i need to add/change.... I'm running AMD 3950X - Monterey VM working fine.
old (works with Monterey not Ventura)
<qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+avx2,+aes,+fma,+bmi1,+bmi2,+xsave,+xsaveopt,check'/>
new (still doesnt work with Ventura)
<qemu:arg value='Haswell,vendor=GenuineIntel,+kvm_pv_eoi,+kvm_pv_unhalt,+hypervisor,+invtsc,kvm=on'/>
<qemu:commandline>
<qemu:arg value='-usb'/>
<qemu:arg value='-device'/>
<qemu:arg value='usb-kbd,bus=usb-bus.0'/>
<qemu:arg value='-device'/>
<qemu:arg value='isa-applesmc,osk=ynwa'/>
<qemu:arg value='-smbios'/>
<qemu:arg value='type=2'/>
<qemu:arg value='-cpu'/>
<qemu:arg value='Haswell,vendor=GenuineIntel,+kvm_pv_eoi,+kvm_pv_unhalt,+hypervisor,+invtsc,kvm=on'/>
<qemu:arg value='-global'/>
<qemu:arg value='ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off'/>
</qemu:commandline> -
Today I tried to update my Monterey Macinabox VM to Ventura B4 with 0 success.
I downloaded the beta via apple dev, ran the installer, waited 15 mins and the VM rebooted back to Monterey as if nothing had happened, no errors, nada. Anyone had any success getting Ventura installed?
-
3 hours ago, BVD said:
I couldnt call it a "known issue" per se, just that achieving full 10Gb throughput almost always takes some tuning.
10Gb is a whole other can of worms, and achieving that level of throughput requires both careful planning, and a decent amount of optimization (both host and hypervisor side).
For one, you're far more likely to need to worry about your peak CPU frequency, context switching, and high interrupt counts. Beyond that, you're much more likely to encounter IO bottlenecks in "weird" (or at least previously unexpected) places. You'll have to start by determining where the bottleneck is. For instance, are you simply mounting an SMB share? Have you tested NFS to see if you get similar IO behavior? What about share passthrough in the VM config (this usually sucks)? Tried the virtio network driver instead of virtio-net? And so on and so on. Just changing things without at least having an inkling of where you're bottlenecking is a recipe for pain.
I'd start by installing something like the netdata docker container; start it up, initiate your 10GB copy, and look for anything that appears to spike in the reported statistics. High IRQ remapping? Single core pegged at 100% utilization? What else does that core have going on if so? What's the reported disk utilization at that time?
Once you figure out what the bottleneck is, then you can start doing research on how to correct it; the solution will be unique to your configuration and the cause of the bottleneck, so just be prepared to do a little googling, and some trial and error along the way.
Happy hunting!
Some good tips, thanks. Switched from vitio-net to vitio and boom! avg 700MB/s - happy with that.
-
3 hours ago, Vr2Io said:
It is know issue.
Not related.
How about enabling smb multichannel will that help? What is the known issue exactly?
-
Hello
I have a bunch of media shares on my UNRAID server and tried copying a 10GB+ file to a W11 VM on the same UNRAID server.
The virtio NIC on the W11 VM is running at 10gbps but I cannot copy from the UNRAID shares any faster than 200MB/s approx 2gbps.
My physical NIC on the UNRAID server is a 2.5gbps onboard adaptor, is this the limiting factor? Is it possible to create a seperate virtual 10gb network so that VMs and shares on the same UNRAID server can copy at the full 10gbps speed available?
Just to add, all shares and VMS are on nvme/ssd drives (seperate).
-
This has started happening to me too. Today I tried to start a 3rd VM, the VM would not start and then the VM page and VM settings page become unresponsive. The only way to resolve is to restart the UNRAID host. Just to add, when this happens, all opther VMs, dockers etc are running fine and no other issues. Just the UNRAID UI VM and VM settings page wont load. Logs show nothing out of the ordinary.
I'm running 6.10 latest RC.
-
On 5/29/2022 at 8:08 AM, ich777 said:
@madelectron & @mikeyosm & @wallas9512 where you able to resolve this issue, or does it run finaly on 6.10.2?
I can surely create a plugin for this chip with the modified driver from the linked GitHub repository but I have to say this driver can cause some funky behavior to the system itself and maybe also cause crashes...
@ich777 Please create a plugin. I have to resort to using acpi_enforce_resources=lax and modprobe it87 force_id=0x8628 to get the system to show temps/fans.
My board is Gigabyte Z690 - https://www.gigabyte.com/Motherboard/Z690-AORUS-MASTER-rev-1x/sp#sp
-
On 2/25/2022 at 12:00 AM, RiDDiX said:
Edit VM with advanced view:
look up these here and add this one marked with the star but please add them without the star
<features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='1234567890ab'/>* </hyperv> <kvm> <hidden state='on'/>* </kvm> <vmport state='off'/>* <ioapic driver='kvm'/>* </features>
Should then looks like this:
<?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='1'> <name>Windows 11</name> <uuid>2993aff2-080c-c6a7-6fd0-cff5b23e0355</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='7'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='9'/> <vcpupin vcpu='4' cpuset='5'/> <vcpupin vcpu='5' cpuset='11'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-6.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/2993aff2-080c-c6a7-6fd0-cff5b23e0355_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='1234567890ab'/> </hyperv> <kvm> <hidden state='on'/> </kvm> <vmport state='off'/> <ioapic driver='kvm'/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='3' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 11/vdisk1.img' index='2'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.190-1.iso' index='1'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:ce:2c:a3'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-Windows 11/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> <alias name='tpm0'/> </tpm> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/vbios/GF108_GT730_UEFI.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x1'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>
Thanks so much for this. Ever since I upgraded from 6.9.2 to 6.10 RCx GPU passthrough was broken. now making these changes, all OK. Star!
-
Anyone? Keen to know if this config would work. Thanks.
-
I too would like to know. I have a X570 mobo that would benefit from the Gigabyte drivers.
I raised another topic here but no response so far.
-
Hi Unraiders
Is it possible in latest UNRAID to dedicate vgpus to vms and dockers using a card like Nvidia A40?
https://www.servethehome.com/nvidia-a40-48gb-gpu-mini-review/
I want to have 2 vGPUs for video out and 1+ vGPU for docker transcoding etc. Does UNRAID goup each vgpu in own IOMMU?
Please advise as 5K is ALOT to spend for a GPU.
Thanks
-
What do you all think of my new build? Decided to spruce up the Torrent case due to the sheer amount of space inside the case.
Just waiting for a new GPU to stick in the top slot for my gaming streaming VM. The RGB panels I got from ColdZero (SSD RGB covers).
4 fit perfectly vertically.
Spec: Gigabyte X570s, Ryzen 3950X, 128GB Mem, 3xSSD, 2xnvme, WX4100 GPU, GT1030 GPU, BeQuiet Fans, Fractal Torrent case, Noctua CPU cooler and fans.
-
4
-
-
Be careful when buying the Samsung Fit drives. I bought one from Amazon UK and it was dead within a week. Got one direct from Samsung and no probs so far.
They also run quite warm when accessed continuously so lifespan wont be that great.
-
1
-
1
-
-
Has anyone here successfully managed to control the fan speed on their AMD GPU within OSX?
I have a RX460 passed through to Monterey but unable to see the fan speeds and/or sensor temps in HW Monitor/iStats.
-
On 6/8/2021 at 12:04 PM, ryanleeis said:
why would I keep getting this error.. I have changed slots.. I've tried this with my 1070ti also.. I can't get the dump??
Script location: /tmp/user.scripts/tmpScripts/dump Vbios/script
Note that closing this window will abort the execution of this script
You have selected this device to dump the vbios from
41:00.0 VGA compatible controller: NVIDIA Corporation GP107GL [Quadro P400] (rev a1)
This does look like a valid GPU to me. Continuing .........
Checking if location to put vbios file exists
Vbios folder already exists
I will try and dump the vbios without disconnecting and reconnecting the GPU
This normally only works if the GPU is NOT the Primary or the only GPU
I will check the vbios at the end. If it seems wrong I will then retry after disconnecting the GPU
Defining temp vm with gpu attached
Domain dumpvbios defined from /tmp/dumpvbios.xml
Starting the temp vm to allow dump
Domain dumpvbios started
Waiting for a few seconds .....
Stopping the temp vm
Domain dumpvbios destroyed
Removing the temp vm
Domain dumpvbios has been undefined
Okay dumping vbios file named p400 gpu.rom to the location /mnt/user/isos/vbios/
cat: rom: Input/output error
Um.... somethings gone wrong and I couldn't dump the vbios for some reason
Sometimes when this happens all we need to do to fix this is 'stub' or 'bind to the vfio' the gpu and reboot the server
This can be done in Unraid 6.8.3 with the use of the vfio config plugin or if you are on Unraid 6.9 or above it can be done
directly from the gui in Tools/System Devices .....So please do this and run the script againDid you figure this out?
-
Same problem with my GT730. Did anyone manage to figure it out?
-
18 hours ago, KnottySean said:
Did you get this figured out? I too would like to get this working fully.
I have been running a windows 10 vm to handle the fans/AIO, it would be great to not have to.
18 hours ago, KnottySean said:Did you get this figured out? I too would like to get this working fully.
I have been running a windows 10 vm to handle the fans/AIO, it would be great to not have to.
So it turns out that the fans are visible to UNRAID/Linux and appear in the UNRAID dashboard. I haven't installed the dynamix fan control plugin as I dont need to control the speed of the fans. The trick is to not tick the fans in the dynamix sys temp settings, that's when things get messy.
-
Hi
I think I have found a bug with the way sys temp handles HID devices for sensor output.
For more detail on the issue, I raised an issue on github here - https://github.com/lm-sensors/lm-sensors/issues/369
In summary -
I have the Corsair Commander Pro connected to my UNRAID server. Sensors show the correct info:
# sensors
corsaircpro-hid-3-2
Adapter: HID adapter
in0: 12.11 V
in1: 4.99 V
in2: 3.35 V
fan1 4pin: 681 RPM
fan2 4pin: 680 RPM
fan3 4pin: 679 RPMThe problem is when I choose one of the fans in sys temp plugin settings - I get this error...
# sensors
Error: File /etc/sensors.d/sensors.conf, line 5: Undeclared bus id referenced
sensors_init: Can't parse bus nameThe sensors.conf file in the plugin dir looks like this -
chip "k10temp-pci-00c3"
label "temp2" "CPU Temp"
chip "corsaircpro-hid-3-2"
label "fan1" "Array Fan"It is line 3 that is generated by sys temp plugin that then causes an issue with sensors.
What could be the problem here?
-
Hi
Running 6.9.2 and connected my Corsair Commander Pro to a USB port to see if I can get fan control working under UNRAID/Linux.
According to the following articles
https://blog.ktz.me/a-usb-fan-controller-that-now-works-under-linux/
https://www.phoronix.com/scan.php?page=news_item&px=Corsair-Commander-Pro-Linux-5.9
the CPro should be detected under Linux kernel 5.9+ but unfortunately it's not being detected in UNRAID.
Running sensors-detect does not list the commander pro at all so not sure if the driver is loaded or indeed even added to the kernel.
The Commander Pro is available for passthrough to a VM and shows up in my USB list so it's defo working OK.
Is there any way I can check if the driver named (corsair-cpro) is available in 6.9.2 UNRAID kernel and if not is it available in 6.10 RC1?
Thank you for your help.
EDIT: lspro shows the driver exists but is not in use.
corsair_cpro 16384 0
-
That's interesting. I just upgraded to PCIE4 motherboard and noticed the same thing. Got a Sabrent Rocket 4.0 2tb in my x570s and benching in UNRAID is in line with your speeds.
Have you figured out a fix yet?
-
Hi
For over a year now I've been using a W10 VM and Nvidia 1030 with Steam installed that I can use to stream games to various devices on my LAN and also to my mobile when I'm out and about. It's working well but can be a drain on my somewhat limited UNRAID resources.
Since the evolution of Stadia, Xbox game streaming etc, I often thought of running something similar on UNRAID if possible.
What would be the most efficient way of setting up a gaming streaming service/docker/vm other than the way I'm currently using it?
Any tips would be most welcome. I'm even thinking of dedicating a more powerful GPU for game streaming but at the moment 1080p over 1Gbps network using GTX 1030 seems to suffice.
Thoughts, ideas welcome please.
Tesla M40 as second GPU Passthrough
in VM Engine (KVM)
Posted
DId this work? I'm thinking of buying a Telsa P4 and splitting the vgpu across multiple Windows 11 VMs