ThePirateBay Posted July 20 Share Posted July 20 Hi Peeps, I’m trying to set up a hyper V instance within my Windows 11 VM which is running on my unraid server. Problem I’m having is: 1. If a turn on the windows feature required for Hyper-V, my VM doesn’t boot up. if I change the cpu mode to emulated, it boots up. 2. From the emulated mode when I set up a VM via Hyper-V it doesn’t start up and gives back a error stating services are missing. Is it even possible to achieve what I want? I would like to have a VM for demo/testing goals for Microsoft Autopilot (intune). With hyper-V a can create checkpoints very easy. Maybe someone else has a better solution for me 😀😀 Quote Link to comment
SimonF Posted July 20 Share Posted July 20 37 minutes ago, ThePirateBay said: Hi Peeps, I’m trying to set up a hyper V instance within my Windows 11 VM which is running on my unraid server. Problem I’m having is: 1. If a turn on the windows feature required for Hyper-V, my VM doesn’t boot up. if I change the cpu mode to emulated, it boots up. 2. From the emulated mode when I set up a VM via Hyper-V it doesn’t start up and gives back a error stating services are missing. Is it even possible to achieve what I want? I would like to have a VM for demo/testing goals for Microsoft Autopilot (intune). With hyper-V a can create checkpoints very easy. Maybe someone else has a better solution for me 😀😀 I use this for wsl. <cpu mode='custom' match='exact' check='partial'> <model fallback='allow'>Skylake-Client-noTSX-IBRS</model> <topology sockets='1' dies='1' clusters='1' cores='4' threads='1'/> <feature policy='disable' name='mpx'/> <feature policy='disable' name='hypervisor'/> <feature policy='require' name='vmx'/> </cpu I do have a 2k6 server running with hyperv but not able to get xml to you at present but use similar settings Quote Link to comment
ThePirateBay Posted July 20 Author Share Posted July 20 Thx. I’m kinda nooby in this. What does this XML file exactly do? And where do I use it? Quote Link to comment
SimonF Posted July 20 Share Posted July 20 7 minutes ago, ThePirateBay said: Thx. I’m kinda nooby in this. What does this XML file exactly do? And where do I use it? The XML is the way the VM is defined. CPU and features sections are important. You may need to do a XML edit, there is a switch at the top right of the template. Note that some of the changes in the XML will be lost if you do an update via the GUI form. I am on the 7beta so you may not see the inline switch. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows Server 2019</name> <uuid>9bf0e804-9828-2c91-4acb-b818a5a4938f</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows Server 2016" icon="windows.png" os="windows2016" storage="default" webui=""/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='8'/> <vcpupin vcpu='1' cpuset='9'/> <vcpupin vcpu='2' cpuset='11'/> <vcpupin vcpu='3' cpuset='10'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-7.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/9bf0e804-9828-2c91-4acb-b818a5a4938f_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vpindex state='on'/> <synic state='on'/> <stimer state='on'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='custom' match='exact' check='partial'> <model fallback='allow'>Skylake-Client-noTSX-IBRS</model> <topology sockets='1' dies='1' clusters='1' cores='4' threads='1'/> <feature policy='disable' name='mpx'/> <feature policy='disable' name='hypervisor'/> <feature policy='require' name='vmx'/> </cpu> <clock offset='localtime'> <timer name='hpet' present='no'/> <timer name='hypervclock' present='yes'/> </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/domains2/Windows Server 2019/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/17763.3650.221105-1748.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.96.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <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'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:d5:b6:c5'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 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='en-us' sharePolicy='ignore'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain> Quote Link to comment
ThePirateBay Posted July 21 Author Share Posted July 21 The first you explaining I understand. But the rest of what you shared, yeah this way to technical for me. Would like to understand though. Maybe you have time to plan a call tommorow via team perhaps. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.