Many thanks Grzesiek! It seems there's a command line tool to handle the menu,
so it can be done this way:
sudo xdg-desktop-menu uninstall fedora-23-vm.directory
fedora-23-qubes-appmenu-select.desktop
Those latter two identified by looking in the directory you specified,
Hmm. Two devices with the same major:minor numbers? /dev/mapper/dmroot &
/dev/dm-0
/dev/mapper/dmroot does not appear in Dom0, nor does any error appear in
journalctl. I do find that device in sys-{net,firewall,whonix,usb} and in
those cases it always appears as:
ls -l /dev/mapper/dmroot
I'm getting this error in a popup login:
> Oops!
> We're sorry, it looks like root=/dev/mapper/dmroot crashed.
> Please contact the developer if you want to report the issue.
I haven't identified any problems, though. It happened subsequent to this
mistake and repair:
Ok, for anyone else who makes such a stupid mistake, you can change the
templates of all the VM's through the Dom0 command line. To get the list of
properties of a VM, use:
qvm-prefs -l
Then, change the the template property (not the root_img property) for each of
the VM's:
qvm-prefs -s
Patrick - I couldn't wait until evening. :)
Your suggestion worked miracles. Only point: install, then reboot with VT-d
_off_ and complete the setup process. When that's done, follow the
instructions in your link.
Now looking at the HCL, it's woefully out of date for this machine. What
Patrick - Ok, the main thing in there seems to be to disable VT-d and do the
install, with some grub trickery to re-enable it later. I'll try that tonight
and report back. Thanks.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To
I'm experimenting by installing on a Thinkpad T500, which has integrated
(intel) graphics. Since the install freezes after loading the initrd, I try
installing in "basic graphics mode". A lot of text streams by, of which I can
only see the end, but I notice:
"Not asking for VNC because we