Code 43 NVIDIA driver error within Windows 10 VM, Geforce 750 Ti Passthrough

[nafees]

Hi all, I don't normally post on forums but this problem has left me stumped all week and now I am desperate!

I have a new TS140 ThinkServer, I wanted to run an Xpenology NAS VM and a Windows 10 VM (Kodi/Emby) with HDMI out (all within Proxmox KVM).

Having read countless threads and blogs and the Proxmox PCI Passthrough guide, I had assumed that NVIDIA's driver blacklisting of its consumer range cards was a problem that was relatively easy to solve - just need to switch off KVM cpu and disable possible Hyper-V style enhancements - however after trying several old and new driver versions I am still getting the Code 43 Driver Device Manager error within Windows 10 Professional.

I followed the instructions on Proxmox PCI Passthrough Wiki and Alex Williams VGA Passthrough Blog, as well as reading through much of the Arch Linux VGA Passthrough megathread. Unfortunately, whilst the card is visible within the VM I am still getting the Code 43 error. I have tried the following NVIDIA driver versions: 334.89, 340.52, 344.75 and 355.98.

Intel Xeon CPU E3-1226 v3 3.30GHz, 16GB ECC RAM, GPU (apart from onboard Intel) MSI NVIDIA GeForce 750 Ti 2GB RAM (PCI Express)
PVE Manager version: pve-manager 4.0-36
Kernel version: Linux 4.2.0-1-pve #1 SMP Sat Sep 5 21:21:40 CEST 2015

Here is my Windows 10 VM Conf:

balloon: 6288
boot: cdn
bootdisk: virtio0
cores: 4
cpu: host
hostpci0: 01:00,x-vga=on,pcie=1,driver=vfio
keyboard: en-gb
machine: q35
memory: 14288
name: Windows
net0: virtio=21:64:95:67:B6:FC,bridge=vmbr0
numa: 0
ostype: other
smbios1: uuid=c749cd22-9cc4-4856-90d5-a5480a7e1e86
sockets: 1
virtio0: local:101/vm-101-disk-1.raw,cache=writeback,size=72G

The graphics card does work as it displays the host BIOS and GRUB loader when I reboot the host machine, however there is no output to the monitor when the Windows 10 VM is started (I have to use remote desktop to view the display).

Finally, the only key difference between my Proxmox setup and other ones that I have read about, is that I am using the latest Proxmox 4.0 beta2 instead of version 3.10 - could this have an impact?. I am assuming the problem is with the Nvidia driver still detecting that it is still running within a virtual machine but I going crazy trying to find how it could possibly detect that.

Please could any members of this forum advise on what I might be missing?

Many thanks,

 

[tom]

do you see this problem also with latest kernel (4.2.1, apt-get dist-upgrade to get it)?

 

[nafees]

Thanks Tom, updated the kernel as per your suggestion but still getting no output to the monitor and code 43 error. The VGA Passthrough guide on the Proxmox Wiki mentioned that the 750 Ti it works with 3.1 - is it worth downgrading? If so what's the best way to do that. Thanks.

 

[nafees]

Ok, I have realised that the KVM virtualisation option was enabled for the VM - I assume this translates into KVM=on in QEMU. If disable the setting I get the following error when trying to boot the the VM:

unknown hostpci setting 'driver=vfio'
unknown hostpci setting 'driver=vfio'
Running as unit 101.scope.
unknown hostpci setting 'driver=vfio'
kvm: CPU model 'host' requires KVM...

UPDATE: I know now that I need KVM virtualisation to be on for the whole thing to work, it just that I need to set the CPU flag somehow. I some have said that it is implicit in some of the CPU choice options (i.e. 'host') but I can't see the run command for starting the VM to know that. Is there a way I can easily view/edit the actual QEMU command to see what it is actually doing?

 

[fireon]

you have enabled these things?

- on your /etc/default/grub ---> intel_iommu=on ?
- KVM is switched on, on your VM?
- Works your VM incl. Graphicscard with an other OS, like Ubuntu?
- start an livedisc like Ubuntu and enter in CMD "lscpi", did you see the card?

Best Regards

 

[Stewge]

AFAIK the code 43 errors are actually due to the VM detecting KVM, not that it doesn't work. I had this happen on my older 670 and 580 cards. The fix was to roll back to a driver release PRIOR to Geforce experience, which is really old.

