sounds promising. :)
One question: (when) will the gui-domain be made 'mandatory' in qubes 4.1?
I may prefer my meagerly hardware accelerated KDE 5.17/18 in dom0 until
it's clear under which circumstances GPU virtualization works properly.
--
You received this message because you are
Oh no.. I feel the pain. I had a similar disaster, I got a 2nd ssd and
installed windows on its own ssd. Physically remove qubes drive before
installing windows and vise versa. I had to reinstall qubes os.. I was able
to save most of my stuff by creating each qube disk image mouting to usb
and
Xen 4.4 has support for OVMF. Which version of Xen does Qubes uses?
Shouldn't it already have this option?
--
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
Guerlan:
> Xen 4.4 has support for OVMF. Which version of Xen does Qubes uses?
> Shouldn't it already have this option?
>
"xl info" in dom0 will tell you exactly. Mine says 4.8.5-14. Xen might
be able to support it (although looks like it's not in the default
build), but not the Qubes or
Guerlan:
>
>
> My Qubes is closing my windows 10 VMs which are based on my Win10 template
> after 60 seconds, even though they are ok. It says
>
>
> Domain win10 failed to start: cannot connect to qrexec agent for 60 seconds
>
>
> even though it already had started and I was using it.
>
>
General:
> I ran out of space on a thin lvm pool due to a runaway process. This
> corrupted /var/lib/qubes/qubes.XML which I restored from a backup.
>
> To recover space, I cleared 2GB of logs RM -rf /var/log/*
>
> I then had to mkdir /var/log/qubes
>
> Now qubesd service starts, but on
taran1s:
> Most probably, the
> "unrecommended" notice is just something in the Nyx monitor which
> preferes some other versions?
Probably. Check the Nyx documentation; unlikely it's related to Qubes
(or Whonix).
--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant
Stumpy:
> I recently made a fedora 30 based standalone VM so i wouldnt have to
> goop up my templates with some employer-required programs.
>
> It was working fine for a day or two but earlier today I sat down and
> wasnt able to start any programs up in this standalown vm?
> I hhave tried from
On Fri, Apr 10, 2020 at 02:54:01AM -0700, Foppe de Haan wrote:
> I may prefer my meagerly hardware accelerated KDE 5.17/18 in dom0 until
> it's clear under which circumstances GPU virtualization works properly.
Forgive me from taking this off-topic from the original thread. I have
tried and
