Please help, can't get into Qubes

[Fred]

I made a change to the PCI devices for the sys-net VM and now Qubes
hangs on boot when starting this vm.

I've tried using the installation image to get to system rescue via the
troubleshooting link in the installer. I can get into my system this way
but I'm unsure what to change as removing the pci device from the
sys-net XML file doesn't seem to make this change persist -- something
keeps generating a new one with the bad PCI device XML node.

How can I disable sys-net from starting when connected via a rescue shell?

[Sec Tester]

why not just delete sys-net VM and build a new one?

once created, remember assign the adaptor to it
https://www.qubes-os.org/doc/assigning-devices/

[Alex]

On 11/12/2016 04:32 AM, Sec Tester wrote:
> On Saturday, 12 November 2016 06:39:50 UTC+10, Fred wrote:
>> I made a change to the PCI devices for the sys-net VM and now
>> Qubes hangs on boot when starting this vm.
>>
>> I've tried using the installation image to get to system rescue via
>> the troubleshooting link in the installer. I can get into my system
>> this way but I'm unsure what to change as removing the pci device
>> from the sys-net XML file doesn't seem to make this change persist
>> -- something keeps generating a new one with the bad PCI device XML
>> node.
>>
>> How can I disable sys-net from starting when connected via a rescue
>> shell?

Try editing /var/lib/qubes/qubes.xml and set "autostart" to False
instead of True for the sys-net vm

--
Alex

[Marek Marczykowski-Górecki]

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

This wont help on its own.
Take a look at this thread:
https://groups.google.com/forum/#!msg/qubes-users/LH_HsTRdvtY/Ii2zq78pAwAJ

- --
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

iQEcBAEBCAAGBQJYJ0YWAAoJENuP0xzK19cs7uAH/0NaFFobOfQ6vUMK8HWJgoGn
k/GhQFcNITJnUJpxP3debGgPQwZiVlpOoTodZy84iypksp45p7kP5kqEYnI3GlDP
dYUfJiOYxrVB/6bUJrbhSx2ZcY1/tsMRxz2404hJG7YXf6k5txHEnj9Hsfvwt2Oj
yFwI23yX+k9PjfatJ0yfmucfxap2BQVPsrrrQv1mevrmW02EzPIGIc/jaJ5MoCEI
sITTnlO9FOWaEaWRyNUml2K275H7Lmq1Gkxej53eQSpuyI3ocMCuok8DxXyKXVc8
7t1A1hCM53scHb9qSRbXlemggjCLWyH7yXx2ijaLBydQRrWD9T/trZg+0z/NCyo=
=6x79
-----END PGP SIGNATURE-----

[Fred]

On 12/11/2016 08:27, Alex wrote:
> Try editing /var/lib/qubes/qubes.xml and set "autostart" to False
> instead of True for the sys-net vm

I had actually found this file and tried setting the autostart attribute
but the VM still auto-started.

I also tried editing the sys-net XML file directly (removing the bad
assigned device(s)). There was a warning in the comments at the top
about this file about changes potentially being overwitten but I
couldn't find the correct file to make these changes manually. This file
also existed in more than one place and the qvm-* commands didn't work
as they couldn't connect.

In any case I just reinstalled as it was quicker.

The offline mode of the qvm-* commands may have worked (referred to in
the link in Marek's response). Or maybe disabling the sysVM service via
systemctl ?

[Unman]

For future reference, I think the sys-net started because there were
OTHER qubes downstream set to autostart, e.g sys-firewall. If they are
still starting they will trigger the sys-net. So you need to either set
the netvm to none for them or stop them starting.

unman

[Fred]

On 14/11/2016 13:46, Unman wrote:
> For future reference, I think the sys-net started because there were
> OTHER qubes downstream set to autostart, e.g sys-firewall. If they are
> still starting they will trigger the sys-net. So you need to either set
> the netvm to none for them or stop them starting.

That makes more sense. Thanks.

[Marek Marczykowski-Górecki]

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

On Mon, Nov 14, 2016 at 01:31:28PM +0000, Fred wrote:

Both should work. As for services, you need to disable:
- qubes-netvm.service
- qube...@sys-net.service (this is really what 'autostart' VM property
really does)
- qube...@sys-firewall.service - and any other using sys-net for its
network - or set those to not use sys-net.

- --
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

iQEcBAEBCAAGBQJYKjDXAAoJENuP0xzK19csJs8H/0cEeo7N7EnYzIIi5s0QiPri
s0djWNxg4I72EW/HIMdmTh6+YHNFoY+ZSIQpr4/6RH4047EyE3F8hSB8N+fxwpha
rgMFiHWqsZGGoHxAFvl5goPKpWg91E3mUpgh4fJ991zq71P+D9nhX0EmLM1tGwoE
sGeAzI5MfdBdxrjCSkH0mW7oGdhxEELQ3oQxZNjPn4/8TqIqOkWztB3DNs+T/Quv
5CeX3GfZDjLRH60lfrdkDvWCqlr7XsySueRwjPELC2Khagql+2jCWHbLThakWhMx
arEZSVhs7gQ0SiMQQjifzjQ708p00cLwKiLyZDQMcdDGo87ID8JRK+8HlHllt3c=
=Wuoj
-----END PGP SIGNATURE-----