I believe there were some newer work-arounds done in KVM to fix this, but it wouldn't surprise me if each time KVM is updated to get around it, Nvidia patches it out in their next driver.

Have a look on generic KVM forums regarding Maxwell cards + PCIE-Passthru as you may find some better info there.

 

[nafees]

Thank you both for your responses, I have been spending countless hours on this problem for the past week, evenings and weekends it's frustrating to be so near the perfect setup but not get over this last hurdle.

Anyway - fireon, : Yes, intel_iommu=on and KVM is enabled. Following your suggestion I tried vga passthrough to a Ubuntu VM and it worked (display on the monitor). I also ran Ubuntu live disk and yes I saw the card via lspci.

Stewge - yes I think this is the NVIDIA drivers detecting the host but somehow my Proxmox settings aren't doing the job of hiding KVM from them. I have tried the earliest drivers available for the 750 Ti but unfortunately it seems that by the time this card was released, the NVIDIA drivers hard already begun checking for virtualisation.

Going by the latest discussions, it seems that I need QEMU needs the following flags: kvm=off and vga=none; both options aren't apparent in the Proxmox GUI. I have tried to translate these in the proxmox VM conf file by adding the following:

args: -cpu host,kvm=off
vga: none

But still getting the Code 43 error although I am not sure if I have specified them correctly.

UPDATE: I would add that I get the following error for the proxmox task even though both the Ubuntu and Windows VM start fine - unknown hostpci setting 'driver=vfio'.

 

[nafees]

Just want to follow this up for anyone searching on Google. I did try earlier version of Proxmox, then tried using a Ubuntu desktop as a hypervisor and using libvrt / virt-manager to run the machines but still came across the same problem. In the end the problem wasn't with Proxmox - which is great stable software by the way - it was my machine: the Lenovo TS140 ThinkServer. The motherboard combined with my Nvidia graphics card in the main PCIe 16x slot wasn't playing nicely. My 'solution' was to move the card into the spare PCIe x4 slot instead and enable the onboard IGD graphics. The reduced bandwidth of PCIe x4 is not ideal but recent Tom's Hardware articles seem to indicate that it doesn't seem to make that much of a difference to most games - especially at the lower HD resolutions which I will be playing at.

 

[spirit]

Hi, can you test the lasts updates from pvetest repostiory ?
We have disabled hyperv enlightments when a vga pci pasthrougth is done. This should fix the "code 43" error with gforce drivers.

 

[boethius]

Hi, can you test the lasts updates from pvetest repostiory ?
We have disabled hyperv enlightments when a vga pci pasthrougth is done. This should fix the "code 43" error with gforce drivers.

Hello spirit,

I added the pvetest repository and commented out the rest, updated, upgraded, and I am still getting error 43. I am using a 750 Ti as well.

When I disable KVM, the Win10 guest does not boot, hangs @ 50% cpu utilization. I tried specifying Core2Duo as CPU type, no dice.

Everything is working for me except the driver. I am locked at 800x600, and it was defaulting to Windows Display Driver... Uninstalled, tried a few different versions of the nVidia driver...

bios: ovmf
bootdisk: scsi0
cores: 2
hostpci0: 01:00.0,x-vga=on
ide0: local:iso/virtio-win-0.1.102.iso,media=cdrom,size=156988K
ide2: local:iso/Win10_1511_english_x64.iso,media=cdrom
memory: 6048
name:win10
net0: virtio=36:30:35:30:31:34,bridge=vmbr0
numa: 0
ostype: win8
scsi0: local:101/vm-101-disk-1.qcow2,cache=writeback,size=100G
scsihw: virtio-scsi-pci
smbios1: uuid=0dc3fc58-d599-4e62-b04b-4c39ecd939e0
sockets: 1
usb0: host=1-3
usb1: host=1-4

System details...
Motherboard: Asrock Extreme 7+
Proc: i5 6500
GPU : Evga GeForce 750ti


Any advice?​

 

[spirit]

can you send me the kvm command line of the vm ?

(on the host : ps -aux|grep <vmid>)

 

[boethius]

