[Xen-users] xen+rbd(ceph)+qemu on centos 7

[Daniel Mezentsev <dan@xxxxxxxxxx>]

Hi Xen-Users,

Need i need help with issue troubleshooting. Here is my setup latest setup:
CentOS 7.2, Xen 4.7rc4 (installed from RPM. cbs.centos.org), qemu 2.6 (recompiled with rbd and xen support), ceph 10.2 (from ceph repo), kernel 4.6 from elrepo.
I did try previouse versions but all results were the same.
So basically i can't start VM. qemu which is coming from xen-runtime package compiled without rbd support, so it can't get image info, that is why i rebuild qemu, so i can read information about image:

qemu-img info rbd:vm_images/vol-spacewalk.soleks.net:id=admin:conf=/etc/ceph/ceph.conf
image: rbd:vm_images/vol-spacewalk.soleks.net:id=admin:conf=/etc/ceph/ceph.conf
file format: raw
virtual size: 256G (274877906944 bytes)
disk size: unavailable
cluster_size: 4194304

so that portion works.

I can boot VM kernel, here is VM configuration file:

# bootloader="pygrub"
device_model_override = "/usr/local/bin/qemu-system-i386"
device_model_version = "qemu-xen"

name = "spacewalk.soleks.net"

# kernel = '/boot/VM/vmlinuz-2.6.32-504.30.3.el6.x86_64'
# kernel = '/boot/VM/vmlinuz-2.6.32-642.1.1.el6.x86_64'
kernel = '/boot/VM/vmlinuz-4.6.2-1.el6.elrepo.x86_64'
# ramdisk = '/boot/VM/initramfs-2.6.32-504.30.3.el6.x86_64.img'
# ramdisk = '/boot/VM/initramfs-2.6.32-642.1.1.el6.x86_64.img'
ramdisk = '/boot/VM/initramfs-4.6.2-1.el6.elrepo.x86_64.img'
extra = 'console=hvc0'

vcpus=4

memory = "8192"

disk = [ 'backendtype=qdisk, vdev=xvda, target=rbd:vm_images/vol-spacewalk.soleks.net:id=admin' ]

root = '/dev/mapper/vg_spacewalk-vol_root'

vif = [
    'mac=00:16:3E:03:FF:00, bridge=br-core41',
    'mac=00:16:3E:03:FF:01, bridge=br-dmz42'
]
serial = 'pty'

_on_reboot_ = 'restart'
_on_shutdown_ = 'destroy'
_on_crash_ = 'destroy'

but kernel is reporting the following:
xenbus_probe_frontend: Device with no driver: device/vbd/51712
xenbus_probe_frontend: Device with no driver: device/vif/0
xenbus_probe_frontend: Device with no driver: device/vif/1

and in the log qemu-dm:
xen be core: xen be core: xen be: watching backend path (backend/console/4) failed
xen be: watching backend path (backend/console/4) failed
xen be core: xen be core: xen be: watching backend path (backend/vkbd/4) failed
xen be: watching backend path (backend/vkbd/4) failed
xen be core: xen be core: xen be: watching backend path (backend/vfb/4) failed
xen be: watching backend path (backend/vfb/4) failed
xen be core: xen be core: xen be: watching backend path (backend/qdisk/4) failed
xen be: watching backend path (backend/qdisk/4) failed
xen be core: xen be core: xen be: watching backend path (backend/qnic/4) failed
xen be: watching backend path (backend/qnic/4) failed
qemu-system-i386: terminating on signal 1 from pid 30579

i don't know where to go from there, so need help from community.

Daniel Mezentsev, founder
(+1) 604 313 8592.
Soleks Data Group.
Shaping the clouds.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users