Error PCI deviceis in use by Xenlight

[ndbuc...@gmail.com]

oops I did it again. I removed the panel with the networking icon from sys-net (qubes 3.1 rc1) In trying to fix this I have stumbled into a state where when I try to boot any VM i get

Error starting VM: requested operation is not valid: PCI device 000:000:19.0 is in use by driver Xenlight, domain sys-net

interesting the error is the same whether i try to start sys-net or work or firewall VMs. Is there a way to fix this?

if not, is there way from dom0 to copy my users files on backup disk. I only need to get about 10 files. I was planning to install qubes 3.1 rc3 anyway ;) I know where to find template files in dom0 file manager but I cannot find my user files.

Buck

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Thu, Mar 03, 2016 at 06:14:46AM -0800, ndbuc...@gmail.com wrote:
> oops I did it again. I removed the panel with the networking icon from sys-net (qubes 3.1 rc1) In trying to fix this I have stumbled into a state where when I try to boot any VM i get
>
> Error starting VM: requested operation is not valid: PCI device 000:000:19.0 is in use by driver Xenlight, domain sys-net
>
> interesting the error is the same whether i try to start sys-net or work or firewall VMs.

This is bacause all of those VMs need to start sys-net first.

> Is there a way to fix this?

Have you tried simple reboot?

> if not, is there way from dom0 to copy my users files on backup disk. I only need to get about 10 files. I was planning to install qubes 3.1 rc3 anyway ;) I know where to find template files in dom0 file manager but I cannot find my user files.
>
> Buck
>

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJW2Mj7AAoJENuP0xzK19csqDQIAIAk5KyM3ZIWVdpFfbKJ2qgW
pS+NRuYIg4BHVy89Zr4LOktd35ceGbqvyvljbpxRAQN4YjQRwYajfKeuMRmcC5Am
2dJrFyWDmwYy1KFL0L8JPiIWHU+C3pwsjFnih4DJn+1Y+irrtPiCeiY0yadtvCHX
Hdp5a/Pwd9gqDyJE4gXCHXJXIPLrQNJnSRNX+wICM6Y1mbo6We64AihYbrKA2kPZ
dj8VxpdeqSPPNWJHLAfxliiRRJbSIe9TGmu0cVQ6BXmCRFSm9Wsk7V0T3Mn+GiKX
D01VUSQ7KTR+QfZk/2sx392u5LjONvRC5XkE0+/0W6ELXi0h7T8rqRzAFtWd5wI=
=laLj
-----END PGP SIGNATURE-----

[raah...@gmail.com]

I got this message in qubes manager trying to start a sys-net.

[timet...@gmail.com]

I too have had this problem multiple times. In my case it seems to happen when my external USB cord gets nudged out of position on the USB port. A reboot does fix the problem but it is very annoying to have to reboot in the middle of one's work because of a hardware SNAFU.

I can confirm that shutting down all the VMs and restarting them does not work. What does work (partially) is if one goes into VM Settings/Devices and remove all the offending devices, click OK, and then you can reboot the VM that causing problems. However, this leaves you without networking. The only way to get networking back is reboot.

[raah...@gmail.com]

On Thursday, March 24, 2016 at 6:44:52 PM UTC-4, timet...@gmail.com wrote:
> I too have had this problem multiple times. In my case it seems to happen when my external USB cord gets nudged out of position on the USB port. A reboot does fix the problem but it is very annoying to have to reboot in the middle of one's work because of a hardware SNAFU.
>
> I can confirm that shutting down all the VMs and restarting them does not work. What does work (partially) is if one goes into VM Settings/Devices and remove all the offending devices, click OK, and then you can reboot the VM that causing problems. However, this leaves you without networking. The only way to get networking back is reboot.

ran into exactly same thing recently. for me it was bewcause i had shut down all vms. then when returning to pc 20 mins later and unlocking screen i first went to manually start sys-net and it wouldn't start getting that same error. I believe i tried to start sys-usb first, and it didn't help. But i'll keep an eye out for it to happen again. tks for your posts to know I aint the only one.