root      1010  0.0  0.0  21724  2648 ?        S    17:04   0:00 /bin/bash /usr/sbin/ksmtuned
root      1322 40.3 38.5 7354196 6230252 ?     SLl  17:06   3:13 /usr/bin/kvm -id 101 -chardev socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait -mon chardev=qmp,mode=control -vnc unix:/var/run/qemu-server/101.vnc,x509,password -pidfile /var/run/qemu-server/101.pid -daemonize -smbios type=1,uuid=0dc3fc58-d699-4e72-b04b-4c39ecd929e0 -drive if=pflash,format=raw,readonly,file=/usr/share/kvm/OVMF-pure-efi.fd -drive if=pflash,format=raw,file=/tmp/101-OVMF_VARS-pure-efi.fd -name win10main -smp 2,sockets=1,cores=2,maxcpus=2 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000 -vga none -no-hpet -cpu kvm64,kvm=off,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_relaxed,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 6048 -k en-us -device pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f -device pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -readconfig /usr/share/qemu-server/pve-usb.cfg -device usb-tablet,id=tablet,bus=uhci.0,port=1 -device vfio-pci,host=01:00.0,id=hostpci0,bus=pci.0,addr=0x10,x-vga=on -device usb-host,hostbus=1,hostport=3 -device usb-host,hostbus=1,hostport=4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -iscsi initiator-name=iqn.1993-08.org.debian:01:63b8542aec40 -device virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5 -drive file=/var/lib/vz/images/101/vm-101-disk-1.qcow2,if=none,id=drive-scsi0,cache=writeback,format=qcow2,aio=threads,detect-zeroes=on -device scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100 -drive file=/var/lib/vz/template/iso/virtio-win-0.1.102.iso,if=none,id=drive-ide0,media=cdrom,aio=threads -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=200 -drive file=/var/lib/vz/template/iso/Win10_1511_English_x64.iso,if=none,id=drive-ide2,media=cdrom,aio=threads -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=201 -netdev type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on -device virtio-net-pci,mac=36:30:35:30:31:34,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300 -rtc driftfix=slew,base=localtime -global kvm-pit.lost_tick_policy=discard

 

[spirit]

ok,

-cpu kvm64,kvm=off,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_relaxed,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce

can you try with "host" cpu model

also, Seem that hyperv features are not disabled. Are you really sure to have done all last proxmox updates ?
#pveversion -v ?

you can try with copy/paste the full kvm command line, and replace cpu arg with
-cpu host,kvm=off

 

[boethius]

spirit,
Thanks so much for helping.

I am ashamed!! I messed up the repository entry, .cm!!!

I just upgraded w/ the entry corrected, and things are.. different. I tried to install the nVidia drivers via the driver only install and during the install the screen shows a pixelated mess, like the card itself is broken...

Then I tried to update via GeForce Experience express install, and after reboot
1) Audio now works
2) Resolution still locked in display manager, but now at 1024 x 768 instead of 800 x 600.
3) Code 43 persists. I will try editing the CPU arg now

Do I add "cpu: host,kvm=off" to the vmid.conf file?

Edit: I have tried several configurations...
in the <vmid>.conf ...
args: -cpu host,kvm=off

also "cpu: host" in the conf file.

I have also tried setting operating system to "other".

I start VM, then install the 361.75 drivers. Reboot results in broken screen most often, one time I booted into windows recovery. A few others times it hangs at windows icon after boot.
If I shutdown the VM, then start, another broken screen. A 3rd shutdown and start of the VM brings it back to 1024 x 768 resolution, audio working, code 43 still present.

I am now also getting "kvm: vcpu1 unhandled rdmsr: 0x641" on host.

I tested the 750ti in a Ubuntu machine with no IGP and it worked fine.

Picture of screen after installing drivers and rebooting: http://imgur.com/E2vMkSq
This also happens without having just run driver installations, but 3 shutdowns of the VM later I can get booted to the desktop.
pve version:

proxmox-ve: 4.1-26 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-13 (running version: 4.1-13/cfb599fb)
pve-kernel-4.2.6-1-pve: 4.2.6-36
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-32
qemu-server: 4.0-55
pve-firmware: 1.1-7
libpve-common-perl: 4.0-48
libpve-access-control: 4.0-11
libpve-storage-perl: 4.0-40
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-5
pve-container: 1.0-44
pve-firewall: 2.0-17
pve-ha-manager: 1.0-21
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 0.13-pve3
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve7~jessie

 

[spirit]

