Why not hehe, though I must admit it's easier, yes you can have a simpler template :)just copy a libvirt.xml and update the instance name.You could even come up with a small bash script./recover.sh $instance-name that would perform the following steps :• Retrieve the instance name and put it into t
anytime this happend with me I do the following.
create a lost_instance.xml with the content below(I think it's possible to
create a simpler file, with less content) just to register a VM with
libvirt. Make sure to change the tag. In your case
instance-002a
4194304
4194304
4
I think the instance ID is the database ID (base 8) encoded in base 16. 0x2A = ID 52 into the database.Did you updated the ID 52 ?I may be wrong ^^
Razique Mahroua - Nuage & Corazique.mahr...@gmail.comTel : +33 9 72 37 94 15
Le 13 déc. 2012 à 11:51, Joe Warren-Meeks a
It turned out to be that last one. What I don't understand is where
openstack found the instance id from. That doesn't exist in the database,
or anywhere on the file system I could find.
Kind regards
-- joe.
On 13 December 2012 10:27, Razique Mahroua wrote:
> Hey Joe,
> yes, several solutions
Hey Joe, yes, several solutions thereFirst, check if the domain exists by running$ virsh list --all (supposing you use libvirt)check /var/lib/nova/instances/instance-002aif the dir. exists $cd into it and run "virsh define libvirt.xml"then restart nova-computeIf the dir. doesn't exist, you may
Hi guys,
You think you have Openstack working, then you cough and it all breaks.
I'm getting the following error when trying to start nova-compute after a
reboot of the compute node (to install non-related patches)
libvirtError: Domain not found: no domain with matching name
'instance-002a'
6 matches
Mail list logo