• Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

ab5g's Achievements


Rookie (2/14)



  1. I have narrowed the cause down to the AMD reset plugin. When I remove the plug-in, the sleep wake works fine. I have tweaked a few parameters in the BIOS and the config.plist but to no avail. The windows VM with the AMD reset plugin sleeps/wakes up fine. The Mac one is an issue. One other thing, I see less power draw when using the AMD reset plug-in (booting the system ~20W difference and when it is sleeping ~10W difference). So on one hand it is excellent but cannot get the VM to sleep/wake. Any ideas ? P.S - I have an Rx560 (Polaris) - that 90% of the times is ok without the vendor reset but sometimes rebooting the VM leaves the card in a dirty state and requires the Unraid reboot. I'd prefer to have the vendor_reset on for the predictability.
  2. Do you mind sharing your config.plist ? I somehow managed to get sleep/wake to break. It worked perfectly in some earlier versions and now doesn't. My Ubuntu VM on the same hardware can sleep wake perfectly which makes me believe its something to do with my config.plist.
  3. I have the verbose mode on. The screen turn off, the network adapter I think turns off - cause I am unable to ping the VM. The VM though reports to be in execution (from the unraid UI) - I also have a power meter attached to the server and there I can see the server pulling in higher watts that when it would when the VM would be off. Which means unraid is correct in reporting the VM is in execution state. I will then go and force shut the VM and the power from the socket would come down to normal.
  4. thank you as always for the suggestions. It's happening randomly for me. Sometimes the VM shuts down cleanly and sometimes it needs a force stop. I've always been shutting down the VM from inside the guest. I'll try the other methods you've suggested. Thank you !
  5. The guest is running properly. No installations or deep sleep. I'd let the vm run for a while then use the Mac menu to shut it down.
  6. Would anyone know why a shutdown of the VM doesn't work - I have to force shutdown the VM. The monitors go blank - I think it does shutdown the network card cause I can't ping the VM anymore (I will double check this) Trim is enabled i9 proc and passthrough Rx560. Vendor_reset enabled FL1000 and Fenvi passthrough. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>MacOS BigSur</name> <uuid>232b9f1c-e0e3-4164-650f-f1ff33e3b380</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>33554432</memory> <currentMemory unit='KiB'>33554432</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='5'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='7'/> <vcpupin vcpu='6' cpuset='8'/> <vcpupin vcpu='7' cpuset='9'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-6.2'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/user/system/custom_ovmf/OVMF_CODE.fd</loader> <nvram>/etc/libvirt/qemu/nvram/d45a00d5-3592-413a-82c3-786cd7f22254_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='8' threads='1'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <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='none' io='native' discard='unmap'/> <source file='/mnt/disks/Samsung_SSD/macos_disk.img'/> <backingStore/> <target dev='hdc' bus='sata' rotation_rate='1'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xc'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xd'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:74:44:f9'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </interface> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <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> <rom file='/mnt/user/isos/vbios/amd560.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x70' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'/> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=xxxxxxxx'/> <qemu:arg value='-cpu'/> <qemu:arg value='host,vendor=GenuineIntel,kvm=on'/> <qemu:arg value='-global'/> <qemu:arg value='ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off'/> </qemu:commandline> </domain>
  7. Did you see any reboot issues with the newest update with this ? 12.2 or 12.2.1
  8. +1 to the issue. Reinstalled the flash drive again. Copied contents from the old /boot/config directory and I am seeing the same errors related to permission on the /tmp.
  9. Look at this. https://hub.docker.com/r/onlyoffice/documentserver/ section "Running ONLYOFFICE Document Server using HTTPS"
  10. Cloned work laptop !! What the use for it - I am interested
  11. Apologies - it is the only office document server
  12. Hi Siwat2545 - I am on Unraid 6.10-RC1 and I get the following error when the container starts. It is easily fixed by chmod 640 etc/ssl/private/ssl-cert-snakeoil.key Can you incorporate this into the container image please ? 2021-10-04 04:10:50.135 UTC [135] FATAL: private key file "/etc/ssl/private/ssl-cert-snakeoil.key" has group or world access 2021-10-04 04:10:50.135 UTC [135] DETAIL: File must have permissions u=rw (0600) or less if owned by the database user, or permissions u=rw,g=r (0640) or less if owned by root. 2021-10-04 04:10:50.143 UTC [135] LOG: database system is shut down pg_ctl: could not start server Examine the log output. ...fail! * Starting RabbitMQ Messaging Server rabbitmq-server ...done. Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432 Waiting for connection to the localhost host on port 5432
  13. I have a msi aero itx Rx560 4G with no reset bug on it. You can try that. EDIT: On Linux VM's - I do get error 127 with this Graphics card.
  14. The USB map seems to be correct and so do the power properties. I'll see if the issue persists in Monterey. On a side note I was trying to pass through a iGPU to the VM - just to see if it works instead of the dGPU. The iGPU passthrough works fine in a Windows VM - except I don't get the Tiano Core splash screen. The screen initialized some time into the windows boot process. For MacOS I tried altering the config.plist, applying the framebuffer patches and also changing the smbios to 19.1 but I can't get it to boot. Would be easier to troubleshoot if I could see the verbose logs but that doesn't happen because the display using iGPU does not get initialized. So the question is - is it normal for the display to initialize long after the OS boot process when doing a iGPU passthrough ?