Win10 VM not working after 6.9.2

[damnshaneisthatu]

Win10 VM was working fine prior to upgrade. Now, when I attempt to start the VM, my monitor goes into Power Save mode, and the VM pauses.

 

Seeing this in the logs when attempting to start up VM:

2021-04-26T20:13:03.926942Z qemu-system-x86_64: vfio: Cannot reset device 0000:0e:00.1, depends on group 22 which is not owned.

 

Group 22 IOMMU attached.

PCIe ACS override set to "Multi-function".

 

Any insight would be helpful. Thanks!

 

 

[bastl]

On 4/26/2021 at 10:30 PM, damnshaneisthatu said:

Seeing this in the logs when attempting to start up VM:

2021-04-26T20:13:03.926942Z qemu-system-x86_64: vfio: Cannot reset device 0000:0e:00.1, depends on group 22 which is not owned.

 

Make sure you passthrough all parts for the GPU. The GPU itself i guess group20, the Nvidia Audio Controller group21 and the Nvidia USB Controller group22

 

Edit: I forgot group23 is also part from your GPU

Edited April 29, 2021 by bastl

[damnshaneisthatu]

Yep, I thought I had it edited correctly in the XML, but still running into the issue.

[SimonF]

24 minutes ago, damnshaneisthatu said:

Yep, I thought I had it edited correctly in the XML, but still running into the issue.

What does your system devices on tools tab look like? GPU should be ticked, this is my K4000.

 

[dvd.collector]

I had exactly the same problem and raised a thread on here.   No updates, so rolled back to 6.8.3.

[damnshaneisthatu]

On 5/1/2021 at 1:04 PM, SimonF said:

What does your system devices on tools tab look like? GPU should be ticked, this is my K4000.

 

Ahhh... mine are unticked. Will update mine later this evening. Appreciate the tip!

Anything else I should look out for?

[damnshaneisthatu]

On 5/1/2021 at 1:04 PM, SimonF said:

What does your system devices on tools tab look like? GPU should be ticked, this is my K4000.

 

Yeah, still getting this after ticking all IOMMU groups.

[SimonF]

15 minutes ago, damnshaneisthatu said:

Yeah, still getting this after ticking all IOMMU groups.

Just to confirm you have ticked 20,21,22 and 23? rebooted and you still have the issue?

Edited May 7, 2021 by SimonF

[damnshaneisthatu]

5 minutes ago, SimonF said:

Just to confirm you have ticked 20,21,22 and 23? rebooted and you still have the issue?

Correct. Do I need to edit my XML?

[SimonF]

Shouldn't need to should just need to add them to the VM.

 

Can you provide screen print similar to this.

 

[damnshaneisthatu]

22 minutes ago, SimonF said:

Shouldn't need to should just need to add them to the VM.

 

Can you provide screen print similar to this.

 

Ah yes, 00.3 was unchecked. Now I'm getting a "Unknown PCI header type '127'" error. 😂

[SimonF]

9 minutes ago, damnshaneisthatu said:

Ah yes, 00.3 was unchecked. Now I'm getting a "Unknown PCI header type '127'" error. 😂

Untick both nvidia usb devices and just have gpu and sound defined. Try that to see if vm boots

[damnshaneisthatu]

2 minutes ago, SimonF said:

Untick both nvidia usb devices and just have gpu and sound defined. Try that to see if vm boots

No go. Still getting the '127'.

[SimonF]

27 minutes ago, damnshaneisthatu said:

No go. Still getting the '127'.

Can you screen print the gpu allocation are you using a vbios?

[damnshaneisthatu]

48 minutes ago, SimonF said:

Can you screen print the gpu allocation are you using a vbios?

 

Yes.

[damnshaneisthatu]

Seeing this on boot.

[SimonF]

Try without vbios

[damnshaneisthatu]

Still erroring.

[damnshaneisthatu]

Received "vfio: Unable to power on device, stuck in D3" without vbios, both NVIDIA usb devices ticked.

[damnshaneisthatu]

On 5/6/2021 at 7:05 AM, dvd.collector said:

I had exactly the same problem and raised a thread on here.   No updates, so rolled back to 6.8.3.

how did you roll back?

[damnshaneisthatu]

Still no luck

[wkbenpao]

does the promble is solved?

[sheldz8]

You must modify your VM settings to use the new version

Sent from my SM-A305F using Tapatalk