proxyvm without autostart flag does start automatically

Joonas Lehtonen

unread,

Jul 11, 2014, 4:36:51 PM7/11/14

to qubes...@googlegroups.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

A custom proxyvm (default netvm (b)) is starting up without having the
autostart flag set. No AppVM using that netvm is set to autostart.

I guess Qubes OS does a "hardcoded" autostart of the default netvm(b).

How can I prevent that autostart? Is there a way to configure that?
(doing a manual shutdown everytime at system boot seems like a waste
of time)

due to the ambiguous usage of the word 'netvm' within the Qubes
project, I feel like this explanation is necessary:
a) netvm - the VM that hosts the networking hardware
b) netvm - the default gw of an appvm
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJTwErQAAoJEG58zmw5nc+vuhoQAIvfcxrD+/HzfWaNN5/wMVID
N+KZe1Xm7HIgtJrjh0Rzwl3R5YT8Zis1zzPbL8F3wh/5bbgBOJhcpV2DAYNhy53w
YDnP1WslsO5+bo5GHzDcMK9Fytzhk/IZ9nMyCS9Gi5I4WEJEej0l4ASXDhJCvbhS
jhLq4hgkqu+3fre76GtpND/7FFK1ve0Di/xjjfjbUJDqhLKsRU3uzFNis8+XCeZK
z7FsUKqflBkzZAOFl/TMX1K7Pa2CQMzyiYQyc/Pyq0qwLeW3I3aMPky15lnLYi0d
ZEJBU2a4lm2EttmvZJ9koLCkA9mqPGyPOBvI9M0YxXBOeOE2wlUpkovBR/z/IRAL
VOBaC0FIy02v6KNnQFEXSKquadeI4jRKdjwQO+TbbQPAYUPfkz7+HR7Gt0dClbjH
CG1IZwAPGme5Qal4oiJTEUKzjyb1Az7f+yjymMCikqpqCgF/jDrd3sXFzvvL7v5y
L5sdUmoYSkyDBmthFJFJ1NAdyZscKcf52BdRyfH6p8jYat2DIjxJ55TrOImMpD7s
LTys1fb4MVCdIWuRrm7tYGf60xA4W+dM8a63/e2ryXhuIUxwblK9T3zBOe84mLs4
M0qhljYo+WZIAZZtqIS6Qi639ZoLQGiHES6Rp292pX/q9qTZhRuDdejjTKfAAoEq
xOZHpNJ4bivJj+STqCyy
=5NQy
-----END PGP SIGNATURE-----

Marek Marczykowski-Górecki

unread,

Jul 11, 2014, 4:49:57 PM7/11/14

to Joonas Lehtonen, qubes...@googlegroups.com

On 11.07.2014 22:36, Joonas Lehtonen wrote:
> A custom proxyvm (default netvm (b)) is starting up without having the
> autostart flag set. No AppVM using that netvm is set to autostart.
>
> I guess Qubes OS does a "hardcoded" autostart of the default netvm(b).
>
> How can I prevent that autostart? Is there a way to configure that?
> (doing a manual shutdown everytime at system boot seems like a waste
> of time)

The default netvm is started by qubes-netvm dom0 service. If you don't want
that, simply disable the service.

> due to the ambiguous usage of the word 'netvm' within the Qubes
> project, I feel like this explanation is necessary:
> a) netvm - the VM that hosts the networking hardware
> b) netvm - the default gw of an appvm

--

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?

signature.asc

Joonas Lehtonen

unread,

Jul 11, 2014, 6:21:23 PM7/11/14

to qubes...@googlegroups.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

>> A custom proxyvm (default netvm (b)) is starting up without
>> having the autostart flag set. No AppVM using that netvm is set
>> to autostart.
>>
>> I guess Qubes OS does a "hardcoded" autostart of the default
>> netvm(b).
>>
>> How can I prevent that autostart? Is there a way to configure
>> that? (doing a manual shutdown everytime at system boot seems
>> like a waste of time)
>
> The default netvm is started by qubes-netvm dom0 service. If you
> don't want that, simply disable the service.

thank you for that explanation. Now the netvm(a) and firewall-vm do
not start anymore even after enabling the autostart flag for them?

>> due to the ambiguous usage of the word 'netvm' within the Qubes
>> project, I feel like this explanation is necessary: a) netvm -
>> the VM that hosts the networking hardware b) netvm - the default
>> gw of an appvm

Reply all

Reply to author

Forward