Ask Your Question
0

nova instance fails with libvirtError: internal error Process exited while reading console log output

asked 2013-07-03 04:32:21 -0500

updated 2013-07-05 10:57:40 -0500

Installation Details: DevStack installed on ubuntu 12.10 64bit with KVM as hypervisor. I was able to create the instances. Once I have restarted the instance, I am not able to login to the dashboard and create instances. Apache is failing with some permission error, but i can submit the requests with nova-client. But the request fails with following error.

ERROR nova.scheduler.filter_scheduler [req-3927ad08-f236-4e84-960e-a592c68174c5 admin admin] [instance: 6c24819d-9be0-4c7d-b5fc-61d075f10429] Error from last host: swapnil-ThinkCentre-A58 (node swapnil-ThinkCentre-A58): [u'Traceback (most recent call last):\n', u' File "/opt/stack/nova/nova/compute/manager.py", line 995, in _build_instance\n set_access_ip=set_access_ip)\n', u' File "/opt/stack/nova/nova/compute/manager.py", line 1249, in _spawn\n LOG.exception(_(\'Instance failed to spawn\'), instance=instance)\n', u' File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__\n self.gen.next()\n', u' File "/opt/stack/nova/nova/compute/manager.py", line 1245, in _spawn\n block_device_info)\n', u' File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 1596, in spawn\n block_device_info)\n', u' File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 2569, in _create_domain_and_network\n domain = self._create_domain(xml, instance=instance, power_on=power_on)\n', u' File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 2524, in _create_domain\n domain.XMLDesc(0))\n', u' File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__\n self.gen.next()\n', u' File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 2519, in _create_domain\n domain.createWithFlags(launch_flags)\n', u' File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 187, in doit\n result = proxy_call(self._autowrap, f, args, kwargs)\n', u' File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 147, in proxy_call\n rv = execute(f,args,kwargs)\n', u' File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 76, in tworker\n rv = meth(args,*kwargs)\n', u' File "/usr/lib/python2.7/dist-packages/libvirt.py", line 650, in createWithFlags\n if ret == -1: raise libvirtError (\'virDomainCreateWithFlags() failed\', dom=self)\n', u'libvirtError: internal error Process exited while reading console log output: Warning: option deprecated, use lost_tick_policy property of kvm-pit instead.\nchardev: opening backend "file" failed\n\n']

**Error : libvirtError: internal error Process exited while reading console log output: Warning: option deprecated, use lost_tick_policy property of kvm-pit instead.\nchardev: opening backend "file**
edit retag flag offensive close merge delete

Comments

please add more details about your installation. It's almost impossible to help you with only an error log.

smaffulli gravatar imagesmaffulli ( 2013-07-05 08:04:28 -0500 )edit

smaffulli : I think its mostly some KVM update issue, I read some blog posts related to it, but could not get the clear idea.

coolsvap gravatar imagecoolsvap ( 2013-07-05 11:29:24 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
1

answered 2014-05-29 07:04:07 -0500

Avi Zohary gravatar image

Here is some more information about my installation:

Using Openstack Havana (glance, keystone, horizon, nova, heat and ceilometer), split between controller and compute node. The controller node doesn't have the nova-compute service enabled, so all instances are created on the compute node.

Regarding the images - I have a few images, all in qcow2 format (created them in virtual box). All but two of them seem to be working fine - I can create instances from them, and the other two, basically the same image, are the ones I'm having problems with.

The image contents in all cases is Oracle Linux (Basically RHEL), with a Weblogic application installed on them. The images that are working are those without cloud-init on them, and the ones that don't are the ones without.

BTW, here is a the instance log that was created in the /var/log/libvirt/qemu/instance-...log :

2014-05-29 11:46:32.956+0000: starting up
LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name instance-000000e7 -S -M rhel6.5.0 -cpu SandyBridge,+pdpe1gb,+osxsave,+dca,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme -enable-kvm -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid a487b3e2-4ae2-47e1-b596-0e919b049399 -smbios type=1,manufacturer=Red Hat Inc.,product=OpenStack Nova,version=2013.2.3-1.el6,serial=e00d6db6-0010-ffff-ffff-ffffff200008,uuid=a487b3e2-4ae2-47e1-b596-0e919b049399 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-000000e7.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/home/nova/instances/a487b3e2-4ae2-47e1-b596-0e919b049399/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=32 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:c1:53:56,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/home/nova/instances/a487b3e2-4ae2-47e1-b596-0e919b049399/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:5 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
char device redirected to /dev/pts/8
qemu-kvm: -drive file=/home/nova/instances/a487b3e2-4ae2-47e1-b596-0e919b049399/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none: could not open disk image /home/nova/instances/a487b3e2-4ae2-47e1-b596-0e919b049399/disk: Operation not supported
2014-05-29 11:46:33.338+0000: shutting down

And this is what I see in /var/log/libvirt/libvirtd.log:

2014-05-29 11:46:33.338+0000: 2730: error : qemuMonitorIORead:514 : Unable to read from monitor: Connection reset by peer
2014-05-29 11:46:33.338+0000: 2734: error : virNWFilterDHCPSnoopEnd:2131 : internal error ifname "vnet5" not in key map
2014-05-29 11:46:33.356+0000: 2734: error : virNetDevGetIndex:653 : Unable to get index for interface vnet5: No such device
edit flag offensive delete link more

Comments

Have you solved the issue ? I'm coming across the same problem with you..

moiyer gravatar imagemoiyer ( 2014-10-23 00:53:01 -0500 )edit

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

Stats

Asked: 2013-07-03 04:32:21 -0500

Seen: 3,315 times

Last updated: May 29 '14