From: Matthew Hall <matt-Etm38r6YSMlqcVXhcSD7Ah2eb7JE58TQ@public.gmane.org>
To: Joerg Roedel <joerg.roedel-5C7GfCeVMHo@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: KVM, AMD & Interrupts
Date: Fri, 26 Jan 2007 06:42:32 +0000 [thread overview]
Message-ID: <45B9A2D8.6070005@castleinthesky.org> (raw)
In-Reply-To: <20070125133656.GA22891-5C7GfCeVMHo@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1623 bytes --]
Joerg Roedel wrote:
> I didn't follow your discussion about the problem in the #kvm channel.
> Could you provide more information about the problem itself and about
> your test environment? If I am able to reproduce the problem, we may be
> able to fix it.
Sure.
My host is a Dell SC1435, with 2 dual core Opteron 2212 HE's @2GHz.
There's 4Gb memory and a 120Gb Sata disk (sata_svw). The host is running
FC6 x86_64 with 'kernel-2.6.19-1.2906.fc7' (2.6.20-rc4 from fc7
devel) and kvm-12.
(The fc kernel comes with the kvm drivers from an earlier version, i've
deleted these and have been testing bith the trunk and release kvm code).
The symptoms I saw were that the guest was not able to access any hd*
devices 'properly'.
The local boot iso images (I tried the fc6 installer and some live-cd's)
booted the kernel, but when linux attempted to enumerate the hd devices
(before init) it stalled and eventually printed errors like 'hda: lost
interrupt' and 'drive ready seek command failed' et al.
I got to the point of turning on the debug messages from qemu/hw/ide.c
(DEBUG_IDE*).
At the point where the guest stalled (just after printing the CHS of
hda) the host printed 'ide: CMD=91' (then there was a significant pause
before anything else was printed). The guest then prints 'hda: lost
interrupt' and the next pause was just after 'ide: CMD=10' (it then
carries on like this until I give up hope and ctrl-c qemu). I've
attached the debug output from that test.
The box is not live atm - so I have carte blanche to run any tests
should you not be able to reproduce this yourselves.
Thanks,
Matt
[-- Attachment #2: debug.log.bz2 --]
[-- Type: application/x-bzip, Size: 2758 bytes --]
[-- Attachment #3: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #4: Type: text/plain, Size: 186 bytes --]
_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel
prev parent reply other threads:[~2007-01-26 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 1:03 KVM, AMD & Interrupts Matthew Hall
[not found] ` <45B801C4.4060201-Etm38r6YSMlqcVXhcSD7Ah2eb7JE58TQ@public.gmane.org>
2007-01-25 1:52 ` Anthony Liguori
2007-01-25 7:49 ` Avi Kivity
2007-01-25 13:36 ` Joerg Roedel
[not found] ` <20070125133656.GA22891-5C7GfCeVMHo@public.gmane.org>
2007-01-26 6:42 ` Matthew Hall [this message]
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=45B9A2D8.6070005@castleinthesky.org \
--to=matt-etm38r6ysmlqcvxhcsd7ah2eb7je58tq@public.gmane.org \
--cc=joerg.roedel-5C7GfCeVMHo@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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