Ok, so then what would make a host not mapping the appropriate drive
name? Is there a script dropped on XenServer or something?
It works fine on some host, and doesn't on some other on the same cluster :S
FG
On 2015-04-07 10:44 PM, Mike Tutkowski wrote:
CloudStack picks a disk sequence number from the DB and passes it to
the XenServer agent. It appears the /dev path you see is perhaps
selected inside of XAPI.
This is the relevant CloudStack code in XenServerStorageProcessor
(diskNumber is the disk sequence number):
vbdr.VM = vm;
vbdr.VDI = vdi;
vbdr.bootable = false;
vbdr.userdevice = diskNumber;
vbdr.mode = Types.VbdMode.RW;
vbdr.type = Types.VbdType.DISK;
vbdr.unpluggable = true;
VBD vbd = VBD.create(conn, vbdr);
// Attach the VBD to the VM
vbd.plug(conn);
On Tue, Apr 7, 2015 at 8:31 PM, Francois Gaudreault
<fgaudrea...@cloudops.com <mailto:fgaudrea...@cloudops.com>> wrote:
Hi,
Quick question. On Volume attach code for XenServer, does
CloudStack push the /dev/sd* or /dev/xvd* for XenServer to use?
Is there any potential reasons why on some host, ACS would push
/dev/hde instead of /dev/xvde for the 5th drive?
We use 4.4
--
Francois Gaudreault
Gestionnaire de Produit | Product Manager - Cloud Platform & Services
t:514-629-6775 <tel:514-629-6775>
CloudOps Votre partenaire infonuagique | Cloud Solutions Experts
420 rue Guy | Montreal | Quebec | H3J 1S6
w: cloudops.com <http://cloudops.com> | tw: @CloudOps_
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com <mailto:mike.tutkow...@solidfire.com>
o: 303.746.7302
Advancing the way the world uses the cloud
<http://solidfire.com/solution/overview/?video=play>/™/
--
Francois Gaudreault
Gestionnaire de Produit | Product Manager - Cloud Platform & Services
t:514-629-6775
CloudOps Votre partenaire infonuagique | Cloud Solutions Experts
420 rue Guy | Montreal | Quebec | H3J 1S6
w: cloudops.com | tw: @CloudOps_
