RenatoEurope

Hi, my system is located in the CET timezone and the system bios is set accordingly. However when I start a VM, I get the clock set to a totally different time, by the look of it it must be US central or US pacific, albeit the windows setting, in the VM is set for the CET time zone. I have to speculate it is the OVMF bios which has a different setting. How do I correct it? Thank you in advance

Hi Robin, Thank you for helping. In relation to your questions: 1) Rebooting the Unraid system does not change the situation. 2) in relation to nvram, I normally just modify in form mode the standard templates for Linux and Windows 10, I never messed around with the nvram settings, I went to check in the XML view one Windows 10 derived template and indeed found : <os> <type arch='x86_64' machine='pc-q35-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/0d25bedb-67e7-0d1f-a1cd-c570768c2f85_VARS-pure-efi.fd</nvram> </os> As an ignorant on the subject, and not knowing the first think about nvram, what it is and what it does, I can observe the nvram files seem to have the creation timestamp of the VM they belong to and hence I could speculate, to test your theory, I could save those files on an hd and try to restore them when a VM I force to stop, fails to restart and see whether, with the restored file, the VM can come to life again.

I do not know what hook files are in this context so I can speculate I do not. I attached the zip file of my diagnostics. Thank you for any help you could provide. tower-diagnostics-20221101-1146.zip

Hi, I just upgraded to 6.11.1 from 6.9.2, in hope to find a solution to a weired problem: Most of the times (not all of the times) forcing to stop a VM in 6.9.2 mean having to re-create the VM template because the one used would not work anymore, the VM would allegedly start but than never work. The only way to re-launch that VM would be to re-create the VM template, assigning the same HD, video card, etc. Launching the "old" template with VNC and than connecting to the VM via VNC showed a "The system has not initialized the display" window. Recreating the Vm template, by clowning it , allowed the VM to restart correctly. Is there a work around to this problem? Thank you in advance for helping.

I have a similar problem, just making sure it is not EXACTLY the same problem do you know if the problem with the shutdown surfaces just after you have used a VM? In my case, if I just start the system up and then shut it down, it shuts down ok, just if I have used a VM, the shutdown never completes.

Hello, the problem appeared since the upgrade, it was working fine before. From a clean boot up of the system I can perform a clean shutdown, but if I launch any VM (the VM loads correctly, works perfectly and apparently shuts down correctly) than the VMS page stops loading. My system is based on a threadripper 3270 with a 3080ti and a vega64 video cards loaded. 128 GB Ram. anybody has any idea on where to start troubleshooting this problem?

Hello, the problem appeared since the upgrade, it was working fine before. From a clean boot up of the system I can perform a clean shutdown, but if I launch any VM (the VM loads correctly, works perfectly and apparently shuts down correctly) than the VMS page stops loading. My system is based on a threadripper 3270 with a 3080ti and a vega64 video cards loaded. 128 GB Ram. anybody has any idea on where to start troubleshooting this problem?

Is it just me or it shows an amateurish approach not to support by default AMD products and where the solution proposed is for the user to load a different module? This should be taken care by unraid, that is what we pay the license for. BTW, I am another unhappy customer who cannot get unraid 6.10.3 to boot because I have a threadripper. I canot even load the alternative module by myself as I never get to the point where I can run a terminal.

I got it to work, I do not think I have hardware acceleration, but I just run it using VNC as I wanted to be able to run it inside other OS.

Hi, I create a virtual machine, specifying VNC as the graphic card. I can connect with VNC using the VNC client but I was after a better experience so I installed VNC viewer. At the prompt, I enter the machine IP, ex: 192.168.0.222:5900 I, I checked on my VM IP address but VNC viewer tells me "The Connection was refused by the computer" what else do I need to do? Thanks for any help.

Hi, I would need to install an Android x86 vm in my unraid system. I am able to execute the installation that seems ok but then they system cannot boot from the virtual HD, I tried also to set the disk as a sata, but it does not help.ody Has any experience with this? Thank you in advance. well, it was convoluted but I could repeat it. chose Install and create the partition. than, after you made sure the installer has written the partition to disk, reboot your system and, at the prompt, chose "more options". One of those is auto install. go for it and it works.

Not sure what hardware I have, however my bluetooth is working perfectly under Big Sur (I installed that and it is now working great) so I would speculate this is aa Monterey problem, unrelated to my hardware. Thank you for your help never the less.

Hi, I have installed Monterey an I am having bluetooth problems, the bluetooth device is recognized and, in theory is working, however I cannot pair any device, sometimes they get recognized, sometime not, however I never manage to pair any. Anybody has any idea? Thank you in avance.

Entering the ovmf bios setup works, I will try your other option, thank you for your help in the meantime, I will post the update.

