[rhos-list] Nova-network v.s. Quantum in Openstack preview

Perry Myers pmyers at redhat.com
Fri Feb 15 11:04:58 UTC 2013


On 02/15/2013 04:31 AM, Gary Kotton wrote:
> On 02/15/2013 04:54 AM, Shixiong Shang (shshang) wrote:
>> Hi, Gary:
>>
>> I tried to put SELinux in PERMISSIVE mode and spawned up new VM using
>> cirros image today, but still no luck. I spent the rest of the day
>> searching Redhat bugs based on numerous error msgs in various log
>> files. Found tons of stuff, but most of them didn't seem to be
>> relevant and helpful.
>>
>> One thing caught my eyes is a case submitted back in 2010 and updated
>> early this year. The KVM error message in instance console log is
>> similar to the one in my case. Based on the description, seems like
>> the KVM crash is caused by defective CPU or unsupported CPU model. I
>> will try different machine for better luck. 
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=639208

Shixiong,

Is it a kvm crash during operation or does it fail to start at all?

Just as a sanity check, can you run virsh capabilities and give us the
output?

And also:
lsmod | grep kvm

>> Will keep you posted if I can root cause the problem. In the
>> meanwhile, if anything pops to your mind, please let me know.
> 
> Thanks for the update. Which RHEL version are you using? I am using RHEL
> 6.4. I do the following:
> - install from disk
> - subscripion registration
> - i then make sure that the RHEL 6.4 beta repo is added:
> 
> 	[rhel64beta]
> 	name=RHEL64 BETA
> 	#baseurl=http://download.eng.tlv.redhat.com/pub/rhel/rel-eng/RHEL6.4-20130130.0/6.4/source
> 	baseurl=http://download.eng.tlv.redhat.com/pub/rhel/rel-eng/RHEL6.4-20130130.0/6.4/Server/x86_64/os/
> 	enabled=1
> 	gpgcheck=0
> (please do not do a yum update after this - it causes conflicts with packstack)
> - then i install the latest packstack
> - run packstack and everything works (bar the minor iptable issue we have discussed)

One hiccup in the above...

Because the RHEL 6.4 GA release is imminent, the RHEL 6.4 Beta Repos
have been emptied.  It's part of the normal release engineering process.
 So for a short time, you might be stuck with getting updated packages
or reinstalling from scratch on a new host.

This issue should clear up in the next week as we get GA packages out
the door.  I'll send a more general note to the list about it.

Perry




More information about the rhos-list mailing list