Seven7527 Posted March 25, 2021 Share Posted March 25, 2021 So I am trying to create a gaming VM. I have a Windows VM up and running after following Space Invader One. except I Can not use my graphics card. If I try to add it the VM crashes when I try to start it up. its a Gigabyte GTX 1650 Super. So I am trying to create a 2nd VM ( and have not added a graphics card to it yet )of windows 10 but when I go to create it I just get this (in the pic below). I should also mention I am very self taught. I have leaned this all reading and watching videos. Thanks Quote Link to comment
Minimushroomman Posted March 25, 2021 Share Posted March 25, 2021 Posting the XML view of your VMs might give better information to help find a solution to your problem. You can view that when you edit your VM, in the top right is a button to switch between the views. Other than that I'm not sure, sorry. Quote Link to comment
Seven7527 Posted March 26, 2021 Author Share Posted March 26, 2021 (edited) ?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Gaming rig</name> <uuid>9388ad92-c504-0780-3e59-e31bc10b1613</uuid> <description>Gaming rig</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </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='6'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/9388ad92-c504-0780-3e59-e31bc10b1613_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='1' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <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='writeback'/> <source file='/mnt/user/domains/Gaming rig/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <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/Win10_20H2_v2_English_x64.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <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.173-2.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:4b:65:01'/> <source bridge='br0'/> <model type='virtio'/> <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'> <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='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> W10 Gaming Edited March 26, 2021 by Seven7527 Quote Link to comment
ghost82 Posted June 4, 2021 Share Posted June 4, 2021 (edited) On 3/25/2021 at 11:14 PM, Seven7527 said: So I am trying to create a gaming VM. I have a Windows VM up and running after following Space Invader One. except I Can not use my graphics card. If I try to add it the VM crashes when I try to start it up. its a Gigabyte GTX 1650 Super. So I am trying to create a 2nd VM ( and have not added a graphics card to it yet )of windows 10 but when I go to create it I just get this (in the pic below). I should also mention I am very self taught. I have leaned this all reading and watching videos. Thanks I think you need to be fast enough to connect with vnc to see the "press any key to boot from the cd rom", otherwise you get the uefi shell. I think you can also start the installation from the uefi shell. FS0 should refer to the cd rom with the install iso: so just type in the uefi shell: fs0: then: cd \EFI\BOOT finally: BOOTX64.EFI Edited June 4, 2021 by ghost82 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.