cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Godard (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-8826) XenServer - Use device id passed as part of attach volume API properly
Date Wed, 20 Apr 2016 18:32:25 GMT


Simon Godard commented on CLOUDSTACK-8826:

This bug fix looks like it broke a simple HVM VM start when more than 2 volumes are attached.
Using 'autodetect' as the device Id is also rejected by XenServer when using HVM.

I tested with a PV VM and it seems to work fine.

> XenServer - Use device id passed as part of attach volume API properly
> ----------------------------------------------------------------------
>                 Key: CLOUDSTACK-8826
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: XenServer
>    Affects Versions: 4.6.0
>            Reporter: Koushik Das
>            Assignee: Koushik Das
>             Fix For: 4.6.0
> Random failures were seen in XS attach/detach volume test scenarios (many attach/detach
were performed on the same VM over a span of 24 hrs).
> The failures happened as the device id for attaching volume wasn't available in HV. Some
detached volume didn't got cleaned up properly and so the device id wasn't released.
> The fix would be clean up stale volumes before attaching new ones so the device slots
are released. Also using the device id should be best effort and if that particular id is
not available in XS, it should fallback on using an id that is available and automatically

This message was sent by Atlassian JIRA

View raw message