ab5g
-
Posts
80 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by ab5g
-
-
On 4/28/2023 at 4:57 PM, ghost82 said:
For future purposes I just tested qemu 8.0 without any luck.
My monterey vm is not able to boot (apple screen with prohibition symbol).
keyboard (attached to emulated usb controller) doesn't seem to work too, to boot into opencanopy.
Changing machine type to older versions seems to have no effect.
There are several changes in qemu 8, including acpi-index for hotplug and vfio upgraded to v2.
Opencore log doesn't contain any useful info
I'm passing through a sata controller and it seems mac os is not able to boot from the hd, because it outputs "still waiting for root device"; opencore is able to detect the disk.
My question is if someone has successfully tested qemu 8 with devices passed through, possibly with at least a multifunction device (gpu for example).
Same behaviour on proxmox8 with qemu8. Works well on Proxmox 7.4 with kernel 5.15.
On Proxmox 8, the AMD gpu is the one which causes the machine to hang (removing it and using VMware virtual display adapter works fine). Downgrading the machine type or using an older kernel does not work. So consistent result with what you have there. BTW how did you inject the older DSDT ? and do you have a copy of it
-
On 11/4/2022 at 3:30 PM, ghost82 said:
This could suggest a kernel issue:
6.10.3 --> kernel 5.15.46
6.11.x --> kernel 5.19.x
Can confirm it doesnt work with 6.11.2 also.
Windows on the other hand with 6.11.2 does not seem to have any isses with passed through Fenvi card.
-
+1 to this issue with Fenvi and Unraid 6.11.0(6.11.1). If I keep the Wifi off, the VM boots.
Absolutely no issues with 6.10.3. I am on 1,1 - doesn't look to be a smbios issue but rather a passthrough issue.
The moment it connects to the Wifi, the VM freezes.
-
+1 to this issue with Fenvi and Unraid 6.11.0(6.11.1). If I keep the Wifi off, the VM boots.
Absolutely no issues with 6.10.3.
The moment it connects to the Wifi, the VM freezes.
-
3 hours ago, ab5g said:
I did the port map earlier and it has worked for me since BigSur. The exact config boots normally with Monterey but fails with Ventura.
The EFI is 0.8.4. I'll try tonight to upgrade it to 0.8.5 and see if that makes a difference.
6 hours ago, ghost82 said:the cpu is perfectly capable of running Ventura, so the issue is somewhere else.
Did you upgrade opencore and kexts to support ventura?How old is your efi folder?
Try to boot with basic hardware, i.e. if you have wifi remove it from xml, if you have additional usb controllers remove them, same for ethernet passed through, etc.
Moreover with Ventura usb port mapping becomes very important.
Have narrowed it down to the Ethernet <model type='e1000-82545em'/> that is used. Without it, the OS loads fine (I updated to OC to 0.8.5 too).
Recommended to uninstall Little Snitch as it significantly slows down Wifi.
When I disable the Ethernet adapter, the OS loads fine (I have to disable the adapter within a few seconds of after I enter my password on the login screen). Any ideas ?
-
1
-
-
6 hours ago, ghost82 said:
the cpu is perfectly capable of running Ventura, so the issue is somewhere else.
Did you upgrade opencore and kexts to support ventura?How old is your efi folder?
Try to boot with basic hardware, i.e. if you have wifi remove it from xml, if you have additional usb controllers remove them, same for ethernet passed through, etc.
Moreover with Ventura usb port mapping becomes very important.
I did the port map earlier and it has worked for me since BigSur. The exact config boots normally with Monterey but fails with Ventura.
The EFI is 0.8.4. I'll try tonight to upgrade it to 0.8.5 and see if that makes a difference.
-
On 9/27/2022 at 3:36 PM, ghost82 said:
WARNING: before the official release of mac os Ventura, please note that if you have a physical cpu without avx2 instructions (sandy, ivy bridge for example), it is strongly recommended to disable automatic downloads for updates: if you are using a smbios like the imacpro1,1 (offical mac is compatible with ventura) the update should popup, download and install, but your working vm will stop working because cpus without avx2 are not compatible with Ventura.
Note that there is no emulation for avx2.
So I have a i9-10850K CPU which is passed through to the OSX VM.
<cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='8' threads='1'/> <cache mode='passthrough'/> </cpu>
<qemu:arg value='-cpu'/>
<qemu:arg value='host,vendor=GenuineIntel,+hypervisor,+invtsc,kvm=on,vmware-cpuid-freq=on'/>sysctl -a | grep machdep.cpu.features | grep AVX
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH MMX FXSR SSE SSE2 SS HTT SSE3 PCLMULQDQ VMX SSSE3 FMA CX16 PDCM SSE4.1 SSE4.2 x2APIC MOVBE POPCNT AES VMM PCID XSAVE OSXSAVE TSCTMR AVX1.0 RDRAND F16C
sysctl -a | grep avx
hw.optional.avx1_0: 1
hw.optional.avx2_0: 1
So I am guessing I have avx2.0 present. I tried to upgrade to Ventura, the upgrade went through fine but the system freezes after login window. Any ideas pls ?
-
On 4/25/2022 at 10:38 PM, ghost82 said:
It never happen to me with mac os vms, but this can be very tricky to solve, it happens sometimes with my win 11 vm and still I don't understand why, the system is shutting down, black screen, but the vm is reporting in execution and needs a force stop.
Does it happen randomly or always with your vm?
You can try these, hope it helps:
1. try to lower the pc-q35 version, try for example 5.1, without ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off
2. try to shutdown from the guest
3. try to shutdown from unraid terminal:
virsh shutdown macosVMnameThis uses acpi command
Or:
virsh shutdown macosVMname --mode agentThis uses qemu-guest-agent instead of acpi
Or:
virsh -c qemu:///system shutdown macosVMnameThis last command seems working ok for my win11 vm, no more random hangs.
4. It can be related to hardware passthrough: you could try to remove all optional passed through hardware, add one at a time, and look at what it's causing the hang.
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.
-
On 4/29/2022 at 10:27 PM, ghost82 said:
You can also try to add "-v" verbose boot argument in opencore config, so on shutdown you could see on screen, hopefully, if it's mac os that hangs..
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.
-
10 hours ago, ghost82 said:
You can also try to add "-v" verbose boot argument in opencore config, so on shutdown you could see on screen, hopefully, if it's mac os that hangs..
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.
-
On 4/25/2022 at 10:38 PM, ghost82 said:
It never happen to me with mac os vms, but this can be very tricky to solve, it happens sometimes with my win 11 vm and still I don't understand why, the system is shutting down, black screen, but the vm is reporting in execution and needs a force stop.
Does it happen randomly or always with your vm?
You can try these, hope it helps:
1. try to lower the pc-q35 version, try for example 5.1, without ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off
2. try to shutdown from the guest
3. try to shutdown from unraid terminal:
virsh shutdown macosVMnameThis uses acpi command
Or:
virsh shutdown macosVMname --mode agentThis uses qemu-guest-agent instead of acpi
Or:
virsh -c qemu:///system shutdown macosVMnameThis last command seems working ok for my win11 vm, no more random hangs.
4. It can be related to hardware passthrough: you could try to remove all optional passed through hardware, add one at a time, and look at what it's causing the hang.
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 !
-
22 hours ago, jugaadkabaap said:
Is the guest OS running properly or is performing something like installation / deep sleep states etc ? If latter, the shutdown signals doesn't gets responded - I dunno why. But it had been my experienceThe 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.
-
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>
-
On 12/27/2021 at 11:55 PM, ghost82 said:
I usually share here ovmf files updated to the latest stable releases.
Well, this time I didn't and I wont share stable release 202111, because it seems the package has issues with gpu passthrough, most probably related to this pr, merged after that stable release:
https://github.com/tianocore/edk2/commit/ee1f8262b83dd88b30091e6e81221ff299796099
With the stable release I wasn't able to have a video output of the bios, so no bios access.
There were also some comments on reddit, for example:
So, for who is not able to compile or can't compile the files here are the updated ovmf files, commit 6612ff8 (24/12/2021).
I tested them in mac os 12.1 and kali linux.
I didn't test them in mac os 12.1 after a system update, if they allow for automatic reboot or not (latest working version without this issue for me is v. 202011).
Anyway, if the issue is still there, a forced reboot of the vm solves the issue.
These were built with gcc 10; gcc 11 gives errors due to brotli dependency, a working pr was issued, hopefully it will be merged soon.
Did you see any reboot issues with the newest update with this ? 12.2 or 12.2.1
-
On 12/9/2021 at 2:34 PM, sonic6 said:
Hey @ab5g did you found a solution?
Nope. Living with it
-
+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.
-
On 10/5/2021 at 12:00 AM, HHUBS said:
Where should I get these? I'm just using free cloudflare free ssl and when I check on it, I only have the .pem file, not the .cert file. Sorry I'm not as technical as you are. 😔
Look at this. https://hub.docker.com/r/onlyoffice/documentserver/ section "Running ONLYOFFICE Document Server using HTTPS"
-
On 10/3/2021 at 3:30 AM, okkies said:
yeah, but i needed it now for my cloned work laptop, Now is earlier then sooner than soon
.
i backed up the recovery keys on a seperate drive, also i presume next week when i see an unraid update ill first disable the TPM then upgrade
Cloned work laptop !! What the use for it - I am interested
-
13 minutes ago, Siwat2545 said:
Which container are you referring to?
Apologies - it is the only office document server
-
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
-
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.
-
On 9/25/2021 at 6:06 PM, ghost82 said:
This may be tricky...because also real macs suffer audio issues with usb.
What you can do here is to make sure that you have the correct usb map port kext with applied power values.
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 ?
-
13 hours ago, Squid said:
You can try switching the host reference from /mnt/user/OCIS_TEST to instead be /mnt/cache/OCIS_TEST
Thank you for responding. Umm I do seem to being getting those /tmp related permission errors on a lot of community containers too - owncloud, nextcloud, mariadb. I am on 6.10-RC1. The difference is that those containers do start and I then manually change the permissions on /tmp of the container to 777. I think I have an underlying issue - would you know where to start troubleshooting ?
-
9 hours ago, dlandon said:
I am not seeing this issue and I'm uncomfortable changing the /tmp permissions.
It looks like one of the apps you use might be having an issue writing to the /tmp directory.
Noted. I do seem to have other containers also reporting issues writing to /tmp. Will check in the other thread
** Hackintosh ** Tips to make a bare metal MacOS
in VM Engine (KVM)
Posted
I just upgraded to Proxmox 8.09 and the issue persists.
I was able to get the VM to boot by removing the pcie-express checkmark in the VM definition. @ghost82 - I dont understand what it means but the VM boots under q35 8.1.
I know a lot of users complained about being stuck in Unraid 6.11 because of this issue - perhaps this works for them ?