On Mon, Aug 13, 2012 at 08:35:28PM -0700, Vishvananda Ishaya wrote:
> a) The device name only makes sense for linux. FreeBSD will select different
> device names, and windows doesn't even use device names. In addition xen uses
> /dev/xvda and kvm uses /dev/vda
>
> b) The device sent in kvm will
> From: Daniel P. Berrange [mailto:berra...@redhat.com]
> On Wed, Aug 15, 2012 at 03:49:45PM +0100, John Garbutt wrote:
> > You can see what XenAPI exposes here:
> > http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/api/?c=VBD
> >
> > I think the only thing you can influence when plugging in th
On Wed, Aug 15, 2012 at 03:49:45PM +0100, John Garbutt wrote:
> You can see what XenAPI exposes here:
> http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/api/?c=VBD
>
> I think the only thing you can influence when plugging in the disk is the
> “userdevice”
> which is the disk position: 0,1,2
garbutt=citrix@lists.launchpad.net
> [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On
> Behalf Of Wangpan
> Sent: 15 August 2012 5:11
> To: Vishvananda Ishaya
> Cc: openstack
> Subject: Re: [Openstack] [nova] Disk attachment consistency
> > This is defin
> This is definitely another solution, although it seems less usable than the
> device serial number which can be an arbitrary string. If this works for xen
> though, that would be a plus.
> Vish
I don't have a Xen hypervisor in hand, so anybody else can try it on Xen ?
thanks___
On Aug 14, 2012, at 7:55 PM, "Wangpan" wrote:
> How about using the pci address as the UUID of target devices in one VM?
> the pci address is generated by libvirt and we can see it in VM by cmd "ls
> -la /sys/block/",
> and it has no dependency with the kernel version, I can see it in 2.6.32*
>
How about using the pci address as the UUID of target devices in one VM?
the pci address is generated by libvirt and we can see it in VM by cmd "ls -la
/sys/block/",
and it has no dependency with the kernel version, I can see it in 2.6.32*
when an user attached a disk to VM, we find a free target
Hey Everyone,
Overview
One of the things that we are striving for in nova is interface consistency,
that is, we'd like someone to be able to use an openstack cloud without knowing
or caring which hypervisor is running underneath. There is a nasty bit of
inconsistency in the way that d
8 matches
Mail list logo
