Ok, it worked: [QEMU (instance-00000001)]
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 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? Will be much obliged, -Aron On Thu, Aug 4, 2011 at 2:11 AM, Nathanael Burton < nathanael.i.bur...@gmail.com> wrote: > 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 5901, etc... > > /nate > On Aug 3, 2011 7:07 PM, "Mark Gius" <m...@markgius.com> wrote: > > Ugh this was a few months ago and I haven't done much with nova recently. > > IIRC, all you have to do is connect to the :1 vnc on the nova host. So if > > you have VNC and a GUI on your nova host, you can do that from the host > with > > your favorite vncviewer (ubuntu comes with remote desktop viewer) and > > connect to :1. So the string you would type into the remote desktop > viewer > > program would be > > > > localhost:1 > > > > You can do this through ssh port forwarding as well. > > > > Hopefully the above is sensical. > > > > Mark > > > > On Wed, Aug 3, 2011 at 3:32 PM, Aron Matskin <aron.mats...@gmail.com> > wrote: > > > >> Mark, > >> > >> Thanks for the advice - I'll take a look at it tomorrow. Just to save me > >> some time: where is the log or/and how do I display it? > >> > >> -AM > >> > >> > >> On Thu, Aug 4, 2011 at 1:24 AM, Mark Gius <m...@markgius.com> wrote: > >> > >>> 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 nova logs to figure out what VNC address to hit for the instance. > >>> > >>> Mark > >>> > >>> On Wed, Aug 3, 2011 at 4:33 AM, Aron Matskin <aron.mats...@gmail.com > >wrote: > >>> > >>>> Hi all! > >>>> > >>>> Just joined the mailing list. I'd like to do some development on the > >>>> project (probably Nova). Some questions regarding how to start: > >>>> > >>>> Q1. I'm trying to setup Nova in a virtual environment - > >>>> > http://uksysadmin.wordpress.com/2011/02/17/running-openstack-under-virtualbox-a-complete-guide/- > >>>> on a Windows host. I've successfully started an instance and assigned > it a > >>>> network address: > >>>> > >>>> aron@cloud1:~/openstack/cloud/creds$ euca-describe-instances > >>>> RESERVATION r-k6e14a5w myproject default > >>>> INSTANCE i-00000001 ami-0a892947 172.241.0.1 10.0.0.3 running > openstack > >>>> (myproject, cloud1) 0 m1.tiny 2011-08-02T20:28:46Z nova > >>>> > >>>> but I'm unable to connect to the address (neither from the guest nor > from > >>>> the host): > >>>> > >>>> From the guest: > >>>> > >>>> aron@cloud1:~/openstack/cloud/creds$ ping 172.241.0.1 > >>>> PING 172.241.0.1 (172.241.0.1) 56(84) bytes of data. > >>>> From 172.241.0.1 icmp_seq=2 Destination Host Unreachable > >>>> > >>>> aron@cloud1:~/openstack/cloud/creds$ ping 10.0.0.3 > >>>> PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data. > >>>> From 10.0.0.1 icmp_seq=1 Destination Host Unreachable > >>>> > >>>> From the host: > >>>> > >>>> C:\>ping 172.241.0.1 > >>>> > >>>> Pinging 172.241.0.1 with 32 bytes of data: > >>>> Reply from 172.241.0.1: Destination host unreachable. > >>>> > >>>> Pinging the guest from the host and vice versa is ok, e.g.: > >>>> > >>>> C:\>ping 172.241.0.101 > >>>> > >>>> Pinging 172.241.0.101 with 32 bytes of data: > >>>> Reply from 172.241.0.101: bytes=32 time=1ms TTL=64 > >>>> > >>>> What may be wrong? > >>>> > >>>> Q2. When I do succeed to setup the environment, can anybody to point > me > >>>> to documentation on how to write simple code for OpenStack? Something > along > >>>> the lines of "Hello, world!", but using some features peculiar to > cloud > >>>> applications. > >>>> > >>>> Q3. I have no technical knowledge about the cloud at all. Can anybody > >>>> suggest a learning path so that I quickly can gain the basic necessary > >>>> general and specific knowledge to start coding (i.e. first read the > code and > >>>> know what's flying, then fix some bugs, etc.)? > >>>> > >>>> Thanks in advance, -Aron > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> Mailing list: https://launchpad.net/~openstack > >>>> Post to : openstack@lists.launchpad.net > >>>> Unsubscribe : https://launchpad.net/~openstack > >>>> More help : https://help.launchpad.net/ListHelp > >>>> > >>>> > >>> > >> >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp