Ask Your Question
0

libvirtError: invalid argument: monitor must not be NULL

asked 2015-05-15 22:43:45 -0500

senwang921 gravatar image

updated 2015-05-17 14:22:42 -0500

dbaxps gravatar image

I follow the installation guide of juno. When I try to start a instance with command "nova boot --flavor m1.tiny --image cirros-0.3.3-x86_64 --nic net- id=DEMO_NET_ID --security-group default --key-name demo-key demo-instance1", I got the following log in the nova-compute.log at the compute node.

==> /var/log/nova/nova-compute.log <==

2015-05-16 10:17:16.309 16637 AUDIT nova.compute.manager [req-6b84f658-0c14-4a3f-ab1e-4dde6912c8e1 None] [instance: e38ec443-d11c-4aa7-8bfe-53083c25d761] Starting instance...
2015-05-16 10:17:16.377 16637 AUDIT nova.compute.claims [-] [instance: e38ec443-d11c-4aa7-8bfe-53083c25d761] Attempting claim: memory 512 MB, disk 1 GB
2015-05-16 10:17:16.378 16637 AUDIT nova.compute.claims [-] [instance: e38ec443-d11c-4aa7-8bfe-53083c25d761] Total memory: 2375 MB, used: 1536.00 MB
2015-05-16 10:17:16.378 16637 AUDIT nova.compute.claims [-] [instance: e38ec443-d11c-4aa7-8bfe-53083c25d761] memory limit: 3562.50 MB, free: 2026.50 MB
2015-05-16 10:17:16.378 16637 AUDIT nova.compute.claims [-] [instance: e38ec443-d11c-4aa7-8bfe-53083c25d761] Total disk: 18 GB, used: 2.00 GB
2015-05-16 10:17:16.379 16637 AUDIT nova.compute.claims [-] [instance: e38ec443-d11c-4aa7-8bfe-53083c25d761] disk limit not specified, defaulting to unlimited
2015-05-16 10:17:16.395 16637 AUDIT nova.compute.claims [-] [instance: e38ec443-d11c-4aa7-8bfe-53083c25d761] Claim successful
2015-05-16 10:17:16.489 16637 INFO nova.scheduler.client.report [-] Compute_service record updated for ('compute1', 'compute1')
2015-05-16 10:17:16.557 16637 INFO nova.scheduler.client.report [-] Compute_service record updated for ('compute1', 'compute1')
2015-05-16 10:17:16.718 16637 INFO nova.virt.libvirt.driver [-] [instance: e38ec443-d11c-4aa7-8bfe-53083c25d761] Creating image
2015-05-16 10:17:16.984 16637 INFO nova.scheduler.client.report [-] Compute_service record updated for ('compute1', 'compute1')
2015-05-16 10:17:17.246 16637 INFO nova.virt.disk.vfs.api [-] Unable to import guestfsfalling back to VFSLocalFS
2015-05-16 10:17:19.202 16637 INFO nova.compute.manager [-] [instance: e38ec443-d11c-4aa7-8bfe-53083c25d761] VM Stopped (Lifecycle Event)
2015-05-16 10:17:19.203 16637 ERROR nova.virt.libvirt.driver [-] Error launching a defined domain with XML: <domain type='kvm'>
  <name>instance-00000015</name>
  <uuid>e38ec443-d11c-4aa7-8bfe-53083c25d761</uuid>
  <metadata>
    <nova:instance xmlns:nova="http://openstack.org/xmlns/libvirt/nova/1.0">
      <nova:package version="2014.2.2"/>
      <nova:name>demo-instance1</nova:name>
      <nova:creationTime>2015-05-16 02:17:17</nova:creationTime>
      <nova:flavor name="m1.tiny">
        <nova:memory>512</nova:memory>
        <nova:disk>1</nova:disk>
        <nova:swap>0</nova:swap>
        <nova:ephemeral>0</nova:ephemeral>
        <nova:vcpus>1</nova:vcpus>
      </nova:flavor>
      <nova:owner>
        <nova:user uuid="68b21ab0067a42c0a953c3ae6340b6ec">demo</nova:user>
        <nova:project uuid="4a0bdfa5d2604d1cb6b707acbbd1f371">demo</nova:project>
      </nova:owner>
      <nova:root type="image" uuid="1e662bd3-d647-4bd6-a588-7945956e7069"/>
    </nova:instance>
  </metadata>
  <memory unit='KiB'>524288</memory>
  <currentMemory unit='KiB'>524288</currentMemory>
  <vcpu placement='static' cpuset='0-1'>1</vcpu>
  <sysinfo type='smbios'>
    <system>
      <entry name='manufacturer'>OpenStack Foundation</entry>
      <entry name='product'>OpenStack Nova</entry>
      <entry name='version'>2014.2.2</entry>
      <entry name='serial'>564d2ad8-865e-1f42-ba3d-6f33478a95ba</entry>
      <entry name='uuid'>e38ec443-d11c-4aa7-8bfe-53083c25d761</entry>
    </system>
  </sysinfo>
  <os>
    <type arch='x86_64' machine='pc-i440fx-trusty'>hvm</type>
    <boot dev='hd'/>
    <smbios mode='sysinfo'/>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-model'>
    <model fallback='allow'/>
    <topology sockets='1' cores='1' threads='1'/>
  </cpu>
  <clock offset='utc'>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer ...
(more)
edit retag flag offensive close merge delete

Comments

I hit the same problem as this one too, but can't find any clue about it.. anyone can give suggstion please?

Steven Li gravatar imageSteven Li ( 2015-11-05 00:51:02 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2015-11-06 19:03:27 -0500

I accessed this page more than 10 tiems, but never got a solution, and now I think I can give a suggestion:

 2015-11-06 15:24:28.844 3411 TRACE nova.compute.manager [instance: 94cf1f3d-b3bc-4fdc-9462-5fa3cd1335b0]   File "/usr/lib/python2.7/dist-packages/libvirt.py", line 896, in createWithFlags
2015-11-06 15:24:28.844 3411 TRACE nova.compute.manager [instance: 94cf1f3d-b3bc-4fdc-9462-5fa3cd1335b0]     if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self)
2015-11-06 15:24:28.844 3411 TRACE nova.compute.manager [instance: 94cf1f3d-b3bc-4fdc-9462-5fa3cd1335b0] libvirtError: invalid argument: monitor must not be NULL
2015-11-06 15:24:28.844 3411 TRACE nova.compute.manager [instance: 94cf1f3d-b3bc-4fdc-9462-5fa3cd1335b0]
2015-11-06 15:24:28.857 3411 INFO nova.compute.manager [req-b528e702-7262-4829-acbd-256da135fdcd 83d0855ae5c24b9f8cb1a14ea2b079ec ba4b954a23b040e4bcf7777d260164d4 - - -] [instance: 94cf1f3d-b3bc-4fdc-9462-5fa3cd1335b0] Terminating instance

The error sometimes like "libvirtError: Unable to read from monitor: Connection reset by peer", but they are calling the same issue I think.

I was thinking this is a VNC issue which means I configured a wrong VNC ip or something, but after I set "vnc_enable=False", the problem is still...

Then I traced back to /usr/lib/python2.7/dist-packages/libvirt.py, virDomainCreateWithFlags method is pointed to /usr/lib/libvirt/connection-driver/*, so it could be something wrong with this driver...

Finally I updated libvirt-bin libvirt0 and libxen-4.4, then upgrade nova-compute, all is done!

It's really crazy troubleshooting for openstack :-(

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: 2015-05-15 22:43:45 -0500

Seen: 667 times

Last updated: Nov 06 '15