-
Posts
91 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Dava2k7
-
-
Hi Space Invader I recently Dumped my new Asus Dual OC RTX 3070 8gb bios Rom with GPU-Z I have attached it below I couldn't remove the Nvidia header because it didn't look the same as was stated on your past video if you could have alook for me id appreciate it I'm not looking to put this in my server as of yet!! but may do in the future once I get a much bigger case hopefullly this will help other people with RTX 3070
-
43 minutes ago, paperblankets said:
I have not been passing through a gpu to a vm in the last few months. Eventually I will be transitioning to a Ryzen build and may be able to help more. I suspect some things have changed but I don't know what they are at this time.
Yeah thank you I’m not sure what’s happened either I’ve looked around different comments everything points to vbios and I got mine from techpowerup but mine was working for months on 6.8.3 using that vbios I lost Vm completely in 6.9.0 beta 25
-
Hey all I’m getting similar problems with my 1050ti my VM seems to work but with no graphics output I don’t even see unraid load up screen now I think my vbios is ok since I’ve been on my VM previously playing games on it when I update to 6.9.0 beta 29 the Vm worked for two days before screen went blank with cpu cores going crazy so I force shutdown VM and haven’t had no hdmi output since pls help.... Vm seem to work in background but can’t see nothing....
-
Hey all is anyone able to tell me a soloution to this? i have same issue one minute i can passthrough fine next minute my game crashed now i can start my VM but don't get output from tv any ideas please driving me mental........
Oct 5 08:09:37 MovBuster kernel: br0: port 2(vnet0) entered blocking state
Oct 5 08:09:37 MovBuster kernel: br0: port 2(vnet0) entered forwarding state
Oct 5 08:09:38 MovBuster avahi-daemon[10156]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe81::fc55:ff:fe39:50bd.
Oct 5 08:09:38 MovBuster avahi-daemon[10156]: New relevant interface vnet0.IPv6 for mDNS.
Oct 5 08:09:38 MovBuster avahi-daemon[10156]: Registering new address record for fe81::fc55:ff:fe39:50bd on vnet0.*.
Oct 5 08:10:02 MovBuster kernel: vfio-pci 0000:09:00.0: vfio_ecap_init: hiding ecap 0x19@0x900
Oct 5 08:10:02 MovBuster kernel: vfio-pci 0000:09:00.0: No more image in the PCI ROM
Oct 5 08:10:02 MovBuster acpid: input device has been disconnected, fd 9
Oct 5 08:10:02 MovBuster acpid: input device has been disconnected, fd 10
Oct 5 08:10:02 MovBuster acpid: input device has been disconnected, fd 11
Oct 5 08:10:02 MovBuster acpid: input device has been disconnected, fd 6
Oct 5 08:10:02 MovBuster acpid: input device has been disconnected, fd 7
Oct 5 08:10:02 MovBuster acpid: input device has been disconnected, fd 8
Oct 5 08:10:12 MovBuster kernel: usb 3-2: reset full-speed USB device number 2 using xhci_hcd
Oct 5 08:10:12 MovBuster kernel: usb 5-4.1: reset full-speed USB device number 5 using xhci_hcd
Oct 5 08:10:12 MovBuster kernel: usb 5-4.4: reset full-speed USB device number 6 using xhci_hcd
Oct 5 08:10:46 MovBuster avahi-daemon[10156]: Interface vnet0.IPv6 no longer relevant for mDNS.
Oct 5 08:10:46 MovBuster avahi-daemon[10156]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe81::fc55:ff:fe39:50bd.
Oct 5 08:10:46 MovBuster kernel: br0: port 2(vnet0) entered disabled state
Oct 5 08:10:46 MovBuster kernel: device vnet0 left promiscuous mode
Oct 5 08:10:46 MovBuster kernel: br0: port 2(vnet0) entered disabled state
Oct 5 08:10:46 MovBuster avahi-daemon[10156]: Withdrawing address record for fe81::fc55:ff:fe39:50bd on vnet0.
Oct 5 08:10:46 MovBuster kernel: usb 5-4.4: reset full-speed USB device number 6 using xhci_hcd
Oct 5 08:10:46 MovBuster kernel: usb 5-4.1: reset full-speed USB device number 5 using xhci_hcd
Oct 5 08:10:46 MovBuster kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:08.1/0000:0b:00.3/usb5/5-4/5-4.1/5-4.1:1.0/0003:046D:C534.0013/input/input51
Oct 5 08:10:46 MovBuster kernel: hid-generic 0003:046D:C534.0013: input,hidraw1: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:0b:00.3-4.1/input0
Oct 5 08:10:46 MovBuster kernel: input: Logitech USB Receiver Mouse as /devices/pci0000:00/0000:00:08.1/0000:0b:00.3/usb5/5-4/5-4.1/5-4.1:1.1/0003:046D:C534.0014/input/input52
Oct 5 08:10:46 MovBuster kernel: input: Logitech USB Receiver Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:0b:00.3/usb5/5-4/5-4.1/5-4.1:1.1/0003:046D:C534.0014/input/input53
Oct 5 08:10:46 MovBuster kernel: input: Logitech USB Receiver System Control as /devices/pci0000:00/0000:00:08.1/0000:0b:00.3/usb5/5-4/5-4.1/5-4.1:1.1/0003:046D:C534.0014/input/input54
Oct 5 08:10:46 MovBuster kernel: hid-generic 0003:046D:C534.0014: input,hiddev97,hidraw2: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:0b:00.3-4.1/input1
Oct 5 08:10:46 MovBuster kernel: usb 3-2: reset full-speed USB device number 2 using xhci_hcd
Oct 5 08:10:47 MovBuster kernel: input: Logitech G502 HERO SE as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.3/usb3/3-2/3-2:1.0/0003:046D:C08B.0015/input/input57
Oct 5 08:10:47 MovBuster kernel: hid-generic 0003:046D:C08B.0015: input,hidraw4: USB HID v1.11 Mouse [Logitech G502 HERO SE] on usb-0000:06:00.3-2/input0
Oct 5 08:10:47 MovBuster kernel: input: Logitech G502 HERO SE Keyboard as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.3/usb3/3-2/3-2:1.1/0003:046D:C08B.0016/input/input58
Oct 5 08:10:47 MovBuster kernel: input: Logitech G502 HERO SE Consumer Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.3/usb3/3-2/3-2:1.1/0003:046D:C08B.0016/input/input59
Oct 5 08:10:47 MovBuster kernel: input: Logitech G502 HERO SE System Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.3/usb3/3-2/3-2:1.1/0003:046D:C08B.0016/input/input60
Oct 5 08:10:47 MovBuster kernel: hid-generic 0003:046D:C08B.0016: input,hiddev99,hidraw5: USB HID v1.11 Keyboard [Logitech G502 HERO SE] on usb-0000:06:00.3-2/input1
Oct 5 08:10:48 MovBuster kernel: vfio-pci 0000:09:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem -
I’m doubtful this will ever get sorted I can’t understand why unraid staff can’t type up how to downgrade properly from 6.9.0 beta 25 to 6.8.3 again without losing cache drives the tiny little info on the pre release you get doesn’t make any sense to me
-
Is this solution working via graphics card with monitor ect or vnc Cause I’ve tried host-model and a bunch of different commands I found on this forum and nothing is getting my Vm to come up on my screen
-
Thanks for making the kernel @rachid596 nice of you to make one so quick aswell but for me i don’t like the sound of messing around with the kernel I’ve got so much data and I just don’t wanna lose it how long do you think it’ll be before unraid release the fix?
-
10 minutes ago, Dava2k7 said:
are you on about the edited rom vbios cause i used space invader ones tutorial to change header in the past i usually do pass the edited rom bios with the g card but it doesn't do anything different i get the same thing unfortunately....
this is my log after making changes ect
-display none \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=31,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=localtime \
-no-hpet \
-no-shutdown \
-boot strict=on \
-device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.0,addr=0x7 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \
-blockdev '{"driver":"file","filename":"/mnt/user/domains/Gaming Vm/vdisk1.img","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \
-device virtio-blk-pci,bus=pci.0,addr=0x4,drive=libvirt-3-format,id=virtio-disk2,bootindex=1,write-cache=on \
-blockdev '{"driver":"file","filename":"/mnt/user/isos/Win10_1909_English_x64.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \
-device ide-cd,bus=ide.0,unit=0,drive=libvirt-2-format,id=ide0-0-0,bootindex=2 \
-blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.173-2.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \
-device ide-cd,bus=ide.0,unit=1,drive=libvirt-1-format,id=ide0-0-1 \
-netdev tap,fd=33,id=hostnet0 \
-device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:fa:9e:8d,bus=pci.0,addr=0x2 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=34,server,nowait \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device usb-tablet,id=input0,bus=usb.0,port=5 \
-device 'vfio-pci,host=0000:09:00.0,id=hostdev0,bus=pci.0,multifunction=on,addr=0x5,romfile=/mnt/cache/domains/Gigabyte.GTX1050Ti hacked.rom' \
-device vfio-pci,host=0000:09:00.1,id=hostdev1,bus=pci.0,addr=0x5.0x1 \
-device usb-host,hostbus=5,hostaddr=56,id=hostdev2,bus=usb.0,port=1 \
-device usb-host,hostbus=5,hostaddr=57,id=hostdev3,bus=usb.0,port=2 \
-device usb-host,hostbus=5,hostaddr=5,id=hostdev4,bus=usb.0,port=3 \
-device usb-host,hostbus=5,hostaddr=7,id=hostdev5,bus=usb.0,port=4 \
-cpu host,topoext=on,invtsc=on,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff,hv-vpindex,hv-synic,hv-stimer,hv-reset,hv-frequencies,host-cache-info=on,l3-cache=off,-amd-stibp \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2020-06-20 09:24:38.815+0000: Domain id=9 is tainted: high-privileges
2020-06-20 09:24:38.815+0000: Domain id=9 is tainted: custom-argv
2020-06-20 09:24:38.815+0000: Domain id=9 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)id=9 seems to change number 7 8 ect no idea heres the new xml
<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='9' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
<name>Gaming Vm</name>
<uuid>eb4747a6-bb10-6ce9-2d0d-a704560b5992</uuid>
<metadata>
<vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
</metadata>
<memory unit='KiB'>17301504</memory>
<currentMemory unit='KiB'>17301504</currentMemory>
<memoryBacking>
<nosharepages/>
</memoryBacking>
<vcpu placement='static'>12</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='6'/>
<vcpupin vcpu='1' cpuset='18'/>
<vcpupin vcpu='2' cpuset='7'/>
<vcpupin vcpu='3' cpuset='19'/>
<vcpupin vcpu='4' cpuset='8'/>
<vcpupin vcpu='5' cpuset='20'/>
<vcpupin vcpu='6' cpuset='9'/>
<vcpupin vcpu='7' cpuset='21'/>
<vcpupin vcpu='8' cpuset='10'/>
<vcpupin vcpu='9' cpuset='22'/>
<vcpupin vcpu='10' cpuset='11'/>
<vcpupin vcpu='11' cpuset='23'/>
</cputune>
<resource>
<partition>/machine</partition>
</resource>
<os>
<type arch='x86_64' machine='pc-i440fx-5.0'>hvm</type>
<loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
<nvram>/etc/libvirt/qemu/nvram/eb4747a6-bb10-6ce9-2d0d-a704560b5992_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' dies='1' cores='6' 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 Vm/vdisk1.img' index='3'/>
<backingStore/>
<target dev='hdc' bus='virtio'/>
<boot order='1'/>
<alias name='virtio-disk2'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/mnt/user/isos/Win10_1909_English_x64.iso' index='2'/>
<backingStore/>
<target dev='hda' bus='ide'/>
<readonly/>
<boot order='2'/>
<alias name='ide0-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/isos/virtio-win-0.1.173-2.iso' index='1'/>
<backingStore/>
<target dev='hdb' bus='ide'/>
<readonly/>
<alias name='ide0-0-1'/>
<address type='drive' controller='0' bus='0' target='0' unit='1'/>
</disk>
<controller type='usb' index='0' model='qemu-xhci' ports='15'>
<alias name='usb'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
</controller>
<controller type='pci' index='0' model='pci-root'>
<alias name='pci.0'/>
</controller>
<controller type='ide' index='0'>
<alias name='ide'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
</controller>
<controller type='virtio-serial' index='0'>
<alias name='virtio-serial0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</controller>
<interface type='bridge'>
<mac address='52:54:00:fa:9e:8d'/>
<source bridge='virbr0'/>
<target dev='vnet0'/>
<model type='virtio-net'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' 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-9-Gaming Vm/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='5'/>
</input>
<input type='mouse' bus='ps2'>
<alias name='input1'/>
</input>
<input type='keyboard' bus='ps2'>
<alias name='input2'/>
</input>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x09' slot='0x00' function='0x0'/>
</source>
<alias name='hostdev0'/>
<rom file='/mnt/cache/domains/Gigabyte.GTX1050Ti hacked.rom'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x09' slot='0x00' function='0x1'/>
</source>
<alias name='hostdev1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x1'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x046d'/>
<product id='0xc08b'/>
<address bus='5' device='56'/>
</source>
<alias name='hostdev2'/>
<address type='usb' bus='0' port='1'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x046d'/>
<product id='0xc21c'/>
<address bus='5' device='57'/>
</source>
<alias name='hostdev3'/>
<address type='usb' bus='0' port='2'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x046d'/>
<product id='0xc534'/>
<address bus='5' device='5'/>
</source>
<alias name='hostdev4'/>
<address type='usb' bus='0' port='3'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x0a12'/>
<product id='0x0001'/>
<address bus='5' device='7'/>
</source>
<alias name='hostdev5'/>
<address type='usb' bus='0' port='4'/>
</hostdev>
<memballoon model='none'/>
</devices>
<seclabel type='dynamic' model='dac' relabel='yes'>
<label>+0:+100</label>
<imagelabel>+0:+100</imagelabel>
</seclabel>
<qemu:commandline>
<qemu:arg value='-cpu'/>
<qemu:arg value='host,topoext=on,invtsc=on,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff,hv-vpindex,hv-synic,hv-stimer,hv-reset,hv-frequencies,host-cache-info=on,l3-cache=off,-amd-stibp'/>
</qemu:commandline>
</domain>
-
7 hours ago, david279 said:
Can't hurt to try. But I really think you need to pass that bios with the GPU. Also try a Linux VM to see if your windows VM could be the issue.
are you on about the edited rom vbios cause i used space invader ones tutorial to change header in the past i usually do pass the edited rom bios with the g card but it doesn't do anything different i get the same thing unfortunately....
-
1 hour ago, david279 said:
Yeah that's usually the best way to go about passing a single GPU thru to a VM.
Do you think passing through gpu and usbs via vfio in system devices will do the trick?? just read on beta release thats the way they want people to do it maybe that's my problem
-
i done it before cause it was working on 6.9.0 beta 1 and 6.8.3 im at a loss to be honest i love my vm and have had great times on it already i finally get my ryzen k10temp Drivers on this kernal and this happens lol not what i need no doubt i'm the only one with a setup like this and alot of people be in the same boat
-
2 minutes ago, david279 said:
You need to pass the bios from the card in the xml if it's the only GPU.
are you on about the hacked rom bios? cause i have that no joy
-
yeah i have just one
-
5 minutes ago, david279 said:
What GPU are you using?
Gigabyte gtx 1050ti 4gb mini and thanks for your help btw
-
1 minute ago, david279 said:
Try making a brand new VM using the GPU but using the your current windows vdisk. Just want to see if a clean VM setup will fix it.
first thing i done bud that xml is after i recreated it
-
1 hour ago, xommit said:
Are you try :
<cpu mode='host-model' check='none'>
And delete :
<cache mode='passthrough'/>?
yeah that works aswell but only for VNC cant see nothing through hdmi
-
It seems to be working via VNC but cant see nothing cause my signal to tv isnt coming on don’t think it’s passing through the graphics card properly I can see bios on startup both ways worked for me via VNC host-model and host-passthrough 👍🏻 here’s my xml I hope this helps
<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
<name>Gaming Vm</name>
<uuid>eb4747a6-bb10-6ce9-2d0d-a704560b5992</uuid>
<metadata>
<vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
</metadata>
<memory unit='KiB'>17301504</memory>
<currentMemory unit='KiB'>17301504</currentMemory>
<memoryBacking>
<nosharepages/>
</memoryBacking>
<vcpu placement='static'>12</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='6'/>
<vcpupin vcpu='1' cpuset='18'/>
<vcpupin vcpu='2' cpuset='7'/>
<vcpupin vcpu='3' cpuset='19'/>
<vcpupin vcpu='4' cpuset='8'/>
<vcpupin vcpu='5' cpuset='20'/>
<vcpupin vcpu='6' cpuset='9'/>
<vcpupin vcpu='7' cpuset='21'/>
<vcpupin vcpu='8' cpuset='10'/>
<vcpupin vcpu='9' cpuset='22'/>
<vcpupin vcpu='10' cpuset='11'/>
<vcpupin vcpu='11' cpuset='23'/>
</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/eb4747a6-bb10-6ce9-2d0d-a704560b5992_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' dies='1' cores='6' 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/cache/domains/Gaming VM/vdisk1.img'/>
<target dev='hdc' bus='virtio'/>
<boot order='1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/mnt/user/isos/Win10_1909_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='usb' index='0' model='qemu-xhci' ports='15'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
</controller>
<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='0x03' function='0x0'/>
</controller>
<controller type='pci' index='0' model='pci-root'/>
<interface type='bridge'>
<mac address='52:54:00:fa:9e:8d'/>
<source bridge='virbr0'/>
<model type='virtio-net'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' 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='5'/>
</input>
<input type='mouse' bus='ps2'/>
<input type='keyboard' bus='ps2'/>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x09' slot='0x00' function='0x0'/>
</source>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x09' slot='0x00' function='0x1'/>
</source>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x046d'/>
<product id='0xc08b'/>
</source>
<address type='usb' bus='0' port='1'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x046d'/>
<product id='0xc21c'/>
</source>
<address type='usb' bus='0' port='2'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x046d'/>
<product id='0xc534'/>
</source>
<address type='usb' bus='0' port='3'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x0a12'/>
<product id='0x0001'/>
</source>
<address type='usb' bus='0' port='4'/>
</hostdev>
<memballoon model='none'/>
</devices>
<qemu:commandline> <qemu:arg value='-cpu'/> <qemu:arg value='host,topoext=on,invtsc=on,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff,hv-vpindex,hv-synic,hv-stimer,hv-reset,hv-frequencies,host-cache-info=on,l3-cache=off,-amd-stibp'/> </qemu:commandline>
</domain>
-
My VM Log
-nodefaults \
-chardev socket,id=charmonitor,fd=31,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=localtime \
-no-hpet \
-no-shutdown \
-boot strict=on \
-device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.0,addr=0x7 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \
-blockdev '{"driver":"file","filename":"/mnt/cache/domains/Gaming VM/vdisk1.img","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \
-device virtio-blk-pci,bus=pci.0,addr=0x4,drive=libvirt-3-format,id=virtio-disk2,bootindex=1,write-cache=on \
-blockdev '{"driver":"file","filename":"/mnt/user/isos/Win10_1909_English_x64.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \
-device ide-cd,bus=ide.0,unit=0,drive=libvirt-2-format,id=ide0-0-0,bootindex=2 \
-blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.173-2.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \
-device ide-cd,bus=ide.0,unit=1,drive=libvirt-1-format,id=ide0-0-1 \
-netdev tap,fd=33,id=hostnet0 \
-device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:fa:9e:8d,bus=pci.0,addr=0x2 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=34,server,nowait \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device usb-tablet,id=input0,bus=usb.0,port=5 \
-device vfio-pci,host=0000:09:00.0,id=hostdev0,bus=pci.0,addr=0x5 \
-device vfio-pci,host=0000:09:00.1,id=hostdev1,bus=pci.0,addr=0x6 \
-device usb-host,hostbus=5,hostaddr=14,id=hostdev2,bus=usb.0,port=1 \
-device usb-host,hostbus=5,hostaddr=19,id=hostdev3,bus=usb.0,port=2 \
-device usb-host,hostbus=5,hostaddr=5,id=hostdev4,bus=usb.0,port=3 \
-device usb-host,hostbus=5,hostaddr=7,id=hostdev5,bus=usb.0,port=4 \
-cpu host,topoext=on,invtsc=on,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff,hv-vpindex,hv-synic,hv-stimer,hv-reset,hv-frequencies,host-cache-info=on,l3-cache=off,-amd-stibp \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2020-06-19 15:20:27.761+0000: Domain id=24 is tainted: high-privileges
2020-06-19 15:20:27.761+0000: Domain id=24 is tainted: custom-argv
2020-06-19 15:20:27.761+0000: Domain id=24 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2020-06-19T15:22:22.676691Z qemu-system-x86_64: terminating on signal 15 from pid 11543 (/usr/sbin/libvirtd)
2020-06-19 15:22:25.078+0000: shutting down, reason=destroyed -
So I went to the end of my xml where domain was I cut <domain> out and pasted
<qemu:commandline> <qemu:arg value='-cpu'/> <qemu:arg value='host,topoext=on,invtsc=on,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff,hv-vpindex,hv-synic,hv-stimer,hv-reset,hv-frequencies,host-cache-info=on,l3-cache=off,-amd-stibp'/> </qemu:commandline>
I then added <domain> To the end of the line which worked for VNC but when trying to use Graphics passthrough just crazy 100% core readings for me with nothing on screen 😑
But I couldn’t access through vnc before so.. we’re getting there lol
-
5 hours ago, david279 said:
Gone through that bud bit difficult to get the grasp of I tried going by instructions and didn’t work for me after putting the lines in if you have better detailed instructions on how to do it il have another go thank you for helping tho could do with a few more people like that on here
-
Hi all recently upgraded to 6.9.0 beta 22 Some great new features and k10temp readings being displayed but since changing from 6.9.0 beta 1 my Vm has stopped working no signal on tv what so ever I’m using vnc and you can see windows starting and restarting with a kernel security check failure I’ve seen other posts but I think this could be a big issue for people especially if you don’t want to downgrade any in detailed help getting around this would be Great 👍🏻
-
Hi all If you go on your windows VM and goto Power settings then Advanced Power settings then to Usb settings/Usb selective suspend settings then click disable should stop the usbs from sleeping hence stopping your screen glitching out but that doesn't mean your screen resolution wont go weird time from time cause believe me it does lol Try This Before Spending Money.....
-
have you tried a newer machine pc-i440fx-4.2 - 5.0 if your still having issues id advise looking at this should get you up and going follow steps carefully @SpaceInvaderOne
-
Since upgrading to 6.9.0 beta 22 i have all my temps but can anyone please tell me the difference between k10temp Tctl & Tccd??? bit unclear on which ones for what at the moment i have tccd set as motherboard and tctl set as cpu? is this correct???
** VIDEO GUIDE - How to Easily Dump a vBIOS from any GPU directly from the Server for passthrough
in VM Engine (KVM)
Posted
No but Spaceinvaderone has got an updated video on things I think.... I just got another pc to game on rather then mess about with VM's