openstack team mailing list archive

[Joshua Harlow <harlowja@xxxxxxxxxxxxx>]

Ok but I am going through libvirt instead of xenapi since I am just using a debian + xen-hypervisor package.

Also going through libvirt seems to be better, since it doesn't make your setup as "strongly" connected to xen.

For those using the following in debian/ubunbu would the usage of the xenapi still work?

ii  libxenstore3.0                       4.0.1-2                           Xenstore communications library for Xen
ii  linux-image-2.6.32-5-xen-amd64       2.6.32-35                         Linux 2.6.32 for 64-bit PCs, Xen dom0 support
ii  xen-hypervisor-4.0-amd64             4.0.1-2                           The Xen Hypervisor on AMD64
ii  xen-qemu-dm-4.0                      4.0.1-2                           Xen Qemu Device Model virtual machine hardware emulator
ii  xen-utils-4.0                        4.0.1-2                           XEN administrative tools
ii  xen-utils-common                     4.0.0-1                           XEN administrative tools - common files
ii  xenstore-utils                       4.0.1-2                           Xenstore utilities for Xen

Since I thought xenserver was a separate product?

On 8/19/11 9:55 AM, "Wayne A. Walls" <wayne@xxxxxxxxxxxxx> wrote:

It looks like it was maverick, you can find a lot of good info here on xen,if you're not using this already:
http://wiki.openstack.org/XenServerDevelopment

I believe the work around Vish is referring to is made in nova.conf:
--xenapi_remap_vbd_dev=true

Give that a go, hopefully gets you on your way!

Cheers,

Wayne

Sent from my iPad

On Aug 19, 2011, at 11:41, Vishvananda Ishaya <vishvananda@xxxxxxxxx> wrote:

> There was an issue on one version of ubuntu (I think it was natty?), where xen was using /dev/sd* instead of /dev/xd*.  I remember discussion on the mailing list or a bug about having to have a specific workaround.
>
> On Aug 19, 2011, at 1:42 AM, Thomas Goirand wrote:
>
>> On 08/19/2011 01:31 PM, Isaku Yamahata wrote:
>>> It looks you specified "root=/dev/xvda", but the disk that is
>>> instantiated is /dev/sda.
>>> But I didn't see why it happened. Did you customized the template
>>> for libvirt, libvirt.xml.template?
>>
>> This seems wrong then, because under Xen, you should use xvda, not sda
>> anymore.
>>
>> Thomas
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp