HVM Creation - immediate shutdown after boot

[maxhea...@gmail.com]

Next in my qubes learning is the creation of a HVM. I noticed a couple things through the process and wanted to get comments on some of the hang-ups.

First step was to download an .iso into one of my AppVMs. During this process, the AppVMs were failing downloads after a couple of minutes. I suspected it was because that they were filling up their disk space, even with no other files on the AppVM.

After running a 'df -h' I noticed that the "rw" drive was at 100% (is this something Qubes specific?), even after expanding the AppVMs through Qubes Manager.

1. What might be causing this? What is the "rw" drive?

I circumvented this holdup by creating a new AppVM with enough space to download the .iso. After creating the StandadloneVM and pointing its boot 'cdrom' to the .iso file in the AppVM mentioned above, the opening screen of the OS appears and is interactive. However, after choosing to boot the OS, the screen quickly closes and the StandaloneVM shuts down.

2. What do you suspect causes this? The StandaloneVM has been allocated 15GB of space and left the default 4GB RAM.

System: Base Qubes 4.0 installation, Fedora 28 template, Thinkpad T480 w/32Gb RAM.

Expected results: StandaloneVM boots into basic OS configuration wizard for the .iso and installation can proceed.

Thanks again for any help in advance!

- Max

[pieter lems]

Hello max,

I think i know the answer to both questions but if there is something wrong please correct me. (to the people that know a lot about qubes)

Regarding your first question. The download did indeed fail  because there was not enough disk space on your qube. I've had the same problem multiple times but increasing the available disk space should solve the problem. This can be done by increasing the private storage size in the qubes settings manager.

As far as i know is the /rw folder the folder which is persistent after a restart of the qube. The rw folder contains configuration files concerning the specific qube. Did you maybe point the iso download to the rw folder? this could be the reason why its 100% full.

Regarding your second question, Ive had the same problem while installing a kali iso. Increasing the max memory to 8GB solved the problem for me. This can be done under the advanced tab in the qubes settings manager.

I hope some of this info can help you out.

Goodluck!

Op do 29 nov. 2018 om 21:19 schreef <maxhea...@gmail.com>:

--
You received this message because you are subscribed to the Google Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4dbe1307-b47b-4314-bcd7-c5d044a2a9e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[unman]

Pieter - can you remember not to top post please?

You're partly right about /rw - it contains configuration, /usr/local
and /home.
That's why the download ran out of space because /rw is created by
default at 2G. You can change this under settings. /home/user is stored
there so Downloads can rapidly fill that space.

As to booting StandaloneVM, 4GB should be fine, depending on the OS -
certainly enough for kali.
Also worth checking that you have kernel set to '', (and maybe virt_mode
hvm)

unman

[pieter lems]

Hi , im sorry im kinda new to this google-groups feature.

    About the initial question. Iknow 4gb should be enough but it only worked after setting the max value to 8GB.

--
You received this message because you are subscribed to the Google Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20181130005824.bfm35u4ue6b4adhk%40thirdeyesecurity.org.

[maxhea...@gmail.com]

You were right! The .iso needed more RAM initially allocated to it beyond the default values.

As for /rw, that was not only reading the Qubes introductory information but also seeing it in action that helped me understand.

Thank you both so much.

- Max