Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upNewly created standalone VMs don't start #3947
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
3hhh
Jun 1, 2018
Hmmm ok:
qvm-clone --class StandaloneVM debian-9 stest2 works.
I had thought that this was identical and wonder what qvm-create --class StandaloneVM is then meant to be doing?
Btw stest size is shown as 0 by qubes-qube-manager, stest2 size as the size of debian-9.
3hhh
commented
Jun 1, 2018
•
|
Hmmm ok: I had thought that this was identical and wonder what Btw stest size is shown as 0 by |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
3hhh
Jun 1, 2018
Ahh ok I get it:
qvm-create is for an empty VM for CD installation, qvm-clone for the copy. That is different from 3.2.
I.e. this can be handled as part of #3017.
3hhh
commented
Jun 1, 2018
|
Ahh ok I get it: I.e. this can be handled as part of #3017. |
3hhh commentedJun 1, 2018
•
edited
Edited 1 time
-
3hhh
edited Jun 1, 2018 (most recent)
-
3hhh
created Jun 1, 2018
Qubes OS version:
4.0
debian 9 template (didn't test fedora)
4.14.35-1 kernel
Affected component(s):
standalone VMs
Steps to reproduce the behavior:
qvm-create --class StandaloneVM -l red stest
qvm-start stest
Expected behavior:
stest starts
Actual behavior:
stest fails to start
General notes:
Old standalone VMs still start.
I also tried two different kernels and HVM mode (instead of pvh above) - all failed.
Twice the log also mentioned something about the ext4 kernel module not being loaded / existing. Maybe the debian-9 template is missing something required for StandaloneVMs, but not for normal AppVMs?
Related issues:
#3017