Ask Your Question
0

Instances drop immediately (Essex)

asked 2013-05-28 15:07:08 -0500

dmacvittie gravatar image

updated 2013-05-29 18:04:35 -0500

smaffulli gravatar image

Hi all,

I've done a single-instance install as detailed here: http://www.tikalk.com/alm/expreimenting-openstack-essex-ubuntu-1204-lts-under-virtualbox

Using VirtualBox and Essex. I have worked through several issues and gotten down to one I can't readily resolve with my current knowledge, hoping for help.

The instances drop immediately on boot. I can see them for a couple of seconds in VNC (If I'm fast opening it), but then they disappear. They show up in nova list, but not in glance list. The only actual error is in libvirt.log and shows:

 2013-05-28 19:49:08.232+0000: 1793: error : qemuMonitorIO:603 : internal error End of file from monitor

Everything else looks like it ran fine.

Since I can get a VNC window up, even briefly, I'm assuming it is not a networking issue, leaving me with a need for ideas where to look next. I've seen other questions, but no answers around the net on this same topic.

I also tried some different approaches - devstack, switching this install to use folsom or grizzly, but this install I have a bit of time invested in and some knowledge of the detailed config, so trying to get it running, since each had its own issues.

I'm launching a tiny image, memory is set at 4 gig and about 30% used, disk and 20 gig and about 35% used. All services are running, logs only mention the qemuMonitorIO error . Thanks for any help, and apologies if this has been answered, I sure can't find it out there if it has.

Don.

edit retag flag offensive close merge delete

Comments

There are a couple of questions for something like this already - try a search for 'qemuMonitorIO' on the box at the top of the page.

darragh-oreilly gravatar imagedarragh-oreilly ( 2013-05-28 16:07:58 -0500 )edit

This is likely to be caused by a lack of disks space or ram. Check your systems and update the question with more details if disk space is not an issue.

smaffulli gravatar imagesmaffulli ( 2013-05-28 16:31:47 -0500 )edit

I'm launching a tiny image, memory is set at 4 gig and about 30% used, disk and 20 gig and about 35% used. There is no more information that I know of to offer - all services are running, logs only mention the qemuMonitorIO error. tomorrow I'll paw through the code and see what I can find.

dmacvittie gravatar imagedmacvittie ( 2013-05-28 23:46:26 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
1

answered 2013-05-30 03:24:39 -0500

darragh-oreilly gravatar image

I had a quick look at guide. So the image you are trying to boot is an Ubuntu 11.10 i386? This is a monster to run on QEMU (full software) inside VirtualBox. Try the cirros test cloud image instead http://docs.openstack.org/trunk/openstack-compute/admin/content/booting-a-test-image.html

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

2 followers

Stats

Asked: 2013-05-28 15:07:08 -0500

Seen: 341 times

Last updated: May 29 '13