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 16:00:04 +0200 [thread overview]
Message-ID: <4BF29D64.3020709@dlh.net> (raw)
In-Reply-To: <4BF29B78.2000604@suse.de>
Alexander Graf wrote:
> Peter Lieven wrote:
>
>> Alexander Graf wrote:
>>
>>> Peter Lieven wrote:
>>>
>>>
>>>> we are running on intel xeons here:
>>>>
>>>>
>>> That might be the reason. Does it break when passing -no-kvm?
>>>
>>>
>>>
>>>> processor : 0
>>>> vendor_id : GenuineIntel
>>>> cpu family : 6
>>>> model : 26
>>>> model name : Intel(R) Xeon(R) CPU L5530 @ 2.40GHz
>>>> stepping : 5
>>>> cpu MHz : 2394.403
>>>> cache size : 8192 KB
>>>> physical id : 1
>>>> siblings : 4
>>>> core id : 0
>>>> cpu cores : 4
>>>> apicid : 16
>>>> initial apicid : 16
>>>> fpu : yes
>>>> fpu_exception : yes
>>>> cpuid level : 11
>>>> wp : yes
>>>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>>>> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
>>>> syscall rdtscp lm constant_tsc arch_perfmon pebs bts rep_good
>>>> xtopology tsc_reliable nonstop_tsc pni dtes64 monitor ds_cpl vmx est
>>>> tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm tpr_shadow
>>>> vnmi flexpriority ept vpid
>>>> bogomips : 4788.80
>>>> clflush size : 64
>>>> cache_alignment : 64
>>>> address sizes : 40 bits physical, 48 bits virtual
>>>> power management:
>>>>
>>>> kvm-kmod is 2.6.32.7
>>>> ...
>>>>
>>>> which commandline parameters do you supply to qemu-kvm?
>>>>
>>>>
>>> None :)
>>>
>>>
>> It seems to stop working if i supply -no-kvm-irqchip. Can you try to
>> reproduce this?
>>
>> We introduced that parameter because we encountered some problems with
>> the e1000 kernel driver stopped to work in some
>> guests after live migration with a "nobody cared about interupt" (i
>> don't know the exact error anymore). supplying
>> -no-kvm-irqchip made live migration of these guests possible...
>> Sounds that familiar to someone?
>>
>
> So it works with the in-kernel irqchip? That's the normally supported
> configuration anyways. If migration fails with that, that's a different
> thing and definitely needs to be addressed.
>
Yes, it seems, I got the machine booting ~10 times without any problems.
I will try to reproduce the error condition after migration and come back
to the list.
Thanks for your help,
Peter
> Alex
>
>
>
>
next prev parent reply other threads:[~2010-05-18 14:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 9:14 [Qemu-devel] Suggested Parameters for SLES 10 64-bit 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
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 [this message]
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
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=4BF29D64.3020709@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).