Tried that, it does not help.

<?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Macinabox Monterey</name> <uuid>92539b9c-adff-a611-9d89-5eefa0405ef6</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="BigSur.png" os="linux"/> </metadata> <memory unit='KiB'>25165824</memory> <currentMemory unit='KiB'>25165824</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>12</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='4'/> <vcpupin vcpu='4' cpuset='5'/> <vcpupin vcpu='5' cpuset='6'/> <vcpupin vcpu='6' cpuset='7'/> <vcpupin vcpu='7' cpuset='8'/> <vcpupin vcpu='8' cpuset='9'/> <vcpupin vcpu='9' cpuset='10'/> <vcpupin vcpu='10' cpuset='11'/> <vcpupin vcpu='11' cpuset='12'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/92539b9c-adff-a611-9d89-5eefa0405ef6_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'/> <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='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-CT1000BX500SSD1_2020E2A2DEBF-part6'/> <target dev='hdc' bus='sata'/> <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='usb' index='0' model='ich9-uhci1'> <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'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </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='0x10'/> <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'/> <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'/> <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'/> <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='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x16'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0x17'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x7'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </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:b3:97:ae'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='es'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0f' slot='0x00' function='0x0'/> </source> <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='0x19' 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='0x46' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x47' slot='0x00' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x4a' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <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='************************'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <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,+fma4,+bmi1,+bmi2,+xsave,+xsaveopt,+rdrand,check'/> </qemu:commandline> </domain>

Hello, I have a VM to which I pass an NVME drive. It boots ok from it as long as it is the only drive. However, I would like to associate to the VM also a SATA drive which, being the only sata drive, it is always seen as the primary disk and the VM tries to boot from there. How can I change the behaviour so that I can boot from the nvme drive?

I already have it running on unraid, I was planning to mirror the disk image into the nvme drive using dd, I have the controller that can be assigned to the vm and then I will need to tell the vm to use that as the bootable disk. Well, at least that's the plan . for the nvmefix to be loaded, do I just need to put it in the kext directory or do I need to add it to the config.plist?

Hi, I did a quick look to see if this was addressed before but google did not return any useful info. Is it possible to run the MacOs image from an NVME? I saw spaceinvader's video on running windows from an NVME drive but, well, it was windows and, unless it is already set up for doing so, this would require come clover/opencore configuration. Has anybody acheived this? Of course if there is a guide somewhere, feel free to link it. thank you in advance for your help.

Hi thank you for your reply, I thought of using dd but I never used it before (but for preparing a bootable USB for OSX. Does the target disk need to be formatted or it does not matter? Moreover, can I speculate when you say the target disk has to be bigger, do you mean the used part? I mean, The original disk is 2TB, the target disk is 1TB, but I have used just 100GB of the first disk, I would speculate this still works, is that correct?

Hi, I have a virtual machine with OSX installed. Is there a way to move it to a physical disk? I already know how to make the NVME disk visible to the VM, what I do not know is how to clone the disk. anybody has done this? Thank you in advance for your help.

VMWare fusion, till version 8, lets one chose whether to use the MacOs Hypervisor or a built in one and there is a provision(a setting) to allow in VMWare fusion the nested virtualization: vmx.allowNested = "TRUE". These are the features SpaceInvader took advantage of in his video. Yet I could not make it to work but he did . Moreover Penryn does not have VT-X, that is why, in theory, it should make no difference whether you use intel or an AMD..... well, that is the theory

Hi, I have a working macinabox VM. The unraid system runs on a threadripper 3970x. Does anybody here have an ideahow to run paralles or vmware fusion in the Macos VM? I have seen spaceinvader's video and also contacted him. when he made the video he was running a system with an Intel CPU nad lately he uses AMD based system but he hasn't ever plaid around with nested VMs while using his new AMD system albeit, he says, if the Qemu enryn,vendor=GenuineIntel setting is used while setting the VM up, he does not see why it wouldn't work also with AMD. Well, I could not make it work. This seems the right thread, anybody has any idea? Thank you in advance.

Hello, I can report success with the MSI Vega64. What I did was to go to the Clover configurator, and on the Lernel section enable lilu.kext, WhateverGreen, AppleAcl, AGPMinjector nd USBPorts. Moreover, in the helper script, I set REMOVETOPOLOGY=“yes”. Bingo, my Vega 64 is up and running. As I was able to pass through an USB controller, I found out an old bluetooth USB dongle is actually recognized, so I am using my Magic Mouse at the moment.

Has anybody successfully passed a vega 64 to a VM? I have a m created with the Macinabox which works on VNC but I cannot get to work with the card. I can pass the card successfully to a WIN10 VM so it is not the card. I enabled Lilu and whatevergreen, is there any other setting required in opencore?