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 upKernel panic while loading HVM machines on a clean Qubes 4.0 #3911
Comments
evilaliv3
changed the title from
Segmentation fault while loading HVM machines on a clean Qubes 4.0
to
Kernel panic while loading HVM machines on a clean Qubes 4.0
May 19, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
May 19, 2018
Member
This doesn't look like neither ubuntu nor windows...
Have you set kernel to '' (or "(none)" if using GUI)? See here for details for 4.0.
|
This doesn't look like neither ubuntu nor windows... |
andrewdavidwong
added
bug
C: kernel
C: Debian
C: Windows HVM
labels
May 19, 2018
andrewdavidwong
added this to the Release 4.0 updates milestone
May 19, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
evilaliv3
May 19, 2018
Thank you @marmarek !
You totally centerded the issue and suggested the right fix.
This guide would require to include this detail: https://www.qubes-os.org/doc/hvm/
I leave this ticket open so that we can use this to keep track of the update of that specific document.
Here some fixes that i annotated that would be important to apply as well to that guide:
qvm-run --pass-io untrusted 'cat "/media/user/externalhd/win10.raw"' > /home/user/win10-root.img
this command could be update to use dd in order to manage correctly sparse files (like ISOs are); the fix i used is the one documented here: https://groups.google.com/forum/#!topic/qubes-users/l1vuQEjqce4
it is possible in fact that a file of 34GB with a cat command is expanded to be 134GB (like it happened to me today)qvm-create --hvm win10 --label red --mem=4096 --root-move-from /home/user/win10-root.img
this command is outdated. hvm is not recognized as a valid option and the same --mem=4096
the command that i managed to get working is:
qvm-create win10 --label red --root-move-from /home/user/win10-root.img
Then for making it working i've required to manually change the kernel and to set the VM to be of type HVM;
In other comments on a ticket or mail of you @marmarek i remember that specifically in relation to --hvm you were saying that VMs are now created by default as HVM but its seems that this is not the case.
evilaliv3
commented
May 19, 2018
|
Thank you @marmarek ! This guide would require to include this detail: https://www.qubes-os.org/doc/hvm/ I leave this ticket open so that we can use this to keep track of the update of that specific document. Here some fixes that i annotated that would be important to apply as well to that guide:
Then for making it working i've required to manually change the kernel and to set the VM to be of type HVM; |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
evilaliv3
May 19, 2018
As an update with the above integration now windows is able to boot.
It then reaches a restoring state, where it tries to recover itself but dies.
evilaliv3
commented
May 19, 2018
|
As an update with the above integration now windows is able to boot. It then reaches a restoring state, where it tries to recover itself but dies. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
To little memory? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
evilaliv3
commented
May 19, 2018
|
I gave 8GB of RAM and 10GB/10GB of disk |
andrewdavidwong
added
help wanted
C: doc
task
and removed
bug
labels
May 20, 2018
andrewdavidwong
modified the milestones:
Release 4.0 updates,
Documentation/website
May 20, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
May 20, 2018
Member
This guide would require to include this detail: https://www.qubes-os.org/doc/hvm/
I leave this ticket open so that we can use this to keep track of the update of that specific document.
Please consider submitting a PR:
Please consider submitting a PR: |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
May 20, 2018
Member
See /var/log/xen/console/hypervisor.log if there is anything about crashing of that qube. If not, only windows could tell what is wrong, try booting in safe mode and access events log there.
|
See |
evilaliv3 commentedMay 19, 2018
•
edited
Edited 1 time
-
evilaliv3
edited May 19, 2018 (most recent)
I tried to create two HVM machines on a clean Qubes 4.0 setup.
The laptop used for this test is a Thinkpad T480.
For creating the VMs i've followed the official guideline for the Windows Trial that you provide in the documentation (with few adjustments required as dd has to be used for handling sparse files).
In alternative i've also tried to install an ubuntu 18.04 as HVM setup just to identify if the issue was in my procedure or in windows. In this second test i was trying to boot using the ISO.
Here follows the log of the Windows HVM boot:
It follows the Ubuntu 18.04 boot from the ISO:
Qubes OS version:
4.0
Affected component(s):
HVM VMs
Steps to reproduce the behavior:
Create an HVM vm and start it.
I followed the official guide for using the trial of Windows and as well i've tried to boot from the CD of ubuntu.
Expected behavior:
The VM is expected to boot correctly and be visualized.