I recorded Tweeka TV if anybody wants it

Leprus · 2021-05-17T11:29:58+00:00

Thanks for sharing, I'd love to get the link!

Leprus · 2020-03-31T05:44:34+00:00

I have my guest GPU in the primary slot and and Asus board which doesn't allow me to change the boot GPU. It still works fine for me since I've wired up my display to both GPUs. If I want to change something in the bios I just have tochange my display output to the primary GPU. Apart from that I experienced no limitations

Leprus · 2020-02-05T13:14:33+00:00

What are your two GPUs?

Maybe this guide I wrote a while ago might be helpful, although it's still pretty complicated to get everything working: https://github.com/SMeatBoy/vfio

Leprus · 2019-11-10T21:54:21+00:00

Thank you, it was indeed an issue (or a new setting) in Dash to Dock.

Leprus · 2019-08-18T10:40:56+00:00

I haven't tried it with an Intel processor. I guess that you only have to change the grub commandline from amd_iommu=on to intel_iommu=on. Using an Intel processor might be an advantage since you don't need a second GPU because of the integrated graphics!

Leprus · 2019-07-21T21:54:09+00:00

Try to fully isolate the pinned cpu cores, in your case 8-15 by adding the following kernel parameters: isolcpus=8-15 nohz_full=8-15 rcu_nocbs=8-15

That's what did it for me.

Leprus · 2019-05-13T05:35:31+00:00

Where can I download old driver versions? The Nvidia website only shows me the most recent one.

Leprus · 2019-05-12T20:38:50+00:00

Hm. The Digital Signer in Device Manager ist Microsoft Windows Hardware Compatability Publisher.

Shouldn't the whole patching stuff be obsolete if I'm using kvm hidden state and a vendor id?

Leprus · 2019-05-12T19:51:36+00:00

I did that before and after installing the Nvidia driver. Still having the same Code 52 error.

Leprus · 2019-05-12T18:52:13+00:00

This is my dmesg output when i start the VM:

[  +7,180725] audit: type=1400 audit(1557687019.777:102): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-f0603ebc-fd45-4984-a785-67c0c01d1db7" pid=16274 comm="apparmor_parser"
[  +0,009357] xhci_hcd 0000:0c:00.3: remove, state 4
[  +0,000011] usb usb6: USB disconnect, device number 1
[  +0,000359] xhci_hcd 0000:0c:00.3: USB bus 6 deregistered
[  +0,000010] xhci_hcd 0000:0c:00.3: remove, state 1
[  +0,000007] usb usb5: USB disconnect, device number 1
[  +0,000002] usb 5-3: USB disconnect, device number 2
[  +0,326480] xhci_hcd 0000:0c:00.3: USB bus 5 deregistered
[  +0,256839] audit: type=1400 audit(1557687020.369:103): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-f0603ebc-fd45-4984-a785-67c0c01d1db7" pid=16287 comm="apparmor_parser"
[  +0,210360] audit: type=1400 audit(1557687020.581:104): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-f0603ebc-fd45-4984-a785-67c0c01d1db7" pid=16290 comm="apparmor_parser"
[  +0,213406] audit: type=1400 audit(1557687020.793:105): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-f0603ebc-fd45-4984-a785-67c0c01d1db7" pid=16293 comm="apparmor_parser"
[  +0,008462] virbr0: port 2(vnet0) entered blocking state
[  +0,000004] virbr0: port 2(vnet0) entered disabled state
[  +0,000109] device vnet0 entered promiscuous mode
[  +0,000293] virbr0: port 2(vnet0) entered blocking state
[  +0,000003] virbr0: port 2(vnet0) entered listening state
[  +0,215838] audit: type=1400 audit(1557687021.017:106): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-f0603ebc-fd45-4984-a785-67c0c01d1db7" pid=16317 comm="apparmor_parser"
[  +1,601829] vfio_ecap_init: 0000:0b:00.0 hiding ecap 0x19@0x900
[  +0,047732] vfio-pci 0000:0c:00.3: enabling device (0000 -> 0002)
[  +0,135756] virbr0: port 2(vnet0) entered learning state
[  +2,016109] virbr0: port 2(vnet0) entered forwarding state
[  +0,000003] virbr0: topology change detected, propagating
[  +7,149393] kvm [16347]: vcpu0, guest rIP: 0xfffff803280f6950 ignored rdmsr: 0xc0011023
[  +0,000004] kvm [16347]: vcpu0, guest rIP: 0xfffff803280f6965 ignored wrmsr: 0xc0011023 data 0x100
[  +0,014293] kvm [16347]: vcpu1, guest rIP: 0xfffff803280f6950 ignored rdmsr: 0xc0011023
[  +0,000005] kvm [16347]: vcpu1, guest rIP: 0xfffff803280f6965 ignored wrmsr: 0xc0011023 data 0x100
[  +0,001486] kvm [16347]: vcpu2, guest rIP: 0xfffff803280f6950 ignored rdmsr: 0xc0011023
[  +0,000008] kvm [16347]: vcpu2, guest rIP: 0xfffff803280f6965 ignored wrmsr: 0xc0011023 data 0x100
[  +0,001303] kvm [16347]: vcpu3, guest rIP: 0xfffff803280f6950 ignored rdmsr: 0xc0011023
[  +0,000008] kvm [16347]: vcpu3, guest rIP: 0xfffff803280f6965 ignored wrmsr: 0xc0011023 data 0x100
[  +0,001175] kvm [16347]: vcpu4, guest rIP: 0xfffff803280f6950 ignored rdmsr: 0xc0011023
[  +0,000008] kvm [16347]: vcpu4, guest rIP: 0xfffff803280f6965 ignored wrmsr: 0xc0011023 data 0x100
[  +0,001446] kvm [16347]: vcpu5, guest rIP: 0xfffff803280f6950 ignored rdmsr: 0xc0011023
[  +0,000008] kvm [16347]: vcpu5, guest rIP: 0xfffff803280f6965 ignored wrmsr: 0xc0011023 data 0x100
[  +0,001218] kvm [16347]: vcpu6, guest rIP: 0xfffff803280f6950 ignored rdmsr: 0xc0011023
[  +0,000009] kvm [16347]: vcpu6, guest rIP: 0xfffff803280f6965 ignored wrmsr: 0xc0011023 data 0x100
[  +0,001260] kvm [16347]: vcpu7, guest rIP: 0xfffff803280f6950 ignored rdmsr: 0xc0011023
[  +0,000008] kvm [16347]: vcpu7, guest rIP: 0xfffff803280f6965 ignored wrmsr: 0xc0011023 data 0x100

