I used the following commands in dom0 to restore dispVM functionality:
qubes-dom0-update xen-libs-4.6.6-36.fc23.x86_64
xen-hypervisor-4.6.6-36.fc23.x86_64 xen-runtime-4.6.6-36.fc23.x86_64
xen-hvm-4.6.6-36.fc23.x86_64 xen-4.6.6-36.fc23.x86_64
xen-license-4.6.6-36.fc23.x86_64
dnf downgrade
On Sat, Mar 17, 2018 at 11:52:00PM +, qubes-li...@riseup.net wrote:
> What would be the step to downgrade to the previous version to
> get dispVMs working again?
>
> qubes-dom0-update --action=downgrade xen something like this or is it
> necessary to specify all
What would be the step to downgrade to the previous version to
get dispVMs working again?
qubes-dom0-update --action=downgrade xen something like this or is it
necessary to specify all packets individually?
>>>
>>> Depending on how attached you are to Fedora, you might
On Sat, Mar 17, 2018 at 08:13:00PM +, qubes-li...@riseup.net wrote:
>
>
> awokd:
> > On Sat, March 17, 2018 7:57 pm, qubes-li...@riseup.net wrote:
> >
> >> What would be the step to downgrade to the previous version to
> >> get dispVMs working again?
> >>
> >> qubes-dom0-update
On Sat, March 17, 2018 8:13 pm, qubes-li...@riseup.net wrote:
> I get the same error after switching to debian-9 as the dispVM template.
>
>
> So switching to debian-9 for dispVM is unfortunately _not_ a possible
> workaround for this.
I saw Marek confirmed it's a Xen issue too. Thanks for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, Mar 17, 2018 at 08:04:34PM -, 'awokd' via qubes-users wrote:
> On Sat, March 17, 2018 7:57 pm, qubes-li...@riseup.net wrote:
>
> > What would be the step to downgrade to the previous version to
> > get dispVMs working again?
> >
> >
awokd:
> On Sat, March 17, 2018 7:57 pm, qubes-li...@riseup.net wrote:
>
>> What would be the step to downgrade to the previous version to
>> get dispVMs working again?
>>
>> qubes-dom0-update --action=downgrade xen something like this or is it
>> necessary to specify all packets individually?
On Sat, March 17, 2018 7:57 pm, qubes-li...@riseup.net wrote:
> What would be the step to downgrade to the previous version to
> get dispVMs working again?
>
> qubes-dom0-update --action=downgrade xen something like this or is it
> necessary to specify all packets individually?
Depending on how
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2018-03-17 14:57, qubes-li...@riseup.net wrote:
>
>
> Andrew David Wong:
>> On 2018-03-17 11:40, qubes-li...@riseup.net wrote:
>>
Have you made sure that you have updated the packages in the
template and regenerated the DispVM?
Andrew David Wong:
> On 2018-03-17 11:40, qubes-li...@riseup.net wrote:
>
>>> Have you made sure that you have updated the packages in the
>>> template and regenerated the DispVM? That's a common source of
>>> these problems and fixed it for me.
>
>> Yes I've updated and regenerated the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2018-03-17 11:40, qubes-li...@riseup.net wrote:
>
>> Have you made sure that you have updated the packages in the
>> template and regenerated the DispVM? That's a common source of
>> these problems and fixed it for me.
>
> Yes I've updated
> Have you made sure that you have updated the packages in the template
> and regenerated the DispVM?
> That's a common source of these problems and fixed it for me.
Yes I've updated and regenerated the dispvm after the dom0 update.
--
You received this message because you are subscribed to
On Sat, Mar 17, 2018 at 11:53:00AM +, qubes-li...@riseup.net wrote:
> DispVM functionality does no longer work for me in Q3.2 since yesterday.
>
> First I assumed the template is broken but after reinstalling the fedora-26
> template
> from the rpm repo and recreating the DVM I get the very
DispVM functionality does no longer work for me in Q3.2 since yesterday.
First I assumed the template is broken but after reinstalling the fedora-26
template
from the rpm repo and recreating the DVM I get the very same error.
Has anyone else the same problem after installing the latest dom0
14 matches
Mail list logo
