Swampy Posted January 8, 2016 Share Posted January 8, 2016 I just want to share a moment of Ah............................ I spent 4 days trying to find out why I couldn't start VM 10 pro with a video card. I had no problems headless loading. I had no problems loading Ubuntu. I tried all suggestion I could find on this forum. Frustration was building. I finally copied the XML into notepad2 so I could see the code with more line available. What an advantage to actually see more lines. Now I have been concentrating a lot of my time looking at the pass thru portion of the code. Keep in mind that I only have been reading code for 4 day (rube). I could not see much different different than the previous 13 iteration with exception of my passthru of USB and SCSI. This last time I went going down thru the code from top to bottom I seen something. <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='1'/> </cpu> My CPU is threads='2'/> , once I corrected that I had instantaneous gratification. Graphics Card came to life when I hit start......Stress is gone for now, Still a lot of ground to cover. [glow=red,2,300]ASUS C226 WS motherboard with Intel XEON Processor E3-1241 V3[/glow] I feel so much better. Hopefully this will help someone else. Regards Quote Link to comment
natecook Posted January 8, 2016 Share Posted January 8, 2016 So you were setting your VM up with 2 cores but the hyperthread of only one? Your CPU should show cores 0-7 in the edit window, so which were you selecting? Quote Link to comment
jamesyt666 Posted January 8, 2016 Share Posted January 8, 2016 I have had issues with windows 10 too, my usb3 wont work in windows 10 neither will my onboard sound. Asus p9 X79 motherboard. Quote Link to comment
billington.mark Posted January 8, 2016 Share Posted January 8, 2016 Ive always wondered what the correct way was to pass though hyperthreaded cores to VMs is.. not sure the GUI takes this into account as each thread is reported as a core to unraid (thats what the gui suggests anyway) Quote Link to comment
Swampy Posted January 8, 2016 Author Share Posted January 8, 2016 Listen, I am new to this so I have been going thru lots of trial an error because nothing worked from the forum. All I know is I have a quad core dual thread processes. It does report as 8 cores with hyper thread from what I could tell. I can not select Hyper thread in the GUI and make it work. If I enter 2 for treads in the XML it works. If some one wants me to try a limited amount of iteration to flush this out for other I'm willing to help so myself and others can benefit from it. Like I said, I don't know what to look for! Attached is the functional XML and for the Host Pass thru shows 4 being passed thru I had to change threads to 2. <domain type='kvm' id='3' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>11.5</name> <uuid>3a25238d-f2d8-b332-6105-bd920abd7264</uuid> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>13107200</memory> <currentMemory unit='KiB'>13107200</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' threads='2'/> </cpu> <clock offset='localtime'> <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/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/appdata/ISO share/Test11.1/Secondary.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/appdata/ISO share/Windows 10 Pro/Win10.PRO.iso'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-0-0'/> <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/appdata/ISO share/virtio-win-0.1.102.iso'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0' multifunction='on'/> </controller> <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='dmi-to-pci-bridge'> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:f4:58:33'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <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/11.5.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x1058'/> <product id='0x0740'/> <address bus='2' device='2'/> </source> <alias name='hostdev0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x062a'/> <product id='0x4101'/> <address bus='1' device='3'/> </source> <alias name='hostdev1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x413c'/> <product id='0x3012'/> <address bus='1' device='2'/> </source> <alias name='hostdev2'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=02:00.0,bus=pcie.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:1b.0,bus=pcie.0'/> </qemu:commandline> </domain> I just don't want to report a bunch of BS. Regards Quote Link to comment
Swampy Posted January 8, 2016 Author Share Posted January 8, 2016 Oh, Something I did different this time is with the past iterations I used the last 4 of the 8 cores in the GUI. This One I selected the first 4.........So does this mean I had zero cores selected previously so it would never start in VM for Win 10 Pro ? Thanks [update] Today I could not get the VM to load. Yesterday was the first sign of life but was short lived. What totally confusing me is Ubuntu has zero issue in launching....... If I compare the XML there pretty close to being the same. Ubuntu works directly off the template but Win 10 is fussy. 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.