PCI Device Doesn't exist

[Oregano1963]

Qubes OS release

Latest 4.2.3 downloaded a few hours ago from the website.

Brief summary

Upon downloading it, it got the following error. I redownloaded it twice and got the same error at the same time towards the end of the initialization. When trying to use a vm, it gives the same error as below

Steps to reproduce

Download QubesOS and download it. Wait until after it downloads, start it up, and after the scripts are done running, it'll come up with this error.

Expected behavior

Regulat installation and usage

Actual behavior

Screen goes black after clicking off the warning and goes to the password screen, It then returns a similar error regarding sysnet when trying to access a VM.

CPU: 7800x3d
Externals, monitor, mouse, usb, keyboard
If other information should be provided, do ask.

[marmarek]

Can you show output of qvm-pci command in dom0?

[Oregano1963]

Can you show output of qvm-pci command in dom0?

Here's the qvm-pci

Also, when entering, I have to confirm my mouse (by hitting enter a few times). Is that normal and how do I make it not ask to confirm my mouse everytime?

[marmarek]

and what about qvm-pci ls sys-net?

I have to confirm my mouse (by hitting enter a few times). Is that normal and how do I make it not ask to confirm my mouse everytime?

There is a setting for that in "qubes global config"

[Eric678]

I noticed this in 4.2.3 install and mentioned it in #8322 - the wrong PCI device numbers retrieved initially (new to 4.2.3) - one can probably rescue that system by using the qubes.skip_autostart facility and taking the bad device numbers out of sys_net (& sys_usb) and replacing with the correct ones in settings.

[Oregano1963]

Here's the qvm-pci ls sys-net result:

[marmarek]

I'm not quite sure why in your case, but the ethernet controller changed its BDF. Go to sys-net's settings, remove the unknown device and add the correct ethernet controller.

Anyway, this looks like a duplicate of #7792

[Oregano1963]

I noticed this in 4.2.3 install and mentioned it in #8322 - the wrong PCI device numbers retrieved initially (new to 4.2.3) - one can probably rescue that system by using the qubes.skip_autostart facility and taking the bad device numbers out of sys_net (& sys_usb) and replacing with the correct ones in settings.

How do I use the autostart facility/take the device out of sysnet and add the right one??

[Eric678]

Sorry, as Marek said, you are actually running, so you can just go into settings/devices in sys_net and you will see one of the assigned devices says device does not exist or something similar. Move that one to the left, and find the correct one and move it over to the right.

[github-actions]

This issue has been closed as a "duplicate." This means that another issue exists that is very similar to or subsumes this one. If any useful information on this issue is not already present on the other issue, please add it in a comment on the other issue. Here are some common cases of duplicate issues:

• The other issue is closed. The other issue being closed does not prevent this issue from duplicating it. We will examine the closed issue and, if appropriate, reopen it.
• The other issue is for a different Qubes release. We usually maintain only one issue for all affected Qubes releases.
• The other issue is very old. The mere age of an issue is not, by itself, a relevant factor when determining duplicates.

By default, the newer issue will be closed in favor of the older issue. However, we make exceptions when we determine that it would be significantly more useful to keep the newer issue open instead of the older one.

We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community.

If anyone reading this believes that this issue was closed in error or that the resolution of "duplicate" is not accurate, please leave a comment below saying so, and we will review this issue again. For more information, see How issues get closed.