can you simply add "cpu:host",

cpu: host
bios: ovmf
bootdisk: scsi0
cores: 2
hostpci0: 01:00.0,x-vga=on
ide0: local:iso/virtio-win-0.1.102.iso,media=cdrom,size=156988K
ide2: local:iso/Win10_1511_english_x64.iso,media=cdrom
memory: 6048
name:win10
net0: virtio=36:30:35:30:31:34,bridge=vmbr0
numa: 0
ostype: win8
scsi0: local:101/vm-101-disk-1.qcow2,cache=writeback,size=100G
scsihw: virtio-scsi-pci
smbios1: uuid=0dc3fc58-d599-4e62-b04b-4c39ecd939e0
sockets: 1
usb0: host=1-3
usb1: host=1-4

Then give me the kvm command line.

(I just want to be sure that all params are ok)

 

[boethius]

root      1332 34.0 38.5 7745220 6230192 ?     SLl  07:12   0:51 /usr/bin/kvm -id 101 -chardev socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait -mon chardev=qmp,mode=control -vnc unix:/var/run/qemu-server/101.vnc,x509,password -pidfile /var/run/qemu-server/101.pid -daemonize -smbios type=1,uuid=0dc3fc58-d699-4e72-b04b-4c39ecd929e0 -drive if=pflash,format=raw,readonly,file=/usr/share/kvm/OVMF-pure-efi.fd -drive if=pflash,format=raw,file=/tmp/101-OVMF_VARS-pure-efi.fd -name win10main -smp 2,sockets=1,cores=2,maxcpus=2 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000 -vga none -no-hpet -cpu host,+kvm_pv_unhalt,+kvm_pv_eoi,kvm=off -m 6048 -k en-us -device pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f -device pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -readconfig /usr/share/qemu-server/pve-usb.cfg -device usb-tablet,id=tablet,bus=uhci.0,port=1 -device vfio-pci,host=02:00.0,id=hostpci0.0,bus=pci.0,addr=0x10.0,multifunction=on -device vfio-pci,host=02:00.1,id=hostpci0.1,bus=pci.0,addr=0x10.1 -device usb-host,hostbus=1,hostport=4 -device usb-host,hostbus=1,hostport=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -iscsi initiator-name=iqn.1993-08.org.debian:01:63b8542aec40 -drive file=/var/lib/vz/template/iso/Win10_1511_English_x64.iso,if=none,id=drive-ide2,media=cdrom,aio=threads -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200 -device virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5 -drive file=/var/lib/vz/images/101/vm-101-disk-1.qcow2,if=none,id=drive-scsi0,cache=writeback,format=qcow2,aio=threads,detect-zeroes=on -device scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100 -drive file=/var/lib/vz/template/iso/virtio-win-0.1.102.iso,if=none,id=drive-ide0,media=cdrom,aio=threads -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=201 -netdev type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on -device virtio-net-pci,mac=36:30:35:30:31:34,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300 -rtc driftfix=slew,base=localtime -global kvm-pit.lost_tick_policy=discard

 

[spirit]

root      1332 34.0 38.5 7745220 6230192 ?     SLl  07:12   0:51 /usr/bin/kvm -id 101 -chardev socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait -mon chardev=qmp,mode=control -vnc unix:/var/run/qemu-server/101.vnc,x509,password -pidfile /var/run/qemu-server/101.pid -daemonize -smbios type=1,uuid=0dc3fc58-d699-4e72-b04b-4c39ecd929e0 -drive if=pflash,format=raw,readonly,file=/usr/share/kvm/OVMF-pure-efi.fd -drive if=pflash,format=raw,file=/tmp/101-OVMF_VARS-pure-efi.fd -name win10main -smp 2,sockets=1,cores=2,maxcpus=2 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000 -vga none -no-hpet -cpu host,+kvm_pv_unhalt,+kvm_pv_eoi,kvm=off -m 6048 -k en-us -device pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f -device pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -readconfig /usr/share/qemu-server/pve-usb.cfg -device usb-tablet,id=tablet,bus=uhci.0,port=1 -device vfio-pci,host=02:00.0,id=hostpci0.0,bus=pci.0,addr=0x10.0,multifunction=on -device vfio-pci,host=02:00.1,id=hostpci0.1,bus=pci.0,addr=0x10.1 -device usb-host,hostbus=1,hostport=4 -device usb-host,hostbus=1,hostport=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -iscsi initiator-name=iqn.1993-08.org.debian:01:63b8542aec40 -drive file=/var/lib/vz/template/iso/Win10_1511_English_x64.iso,if=none,id=drive-ide2,media=cdrom,aio=threads -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200 -device virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5 -drive file=/var/lib/vz/images/101/vm-101-disk-1.qcow2,if=none,id=drive-scsi0,cache=writeback,format=qcow2,aio=threads,detect-zeroes=on -device scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100 -drive file=/var/lib/vz/template/iso/virtio-win-0.1.102.iso,if=none,id=drive-ide0,media=cdrom,aio=threads -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=201 -netdev type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on -device virtio-net-pci,mac=36:30:35:30:31:34,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300 -rtc driftfix=slew,base=localtime -global kvm-pit.lost_tick_policy=discard

