Re: [qubes-users] Post-install inability to create qube
On Sunday, October 14, 2018 at 7:58:49 AM UTC-6, Chris Laprise wrote: > On 10/12/2018 01:44 AM, 'awokd' via qubes-users wrote: > > e on 10/12/18 5:37 AM: > >> Hello, > >> > >> After completing install (for my first time), I was able to login. > >> > >> Going to the menu, "Create Qubes VM," getting the dialog box titled > >> "[Dom0] Create new qube," the Template select drop-down control only > >> has "default(none)," even if I select type Standalone rather than AppVM. > >> Also, I don't see anything anywhere like work, personal and untrusted, > >> neither sys-net or sys-usb. /var/lib/qubes/vm-templates has a debian > >> and fedora folder, but it seems like these are not available when > >> trying to create qubes via CLI via qvm-create. journalctl all show an > >> AssertionError. > >> Any ideas? > > > > Did you receive any errors on the first post-install boot? There's a > > step there that is supposed to configure all those templates. Is it > > possible you skipped it? Otherwise, often a misbehaving network device > > causes sys-net creation to break, which then causes the rest to fail to > > get created. In that case, try disabling your wifi card temporarily, > > then reinstalling. You can re-enable it afterwards and add it back to > > your sys-net in Qube Settings/Devices. > > > > Try 'sudo dnf list qubes-template*' to see a list of installed > templates. If there are none, try mounting the installation media, > locate a qubes-template*rpm file and install the rpm file directly. This > should be a lot less time-consuming than re-installing Qubes. > > -- > > Chris Laprise, > https://github.com/tasket > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 I tried disabling wifi and reinstalling entire Qubes again (a 12 hour process on my USB 2.0 sticks) but ended up with same thing (actually, since I tried not creating root user this time, I had to manually start some services libvirtd relies on - had to add root user to qubes and libvirtd groups for that to work, and was finally back to the point, again, where the error is just default template missing). The /var/lib/qubes directory had full pack of 2G+ of template and kernel files, and after tracing through python code to decode assertion errors, I was convinced something in the templates did not get completely installed or configured (ie in both full Qubes OS install instances). rpm -ihv Packages/q/qubes-templates (after mounting the installer) said templates were already installed, so I did an rpm --reinstall instead. Then instead of missing template error I started to get no default_kernel, so did similar to Packages/k/qubes-kernel and was finally able to select template in qube creation, and qvm-ls finally displayed more than just AdminVM. Now, I have to figure out how to configure sys-net and connect it to another VM, but this seems to be another matter (Salt, Networking and Template VM documents seem to cover that). BTW, rpm reinstall for both packages ended with errors, but the VM still launched. Thanks for your suggestion - it helped a lot. -- 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/a72f03c3-700b-4458-8bac-c6362178d1ad%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Post-install inability to create qube
Hello, After completing install (for my first time), I was able to login. Going to the menu, "Create Qubes VM," getting the dialog box titled "[Dom0] Create new qube," the Template select drop-down control only has "default(none)," even if I select type Standalone rather than AppVM. Also, I don't see anything anywhere like work, personal and untrusted, neither sys-net or sys-usb. /var/lib/qubes/vm-templates has a debian and fedora folder, but it seems like these are not available when trying to create qubes via CLI via qvm-create. journalctl all show an AssertionError. Any ideas? Thanks in advance -- 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/ba5259e3-402b-4ec1-87a7-3712236c97ea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Celeron N3350 and VT-d
On Monday, October 8, 2018 at 8:42:50 PM UTC-6, awokd wrote: > @gmail.com: > > On Monday, October 8, 2018 at 8:10:17 AM UTC-6, awokd wrote: > >> > >> > >>> Now, for the actual question. :) The installer reports missing > >>> IOMMU/VT-d/AMD-Vi, however the machine's motherboard is an Intel Celeron > >>> N3350 which, according to > >>> https://ark.intel.com/products/95598/Intel-Celeron-Processor-N3350-2M-Cache-up-to-2-4-GHz-, > >>> should have VT-d (unless it needs a specific kind of VT-d?). I am not > >>> sure about IOMMU, perhaps it is missing. Does the error message list > >>> those as alternatives of the same thing? Or is it that I may have VT-d > >>> but not IOMMU, and the error just lists them all if just one has not been > >>> detected? > >> > >> Did you enable the possibly multiple virtualization options in your UEFI > >> config? > > > > There are actually no virtualization options in my UEFI config. I do get to > > turn off secure boot and some TSC stuff, but not much else. There's no vmx > > flag in /proc/cpuinfo (less that file after ctrl+f2 during installation), > > but apparently Qubes is not complaining about a lack of VT-x. There is a > > hypervisor flag, however. > > It's possible your CPU supports the features, but not your motherboard's > chipset and/or UEFI. Not having any options in the config for it is > generally a bad sign. Check to see if there's a firmware update > available for your board. VT-d implies there's at least one IOMMU, and > VT-x is present on everything with VT-d. Indeed... doing more research it does seem that it is not simply a matter at looking at what the chipset supports. Updated UEFI to its latest version, and still there is no option for virtualization settings. Since I used default installation settings and to encrypt drive (actually to a flash drive) I had to gpart it to have fat32 partition with /boot info (used the installer structure as example but with files that were actually installed to the encrypted partition.) Finally logged in. qubes-hcl-report gives HVM active, I/O MMU not active, HAP/SLAT Yes, TPM Device not found (UEFI settings has something about TPM), Remapping No. This is for an Acer Aspire ES1 432. I'll still use Qubes this way, knowing full well that without VT-d, a lot of protection (ie against DMA attacks) is disabled. I'll just cross my fingers that perhaps a future firmware update will allow VT-d to be turned on, if the motherboard supports it. Thanks for the pointers! Cheers -- 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/9732c1ec-58ac-4750-9603-8cb6cbd5c0b8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Celeron N3350 and VT-d
On Monday, October 8, 2018 at 8:10:17 AM UTC-6, awokd wrote: > > > > Now, for the actual question. :) The installer reports missing > > IOMMU/VT-d/AMD-Vi, however the machine's motherboard is an Intel Celeron > > N3350 which, according to > > https://ark.intel.com/products/95598/Intel-Celeron-Processor-N3350-2M-Cache-up-to-2-4-GHz-, > > should have VT-d (unless it needs a specific kind of VT-d?). I am not sure > > about IOMMU, perhaps it is missing. Does the error message list those as > > alternatives of the same thing? Or is it that I may have VT-d but not > > IOMMU, and the error just lists them all if just one has not been detected? > > Did you enable the possibly multiple virtualization options in your UEFI > config? There are actually no virtualization options in my UEFI config. I do get to turn off secure boot and some TSC stuff, but not much else. There's no vmx flag in /proc/cpuinfo (less that file after ctrl+f2 during installation), but apparently Qubes is not complaining about a lack of VT-x. There is a hypervisor flag, however. -- 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/4840c644-5351-45ba-8e0b-270ff1adad14%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Celeron N3350 and VT-d
Kudos to the QubesOS team for the effort and cool idea that is Qubes. I'm new Qubes and a few days ago decided to give it a try. After dd'ing the R4 checksum-checked iso and turning off "secure boot" on target device, I got a printk flood of GPE errors. After being unable to stop/mask them with the acpi_mask_gpe or similar boot option (was not even sure what to use), I edited BOOTX64.cfg to use [qubes] (but modified to still no be quiet) instead of [qubes-verbose]. It booted but always failed to mount /dev/root or /dev/mapper/live-rw. Internet search results had me trying many things to no avail. Finally, I found out my USB stick is a fake (thanks f3write/read). I tried from another (this time good) stick and got the same error. I suspected it had to do with the UEFI-only boot mode of target machine only? using GPT, and therefore deleted all partitions on good stick and created a GPT table with gdisk; then I dd'd, and then it finally booted to the installer. (Perhaps UEFI boot mode stage 2 freaks out if partition 1 is not GPT labelled, even though stage 1 boots fine.) Now, for the actual question. :) The installer reports missing IOMMU/VT-d/AMD-Vi, however the machine's motherboard is an Intel Celeron N3350 which, according to https://ark.intel.com/products/95598/Intel-Celeron-Processor-N3350-2M-Cache-up-to-2-4-GHz-, should have VT-d (unless it needs a specific kind of VT-d?). I am not sure about IOMMU, perhaps it is missing. Does the error message list those as alternatives of the same thing? Or is it that I may have VT-d but not IOMMU, and the error just lists them all if just one has not been detected? Cheers -- 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/d3ebe02a-29ec-468e-b22a-231cb47f1018%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
