Ask Your Question

euca-run-instance: instances shutdown after lauching

asked 2011-07-21 04:33:22 -0500

I have installed Nova on Ubuntu 10.10 from ppa:nova-core/release.When launching an instance, I get the instances shutdown:

RESERVATION r-ca0tvrrq proj default INSTANCE i-00000011 ami-00000002 shutdown key01 (proj, ubuntu) 0 m1.medium 2011-07-21T04:21:26Z nova

More information: + nova.conf:

--dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --verbose --s3_host= --rabbit_host= --cc_host= --ec2_url= --fixed_range= --network_size=256 --FAKE_subdomain=ec2 --routing_source_ip= --sql_connection=mysql://root:nova@ --flat_network_dhcp_start= --public_interface=eth0 --flat_interface=eth1 --flat_injected=False --allow_project_net_traffic=true --user_ipv6=False --glance_host= --image_service=nova.image.glance.GlanceImageService --iscsi_ip_prefix=172.16. --libvirt_type=kvm

  • nova-compute.log:

2011-07-21 11:21:29,812 WARNING nova.virt.libvirt_conn [-] instance instance-00000011: ignoring error injecting data into image 2 (Unexpected error while running comman$ Command: sudo tune2fs -c 0 -i 0 /dev/nbd15 Exit code: 1 Stdout: 'tune2fs 1.41.12 (17-May-2010)\n' Stderr: "tune2fs: Invalid argument while trying to open /dev/nbd15\nCouldn't find valid filesystem superblock.\n") 2011-07-21 11:22:00,899 ERROR nova.exception [-] Uncaught exception (nova.exception): TRACE: Traceback (most recent call last): (nova.exception): TRACE: File "/usr/lib/pymodules/python2.6/nova/", line 120, in _wrap (nova.exception): TRACE: return f(args, *kw) (nova.exception): TRACE: File "/usr/lib/pymodules/python2.6/nova/virt/", line 617, in spawn (nova.exception): TRACE: domain = self._create_new_domain(xml) (nova.exception): TRACE: File "/usr/lib/pymodules/python2.6/nova/virt/", line 1079, in _create_new_domain (nova.exception): TRACE: domain.createWithFlags(launch_flags) (nova.exception): TRACE: File "/usr/lib/python2.6/dist-packages/", line 337, in createWithFlags (nova.exception): TRACE: if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self) (nova.exception): TRACE: libvirtError: internal error process exited while connecting to monitor: char device redirected to /dev/pts/1
(nova.exception): TRACE: (nova.exception): TRACE: 2011-07-21 11:22:00,917 ERROR nova.compute.manager [KM1ZJXJXW1TS30LKEIO3 novaadmin proj] Instance '17' failed to spawn. Is virtualization enabled in the BIOS?
(nova.compute.manager): TRACE: Traceback (most recent call last): (nova.compute.manager): TRACE: File "/usr/lib/pymodules/python2.6/nova/compute/", line 234, in run_instance (nova.compute.manager): TRACE: self.driver.spawn(instance_ref) (nova.compute.manager): TRACE: File "/usr/lib/pymodules/python2.6/nova/", line 126, in _wrap
(nova.compute.manager): TRACE: raise Error(str(e)) (nova.compute.manager): TRACE: Error: internal error process exited while connecting to monitor: char device redirected to /dev/pts/1 (nova.compute.manager): TRACE: (nova.compute.manager): TRACE: 2011-07-21 11:22:01,221 INFO nova.compute.manager [-] Found instance 'instance-00000010' in DB but no VM. State=5, so setting state to shutoff. 2011-07-21 11:22:01,221 INFO nova.compute ...


edit retag flag offensive close merge delete

5 answers

Sort by ยป oldest newest most voted

answered 2011-07-22 06:22:56 -0500

novikov gravatar image

I dont really know then. Its neigther a reason nor error, just fact :) (in libvirt.log) Check size of kernel/ramdisk/disk.img files in /var/lib/nova/instances/instance-0000001c/ if you know their real sizes(it`s fine if there is no ramdisk for example, but bad if disk or kernel has zero size or not the same size they should be - a few Mb for kernel and a few Gb for disk, the last dependds on your image). Or just terminate instance and remove _base dir completely(it will recreate). I suppose that if you create(upload&register) another image - will work fine. Smth strange is that(or any) 0 bytes file in _base dir, though it may not concern your image for current instance.

FUI, from first log error I can say that some image(disk.img or other) for VM eigther not fully transfered to nova-compute, or other bug with image-store service. You can just somehow repeat image creation(i.e bundle&upload&register to you storage-service) or if you want try to download you image bundle manualy.

edit flag offensive delete link more

answered 2011-07-21 17:18:12 -0500

novikov gravatar image

Hi just try - go to the node named "ubuntu"(where nova-compute service) and look into /var/lib/nova/instances There must be non empty _base and dir with your instance name - see console.log, if it is empty see /var/log/libvirt/qemu/instance ...your_Instance_Number.log than you`ll find some reason ;) otherwise you may post some errors from there

edit flag offensive delete link more

answered 2011-07-22 03:25:12 -0500

On node named "Ubuntu", I run an instance named "i-0000001c".there are an _base dir that is not empty.

$ sudo ls -ls /var/lib/nova/instances/_base/ total 4308 4308 -rw-r--r-- 1 nova nogroup 4407632 2011-07-22 09:59 00000001 0 -rw-r--r-- 1 libvirt-qemu kvm 0 2011-07-22 09:59 00000002

0 -rw-r--r-- 1 libvirt-qemu kvm 21474836480 2011-07-22 10:01 local_20

the file: /var/lib/nova/instances/instance-0000001c/console.log is empty.And I find some reason into /var/log/libvirt/qemu/instance-0000001c.log :

2011-07-22 10:01:12.062: starting up

LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 2048 -smp 1,sockets=1,cores=1,threads=1 -name instance-0000001c -uuid f720525a-ac8e-8d18-6e39-5757513e47a2 -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-0000001c.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=readline -rtc base=utc -boot c -kernel /var/lib/nova/instances/instance-0000001c/kernel -append root=/dev/vda console=ttyS0 -drive file=/var/lib/nova/instances/instance-0000001c/disk,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 -drive file=/var/lib/nova/instances/instance-0000001c/disk.local,if=none,id=drive-virtio-disk1,format=qcow2 -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1 -device rtl8139,vlan=0,id=net0,mac=02:16:3e:7b:49:c0,bus=pci.0,addr=0x3 -net tap,fd=18,vlan=0,name=hostnet0 -chardev file,id=charserial0,path=/var/lib/nova/instances/instance-0000001c/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -usb -vnc -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6

char device redirected to /dev/pts/4

2011-07-22 10:01:42.275: shutting down

edit flag offensive delete link more

answered 2011-07-28 05:05:40 -0500

I have tried again with ttylinux in link : ( . And The instance is the running state . Then I tried with ubuntu 10.10 server i 386 on link : ( with instance type m1.tiny ,It 's running . But I always fail when working with other types.And Have the same above error in the nova-compute.log What 's the problem in here ? Thanks for any help .

edit flag offensive delete link more

answered 2011-07-28 07:07:00 -0500

I have solved the problem because my physical machine is not enough resources. I created a new intances type and all is ok. Thanks!

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

1 follower


Asked: 2011-07-21 04:33:22 -0500

Seen: 40 times

Last updated: Jul 28 '11