R3.1 rc2 bug report: In some cases a DVM does not get properly removed.
50 views
Skip to first unread message
sudod...@gmail.com
Jan 18, 2016, 4:25:46 PM1/18/16
to qubes-users
I use a customized DVM. Sometimes the DVM does not shutdown when closing Firefox. I don't know why and this would not be very disturbing as I could just manually shutdown the DVM. But doing so leads to another problem: When calling `poweroff` in the DVM terminal the DVM executes the command as it is expected. Afterwards I'd like the dispXX to be removed. This does not happen. 'Not so bad', you might think. Just remove it using qubes-manager! Well this messes up things really as some parts of fedora-23-dvm get deleted. (Presumably private.img).
I can't tell which parts of Qubes are involved here...
I can't tell which parts of Qubes are involved here...
If necessary I'll try to find out which files of the dvm template get deleted but this is quite nasty because it probably forces me to customize my neat and perfect dvm template anew again :/
Marek Marczykowski-Górecki
Jan 18, 2016, 6:23:32 PM1/18/16
to sudod...@gmail.com, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Mon, Jan 18, 2016 at 01:25:46PM -0800, sudod...@gmail.com wrote:
> I use a customized DVM. Sometimes the DVM does not shutdown when closing Firefox. I don't know why and this would not be very disturbing as I could just manually shutdown the DVM. But doing so leads to another problem: When calling `poweroff` in the DVM terminal the DVM executes the command as it is expected. Afterwards I'd like the dispXX to be removed. This does not happen. 'Not so bad', you might think. Just remove it using qubes-manager! Well this messes up things really as some parts of fedora-23-dvm get deleted. (Presumably private.img).
> I can't tell which parts of Qubes are involved here...
How such DispVM was started? In case of dom0 menu, take a look at
~/.xsession-errors in dom0. In case of some other VM (for example
opening a file from there) - take a look at its qrexec log. There should
be some error message why the VM wasn't removed automatically.
> If necessary I'll try to find out which files of the dvm template get deleted but this is quite nasty because it probably forces me to customize my neat and perfect dvm template anew again :/
>
- --
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
iQEcBAEBCAAGBQJWnXPsAAoJENuP0xzK19cs2DoH/1tiyF7btZgZApozCz0+ciQ/
MXPzq/x90X1w/SgH42+3fiNQnwBOfjvd7cC+OwxTHqD/m4qdhRNPBZWD1KpAZm1n
BHXmEkdcYet9tPjnkRqPKCJ+0ySU4DT+py9koHEpbtUT7p0dQeUvOw0KddgQq8Cj
sxsRMpzRvKd/zwIIUphl/ntqQOc7Qj78EbEq4yHbYSZ1ca/fZrLsEoKfKEaMt0MA
T6NgPqrAq6oVshvDLu/1mXrHvKuOmNMoollC6kqyoB+vFLnfzRF3+Q99PMSkqUS/
xM0HtwWlXeEQsnVbJM5dp5RPHocOh4zHH1bMpcvjDi6Kz9dNjS4h5FFfKVRyNa4=
=CD6B
-----END PGP SIGNATURE-----
Hash: SHA256
On Mon, Jan 18, 2016 at 01:25:46PM -0800, sudod...@gmail.com wrote:
> I use a customized DVM. Sometimes the DVM does not shutdown when closing Firefox. I don't know why and this would not be very disturbing as I could just manually shutdown the DVM. But doing so leads to another problem: When calling `poweroff` in the DVM terminal the DVM executes the command as it is expected. Afterwards I'd like the dispXX to be removed. This does not happen. 'Not so bad', you might think. Just remove it using qubes-manager! Well this messes up things really as some parts of fedora-23-dvm get deleted. (Presumably private.img).
> I can't tell which parts of Qubes are involved here...
~/.xsession-errors in dom0. In case of some other VM (for example
opening a file from there) - take a look at its qrexec log. There should
be some error message why the VM wasn't removed automatically.
> If necessary I'll try to find out which files of the dvm template get deleted but this is quite nasty because it probably forces me to customize my neat and perfect dvm template anew again :/
>
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
iQEcBAEBCAAGBQJWnXPsAAoJENuP0xzK19cs2DoH/1tiyF7btZgZApozCz0+ciQ/
MXPzq/x90X1w/SgH42+3fiNQnwBOfjvd7cC+OwxTHqD/m4qdhRNPBZWD1KpAZm1n
BHXmEkdcYet9tPjnkRqPKCJ+0ySU4DT+py9koHEpbtUT7p0dQeUvOw0KddgQq8Cj
sxsRMpzRvKd/zwIIUphl/ntqQOc7Qj78EbEq4yHbYSZ1ca/fZrLsEoKfKEaMt0MA
T6NgPqrAq6oVshvDLu/1mXrHvKuOmNMoollC6kqyoB+vFLnfzRF3+Q99PMSkqUS/
xM0HtwWlXeEQsnVbJM5dp5RPHocOh4zHH1bMpcvjDi6Kz9dNjS4h5FFfKVRyNa4=
=CD6B
-----END PGP SIGNATURE-----
sudod...@gmail.com
Jan 19, 2016, 1:55:24 PM1/19/16
to qubes-users, sudod...@gmail.com
Am Dienstag, 19. Januar 2016 00:23:32 UTC+1 schrieb Marek Marczykowski-Górecki:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On Mon, Jan 18, 2016 at 01:25:46PM -0800, sudod...@gmail.com wrote:
> > I use a customized DVM. Sometimes the DVM does not shutdown when closing Firefox. I don't know why and this would not be very disturbing as I could just manually shutdown the DVM. But doing so leads to another problem: When calling `poweroff` in the DVM terminal the DVM executes the command as it is expected. Afterwards I'd like the dispXX to be removed. This does not happen. 'Not so bad', you might think. Just remove it using qubes-manager! Well this messes up things really as some parts of fedora-23-dvm get deleted. (Presumably private.img).
> > I can't tell which parts of Qubes are involved here...
>
> How such DispVM was started? In case of dom0 menu, take a look at
> ~/.xsession-errors in dom0. In case of some other VM (for example
> opening a file from there) - take a look at its qrexec log. There should
> be some error message why the VM wasn't removed automatically.
>
> > If necessary I'll try to find out which files of the dvm template get deleted but this is quite nasty because it probably forces me to customize my neat and perfect dvm template anew again :/
> >
>
>
> - --
> Best Regards
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On Mon, Jan 18, 2016 at 01:25:46PM -0800, sudod...@gmail.com wrote:
> > I use a customized DVM. Sometimes the DVM does not shutdown when closing Firefox. I don't know why and this would not be very disturbing as I could just manually shutdown the DVM. But doing so leads to another problem: When calling `poweroff` in the DVM terminal the DVM executes the command as it is expected. Afterwards I'd like the dispXX to be removed. This does not happen. 'Not so bad', you might think. Just remove it using qubes-manager! Well this messes up things really as some parts of fedora-23-dvm get deleted. (Presumably private.img).
> > I can't tell which parts of Qubes are involved here...
>
> How such DispVM was started? In case of dom0 menu, take a look at
> ~/.xsession-errors in dom0. In case of some other VM (for example
> opening a file from there) - take a look at its qrexec log. There should
> be some error message why the VM wasn't removed automatically.
>
> > If necessary I'll try to find out which files of the dvm template get deleted but this is quite nasty because it probably forces me to customize my neat and perfect dvm template anew again :/
> >
>
>
> - --
> 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
>
> iQEcBAEBCAAGBQJWnXPsAAoJENuP0xzK19cs2DoH/1tiyF7btZgZApozCz0+ciQ/
> MXPzq/x90X1w/SgH42+3fiNQnwBOfjvd7cC+OwxTHqD/m4qdhRNPBZWD1KpAZm1n
> BHXmEkdcYet9tPjnkRqPKCJ+0ySU4DT+py9koHEpbtUT7p0dQeUvOw0KddgQq8Cj
> sxsRMpzRvKd/zwIIUphl/ntqQOc7Qj78EbEq4yHbYSZ1ca/fZrLsEoKfKEaMt0MA
> T6NgPqrAq6oVshvDLu/1mXrHvKuOmNMoollC6kqyoB+vFLnfzRF3+Q99PMSkqUS/
> xM0HtwWlXeEQsnVbJM5dp5RPHocOh4zHH1bMpcvjDi6Kz9dNjS4h5FFfKVRyNa4=
> =CD6B
> -----END PGP SIGNATURE-----
This is how I can reliably reproduce the bug:
> 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
>
> iQEcBAEBCAAGBQJWnXPsAAoJENuP0xzK19cs2DoH/1tiyF7btZgZApozCz0+ciQ/
> MXPzq/x90X1w/SgH42+3fiNQnwBOfjvd7cC+OwxTHqD/m4qdhRNPBZWD1KpAZm1n
> BHXmEkdcYet9tPjnkRqPKCJ+0ySU4DT+py9koHEpbtUT7p0dQeUvOw0KddgQq8Cj
> sxsRMpzRvKd/zwIIUphl/ntqQOc7Qj78EbEq4yHbYSZ1ca/fZrLsEoKfKEaMt0MA
> T6NgPqrAq6oVshvDLu/1mXrHvKuOmNMoollC6kqyoB+vFLnfzRF3+Q99PMSkqUS/
> xM0HtwWlXeEQsnVbJM5dp5RPHocOh4zHH1bMpcvjDi6Kz9dNjS4h5FFfKVRyNa4=
> =CD6B
> -----END PGP SIGNATURE-----
* Use a customized DVM.
* Start a DVM in dom0.
* qvm-run disp* poweroff
Then the DVM remains among my appvms and following error gets logged in dom0, ~./xsession-errors:
Traceback (most recent call last):
File "/usr/lib/qubes/qfile-daemon-dvm", line 185, in <module>
main()
File "/usr/lib/qubes/qfile-daemon-dvm", line 182, in main
dispvm.force_shutdown()
File "/usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py", line 1987, in force_shutdown
raise QubesException ("VM already stopped!")
qubes.qubes.QubesException: VM already stopped!
Sometimes this happens without calling `poweroff` in disp* but I don't know why.
Marek Marczykowski-Górecki
Jan 19, 2016, 2:56:45 PM1/19/16
to sudod...@gmail.com, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On Tue, Jan 19, 2016 at 10:55:24AM -0800, sudod...@gmail.com wrote:
> Am Dienstag, 19. Januar 2016 00:23:32 UTC+1 schrieb Marek Marczykowski-Górecki:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > On Mon, Jan 18, 2016 at 01:25:46PM -0800, sudod...@gmail.com wrote:
> > > I use a customized DVM. Sometimes the DVM does not shutdown when closing Firefox. I don't know why and this would not be very disturbing as I could just manually shutdown the DVM. But doing so leads to another problem: When calling `poweroff` in the DVM terminal the DVM executes the command as it is expected. Afterwards I'd like the dispXX to be removed. This does not happen. 'Not so bad', you might think. Just remove it using qubes-manager! Well this messes up things really as some parts of fedora-23-dvm get deleted. (Presumably private.img).
> > > I can't tell which parts of Qubes are involved here...
> >
> > How such DispVM was started? In case of dom0 menu, take a look at
> > ~/.xsession-errors in dom0. In case of some other VM (for example
> > opening a file from there) - take a look at its qrexec log. There should
> > be some error message why the VM wasn't removed automatically.
> >
> > > If necessary I'll try to find out which files of the dvm template get deleted but this is quite nasty because it probably forces me to customize my neat and perfect dvm template anew again :/
> > >
>
> Am Dienstag, 19. Januar 2016 00:23:32 UTC+1 schrieb Marek Marczykowski-Górecki:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > On Mon, Jan 18, 2016 at 01:25:46PM -0800, sudod...@gmail.com wrote:
> > > I use a customized DVM. Sometimes the DVM does not shutdown when closing Firefox. I don't know why and this would not be very disturbing as I could just manually shutdown the DVM. But doing so leads to another problem: When calling `poweroff` in the DVM terminal the DVM executes the command as it is expected. Afterwards I'd like the dispXX to be removed. This does not happen. 'Not so bad', you might think. Just remove it using qubes-manager! Well this messes up things really as some parts of fedora-23-dvm get deleted. (Presumably private.img).
> > > I can't tell which parts of Qubes are involved here...
> >
> > How such DispVM was started? In case of dom0 menu, take a look at
> > ~/.xsession-errors in dom0. In case of some other VM (for example
> > opening a file from there) - take a look at its qrexec log. There should
> > be some error message why the VM wasn't removed automatically.
> >
> > > If necessary I'll try to find out which files of the dvm template get deleted but this is quite nasty because it probably forces me to customize my neat and perfect dvm template anew again :/
> > >
>
> This is how I can reliably reproduce the bug:
> * Use a customized DVM.
> * Start a DVM in dom0.
> * qvm-run disp* poweroff
>
> Then the DVM remains among my appvms and following error gets logged in dom0, ~./xsession-errors:
>
> Traceback (most recent call last):
> File "/usr/lib/qubes/qfile-daemon-dvm", line 185, in <module>
> main()
> File "/usr/lib/qubes/qfile-daemon-dvm", line 182, in main
> dispvm.force_shutdown()
> File "/usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py", line 1987, in force_shutdown
> raise QubesException ("VM already stopped!")
> qubes.qubes.QubesException: VM already stopped!
>
> Sometimes this happens without calling `poweroff` in disp* but I don't know why.
Thanks! This is exactly the input I need to fix the problem!
> * Use a customized DVM.
> * Start a DVM in dom0.
> * qvm-run disp* poweroff
>
> Then the DVM remains among my appvms and following error gets logged in dom0, ~./xsession-errors:
>
> Traceback (most recent call last):
> File "/usr/lib/qubes/qfile-daemon-dvm", line 185, in <module>
> main()
> File "/usr/lib/qubes/qfile-daemon-dvm", line 182, in main
> dispvm.force_shutdown()
> File "/usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py", line 1987, in force_shutdown
> raise QubesException ("VM already stopped!")
> qubes.qubes.QubesException: VM already stopped!
>
> Sometimes this happens without calling `poweroff` in disp* but I don't know why.
https://github.com/QubesOS/qubes-issues/issues/1660
- --
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
iQEcBAEBCAAGBQJWnpT1AAoJENuP0xzK19csg74H/jQQeA06Zb+5p/lXrsEX5jQs
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
0JQDby7K5z9lH8JQBUI+tA/fOwDcaiENUoYz6QN7CtYlDS6qf3p6RGUZseIo55k2
gLG0PY8ZTs7qCqFuFr83//oVCoGdEB0KsUrMTTo7Nko/dLr2lyK4xQkJ+/gMU/Pw
v1BuFnGMcCTSNUhLPhSzBOBLCgrzt0Vvkrn4ui0K/JJ3KhCo4vUlOrKjCgQuLMVj
+fsFPfWWXCgplhOSCwDO+d2S87YibIX57Hsb5JCXoLwuqnKJfLZPf83YDmivvca1
40VMjQH1nUdL2Wqr1MFWqjLssAEfBb9bs7FtRLtiX3HMqz/X+5OVpotkGx1dIt8=
=iUok
-----END PGP SIGNATURE-----
Reply all
Reply to author
Forward
0 new messages