On 08/20/2011 01:52 AM, Joshua Harlow wrote:
> For my nova/virt/libvirt.xml.template on my compute node.
>
> The following is being done.
>
> #if $type == 'xen'
> #set $disk_prefix = 'sd'
> #set $disk_bus = 'scsi'
> linux
> /dev/xvda
>
> Should that be /
On 08/20/2011 01:26 AM, Joshua Harlow wrote:
> 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 t
On 08/20/2011 05:40 AM, Joshua Harlow wrote:
> So what I’ve figured out is the following seems to work with xen4.
The naming of sda vs xvda has nothing to do with the hypervisor, and a
lot to do with your kernel.
Thomas
___
Mailing list: https://launc
Hi,
I followed these instructions to get Openstack/Nova running under VirtualBox:
http://cloudbuilders.github.com/deploy.sh/single-node-nova-installation-using-vagrant-and-chef.html
Now everything is going fine, including running a compute instance with
"euca-run-instances" and connecting to i
The dashboard does not currently detect whether or not a swift endpoint is
present, and instead relies on the boolean setting SWIFT_ENABLED. I would
guess that whatever "all in one" script you are using is deploying an older
version of the local settings file.
You can resolve this error by adding
5 matches
Mail list logo
