Hi Kevin,
If you are using KVM as hyper visor and if your compute node having
any issues with kvm acceleration, it can lead to the below problem - So
ou can try changing the virt_type to qemu from kvm in /etc/nova/nova-
compute.conf . After restarting the nova compute service - try to la
I checked and the disk has plenty of space:
Filesystem Size Used Avail Use% Mounted on
/dev/vda150G 6.2G 41G 14% /
none4.0K 0 4.0K 0% /sys/fs/cgroup
udev3.9G 12K 3.9G 1% /dev
tmpfs 799M 408K 799M 1% /run
none5.0M 0
These VMs that are running devstack are 50GB disk, so there is plenty of disk
space. I don’t have cinder set up with this devstack setup.
I looked in the log for the instance and in the failing case the same message
was displayed (with different MAC and uuid), and then on the next line, I see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I ran into similar behavior once, and it turned out I was running out
of space on the system. This blog post helped me track down the
problem:
http://porkrind.org/missives/libvirt-based-qemu-vm-pausing-by-itself/
Not sure whether it's relevant to you
On Jan 2, 2015, at 4:53 AM, Paul Michali (pcm) wrote:
> I don’t see what the difference is between a working and non-working setup. :(
One other time I’ve seen this happen is if the compute node is low (or out) of
disk space. If there’s connectivity problems with a cinder device, this would
b
No other tools. Running a stock Ubuntu 14.04 server, installed devstack,
created local.conf, stacked, and tried to create a VM. I’ve since seen this on
another VM I have running with Kilo code, so it is not specifically a Juno
issue.
I don’t see what the difference is between a working and non
Ah, doesn't seem to be a Neutron issue then since the
'network-vif-plugged' event is showing up and it's attempting to
resume.
The red flag looks like that "Instance is paused unexpectedly.
Ignore.". If you grep the nova code base for that, it brings up a note
linking to bug 1097806.[1] The VM is
Hi Kevin,
No exceptions/tracebacks/errors in Neutron at all. In the Nova logs, it seems
to create the instance, pause, and then resume, but it looks like maybe it is
not resuming?
2015-01-01 14:44:30.716 3516 DEBUG nova.openstack.common.processutils [-]
Running cmd (subprocess): sudo nova-root
Any exceptions on the Neutron side? It might not be notifying nova
that the network is ready.
On Wed, Dec 31, 2014 at 8:41 AM, Paul Michali (pcm) wrote:
> Not sure if I’m going crazy or what. I’m using DevStack and, after stacking
> I tried booting a Cirros 3.2, 3.3, and Ubuntu cloud 14.04 image.