From: Jan Kiszka <jan.kiszka@web.de>
To: Juergen Lock <nox@jelal.kn-bremen.de>
Cc: Mohammed Gamal <m.gamal005@gmail.com>,
qemu-devel@nongnu.org, Avi Kivity <avi@qumranet.com>
Subject: Re: [Qemu-devel] Re: Breakage with local APIC routing
Date: Mon, 31 Aug 2009 09:47:27 +0200 [thread overview]
Message-ID: <4A9B800F.1040209@web.de> (raw)
In-Reply-To: <20090829211848.GA59305@triton8.kn-bremen.de>
[-- Attachment #1: Type: text/plain, Size: 2897 bytes --]
Juergen Lock wrote:
> On Thu, Aug 27, 2009 at 07:56:41PM +0200, Jan Kiszka wrote:
>> Juergen Lock wrote:
>>> On Tue, Aug 25, 2009 at 12:38:04PM +0200, Jan Kiszka wrote:
>>>> Mohammed Gamal wrote:
>>>>> On Tue, Aug 25, 2009 at 1:16 PM, Mohammed Gamal<m.gamal005@gmail.com> wrote:
>>>>>> On Tue, Aug 25, 2009 at 12:33 PM, Jan Kiszka<jan.kiszka@web.de> wrote:
>>>>>>> Mohammed Gamal wrote:
>>>>>>>> qemu-system-x86_64 -hda /dev/null -cdrom <path_to_ubuntu_iso_image>
>>>>>>>>
>>>>>>> I only have kubuntu-9.04-alternate-amd64.iso at hand ATM, and with that
>>>>>>> image I'm unable to reproduce. Will download and check standard ubuntu
>>>>>>> later today.
>>>>>>>
>>>>>>>> I was using qemu-kvm, but I assume that using -no-kvm would be
>>>>>>>> equivalent to using plain qemu, no?
>>>>>>> Generally yes, but not necessarily (e.g. the BIOSes are different). So
>>>>>>> it's better to check such issues also against "clean" qemu, specifically
>>>>>>> as we are on qemu-devel here.
>>>>>>>
>>>>>>> Jan
>>>>>>>
>>>>>>>
>>>>>> Just tested this now on a vanilla qemu, I am still able to reproduce
>>>>>> the same issue.
>>>>>>
>>>>> This bug might be related to the same problem
>>>>> https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/379000
>>>> I think at least those issues should be solved with recent qemu and
>>>> bioses. Note that this report refers to a fairly old qemu version
>>>> (0.10.0-derived).
>>> Btw I had reported the same symptom as in that ubuntu ticket for FreeBSD 8
>>> hosts both with 0.10.6 and 0.11.0rc1 before:
>>> http://lists.gnu.org/archive/html/qemu-devel/2009-08/msg00396.html
>>> As mentioned in that post I was able to work around the issue by passig
>>> the linux guest kernels `no_timer_check' after which they seemed to boot up
>>> just fine, so I suspect in that case its not actually an apic routing
>>> problem but just guest timer irqs arriving late/irregularly which cause
>>> the guest kernel timer checks to time out and fail.
>> Does this happen with git head and its corresponding bios, too? I cannot
>> imagine that the FreeBSD platform is so irregularly generating timer
>> events for qemu that Linux gets unhappy during this test loop (I think
>> to remember it needs 3 out of 10 ticks or so to be satisfied).
>
> Alright so I testwise updated the FreeBSD qemu-devel port to git head
> (db3c9e08e0d6eaf83f9d7a2c87dc45af3ac8f4dd, update at
> http://people.freebsd.org/~nox/qemu/qemu-devel-20090829.patch
You will have to help me isolating the reason as I don't have any BSD
host. And running recent qemu/-kvm on Linux hosts does not trigger
problems around booting ubuntu here.
> ) - and can report the problem still exists. (btw pcap seems to be
> broken in that patch which was stll working with the 0.11 snapshot,
> will have to take care of that later...)
>
> Thanx,
> Juergen
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-08-31 7:47 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 14:28 [Qemu-devel] Breakage with local APIC routing Johannes Schindelin
2008-08-13 8:14 ` [Qemu-devel] " Jan Kiszka
2008-08-13 9:08 ` Jan Kiszka
2008-08-17 15:00 ` Johannes Schindelin
2008-08-17 15:28 ` Johannes Schindelin
2008-08-17 16:52 ` Jan Kiszka
2009-08-13 16:21 ` Johannes Schindelin
2009-08-25 6:56 ` Jan Kiszka
2009-08-25 8:24 ` Mohammed Gamal
2009-08-25 8:59 ` Jan Kiszka
2009-08-25 9:09 ` Mohammed Gamal
2009-08-25 9:33 ` Jan Kiszka
2009-08-25 10:16 ` Mohammed Gamal
2009-08-25 10:21 ` Mohammed Gamal
2009-08-25 10:38 ` Jan Kiszka
2009-08-26 22:10 ` Juergen Lock
2009-08-27 17:56 ` Jan Kiszka
2009-08-29 21:18 ` Juergen Lock
2009-08-31 7:47 ` Jan Kiszka [this message]
2009-08-31 21:27 ` Juergen Lock
2009-09-01 20:12 ` Juergen Lock
2009-09-07 20:59 ` FreeBSD timing issues and qemu (was: Re: [Qemu-devel] Re: Breakage with local APIC routing) Juergen Lock
2009-09-08 2:17 ` Ryan Stone
2009-09-09 20:15 ` Juergen Lock
2009-09-09 20:39 ` Ryan Stone
2009-09-09 20:46 ` Luigi Rizzo
2009-09-10 17:46 ` Juergen Lock
2009-09-10 19:08 ` Luigi Rizzo
2009-09-10 20:44 ` Juergen Lock
2009-09-11 15:22 ` John Baldwin
2009-09-11 17:03 ` Luigi Rizzo
2009-09-11 17:01 ` John Baldwin
2009-09-12 15:48 ` Luigi Rizzo
2009-08-25 11:48 ` [Qemu-devel] Re: Breakage with local APIC routing Johannes Schindelin
2009-08-25 12:31 ` Jan Kiszka
2009-08-25 13:36 ` Johannes Schindelin
2009-08-26 7:31 ` Jan Kiszka
2009-08-26 9:27 ` Avi Kivity
2009-08-27 18:07 ` Jan Kiszka
2008-08-17 17:32 ` [Qemu-devel] " Stefan Weil
2008-08-17 18:58 ` [Qemu-devel] " Jan Kiszka
2008-08-17 20:40 ` Stefan Weil
2008-08-17 20:23 ` [Qemu-devel] " Aurelien Jarno
2008-08-17 21:10 ` Stefan Weil
2008-08-18 14:27 ` Anthony Liguori
2008-08-17 21:14 ` [Qemu-devel] " Jan Kiszka
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=4A9B800F.1040209@web.de \
--to=jan.kiszka@web.de \
--cc=avi@qumranet.com \
--cc=m.gamal005@gmail.com \
--cc=nox@jelal.kn-bremen.de \
--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).