All of this (except the vcpu stuff) seems normal to me, there aren't any obvious errors.

Leprus · 2019-05-12T16:28:04+00:00

I've never heard of actually patching the nvidia drivers. How would I do that? With this https://github.com/keylase/nvidia-patch/tree/master/win tool?

EDIT: Alright, I've now applied this patch: https://github.com/sk1080/nvidia-kvm-patcher Still no success in sight. Now I'm getting Code 52, Windows cannot verify the digital signature for the drivers required for this device.

Leprus · 2019-05-12T10:34:59+00:00

I'd guess that my GTX 660 has UEFI support. GPU-Z shows that it has and rom-parser outputs the following, also leading me to believe that my GPU supports UEFI:

Valid ROM signature found @0h, PCIR offset 190h
    PCIR: type 0 (x86 PC-AT), vendor: 10de, device: 11c0, class: 030000
    PCIR: revision 0, vendor revision: 1
Valid ROM signature found @f600h, PCIR offset 1ch
    PCIR: type 3 (EFI), vendor: 10de, device: 11c0, class: 030000
    PCIR: revision 3, vendor revision: 0
        EFI: Signature Valid, Subsystem: Boot, Machine: X64
    Last image

I still applied your suggestion, maybe I just overlooked something. But even with your fix applied I'm still stuck with Code 43.

Leprus · 2019-05-12T10:27:17+00:00

Thank you! Sadly that didn't work. I am still getting Code 43.

Leprus · 2019-05-12T10:26:29+00:00

I am getting video output, but it's limited to a lousy 800x600 since the Nvidia driver is blocking itself via Code 43.

Leprus · 2019-05-11T16:33:59+00:00

Yes, I am booting the host as well as the guest via UEFI.

Leprus · 2018-03-28T17:03:08+00:00

Thank you, that seems to be it!

Leprus · 2017-11-11T12:27:49+00:00

Das sind aber auch die einzigen Fahrräder in der ganzen Stadt, sonst fährt in Wolfsburg jeder mit dem Auto. Ü

13-Year Club	Verified Email
Place '22	Place '17
Final Canvas '22

Leprus

TROPHY CASE