[libvirt-users] error: internal error: missing backend for pool type 11 (zfs)

Nick Gilmour nickeforos at gmail.com
Tue Oct 3 15:51:58 UTC 2017


*Errors with journalctl:*

Oct 03 16:27:21 host libvirtd[18183]: 2017-10-03 14:27:21.021+0000: 18201:
error : virNetworkObjAssignDefLocked:594 : opera
tion failed: network 'default' already exists with uuid
a780228d-cf2a-4475-ad03-6f8b72b48dd8


*Multiple XCB errors like this (I don't know if they are related...):*

Oct 03 16:20:39 host plasmashell[1389]: QXcbConnection: XCB error: 2
(BadValue), sequence: 47851, resource id: 100663303, m
ajor code: 142 (Unknown), minor code: 3


*And some others:*
Oct 03 09:25:25 host libvirtd[955]: 2017-10-03 07:25:25.457+0000: 1025:
error : storageDriverAutostart:227 : internal error
: Failed to autostart storage pool 'test-vol': cannot open directory
'/dev/zvol/virt-pool': No such file or directory

Oct 03 01:07:18 host libvirtd[24462]: 2017-10-02 23:07:18.579+0000: 24466:
error : qemuProcessUpdateGuestCPU:5159 : unsuppo
rted configuration: CPU mode 'custom' for x86_64 kvm domain on x86_64 host
is not supported by hypervisor

Oct 03 01:05:37 host libvirtd[24462]: 2017-10-02 23:05:37.152+0000: 24467:
error : virStoragePoolObjSourceFindDuplicate:105
4 : operation failed: Storage source conflict with pool: 'images'
Oct 03 01:06:04 kronos libvirtd[24462]: 2017-10-02 23:06:04.857+0000:
24465: error : qemuProcessUpdateGuestCPU:5159 : unsuppo
rted configuration: CPU mode 'custom' for x86_64 kvm domain on x86_64 host
is not supported by hypervisor

Oct 03 01:06:19 host libvirtd[24462]: 2017-10-02 23:06:19.214+0000: 24464:
error : qemuConnectGetDomainCapabilities:19173 :
invalid argument: KVM is not supported by '/usr/sbin/qemu-system-x86_64' on
this host

Oct 03 01:06:33 host libvirtd[24462]: 2017-10-02 23:06:33.144+0000: 24462:
error : qemuMonitorIORead:595 : Unable to read f
rom monitor: Connection reset by peer

Oct 03 01:06:33 host libvirtd[24462]: 2017-10-02 23:06:33.144+0000: 24462:
error : qemuProcessReportLogError:1880 : interna
l error: qemu unexpectedly closed the monitor:
chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -spice
port=5900,addr
=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on
-device qxl-vga,id=video0,ram_size=67108864,vram_siz
e=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2
-device intel-hda,id=sound0,bus=pci.0,addr=0x4 -dev
ice hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev
spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=ch
arredir0,id=redir0,bus=usb.0,port=1 -chardev
spicevmc,id=charredir1,name=usbredir -device
usb-redir,chardev=charredir1,id=red
ir1,bus=usb.0,port=2 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on

Oct 03 01:06:33 host libvirtd[24462]: 2017-10-02T23:06:33.089796Z
qemu-system-x86_64: -chardev pty,id=charserial0: char dev
ice redirected to /dev/pts/5 (label charserial0)

Oct 03 01:06:33 host libvirtd[24462]: Could not access KVM kernel module:
Permission denied

Oct 03 01:06:33 host libvirtd[24462]: 2017-10-02T23:06:33.089878Z
qemu-system-x86_64: failed to initialize KVM: Permission
denied

Oct 03 01:06:33 host libvirtd[24462]: 2017-10-02 23:06:33.145+0000: 24467:
error : qemuProcessReportLogError:1880 : interna
l error: process exited while connecting to monitor:
chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -spice port=590
0,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on
-device qxl-vga,id=video0,ram_size=67108864,vr
am_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2
-device intel-hda,id=sound0,bus=pci.0,addr=0x
4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev
spicevmc,id=charredir0,name=usbredir -device usb-redir,char
dev=charredir0,id=redir0,bus=usb.0,port=1 -chardev
spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,
id=redir1,bus=usb.0,port=2 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on

Oct 03 01:06:33 host libvirtd[24462]: 2017-10-02T23:06:33.089796Z
qemu-system-x86_64: -chardev pty,id=charserial0: char dev
ice redirected to /dev/pts/5 (label charserial0)

Oct 03 01:06:33 host libvirtd[24462]: Could not access KVM kernel module:
Permission denied

Oct 03 01:06:33 host libvirtd[24462]: 2017-10-02T23:06:33.089878Z
qemu-system-x86_64: failed to initialize KVM: Permission
denied


*I have manually built the zfs pool and the zvol and then tried to define
it in VMM.*



On Tue, Oct 3, 2017 at 5:16 PM, Michal Privoznik <mprivozn at redhat.com>
wrote:

> On 10/03/2017 04:40 PM, Nick Gilmour wrote:
> > I have set root in both for user and group in the qemu.conf and changed
> the
> > file permissions to root like it was before. Now I'm getting this error:
> >
> > *# Error 1#*
> > *Unable to complete install: 'internal error: process exited while
> > connecting to monitor: us=pci.0,addr=0x5.0x7 -device
> > ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,
> multifunction=on,addr=0x5
> > -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=
> 0x5.0x1
> > -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=
> 0x5.0x2
> > -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive
> > file=/dev/zvol/virt-pool/vmm/fedora,format=raw,if=none,id=
> drive-ide0-0-0,cache=none,aio=native
> > -device
> > ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2
> -drive
> > 'file=/home/nick/Downloads/#IMAGES#/Fedora-Workstation-
> Live-x86_64-26-1.5.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on'
> > -device
> > ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1,bootindex=1
> > -netdev user,id=hostnet0 -device
> > rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:ad:21:19,bus=pci.0,addr=0x3
> > -chardev pty,id=charserial0 -device
> > isa-serial,chardev=charserial0,id=serial0 -chardev
> > spicevmc,id=charchannel0,name=vdagent -device
> virtserialport,bus=virtio-se'*
>
> This looks like the error message was cut off. Isn't there a full error
> message somewhere in the logs, e.g. journalctl?
>
> Anyway, qemu is dying because .. and this is where the message would
> help. To help us identify the reason. Maybe
> /dev/zvol/virt-pool/vmm/fedora doesn't exist (just a rough guess)?
>
>
> > <snip/>
> >
> > *Error starting domain: Cannot access storage file
> > '/dev/zvol/virt-pool/test-vol' (as uid:4294967295, gid:4294967295): No
> such
> > file or directory*
>
> Have you built the storage pool or just defined it?
>
> Michal
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20171003/bad3009b/attachment.htm>


More information about the libvirt-users mailing list