Check if you have any space in the instances dir in the filesystem. I've seen this happen when the drive gets full and libvirt gets an io error trying to write to disk so it shuts off the vms.
Vish On Dec 5, 2012, at 6:59 PM, pyw <[email protected]> wrote: > My virtual machine created, often in the absence of intervention into the > stopped state: > > pyw@ven-1:~/devstack$ virsh list --all > Id Name State > ---------------------------------- > - instance-00000040 shut off > - instance-00000044 shut off > - instance-00000045 shut off > - instance-00000046 shut off > - instance-00000047 shut off > - instance-0000005b shut off > - instance-0000005e shut off > - instance-00000065 shut off > - instance-0000006e shut off > - instance-00000075 shut off > - instance-00000076 shut off > - instance-00000077 shut off > - instance-0000007c shut off > - instance-0000007d shut off > - instance-00000081 shut off > - instance-00000082 shut off > - instance-00000083 shut off > - instance-00000084 shut off > - instance-00000085 shut off > > query the nova the database, you can see: > vm_state: stopped > Why is this? > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
