Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Hi Dan,

Thank you for your reply. You were right. I checked the PPA package versions, and found a mismatch. I then reinstalled the nova packages. Running dpkg -l | grep nova on either host server returns:

ii nova-api 2011.2-0ubuntu0ppa1~lucid1 OpenStack Compute - Nova - API frontend ii nova-common 2011.2-0ubuntu0ppa1~lucid1 OpenStack Compute - Nova - common files ii nova-compute 2011.2-0ubuntu0ppa1~lucid1 OpenStack Compute - Nova - compute node ii nova-doc 2011.2-0ubuntu0ppa1~lucid1 OpenStack Compute - Nova - documetation ii nova-network 2011.2-0ubuntu0ppa1~lucid1 OpenStack Compute - Nova - Network thingamaj ii nova-objectstore 2011.2-0ubuntu0ppa1~lucid1 OpenStack Compute - Nova - object store ii nova-scheduler 2011.2-0ubuntu0ppa1~lucid1 OpenStack Compute - Nova - Scheduler ii python-nova 2011.2-0ubuntu0ppa1~lucid1 OpenStack Compute - Nova - Python libraries ii python-novaclient 2.4-0ubuntu1~lucid1 client library for OpenStack Compute API

After restarting both host servers, I get the following output from nova-manage service list: asa-test-a nova-compute enabled :-) 2011-04-17 17:01:59 asa-test-a nova-network enabled :-) 2011-04-17 17:01:57 asa-test-a nova-scheduler enabled :-) 2011-04-17 17:01:57 asa-test-b nova-scheduler enabled XXX 2011-04-17 17:01:06 asa-test-b nova-network enabled XXX 2011-04-17 17:01:05 asa-test-b nova-compute enabled XXX 2011-04-17 17:01:11

I tried starting an instance, ex.: euca-run-instances $emi -k mykey -t m1.tiny I can see that it now tries to launch the instance (sometimes on the primary host, sometimes on the secondary host). They run fine on first host (asa-test-a) but on the second host (asa-test-b) the instance status quickly changes from scheduling to launching to shutdown.
Despite the suggestion in the nova-compute.log, both machines have support for hardware virtualization, and I have successfully run kvm on both of them.


Here is the output from the nova-compute.log file on second host server (asa-test-b) when it tires to launch an instance:

2011-04-17 12:55:08,260 AUDIT nova.compute.manager [Q6TB2JI-BQUULBHOXPGI admin asa] instance 16: starting... 2011-04-17 12:55:08,959 INFO nova [-] called setup_basic_filtering in nwfilter 2011-04-17 12:55:08,960 INFO nova [-] ensuring static filters 2011-04-17 12:55:09,146 INFO nova.virt.libvirt_conn [-] instance instance-00000010: Creating image 2011-04-17 12:55:09,412 INFO nova.virt.libvirt_conn [-] instance instance-00000010: injecting key into image 1853417834 2011-04-17 12:55:09,412 INFO nova.virt.libvirt_conn [-] instance instance-00000010: injecting net into image 1853417834 2011-04-17 12:55:10,512 WARNING nova.virt.libvirt_conn [-] instance instance-00000010: ignoring error injecting data into image 1853417834 (Unexpected error while running command. Command: sudo tune2fs -c 0 -i 0 /dev/nbd15 Exit code: 1 Stdout: 'tune2fs 1.41.11 (14-Mar-2010)\n' Stderr: "tune2fs: Invalid argument while trying to open /dev/nbd15\r\nCouldn't find valid filesystem superblock.\n") 2011-04-17 12:55:41,903 ERROR nova.exception [-] Uncaught exception (nova.exception): TRACE: Traceback (most recent call last): (nova.exception): TRACE: File "/usr/lib/pymodules/python2.6/nova/exception.py", line 120, in _wrap (nova.exception): TRACE: return f(args, *kw) (nova.exception): TRACE: File "/usr/lib/pymodules/python2.6/nova/virt/libvirt_conn.py", line 617, in spawn (nova.exception): TRACE: domain = self._create_new_domain(xml) (nova.exception): TRACE: File "/usr/lib/pymodules/python2.6/nova/virt/libvirt_conn.py", line 1079, in _create_new_domain (nova.exception): TRACE: domain.createWithFlags(launch_flags) (nova.exception): TRACE: File "/usr/lib/python2.6/dist-packages/libvirt.py", line 337, in createWithFlags (nova.exception): TRACE: if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self) (nova.exception): TRACE: libvirtError: internal error process exited while connecting to monitor: char device redirected to /dev/pts/3 (nova.exception): TRACE: qemu: could not load kernel '/var/lib/nova/instances/instance-00000010/kernel': Inappropriate ioctl for device (nova.exception): TRACE: (nova.exception): TRACE: 2011-04-17 12:55:41,905 ERROR nova.compute.manager [Q6TB2JI-BQUULBHOXPGI admin asa] Instance '16' failed to spawn. Is virtualization enabled in the BIOS? (nova.compute.manager): TRACE: Traceback (most recent call last): (nova.compute.manager): TRACE: File "/usr/lib/pymodules/python2.6/nova/compute/manager.py", line 234, in run_instance (nova.compute.manager): TRACE: self.driver.spawn(instance_ref) (nova.compute.manager): TRACE: File "/usr/lib/pymodules/python2.6/nova/exception.py", line 126, in _wrap (nova.compute.manager): TRACE: raise Error(str(e)) (nova.compute.manager): TRACE: Error: internal error process exited while connecting to monitor: char device redirected to /dev/pts/3 (nova.compute.manager): TRACE: qemu: could not load kernel '/var/lib/nova/instances/instance-00000010/kernel': Inappropriate ioctl for device (nova.compute.manager): TRACE: (nova.compute.manager): TRACE: 2011-04-17 12:55:42,105 INFO nova.compute.manager [-] Found instance 'instance-00000010' in DB but no VM. State=5, so setting state to shutoff.


Here is the output from the nova-network.log file on second host server (asa-test-b):

2011-04-17 12:14:01,534 AUDIT nova [-] Starting network node (version 2011.2-workspace:tarmac-20110415024701-a9bdb77vaatk99lh) 2011-04-17 12:14:01,777 INFO nova.rpc [-] Created 'network_fanout' fanout exchange with 'network' routing key


Here is the output from the nova-scheduler.log file on second host server (asa-test-b):

2011-04-17 12:14:01,485 AUDIT nova [-] Starting scheduler node (version 2011.2-workspace:tarmac-20110415024701-a9bdb77vaatk99lh) 2011-04-17 12:14:01,729 INFO nova.rpc [-] Created 'scheduler_fanout' fanout exchange with 'scheduler' routing key