Perhaps Tim Mackey would know (I've CCed him here).
On Tue, Apr 7, 2015 at 8:51 PM, Francois Gaudreault <
fgaudrea...@cloudops.com> wrote:
> 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
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
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;
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 P
