Ask Your Question
0

kvm binary is deprecated

asked 2013-11-27 04:48:34 -0600

Deeptanshu gravatar image

Hi , I am getting the below error while launching the instance.Please suggest the solution.

======================================================================================= internal error: process exited while connecting to monitor: W: kvm binary is deprecated, please use qemu-system-x86_64 instead\nWarning: option deprecated, use lost_tick_policy property of kvm-pit instead.\nchar device redirected to /dev/pts/5 (label charserial1)\nqemu: at most 2047 MB RAM can be simulated\n\n'] 2013-11-27 14:46:54.815 29559 WARNING nova.scheduler.driver [req-5b8cea98-571e-4814-a17e-2bc15090a745 bdaa2a55a568464db722ea91d755bb63 fc7b1f2eeccf456d9d05e63c84746b5f] [instance: 908a83f0-f060-4ff2-9d1b-a017cbd1ad85] Setting instance to ERROR state.

edit retag flag offensive close merge delete
add a comment

2 answers

Sort by ยป oldest newest most voted
0

answered 2013-11-27 05:27:35 -0600

Deeptanshu gravatar image

Hi, After changing to qemu i am getting the different error.Please check the logs and suggest.

=============================================================== /var/log/libvirt/libvirtd.log

2013-11-27 11:21:48.616+0000: 24874: warning : virAuditSend:135 : Failed to send audit message virt=qemu vm="instance-00000013" uuid=7ef609a4-2c31-4398-97be-4532c3a76b91 vm-ctx=108:115 img-ctx=108:115 model=dac: Operation not permitted 2013-11-27 11:21:48.661+0000: 24874: warning : virAuditSend:135 : Failed to send audit message virt=qemu resrc=net reason=open vm="instance-00000013" uuid=7ef609a4-2c31-4398-97be-4532c3a76b91 net=fa:16:3e:f4:85:04 path="/dev/net/tun" rdev=0A:C8: Operation not permitted 2013-11-27 11:21:48.917+0000: 24874: warning : virAuditSend:135 : Failed to send audit message virt=qemu resrc=cgroup reason=deny vm="instance-00000013" uuid=7ef609a4-2c31-4398-97be-4532c3a76b91 cgroup="/sys/fs/cgroup/devices/machine/instance-00000013.libvirt-qemu/" class=all: Operation not permitted 2013-11-27 11:21:48.917+0000: 24874: warning : virAuditSend:135 : Failed to send audit message virt=qemu resrc=cgroup reason=allow vm="instance-00000013" uuid=7ef609a4-2c31-4398-97be-4532c3a76b91 cgroup="/sys/fs/cgroup/devices/machine/instance-00000013.libvirt-qemu/" class=path path="/var/lib/nova/instances/7ef609a4-2c31-4398-97be-4532c3a76b91/disk" rdev=? acl=rw: Operation not permitted 2013-11-27 11:21:48.918+0000: 24874: warning : virAuditSend:135 : Failed to send audit message virt=qemu resrc=cgroup reason=allow vm="instance-00000013" uuid=7ef609a4-2c31-4398-97be-4532c3a76b91 cgroup="/sys/fs/cgroup/devices/machine/instance-00000013.libvirt-qemu/" class=path path="/var/lib/nova/instances/_base/8f3bf93625ad21c8ae95bfe03ea21b3289b51f62" rdev=? acl=rw: Operation not permitted 2013-11-27 11:21:48.918+0000: 24874: warning : virAuditSend:135 : Failed to send audit message virt=qemu resrc=cgroup reason=allow vm="instance-00000013" uuid=7ef609a4-2c31-4398-97be-4532c3a76b91 cgroup="/sys/fs/cgroup/devices/machine/instance-00000013.libvirt-qemu/" class=major category=pty maj=88 acl=rw: Operation not permitted 2013-11-27 11:21:49.119+0000: 24874: error : qemuMonitorOpenUnix:296 : failed to connect to monitor socket: No such process 2013-11-27 11:21:49.119+0000: 24874: error : qemuProcessWaitForMonitor:1809 : internal error: process exited while connecting to monitor: char device redirected to /dev/pts/5 (label charserial1) qemu: at most 2047 MB RAM can be simulated

