[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Importing KVM ivda drives as xdva drives

Hi Guys,

This is my first post to this mailing list so please excuse my
ignorance. I started running Alpine Linux Dom0 about half a year ago and
I am very happy with it. 

Recently I inherited a KVM hypervisor with about dozen guests some of
which are Windows servers.  All KVM guests are either raw or qcow2 image
file formats. I am trying to move them from KVM host to Dom0 (not
block devices or block device partitions).

I did a bit of playing trying to migrate RHEL 7.5 image to Xen Dom0
Alpine. It seems that the only obstacle in importing KVM images into the
Xen is the disk naming. Namely KVM is using virtio (paravirtualization
driver) for disks which are named as


for a OS drive. Xen on the another hand is using different naming
convention where the drives inside disk images .img are denoted for
example as


When I create DomU out of KVM image file the both process proceed
successfully until it drops into dracut shell as it can't find root
partition which is on the /dev/vda drive. Is the HDDs naming superficial
problem or is it fundamental incompatibility on the level of disk
drivers? This is my rhel.cfg file

entebuilder = "hvm"
name = "rhel75"
memory = 4096 
vif = [ 'mac=52:54:00:3b:22:4b, bridge=br0']
disk = [ 'file:/xen-images/rhel75.img,format=raw,xvda,rw' ]
boot = "dc"

Notice that I did try replacing xvda with vda but it is unrecognized
vdev. I also tried putting hda instead which also dropped me to dracut
shell during the both process.

I am sure I am not the first one who is trying this but except this 
unhelpful post


I could not fine any hints about the proper procedure.


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.