DispVM does not work anymore

44 views
Skip to first unread message

mitte...@digitrace.de

unread,
Jan 12, 2017, 9:01:03 AM1/12/17
to qubes-users
Hey there,

today I noticed that my dispVM is no longer working (not in Dom0 and not
in AppVMs). There is the notification that the DispVM starts, but
nothing shows up.
If I start the internal fedora-23-dvm I boots up without any problems
and also allows me to start tools (e.g. Firefox)

any idea what is wrong?

Thanks

Ángel

unread,
Jan 12, 2017, 6:27:14 PM1/12/17
to qubes...@googlegroups.com
I suspect you too may be suffering
https://github.com/QubesOS/qubes-issues/issues/2182

Look at /var/log/libvirt/libxl/libxl-driver.log and see if there is a
line like
xc: error: X86_PV_VCPU_MSRS record truncated: length 8, min 9: Internal
error

The reason that directly booting the dvn works is that the problem lies
in restoring the savefile (and the buggy creation of it).

There are some patches fixing it, but you would need to recompile xen :/

Best regards



raah...@gmail.com

unread,
Jan 13, 2017, 4:30:10 PM1/13/17
to qubes-users, mitte...@digitrace.de

open qubes-manager window. click view and show internal vms. Then remove the dvm qube.

then in a dom0 terminal make a new one. qvm-create-default-dvm fedora-24.

Robert Mittendorf

unread,
Jan 17, 2017, 9:59:20 AM1/17/17
to qubes...@googlegroups.com

> I suspect you too may be suffering
> https://github.com/QubesOS/qubes-issues/issues/2182
>
> Look at /var/log/libvirt/libxl/libxl-driver.log and see if there is a
> line like
> xc: error: X86_PV_VCPU_MSRS record truncated: length 8, min 9: Internal
> error
>
> The reason that directly booting the dvn works is that the problem lies
> in restoring the savefile (and the buggy creation of it).
>
> There are some patches fixing it, but you would need to recompile xen :/
/var/log/libvirt/libxl
(dom0) contains only 2 empty folders ("dump" and "save")

raahelps suggestion to recreate the dvm worked
Reply all
Reply to author
Forward
0 new messages