Ok, I'm not sure, but they are is still
-cpu host,+kvm_pv_unhalt,+kvm_pv_eoi,kvm=off

can you try to add in config

machine: pc-i440fx-2.2

This should remove them.

I known that geforce driver check if they are running in kvm environnement and produce this error code.

you can also try to disable all virtio reference.

balloon: 0

try to use ide/sata for drive, and e1000 for network card.

Please try, and give me kvm command line ouput.

 

[boethius]

Here is with machine: pc-i440fx-2.2 and balloon 0

/usr/bin/systemd-run --scope --slice qemu --unit 101 -p KillMode=none -p CPUShares=1000 /usr/bin/kvm -id 101 -chardev socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait -mon chardev=qmp,mode=control -vnc unix:/var/run/qemu-server/101.vnc,x509,password -pidfile /var/run/qemu-server/101.pid -daemonize -smbios type=1,uuid=0dc3fc58-d699-4e72-b04b-4c39ecd929e0 -drive if=pflash,format=raw,readonly,file=/usr/share/kvm/OVMF-pure-efi.fd -drive if=pflash,format=raw,file=/tmp/101-OVMF_VARS-pure-efi.fd -name win10main -smp 2,sockets=1,cores=2,maxcpus=2 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000 -vga none -no-hpet -cpu host,kvm=off -m 6048 -k en-us -device pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -readconfig /usr/share/qemu-server/pve-usb.cfg -device usb-tablet,id=tablet,bus=uhci.0,port=1 -device vfio-pci,host=02:00.0,id=hostpci0.0,bus=pci.0,addr=0x10.0,multifunction=on -device vfio-pci,host=02:00.1,id=hostpci0.1,bus=pci.0,addr=0x10.1 -device usb-host,hostbus=1,hostport=4 -device usb-host,hostbus=1,hostport=3 -iscsi initiator-name=iqn.1993-08.org.debian:01:63b8542aec40 -drive file=/var/lib/vz/template/iso/virtio-win-0.1.102.iso,if=none,id=drive-ide0,media=cdrom,aio=threads -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=200 -device virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5 -drive file=/var/lib/vz/images/101/vm-101-disk-1.qcow2,if=none,id=drive-scsi0,cache=writeback,format=qcow2,aio=threads,detect-zeroes=on -device scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100 -drive file=/var/lib/vz/template/iso/Win10_1511_English_x64.iso,if=none,id=drive-ide2,media=cdrom,aio=threads -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=201 -netdev type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown -device e1000,mac=36:30:35:30:31:34,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300,romfile=pxe-e1000.rom -rtc driftfix=slew,base=localtime -machine type=pc-i440fx-2.2 -global kvm-pit.lost_tick_policy=discard

 

[boethius]

I created a new VM to test, using no VIRTIO drivers...
Now when I boot, I get a black screen (the monitor has 1 dead pixel which flickers). I restarted after Windows automatically updated display drivers. I can only get to the desktop when booting in safe mode. I uninstalled the 750ti drivers in Safemode, disable automatic driver installation, reboot normally into desktop, and within 10second it crashes to the black screen.

Here is the cmdline from the new VM...

