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 -- 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+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@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.
