[rhos-list] Nova-network v.s. Quantum in Openstack preview
Shixiong Shang (shshang)
shshang at cisco.com
Sat Feb 16 02:31:24 UTC 2013
Hi, Perry and Karen:
I did some further investigation tonight. The VM instance was initiated with lot of parameters, among which, here is one line related to CPU model:
-cpu Nehalem,+rdtscp,+vmx,+ht,+ss,+acpi,+ds,+vme -enable-kvm
Based on qemu-kvm command and cpu_map.xml file, Nehalem and all of the flags are supported. However, when I tried to perform CPU check, KVM crashed again. The backtrace is identical to the ones I saw in failed VM instance log:
[root at as-cmp1 libvirt]# /usr/libexec/qemu-kvm -cpu Nehalem,check
VNC server running on `::1:5900'
KVM internal error. Suberror: 2
extra data[0]: 80000003
extra data[1]: 80000603
rax 00000000000003c3 rbx 00000000000008f2 rcx 000000000000013f rdx 000000000000ffdf
rsi 0000000000000006 rdi 000000000000c993 rsp 00000000000003aa rbp 000000000000f000
r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11 0000000000000000
r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000
rip 00000000000010e2 rflags 00000286
cs c000 (000c0000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
ds c000 (000c0000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
es f000 (000f0000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
ss 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
fs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
gs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
tr 0000 (feffd000/00002088 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
ldt 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0)
gdt fc558/37
idt 0/3ff
cr0 10 cr2 0 cr3 0 cr4 0 cr8 0 efer 0
FYI, I am using this qemu-kvm version:
qemu-kvm-0.12.1.2-2.335.el6.x86_64
The potential workaround is to use generic CPU model, such as KVM64, with performance penalty. I will give it a try and keep you posted. In the meanwhile, if you can think of anything else, please let me at your early convenience.
Thanks for your help!
Shixiong
On Feb 15, 2013, at 10:09 AM, Perry Myers <pmyers at redhat.com<mailto:pmyers at redhat.com>>
wrote:
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,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/rhos-list/attachments/20130216/073aa707/attachment.htm>
More information about the rhos-list
mailing list