[rhos-list] Nova-network v.s. Quantum in Openstack preview
Perry Myers
pmyers at redhat.com
Fri Feb 15 15:09:40 UTC 2013
On 02/15/2013 10:06 AM, Shixiong Shang (shshang) wrote:
> Hi, Perry:
>
> Thanks a lot for chiming in! KVM crashed during operation. VM stayed in
> "starting" mode for about 10 secs and then went straight to "paused" mode.
>
> Here is the output you are looking for and appreciate the head up of
> RHEL 6.4 GA release! I cannot wait!
Thanks for the input below. I don't see anything obvious.
We might need to bring in a member of the kvm team to help out here.
Karen, is there someone that could take a look at this backtrace?
https://www.redhat.com/archives/rhos-list/2013-February/msg00046.html
Cheers,
Perry
> Shixiong
>
>
>
>
> Last login: Thu Feb 14 21:03:17 2013 from 13.23.225.252
> [dmd at as-cmp1 ~]$ virsh capabilities
> <capabilities>
>
> <host>
> <uuid>ad4b57cf-bf15-06ef-a735-0be06abefc82</uuid>
> <cpu>
> <arch>x86_64</arch>
> <model>Nehalem</model>
> <vendor>Intel</vendor>
> <topology sockets='4' cores='2' threads='1'/>
> <feature name='rdtscp'/>
> <feature name='vmx'/>
> <feature name='ht'/>
> <feature name='ss'/>
> <feature name='acpi'/>
> <feature name='ds'/>
> <feature name='vme'/>
> </cpu>
> <power_management>
> <suspend_disk/>
> </power_management>
> <migration_features>
> <live/>
> <uri_transports>
> <uri_transport>tcp</uri_transport>
> </uri_transports>
> </migration_features>
> <topology>
> <cells num='1'>
> <cell id='0'>
> <cpus num='8'>
> <cpu id='0'/>
> <cpu id='1'/>
> <cpu id='2'/>
> <cpu id='3'/>
> <cpu id='4'/>
> <cpu id='5'/>
> <cpu id='6'/>
> <cpu id='7'/>
> </cpus>
> </cell>
> </cells>
> </topology>
> <secmodel>
> <model>selinux</model>
> <doi>0</doi>
> </secmodel>
> </host>
>
> <guest>
> <os_type>hvm</os_type>
> <arch name='i686'>
> <wordsize>32</wordsize>
> <emulator>/usr/libexec/qemu-kvm</emulator>
> <machine>rhel6.4.0</machine>
> <machine canonical='rhel6.4.0'>pc</machine>
> <machine>rhel6.3.0</machine>
> <machine>rhel6.2.0</machine>
> <machine>rhel6.1.0</machine>
> <machine>rhel6.0.0</machine>
> <machine>rhel5.5.0</machine>
> <machine>rhel5.4.4</machine>
> <machine>rhel5.4.0</machine>
> <domain type='qemu'>
> </domain>
> <domain type='kvm'>
> <emulator>/usr/libexec/qemu-kvm</emulator>
> </domain>
> </arch>
> <features>
> <cpuselection/>
> <deviceboot/>
> <acpi default='on' toggle='yes'/>
> <apic default='on' toggle='no'/>
> <pae/>
> <nonpae/>
> </features>
> </guest>
>
> <guest>
> <os_type>hvm</os_type>
> <arch name='x86_64'>
> <wordsize>64</wordsize>
> <emulator>/usr/libexec/qemu-kvm</emulator>
> <machine>rhel6.4.0</machine>
> <machine canonical='rhel6.4.0'>pc</machine>
> <machine>rhel6.3.0</machine>
> <machine>rhel6.2.0</machine>
> <machine>rhel6.1.0</machine>
> <machine>rhel6.0.0</machine>
> <machine>rhel5.5.0</machine>
> <machine>rhel5.4.4</machine>
> <machine>rhel5.4.0</machine>
> <domain type='qemu'>
> </domain>
> <domain type='kvm'>
> <emulator>/usr/libexec/qemu-kvm</emulator>
> </domain>
> </arch>
> <features>
> <cpuselection/>
> <deviceboot/>
> <acpi default='on' toggle='yes'/>
> <apic default='on' toggle='no'/>
> </features>
> </guest>
>
> </capabilities>
>
>
>
> [dmd at as-cmp1 ~]$ lsmod | grep kvm
> kvm_intel 53484 0
> kvm 315450 1 kvm_intel
> [dmd at as-cmp1 ~]$
>
>
>
>
>
>
>
>
>
>
>
> On Feb 15, 2013, at 6:04 AM, Perry Myers <pmyers at redhat.com
> <mailto:pmyers at redhat.com>>
> wrote:
>
>> 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