OpenStack Compute (nova)

Disk prefix in libvirt template

Asked by Alvaro Lopez

Hi there.

I've noticed that the "disk_prefix" variable has been removed from the "nova/virt/libvirt.xml.template" file in commit 2c1b9ac (https://github.com/openstack/nova/commit/2c1b9ac98673c0ef1ae931c6b9d84e4b0741eed9) and now it is hardcoded on the
"nova/virt/libvirt/connection.py".

In our case we are using Xen as the hypervisor, and this is making some of our cloud servers fail since they're are looking for "/dev/xvdX" instead of the coded "/dev/sdX" (this is happening for example with the SUSEStudio appliances) .

Shouldn't this value be configurable in the template again?

Question information

Language:
English Edit question
Status:
Answered
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Vish Ishaya (vishvananda) said : 		#1

Yes, it looks like this should be templated.

On Oct 31, 2011, at 5:01 AM, Alvaro wrote:

> New question #176978 on OpenStack Compute (nova):
> https://answers.launchpad.net/nova/+question/176978
>
> Hi there.
>
> I've noticed that the "disk_prefix" variable has been removed from the "nova/virt/libvirt.xml.template" file in commit 2c1b9ac (https://github.com/openstack/nova/commit/2c1b9ac98673c0ef1ae931c6b9d84e4b0741eed9) and now it is hardcoded on the
> "nova/virt/libvirt/connection.py".
>
> In our case we are using Xen as the hypervisor, and this is making some of our cloud servers fail since they're are looking for "/dev/xvdX" instead of the coded "/dev/sdX" (this is happening for example with the SUSEStudio appliances) .
>
> Shouldn't this value be configurable in the template again?
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

Can you help with this problem?

Provide an answer of your own, or ask Alvaro Lopez for more information if necessary.

To post a message you must log in.