-
Posts
51 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Young_Max
-
-
33 minutes ago, mkfelidae said:
I never did find a fix for this issue.
Maybe you can try:
First, from command line, type the following:
modprobe -r kvm_intel
Then type this:modprobe kvm_intel nested=1
-
On 2020/4/11 at AM12点20分, mkfelidae said:
我在Windows 10 VM上使用Virtualbox遇到麻烦。在 使用以下命令启动Win10 VM 之前,我已手动启用了嵌套VM :
但嵌套的Virtualbox VM挂在其bios页面上。它们都无法成功启动。
请给我一点帮助吗?
Have you solved your problem? I found a problem with nested virtualization in 6.8.
-
On 12/27/2019 at 6:00 PM, Young_Max said:
@LeoyzenI5 8400 ,opencore 5.4,only update liu and weg, other configurations are the same as yours .But Geekbench score too low.
<qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value=''/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='host,kvm=on,+invtsc,+hypervisor,+avx,+avx2,+fma,+popcnt,+xsave,check'/> </qemu:commandline> </domain>
I used geekbench 5, so this score is probably normal.
-
@LeoyzenI5 8400 ,opencore 5.4,only update liu and weg, other configurations are the same as yours .But Geekbench score too low.
<qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value=''/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='host,kvm=on,+invtsc,+hypervisor,+avx,+avx2,+fma,+popcnt,+xsave,check'/> </qemu:commandline> </domain>
-
1 hour ago, Young_Max said:
@Leoyzen Now my power consumption using virtual macos is 100w,but the power consumption of the virtual macOS in the lock screen state is 130w. Do you have this situation?
Has been solved, is the screen saver problem, replaced with a simple screen saver to reduce power consumption
-
@Leoyzen Now my power consumption using virtual macos is 100w,but the power consumption of the virtual macOS in the lock screen state is 130w. Do you have this situation?
-
@Leoyzen Use your opencore.release.qcow2 file,standby power consumption(Screen Lock) is higher(10W) than normal power consumption. Is there something that hasn't been optimized?
-
38 minutes ago, Leoyzen said:
@Young_MaxCompress and upload your clover.qcow2, let me have a look.
Thanks!
-
5 hours ago, Leoyzen said:
It's not useless, add it back.You don't have much knowledge whether the specific kext is work, so do it.
Add this patch in your clover and add '-v keepsyms=1 debug=0x100' in your boot args and report the output back.Then screenshot you post is useless for debuging.
Comment String <-> Disable panic kext logging on 10.14.x,10.15.x Release kernel Disabled Boolean <->No Find Data<-> 8A0284C0 7447 MatchOS String <-> 10.14.x,10.15.x Replace Data<-> 8A0284C0 EB47
Yes, I haven't used Hackintosh for a long time. I'm getting used to it. I add AppleIntelMCEReporter.kext and patch. It seems that shutting down Lilu logging didn't work
-
1 hour ago, Leoyzen said:
We can not give much help if you give nothing but only "it restarts all the time". You have to learn how to asking for help by giving meaningful feedback first.
- Which version of Catalina do you use?10.15 or 10.15.1?
- Do you add "-v" and "debug=0x100" in your boot args?What is the output?
- Which version of Lilu/WEG do you use?
- What error is it?Screenshot is also fine.
- What is your xml like?
- What is your clover.qcow2 structuration?
You may try to do some research or reading by comments of the older installer guide, then you will find it is not a big problem by changing the resolution of clover and OVMF.Please search the keyword in Google to see how to do such thing.
Sorry, I forgot to provide the information. It's my fault. And logo problem has been resolved. I‘m very sorry to disturb you.
MacOS:catalina10.15.1
Lilu:1.3.9
WEG:1.3.4
AppleALC:1.4.3
“-v” and "debug = 0x100":
clover.qcow2 structuration:
I add AppleIntelMCEReporter.kext , it's useless. This is SpaceInvaderOne clover.qcow2, I only update AppleALC, Lilu and WEG. C lover.qcow2 root directory has EFI folder and nvram.plist file.
├──BOOT
└── BOOTx64.efi
├── Clover|
└── cloverx64.efi
└── config.plist
└── startup.nsh
└── kexts
└── Other
└── AppleAlc.kext
└── Lilu.kext
└── WhateverGreen.kext
└── drivers64UEFI
└── themes
└── tools
clover bootload
then show this,catalina not happening,nothing to recover
And then go back to clover interface, so repeatedly
My xml:
<?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='11' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Catalina</name> <uuid>767f3b01-df6f-de85-277a-82deb76002b0</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/user/domains/Catalina/ovmf/OVMF_CODE.fd</loader> <nvram>/mnt/user/domains/Catalina/ovmf/OVMF_VARS.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='2' threads='1'/> </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='qcow2' cache='writeback'/> <source file='/mnt/user/domains/Catalina/Clover.qcow2'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/MacOS Catalina/macos_disk.img'/> <backingStore/> <target dev='hdd' bus='sata'/> <alias name='sata0-0-3'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <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='0x10'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <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> <interface type='bridge'> <mac address='52:54:00:1f:9e:ee'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='vmxnet3'/> <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-11-Catalina/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='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> <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=xxxxxxxxxxxxxxxxxxx'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/> </qemu:commandline> </domain>
-
@Leoyzen I add the lasted Lilu/WEG to my clover/kexts/others ,it's fine. And I add AppleIntelMCEReporter.kext ,no problem. Then I use IMacPro1,1 as product model, boot failed and restart all the time
-
58 minutes ago, Leoyzen said:
@Young_Max You should use iMacPro1,1 as product model, and add Lilu/WEG to your clover/kexts/others to avoid blackscreen.
If you use Catalina, add AppleIntelMCEReporter.kext too.
Do not use imac18/19, because you don't have iGPU.
@LeoyzenOh, thanks, you are so cool. Can I copy clover.qcow2 EFI to OS EFI? And the launch logo is in the upper left, blurred screen.Can I solve these problems through kext files?
-
-
Changing the product model results in boot failure and black screen
system:catalina
clover:spaceinvaderone clover.qcow2
model imac14 to imac18 and imac19
-
On 2019/11/4 at AM5点05分, oc3lot said:
非常感谢这个@SpaceInvaderOne。我已经按照您的指示安装了Catalina,它运行良好。但是,要使我的Nvidia直通正常运行,我现在正在安装High Sierra,并且在安装开始时出现错误,提示“无法联系恢复服务器”。
我已经删除并重新添加了3或4个High Sierra VM,但是他们都使用开箱即用的配置来做相同的事情。我什至尝试从工作的Catalina构建中复制网络接口XML,但是没有运气。有小费吗?
Maybe it's time synchronization
-
I moved the EFI folder in clover. qcow2 to vmdisk, then removed clover.qcow2 guide , hoping to start it from vmdisk. However, the clover interface appeared,but I choice boot from vmdisk, failure, black screen.
I change product modle in clover.qcow2 config.list . Black screen . I choice 19.3 and 18.3
-
5 minutes ago, david279 said:
I would backup the qcow2 file before even booting the VM. That way if you mess it up you can just go back to the original.
Sorry, what do you mean?The custom clover has been saved clover.qcow2?
-
2 minutes ago, david279 said:
Boot up the VM. When in the VM mount the efi partition. You can use clover configurator to mount the efi. Go into the efi partition and edit the config.plist using clover configurator. Thats how you edit clover. You might want to make a backup of the qcow2 file just in case you break something.
Yes, after configuring clover file, backup it into clover. qcow2 file. Is this all right?
-
1 minute ago, david279 said:
Boot into VM using it. Mount it in Mac and use your favorite tool to configure it. I do most of my work with clover configurator.
I know, but I want to custom clover.qcow2. Do you have some idea?
-
@SpaceInvaderOne Can I customize this file clover.qcow2? Or are there other sources of access?I want to custom clover
-
@Leoyzen AMD RX 460 passthough black screen, Is there any solution? Only add 'pci=noaer'.
2019-11-01 06:14:24.178+0000: Domain id=6 is tainted: high-privileges 2019-11-01 06:14:24.178+0000: Domain id=6 is tainted: custom-argv 2019-11-01 06:14:24.178+0000: Domain id=6 is tainted: host-cpu char device redirected to /dev/pts/2 (label charserial0)
-
12 hours ago, Leoyzen said:
@Young_Max Do you use x570 and zen2?Do you put your AMD card in second pci-e slot?
If so, add pci=noaer in your boot args or try move the graphic to the first slot.
Yes, my amd gpu is in second slot, What is the function of this command
pci = noaer
I'll try it, thanks
-
@Leoyzen Thanks , I will try it
-
12 hours ago, Leoyzen said:
@Young_Max see here
Change RX460 to the first slot ,but my second slot only pcie 3.0 x4, how much this would affect my other graphics card, the gtx1060
AMD GPU Passthough Issue (SAPPHIRE RX460)
in VM Engine (KVM)
Posted
Sapphire RX460 2G GPU passthrough displays exceptions to the virtual machine
But my gtx1060 is fine
What I've tried to do:
1、Now the RX460 is in second slot,I'm going to move it to the first slot,also show exceptions
2、I added VBIOS, either black screen, or display an exception
3、I use RX460 to enter the BIOS interface, everything is normal
4、Is it the VBIOS of RX460 or the driver is wrong, or Sapphire RX460 2G is not compatible with UNRAID? Thanks
SAPPHIRE RX460 2G
tower-diagnostics-20200607-1309.zip