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

[Xen-users] xvda1, xvda2 disk configuration with hvm

  • To: xen-users@xxxxxxxxxxxxxxxxxxxx
  • From: Juan Rossi <juan@xxxxxxxxxxxxxxx>
  • Date: Thu, 8 Mar 2018 10:59:35 +1300
  • Delivery-date: Wed, 07 Mar 2018 22:01:11 +0000
  • Domainkey-signature: a=rsa-sha1; c=simple; d=rimuhosting.com; h=to:from :subject:message-id:date:mime-version:content-type :content-transfer-encoding; q=dns; s=mail; b=gdP1j57oq/hycRchuu/ ODkPinNZdl9JmWpKA2Mtx5d4Yxi1VLmAEQZSdkzc3+BU1lvKT25rkqIBYJ5yDWca 6A5uZQzkjjh54fPYofIG1BQ9fGvbpJimv7QSiJL9VCoQUKXdVOxtGgrJt3J8jCrQ TNMHnEa0Lnc/M9kgXuHdkH+w=
  • List-id: Xen user discussion <xen-users.lists.xenproject.org>


We are converting some VMs from pv into hvm, we used to map the disks in the configuration file as follows:

disk = [ 'phy:/dev/users/debian.img,xvda1,w', 'phy:/dev/users/debian.swapfs.swp,xvda9,w' ]

so we are basically mapping block devices that have no partition tables, just file systems to xvdaX style devices.

When moving into type=hvm we hit issues with this, if I am correct it is due qemu-dm and the need to have partition tables, mapping to raw disks and devices have the need to be in different denomination letter, eg /dev/users/debian.img,xvda1 /dev/users/debian.swapfs.swp,xvdb1.

Is there a work around or setting we may be missing that will allows us to map FSs in the form of xvdaX using hvm?



Xen-users mailing list



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