Bug 516545 - qemu-kvm crashed when setting 32bitwin28k with 64G ram
Summary: qemu-kvm crashed when setting 32bitwin28k with 64G ram
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kvm
Version: 5.4
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Gleb Natapov
QA Contact: Lawrence Lim
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-10 11:51 UTC by Miya Chen
Modified: 2014-03-26 01:00 UTC (History)
7 users (show)

Fixed In Version: kvm-83-134.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-30 07:56:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2010:0271 0 normal SHIPPED_LIVE Important: kvm security, bug fix and enhancement update 2010-03-29 13:19:48 UTC

Description Miya Chen 2009-08-10 11:51:15 UTC
Description of problem:
qemu-kvm crashed when setting 32bitwin28k with 64G ram

Got error:
kvm_run: failed entry, reason 7
rax 000000008000003b rbx 0000000000122000 rcx 0000000000000020 rdx 0000000000000000
rsi 0000000000000000 rdi 00000000ffd0a000 rsp 0000000000000000 rbp 00000000803998f4
r8  0000000000000000 r9  0000000000000000 r10 0000000000000000 r11 0000000000000000
r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000
rip 00000000000003a6 rflags 00033006
cs 0200 (00002000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
ds 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0)
es 0000 (00000000/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 (fffbd000/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 803d85d0/3ff
idt 803d89d0/7ff
cr0 60000010 cr2 0 cr3 109000 cr4 20 cr8 0 efer 800
kvm_run returned -8

Version-Release number of selected component (if applicable):
83-105

How reproducible:
100%

Steps to Reproduce:
1.start guest by:
/usr/libexec/qemu-kvm -no-hpet -rtc-td-hack -drive file=win2008-32-virtio.qcow2,if=ide -cpu qemu64,+sse2 -m 64G -smp 8 -net nic,macaddr=20:20:20:90:00:35,model=rtl8139,vlan=0 -net tap,script=/etc/qemu-ifup,vlan=0 -net nic,macaddr=20:20:20:90:00:36,model=e1000,vlan=1 -net tap,script=/etc/qemu-ifup,vlan=1 -vnc :1

  
Actual results:


Expected results:


Additional info:
host info:
 free -lm
             total       used       free     shared    buffers     cached
Mem:        515761       2960     512801          0        228       2332
Low:        515761       2960     512801
High:            0          0          0
-/+ buffers/cache:        398     515363
Swap:         1999          0       1999

cpuinfo:
processor	: 47
vendor_id	: GenuineIntel
cpu family	: 6
model		: 29
model name	: Intel(R) Xeon(R) CPU           E7450  @ 2.40GHz

Comment 1 lihuang 2009-08-13 16:14:09 UTC
FYI
on AMD host . can not boot the guest with 64GB RAM
https://bugzilla.redhat.com/show_bug.cgi?id=517223#c1

Comment 2 Gleb Natapov 2009-10-30 16:23:14 UTC
does -smp 1 work?

Comment 8 Miya Chen 2009-12-23 06:16:51 UTC
Verified in kvm-83-139.el5, this problem does not exist.

steps:
1. boot win2008-32-DC with 64G mem:
/usr/libexec/qemu-kvm -rtc-td-hack -no-hpet -usbdevice tablet -cpu qemu64,+sse2 -drive file=win28k-32-virtio.qcow2,if=virtio,boot=on,format=qcow2,cache=off -smp 8 -m 64G -vnc :2 -net nic,macaddr=20:20:20:11:11:90,model=e1000,vlan=0 -net tap,script=/root/qemu-ifup,vlan=0 -monitor stdio -balloon none

Actual result:
guest can boot up successfully and check physical mem in task manager, it is 64G.
guest works fine after one hour.

Comment 11 errata-xmlrpc 2010-03-30 07:56:21 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0271.html


Note You need to log in before you can comment on or make changes to this bug.