← Back to team overview

openstack team mailing list archive

Re: strange problem when reboot nova-compute node: domain not found: no domain with matching name

 

Hi Razique,

 

Is there anything need to have a deeper look?

Virsh list looks like well,same as the instance I created through nova boot.

 

Romi

 

From: Razique Mahroua [mailto:razique.mahroua@xxxxxxxxx] 
Sent: Friday, September 14, 2012 4:10 AM
To: Ritesh Nanda
Cc: romi zhang; openstack@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack] strange problem when reboot nova-compute node:
domain not found: no domain with matching name

 

Hi Romi, 

what $ virsh list --all gives you ?

Nuage & Co - Razique Mahroua 

razique.mahroua@xxxxxxxxx




 

Le 13 sept. 2012 à 21:11, Ritesh Nanda <riteshnanda09@xxxxxxxxx> a écrit :





Hello romi,

    Image got into a stuck state , only solution is to hack your database
for this particular instance and mark it as deleted, den restart nova-*
service, it would start working.

On Thu, Sep 13, 2012 at 9:45 PM, romi zhang <romizhang1968@xxxxxxx> wrote:

Hi,

 

I’ve installed essex and when I reboot one of the nova-compute node and next
when I start nova-compute service again,the system promote:

Libvirt: QEMU error: Domain not found: no domain with matching name
‘instance-0000000a’

 

Then I found:  

#ls /var/lib/nova/instances

_base instance-0000000a instance-0000000b instance-0000000c

#ls /etc/libvirt/qemu

instance-0000000b.xml instance-0000000c.xml Network

 

So:

/var/lib/nova/instances/instance-0000000a# virsh define libvirt.xml

Domain instance-0000000a defined from libvirt.xml

And:

#ls /etc/libvirt/qemu

Instance-0000000a.xml instance-0000000b.xml instance-0000000c.xml network

 

Then I restart: nova-compute &, and nova-compute could normally started.

I did not understand why reboot compute node,and usually the first
instance’s xml file was deleted and nova-compute will terminate.

 

By the way, when I create a new instance, the first line in the log also is
: Libvirt: QEMU error: Domain not found: no domain with matching name
‘instance-0000000a’

 

Anyone who had met such a problem and why?

 

Regards,

 

romi


_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp




-- 

 With Regards  

 Ritesh Nanda

 

 


_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

 

JPEG image


Follow ups

References