/usr/bin/systemd-run --scope --slice qemu --unit 102 -p KillMode=none -p CPUShares=1000 /usr/bin/kvm -id 102 -chardev socket,id=qmp,path=/var/run/qemu-server/102.qmp,server,nowait -mon chardev=qmp,mode=control -vnc unix:/var/run/qemu-server/102.vnc,x509,password -pidfile /var/run/qemu-server/102.pid -daemonize -smbios type=1,uuid=cdf8af5f-6835-4830-85da-6ea70c2f24df -drive if=pflash,format=raw,readonly,file=/usr/share/kvm/OVMF-pure-efi.fd -drive if=pflash,format=raw,file=/tmp/102-OVMF_VARS-pure-efi.fd -name win102 -smp 4,sockets=1,cores=4,maxcpus=4 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000 -vga none -no-hpet -cpu host,kvm=off -m 8000 -k en-us -device pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -readconfig /usr/share/qemu-server/pve-usb.cfg -device usb-tablet,id=tablet,bus=uhci.0,port=1 -device vfio-pci,host=02:00.0,id=hostpci0.0,bus=pci.0,addr=0x10.0,multifunction=on -device vfio-pci,host=02:00.1,id=hostpci0.1,bus=pci.0,addr=0x10.1 -device usb-host,hostbus=1,hostport=4 -device usb-host,hostbus=1,hostport=3 -iscsi initiator-name=iqn.1993-08.org.debian:01:63b8542aec40 -device ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7 -drive file=/var/lib/vz/images/102/vm-102-disk-1.raw,if=none,id=drive-sata0,cache=writeback,format=raw,aio=threads,detect-zeroes=on -device ide-drive,bus=ahci0.0,drive=drive-sata0,id=sata0,bootindex=100 -drive file=/var/lib/vz/template/iso/Win10_1511_English_x64.iso,if=none,id=drive-ide2,media=cdrom,aio=threads -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200 -netdev type=tap,id=net0,ifname=tap102i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown -device e1000,mac=62:38:37:33:65:33,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300,romfile=pxe-e1000.rom -rtc driftfix=slew,base=localtime -machine type=pc-i440fx-2.2 -global kvm-pit.lost_tick_policy=discard

 

[spirit]

Here is with machine: pc-i440fx-2.2 and balloon 0

/usr/bin/systemd-run --scope --slice qemu --unit 101 -p KillMode=none -p CPUShares=1000 /usr/bin/kvm -id 101 -chardev socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait -mon chardev=qmp,mode=control -vnc unix:/var/run/qemu-server/101.vnc,x509,password -pidfile /var/run/qemu-server/101.pid -daemonize -smbios type=1,uuid=0dc3fc58-d699-4e72-b04b-4c39ecd929e0 -drive if=pflash,format=raw,readonly,file=/usr/share/kvm/OVMF-pure-efi.fd -drive if=pflash,format=raw,file=/tmp/101-OVMF_VARS-pure-efi.fd -name win10main -smp 2,sockets=1,cores=2,maxcpus=2 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000 -vga none -no-hpet -cpu host,kvm=off -m 6048 -k en-us -device pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -readconfig /usr/share/qemu-server/pve-usb.cfg -device usb-tablet,id=tablet,bus=uhci.0,port=1 -device vfio-pci,host=02:00.0,id=hostpci0.0,bus=pci.0,addr=0x10.0,multifunction=on -device vfio-pci,host=02:00.1,id=hostpci0.1,bus=pci.0,addr=0x10.1 -device usb-host,hostbus=1,hostport=4 -device usb-host,hostbus=1,hostport=3 -iscsi initiator-name=iqn.1993-08.org.debian:01:63b8542aec40 -drive file=/var/lib/vz/template/iso/virtio-win-0.1.102.iso,if=none,id=drive-ide0,media=cdrom,aio=threads -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=200 -device virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5 -drive file=/var/lib/vz/images/101/vm-101-disk-1.qcow2,if=none,id=drive-scsi0,cache=writeback,format=qcow2,aio=threads,detect-zeroes=on -device scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100 -drive file=/var/lib/vz/template/iso/Win10_1511_English_x64.iso,if=none,id=drive-ide2,media=cdrom,aio=threads -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=201 -netdev type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown -device e1000,mac=36:30:35:30:31:34,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300,romfile=pxe-e1000.rom -rtc driftfix=slew,base=localtime -machine type=pc-i440fx-2.2 -global kvm-pit.lost_tick_policy=discard

Ok, seem to be ok. Still not working like this ?