Windows 10 Enterprise 1903 + nvidia 441.66 on xen works!

[MAngel666]

Hi

Hardware:
CPU i9-9900K (all 16 cores useable for Windows DomU (VM))
RAM 64GB (Windows DomU 32GB)
Graphics: Nvidia RTX 2070 (Gigabyte) + 441.66 driver
OS: Windows 10 Enterprise 1903
Hypervisor: Xen 4.12 with Centos7

One thing: It was neccessery to add a new signtool path to your script.

One question:
Can I deactivate the testmode after the nvidia driver is installed? Or do I need to leave it on if I want to use the "selfsigned" driver?

BTW: BIG THX FOR THIS PATCH!
TiA

[imtrobin]

Hi, MAngel, did you compile on the same VM or separate machine. I tried compiling on a separate machine, the driver was patched successfully but it did not work when installing.

[MAngel666]

on the same...

[imtrobin]

hmm, I tried on the same machine, and it did not work too. Did you need to turn off Windows Update/internet to patch it?

[MAngel666]

no...

[imtrobin]

hmm. I'm using xcp-ng, where as you are using xen directly..

[MAngel666]

thats right... I'm using xen 4.12

xl info
host : lilith
release : 5.4.8-1.el7.elrepo.x86_64
version : #1 SMP Sat Jan 4 15:29:03 EST 2020
machine : x86_64
nr_cpus : 16
max_cpu_id : 15
nr_nodes : 1
cores_per_socket : 8
threads_per_core : 2
cpu_mhz : 3600.198
hw_caps : bfebfbff:77faf3ff:2c100800:00000121:0000000f:009c67af:00000000:00000100
virt_caps : pv hvm hvm_directio pv_directio
total_memory : 65393
free_memory : 16131
sharing_freed_memory : 0
sharing_used_memory : 0
outstanding_claims : 0
free_cpus : 0
xen_major : 4
xen_minor : 12
xen_extra : .1.132.g8f333d1
xen_version : 4.12.1.132.g8f333d1
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit2
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset :
xen_commandline : placeholder dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 console=com1,vga loglvl=all guest_loglvl=all gnttab_max_frames=128 ucode=scan iommu=dom0-passthrough
cc_compiler : gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39)
cc_compile_by : mockbuild
cc_compile_domain : centos.org
cc_compile_date : Thu Dec 12 12:52:07 UTC 2019
build_id : 50fb411545c2df88f56deb50442d0152994c3199
xend_config_format : 4

[MAngel666]

still works with Windows 10 1909 and nvidia 442.19

[imtrobin]

great to hear. Question, why did use xen directly instead of something like xenserver? Isn't it more troublesome to manage?

[MAngel666]

Citrix xenserver doesnt use all the features of opensource xen... I use it @home on 3 hosts. Its easy to manage it with virsh or/and xl.

[MAngel666]

Windows 10 version 1909 + nvidia driver 442.59 works to...

[MAngel666]

For all they have problem with nvidia here my tips:

• I use nvidia as SECOND card in bios, the first one is the cpu integrated gpu (I use it to show the hypervisor console)
• I use the nvidia as SECOND card for the hvm windows 10 domU
• make the pci hide as kernel parameter, example: xen-pciback.hide=(01:00.0)(01:00.1)(01:00.2)(01:00.3)(00:1f.3)
• blacklist all nvidia modules (I've blacklisted all modules for all pci devices what I use with pci passthrough)
• use pci_permissive = 1
• I use centos7 + xen 4.12 + kernel-ml from elrepo (5.6.1 now) as dom0
• I use this: iommu=dom0-passthrough as parameter for xen in grub

Here my config for windows 10 HVM domU;

name = "marax.chao5.int"
uuid = "e0de3cb7-3937-417d-8d63-b0993b377b6a"
maxmem = 32768
memory = 32768
kernel = '/usr/lib64/xen/boot/hvmloader'
vcpus = 16
rtc_timeoffset = 0
localtime = 1
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
vif = [ "mac=00:16:3e:05:01:10,bridge=xenbr5,script=vif-bridge,model=e1000" ]
parallel = "none"
serial = "none"
type = "hvm"
loader = "/usr/lib64/xen/boot/hvmloader"
disk = [ "phy:/dev/mapper/marax_c,hda,rw", "phy:/dev/vg_lilith/lv_marax_d,hdb,rw" ]
max_grant_frames = "128"
#pci = [ "01:00.0", "01:00.1", "01:00.2", "01:00.3", "06:00.0", "00:1f.3" ]
pci = [ "01:00.0", "01:00.1", "01:00.2", "01:00.3", "00:1f.3" ]
pci_permissive = 1
keymap = "de"
vnclisten="0.0.0.0"
pci_power_mgmt=1
xen_platform_pci=1
pci_msitranslate=1
viridian=1
hpet=1
acpi=1
apic=1
pae=1

Good luck!

[sotiris-bos]

great to hear. Question, why did use xen directly instead of something like xenserver? Isn't it more troublesome to manage?

Hey! Did you manage to make it work with xcp-ng?

[MAngel666]

sorry I dont use it... I use CentOS 8 with pkgs from "Xen made easy" Project and self compiled libvirt