2013-11-27 11:21:49.565+0000: 24874: warning : virAuditSend:135 : Failed to send audit message virt=qemu resrc=disk reason=start vm="instance-00000013" uuid=7ef609a4-2c31-4398-97be-4532c3a76b91 old-disk="?" new-disk="/var/lib/nova/instances/7ef609a4-2c31-4398-97be-4532c3a76b91/disk": Operation not permitted 2013-11-27 11:21:49.566+0000: 24874: warning : virAuditSend:135 : Failed to send audit message virt=qemu resrc=net reason=start vm="instance-00000013" uuid=7ef609a4-2c31-4398-97be-4532c3a76b91 old-net=? new-net=fa:16:3e:f4:85:04: Operation not permitted 2013-11-27 11:21:49.566+0000: 24874: warning : virAuditSend:135 : Failed to send audit message virt=qemu resrc=mem reason=start vm="instance-00000013" uuid=7ef609a4-2c31-4398-97be-4532c3a76b91 old-mem=0 new-mem=2097152: Operation not permitted 2013-11-27 11:21:49.566+0000: 24874: warning : virAuditSend:135 : Failed to send audit message virt=qemu resrc=vcpu reason=start vm="instance-00000013" uuid=7ef609a4-2c31-4398-97be-4532c3a76b91 old-vcpu=0 new-vcpu=1: Operation not permitted 2013-11-27 11:21:49.566+0000: 24874: warning : virAuditSend:135 : Failed to send audit message virt=qemu op=start reason=booted vm="instance-00000013" uuid=7ef609a4-2c31-4398-97be-4532c3a76b91 vm-pid=-1: Operation not permitted

================================================================================= /var/log/nova/nova-compute.log ... (more)

edit flag offensive delete link more

Comments

I will look at them. It is good put the logs in pastebin.com or you can send the logs directly to me. If you want you can send the logs to dheerendra.madhusudhana@gmail.com

dheeru gravatar imagedheeru ( 2013-11-27 05:31:14 -0600 )edit
add a comment
0

answered 2013-11-27 05:00:46 -0600

dheeru gravatar image 
It may help to change /etc/nova/nova-compute.conf on compute with libvirt_type=qemu. 
Refer the following link to troubleshoot more. 
http://virtual2privatecloud.com/2013/11/openstack-nova-instance-creation-fails-troubleshoot/

Look at few logs like 
/var/log/nova/nova-compute.log
/var/log/libvirt/libvirtd.log

If you need further help do let me know.
edit flag offensive delete link more

Comments

Hi dheeru, Please check the above details,

Deeptanshu gravatar imageDeeptanshu ( 2013-11-27 05:28:35 -0600 )edit

Are you trying with dashboard or command line ? Can you try to launch with command line as root or sudo user ?

dheeru gravatar imagedheeru ( 2013-11-27 06:09:57 -0600 )edit

Hi, I have tried from both the methods i.e from horizon and command line. Instance created from default "cirrOS" is working fine. Instance created from any other image is throwing the error as i had updated earlier. Please suggest any clue...

Deeptanshu gravatar imageDeeptanshu ( 2013-11-27 06:59:11 -0600 )edit

which images you are using ? From where did you download them ? ping me on my google chat. We can quickly close this. I'm available for another 30 mins.

dheeru gravatar imagedheeru ( 2013-11-27 07:26:04 -0600 )edit
add a comment

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

subscribe to rss feed

Stats

Asked: 2013-11-27 04:48:34 -0600

Seen: 2,258 times

Last updated: Nov 27 '13

Related questions

is it possible present physical HW to (kvm) guest?

kvm convert to ESX

Downtime of any instance during live-migration

vhost_net panics under heavy load

why poor network throughput with virtio on Kilo

Can't ping or ssh a VM

Receive control failed (result -32)

Slow Instance Snapshot

openstack with kvm and venom concerns

Networking in a multi-hypervisor cloud