DispVM

[Fred]

Are there any known issues with the DispVM in Qubes 3.2 that I should be
aware of?

I cannot get it to work. I have also tried recreating it two ways based
on the default template *and* choosing a different non-default one.

i.e

qvm-create-default-dvm fedora-23 and qvm-create-default-dvm
--default-template both work and seem to create the vms. Trying to use
it however gives no error and the vm does not start in Qubes Manager.

[Unman]

I'm not aware of any particular issues, although there have been some
reports of issues with customisation.
I assume that you have a template : fedora-23-dvm or similar.
Can you remove this using qvm-remove , and then try creating the
template again?
Confirm that the qvm-create-default-dvm script runs properly to
conclusion and that the dvm template is created.
You can try to run a program in that template to make sure all is well.
Then try running program in a dispVM.

unman

[Fred]

On 14/11/2016 17:56, Unman wrote:

> I'm not aware of any particular issues, although there have been some
> reports of issues with customisation.

Here is what I get after removing and recreating. No errors and the save
file says it was created OK. I found an xterm command to run in dom0 to
try and debug and I got the following;

time=1479157412.67, qfile-daemon-dvm init
time=1479157412.67, creating DispVM
time=1479157412.82, collection loaded
time=1479157412.91, VM created
time=1479157412.97, VM starting
time=1479157412.97, creating config file
time=1479157413.32, calling restore
Traceback (most recent call last):
File "/usr/lib/qubes/qfile-daemon-dvm", line 200, in <module>
main()
File "/usr/lib/qubes/qfile-daemon-dvm", line 188, in main
dispvm = qfile.get_dvm()
File "/usr/lib/qubes/qfile-daemon-dvm", line 150, in get_dvm
return self.do_get_dvm()
File "/usr/lib/qubes/qfile-daemon-dvm", line 103, in do_get_dvm
dispvm.start()
File
"/usr/lib64/python2.7/site-packages/qubes/modules/01QubesDisposableVm.py",
line 193, in start
domain_config, libvirt.VIR_DOMAIN_SAVE_PAUSED)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4405, in
restoreFlags
if ret == -1: raise libvirtError ('virDomainRestoreFlags() failed',
conn=self)
libvirt.libvirtError: internal error: libxenlight failed to restore
domain 'disp7'

[Unman]

Is there anything in /var/log/libvirt/libxl logs?

[Fred]

On 14/11/2016 21:32, Unman wrote:
> Is there anything in /var/log/libvirt/libxl logs?

The following;

2016-11-14 20:38:15 GMT libxl: error: libxl_pci.c:1041:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:01:00.1
2016-11-14 20:40:12 GMT xc: error: X86_PV_VCPU_MSRS record truncated: length 8, min 9: Internal error
2016-11-14 20:40:12 GMT xc: error: Restore failed (0 = Success): Internal error
2016-11-14 20:40:12 GMT libxl: error: libxl_stream_read.c:749:libxl__xc_domain_restore_done: restoring domain: Success
2016-11-14 20:40:12 GMT libxl: error: libxl_create.c:1145:domcreate_rebuild_done: cannot (re-)build domain: -3
2016-11-14 20:42:58 GMT xc: error: X86_PV_VCPU_MSRS record truncated: length 8, min 9: Internal error
2016-11-14 20:42:58 GMT xc: error: Restore failed (0 = Success): Internal error
2016-11-14 20:42:58 GMT libxl: error: libxl_stream_read.c:749:libxl__xc_domain_restore_done: restoring domain: Success
2016-11-14 20:42:58 GMT libxl: error: libxl_create.c:1145:domcreate_rebuild_done: cannot (re-)build domain: -3
2016-11-14 20:43:18 GMT xc: error: X86_PV_VCPU_MSRS record truncated: length 8, min 9: Internal error
2016-11-14 20:43:18 GMT xc: error: Restore failed (0 = Success): Internal error
2016-11-14 20:43:18 GMT libxl: error: libxl_stream_read.c:749:libxl__xc_domain_restore_done: restoring domain: Success
2016-11-14 20:43:18 GMT libxl: error: libxl_create.c:1145:domcreate_rebuild_done: cannot (re-)build domain: -3
2016-11-14 20:46:41 GMT xc: error: X86_PV_VCPU_MSRS record truncated: length 8, min 9: Internal error
2016-11-14 20:46:41 GMT xc: error: Restore failed (0 = Success): Internal error
2016-11-14 20:46:41 GMT libxl: error: libxl_stream_read.c:749:libxl__xc_domain_restore_done: restoring domain: Success
2016-11-14 20:46:41 GMT libxl: error: libxl_create.c:1145:domcreate_rebuild_done: cannot (re-)build domain: -3
2016-11-14 20:56:02 GMT xc: error: X86_PV_VCPU_MSRS record truncated: length 8, min 9: Internal error
2016-11-14 20:56:02 GMT xc: error: Restore failed (0 = Success): Internal error
2016-11-14 20:56:02 GMT libxl: error: libxl_stream_read.c:749:libxl__xc_domain_restore_done: restoring domain: Success
2016-11-14 20:56:02 GMT libxl: error: libxl_create.c:1145:domcreate_rebuild_done: cannot (re-)build domain: -3
2016-11-14 20:56:12 GMT xc: error: X86_PV_VCPU_MSRS record truncated: length 8, min 9: Internal error
2016-11-14 20:56:12 GMT xc: error: Restore failed (0 = Success): Internal error
2016-11-14 20:56:12 GMT libxl: error: libxl_stream_read.c:749:libxl__xc_domain_restore_done: restoring domain: Success
2016-11-14 20:56:12 GMT libxl: error: libxl_create.c:1145:domcreate_rebuild_done: cannot (re-)build domain: -3
2016-11-14 21:03:34 GMT xc: error: X86_PV_VCPU_MSRS record truncated: length 8, min 9: Internal error
2016-11-14 21:03:34 GMT xc: error: Restore failed (0 = Success): Internal error
2016-11-14 21:03:34 GMT libxl: error: libxl_stream_read.c:749:libxl__xc_domain_restore_done: restoring domain: Success
2016-11-14 21:03:34 GMT libxl: error: libxl_create.c:1145:domcreate_rebuild_done: cannot (re-)build domain: -3

[Unman]

That's a known Xen bug, and patches are available, but I'm not sure if
they are yet in Qubes - have you done an update in dom0?

[Unman]

Just checked and it's still an open issue - #2182

[Fred]

Thanks!

I'll stop trying to get DispVMs working for now then.