Hi,
it's been a while since I had to deal with that. I wrote a blog post [1] a couple of years ago when we were migrating from xen to kvm. In our case we had to install virtio modules in order to be able to boot those images, they would run into a dracut timeout.
Can I get away with adjusting fstab to use what the partitions are likely to be after transition to OpenStac? Are these of this form: /dev/vda#?
I'm not really sure, I guess you'll have to try it out. And yes, you should replace all references of /dev/xvd* and remove the x.
Regards, Eugen
[1] http://heiterbiswolkig.blogs.nde.ag/2017/08/10/migrate-from-xen-to-kvm/
Zitat von DHilsbos@performair.com:
All;
I've been successful at the tasks listed below, but the resulting volumes don't boot. They stop early in the boot process indicating the root partition cannot be found.
I suspect the issue is with either the disk UUID links, or with partition detection.
When running the VMs under XenServer, we have /dev/disk/by-uuid/<UUID> --> /dev/xvda#
Are these created dynamically by the kernel, or are they static soft-links?
Can I get away with adjusting fstab to use what the partitions are likely to be after transition to OpenStac? Are these of this form: /dev/vda#?
Thank you,
Dominic L. Hilsbos, MBA Vice President – Information Technology Perform Air International Inc. DHilsbos@PerformAir.com www.PerformAir.com
-----Original Message----- From: Sean McGinnis [mailto:sean.mcginnis@gmx.com] Sent: Thursday, April 15, 2021 10:03 AM To: Eugen Block Cc: Dominic Hilsbos; openstack-discuss@lists.openstack.org Subject: Re: [ops][victoria][cinder] Import volume?
On Thu, Apr 15, 2021 at 04:30:45PM +0000, Eugen Block wrote:
Hi,
there’s a ‚cinder manage‘ command to import an rbd image into openstack. But be aware that if you delete it in openstack it will be removed from ceph, too (like a regular cinder volume). I don’t have the exact command syntax at hand right now, but try ‚cinder help manage‘
Regards Eugen
Here is the documentation for that command:
https://docs.openstack.org/python-cinderclient/latest/cli/details.html#cinde...
Also note, if you no longer need to manage the volume in Cinder, but you do not want it to be deleted from your storage backend, there is also the inverse command of `cinder unmanage`. Details for that command can be found here:
https://docs.openstack.org/python-cinderclient/latest/cli/details.html#cinde...
Zitat von DHilsbos@performair.com:
All;
I'm looking to transfer several VMs from XenServer to an OpenStack Victoria cloud. Finding explanations for importing Glance images is easy, but I haven't been able to find a tutorial on importing Cinder volumes.
Since they are currently independent servers / volumes it seems somewhat wasteful and messy to import each VMs disk as an image just to spawn a volume from it.
We're using Ceph as the storage provider for Glance and Cinder.
Thank you,
Dominic L. Hilsbos, MBA Director - Information Technology Perform Air International Inc. DHilsbos@PerformAir.com www.PerformAir.com