From: Peter Lieven <pl@dlh.net>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Suggested Parameters for SLES 10 64-bit
Date: Tue, 18 May 2010 14:00:18 +0200 [thread overview]
Message-ID: <4BF28152.9040100@dlh.net> (raw)
In-Reply-To: <2A9FC14A-EDF8-4369-81BD-5232A4C6F647@suse.de>
hi alex,
here is a backtrace of the sles 10 sp1 vm running on qemu-kvm 0.12.4.
hanging at boot.
a colleguage is meanwhile upgraded a cloned system to sp3 to see if it
is also
not working.
^C
Program received signal SIGINT, Interrupt.
[Switching to Thread 0x7f0b753c76f0 (LWP 25532)]
0x00007f0b73e13742 in select () from /lib/libc.so.6
(gdb) thread apply all bt
Thread 5 (Thread 0x7f0b72115950 (LWP 25546)):
#0 0x00007f0b73e12cd7 in ioctl () from /lib/libc.so.6
#1 0x000000000042b945 in kvm_run (env=0x201cb10) at
/usr/src/qemu-kvm-0.12.4/qemu-kvm.c:921
#2 0x000000000042cea2 in kvm_cpu_exec (env=0x201cb10) at
/usr/src/qemu-kvm-0.12.4/qemu-kvm.c:1651
#3 0x000000000042d62c in kvm_main_loop_cpu (env=0x201cb10) at
/usr/src/qemu-kvm-0.12.4/qemu-kvm.c:1893
#4 0x000000000042d76d in ap_main_loop (_env=0x201cb10) at
/usr/src/qemu-kvm-0.12.4/qemu-kvm.c:1943
#5 0x00007f0b74d983ba in start_thread () from /lib/libpthread.so.0
#6 0x00007f0b73e1afcd in clone () from /lib/libc.so.6
#7 0x0000000000000000 in ?? ()
Thread 4 (Thread 0x7f0b72916950 (LWP 25545)):
#0 0x00007f0b73d69461 in sigtimedwait () from /lib/libc.so.6
#1 0x000000000042d1e5 in kvm_main_loop_wait (env=0x200ed90,
timeout=1000) at /usr/src/qemu-kvm-0.12.4/qemu-kvm.c:1752
#2 0x000000000042d64a in kvm_main_loop_cpu (env=0x200ed90) at
/usr/src/qemu-kvm-0.12.4/qemu-kvm.c:1896
#3 0x000000000042d76d in ap_main_loop (_env=0x200ed90) at
/usr/src/qemu-kvm-0.12.4/qemu-kvm.c:1943
#4 0x00007f0b74d983ba in start_thread () from /lib/libpthread.so.0
#5 0x00007f0b73e1afcd in clone () from /lib/libc.so.6
#6 0x0000000000000000 in ?? ()
Thread 3 (Thread 0x7f0b73117950 (LWP 25544)):
#0 0x00007f0b73d69461 in sigtimedwait () from /lib/libc.so.6
#1 0x000000000042d1e5 in kvm_main_loop_wait (env=0x2001010,
timeout=1000) at /usr/src/qemu-kvm-0.12.4/qemu-kvm.c:1752
#2 0x000000000042d64a in kvm_main_loop_cpu (env=0x2001010) at
/usr/src/qemu-kvm-0.12.4/qemu-kvm.c:1896
#3 0x000000000042d76d in ap_main_loop (_env=0x2001010) at
/usr/src/qemu-kvm-0.12.4/qemu-kvm.c:1943
#4 0x00007f0b74d983ba in start_thread () from /lib/libpthread.so.0
#5 0x00007f0b73e1afcd in clone () from /lib/libc.so.6
#6 0x0000000000000000 in ?? ()
Thread 2 (Thread 0x7f0b73918950 (LWP 25543)):
#0 0x00007f0b73d69461 in sigtimedwait () from /lib/libc.so.6
#1 0x000000000042d1e5 in kvm_main_loop_wait (env=0x1fe75b0,
timeout=1000) at /usr/src/qemu-kvm-0.12.4/qemu-kvm.c:1752
#2 0x000000000042d64a in kvm_main_loop_cpu (env=0x1fe75b0) at
/usr/src/qemu-kvm-0.12.4/qemu-kvm.c:1896
#3 0x000000000042d76d in ap_main_loop (_env=0x1fe75b0) at
/usr/src/qemu-kvm-0.12.4/qemu-kvm.c:1943
#4 0x00007f0b74d983ba in start_thread () from /lib/libpthread.so.0
#5 0x00007f0b73e1afcd in clone () from /lib/libc.so.6
#6 0x0000000000000000 in ?? ()
Thread 1 (Thread 0x7f0b753c76f0 (LWP 25532)):
---Type <return> to continue, or q <return> to quit---
#0 0x00007f0b73e13742 in select () from /lib/libc.so.6
#1 0x000000000040c25a in main_loop_wait (timeout=1000) at
/usr/src/qemu-kvm-0.12.4/vl.c:3994
#2 0x000000000042dcf1 in kvm_main_loop () at
/usr/src/qemu-kvm-0.12.4/qemu-kvm.c:2126
#3 0x000000000040c98c in main_loop () at /usr/src/qemu-kvm-0.12.4/vl.c:4212
#4 0x000000000041054b in main (argc=43, argv=0x7fffcc0c3398,
envp=0x7fffcc0c34f8) at /usr/src/qemu-kvm-0.12.4/vl.c:6252
Alexander Graf wrote:
> On 18.05.2010, at 13:08, Peter Lieven wrote:
>
>
>> Alexander Graf wrote:
>>
>>> On 18.05.2010, at 13:01, Peter Lieven wrote:
>>>
>>>
>>>
>>>> hi alex,
>>>>
>>>> unfortunately -cpu host, -cpu qemu64, -cpu core2duo, -cpu kvm64 (which should be default) doesn't help
>>>> all other cpus available are 32-bit afaik.
>>>>
>>>> as i said if i boot with with kernel parameter "nohpet", but acpi on the guest just hangs at 100% cpu.
>>>>
>>>> would a backtrace help?
>>>>
>>>>
>>> Sigh. Is there any way to upgrade the system to SP3? Preferably incl. the latest maintenance update?
>>>
>>>
>> yes, we will try this. if you don't suspect it is a generall problem with qemu-kvm that should
>> be fixed. keep you posted.
>>
>
> Alright. Installing SLES10 SP1 in a VM in parallel.
>
> Alex
>
>
>
--
Mit freundlichen Grüßen/Kind Regards
Peter Lieven
..........................................................................................................
KAMP Netzwerkdienste GmbH
Vestische Str. 89-91 | 46117 Oberhausen
Tel: +49 (0) 208.89 402-50 | Fax: +49 (0) 208.89 402-40
mailto:pl@kamp.de | http://www.kamp.de
Geschäftsführer: Heiner Lante | Michael Lante
Amtsgericht Duisburg | HRB Nr. 12154
USt-Id-Nr.: DE 120607556
.........................................................................................................
next prev parent reply other threads:[~2010-05-18 12:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 9:14 Suggested Parameters for SLES 10 64-bit Peter Lieven
2010-05-18 9:14 ` [Qemu-devel] " Peter Lieven
2010-05-18 9:23 ` Alexander Graf
2010-05-18 9:57 ` Peter Lieven
2010-05-18 10:07 ` Alexander Graf
2010-05-18 10:12 ` Peter Lieven
2010-05-18 10:21 ` Alexander Graf
2010-05-18 11:01 ` Peter Lieven
2010-05-18 11:07 ` Alexander Graf
2010-05-18 11:08 ` Peter Lieven
2010-05-18 11:09 ` Alexander Graf
2010-05-18 12:00 ` Peter Lieven [this message]
2010-05-18 12:38 ` Alexander Graf
2010-05-18 12:54 ` Peter Lieven
2010-05-18 12:58 ` Alexander Graf
2010-05-18 13:17 ` Peter Lieven
2010-05-18 13:51 ` Alexander Graf
2010-05-18 14:00 ` Peter Lieven
2010-05-23 9:40 ` Peter Lieven
2010-05-18 12:11 ` Peter Lieven
2010-05-18 10:18 ` Peter Lieven
2010-05-18 10:19 ` Alexander Graf
2010-05-18 13:36 ` Andi Kleen
2010-05-18 13:36 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BF28152.9040100@dlh.net \
--to=pl@dlh.net \
--cc=agraf@suse.de \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.