Ok, it worked:
[QEMU (instance-0001)]
Starting SeaBIOS...
This kernel requires an x86-64 CPU, but only detected an i686 CPU.
Unable to boot - please use a kernel appropriate to your CPU.
---
It seems to me that it refers to my Ubuntu installation on the guest, I've
used
2011/8/4 Aron Matskin aron.mats...@gmail.com:
It seems to me that it refers to my Ubuntu installation on the guest, I've
used ubuntu-10.10-desktop-i386.iso , I probably should have
used ubuntu-10.10-desktop-amd64.iso . Can anybody confirm this before I
spend half a day on re-installation?
You
: [Openstack] some newbie questions
2011/8/4 Aron Matskin aron.mats...@gmail.com:
It seems to me that it refers to my Ubuntu installation on the guest,
I've
used ubuntu-10.10-desktop-i386.iso , I probably should have
used ubuntu-10.10-desktop-amd64.iso . Can anybody confirm this before
I
I'm not an Openstack expert, but this might help you:
A1. What's your network config? Whitout any useful information it's very
difficult helping you. It would be useful both ifconfig and nova-manage
network output, virsh output would help too.
A2. You can start looking at
A1: When I had the symptoms you are describing it was because the instance
never managed to boot from the image, and was just spinning cpu cycles
displaying a could not boot disk type message. I figured that out by
connecting to the VNC console of the instance. IIRC, you can look through
the
Actually the VNC display number varies based on how many instances may be
running on the node. Login to the box and run virsh list to list the
instances and get the domain id of the one in question. Then run virsh
vncdisplay id and it will output the VNC display number. :0 means 5900,
:1 means
Sending back to Openstack list since other people might help you better
than me, anyway:
Can you post result from:
$ virsh net-dumpxml default
I'm not sure about this, but It seems host is trying wrong bridge when
connecting your vms, I had similar problem installing from source, since
I
7 matches
Mail list logo
