Dear all, after upgrading to 3.2 (in-place) I noticed the following issue:
qvm-block -A fooVM dom0:/var/lib/qubes/appvms/blaVM/private.imgTraceback (most recent call last):
File "/usr/bin/qvm-block", line 151, in <module>
main()
File "/usr/bin/qvm-block", line 105, in main
block_attach(qvm_collection, vm, dev, **kwargs)
File "/usr/lib64/python2.7/site-packages/qubes/qubesutils.py", line 429, in block_attach vm.libvirt_domain.attachDevice(etree.tostring(disk, encoding='utf-8')) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 530, in attachDevice if ret == -1: raise libvirtError ('virDomainAttachDevice() failed', dom=self) libvirt.libvirtError: internal error: libxenlight failed to attach disk 'xvdi'
Strangely enough, xvdi still appears in fooVM and can be mounted. Attempting to attach another file to fooVM however fails with the same error and xvdj does not appear.
More stranegely, it works perfectly on another Qubes machine (same kernel, same Xen version, no in-place-upgrade though) I got.
Possibly related: I also noticed that netvm and firewallVM don't always start with the 4.4.14-11 kernel on boot anymore; thus I'm currently testing 4.1.13-9.
xl info host : dom0 release : 4.4.14-11.pvops.qubes.x86_64 version : #1 SMP Tue Jul 19 01:14:58 UTC 2016 machine : x86_64 nr_cpus : 4 max_cpu_id : 3 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 3399hw_caps : bfebfbff:2c100800:00000000:00007f00:77fafbff:00000000:00000021:00002fbb
virt_caps : hvm hvm_directio total_memory : 16048 free_memory : 71 sharing_freed_memory : 0 sharing_used_memory : 0 outstanding_claims : 0 free_cpus : 0 xen_major : 4 xen_minor : 6 xen_extra : .1 xen_version : 4.6.1xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : xen_commandline : placeholder console=none cc_compiler : gcc (GCC) 5.3.1 20160406 (Red Hat 5.3.1-6) cc_compile_by : user cc_compile_domain : cc_compile_date : Tue Jul 26 11:55:46 UTC 2016 xend_config_format : 4 Dom0 is 100% up-to-date as of today. Anyone got an idea on how to fix that qvm-block -A issue? Kind Regards David -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1f88a6c6-8e85-2598-42d4-1349490b9bb7%40hackingthe.net. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
