From: malc <av1474@comtv.ru>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] loadvm and APIC
Date: Tue, 17 Jun 2008 09:19:29 +0400 (MSD) [thread overview]
Message-ID: <Pine.LNX.4.64.0806170850540.9835@linmac.oyster.ru> (raw)
Here's the scenario:
1. Start QEMU and boot Linux capable of using APIC
2. Save the VM state
3. Exit QEMU
4. Start QEMU and loadvm
Kernel instantly panics. Here's why:
Upon starting eventually following happens:
... -> pc_init -> ... -> pit_irq_timer_update
-> qemu_set_irq -> ...
-> apic_local_deliver -> cpu_interrupt(CPU_INTERRUPT_HARD)
Then qemu_loadvm_state begins executing load handlers eventually coming
to apic_load which loads the state from the storage overriding all the
effects of apic_local_deliver, in the meantime env->interrupt_request
stays the same.
Then cpu_exec is entered and it arrives at line 399 where
cpu_get_pic_interrupt calls apic_get_interrupt which returns -1, this
bogus interrupt number is then passed to do_interrupt and here it is
finally caught by a IDT limit check at line 649, general protection
fault is generated and kernel inside the VM panics.
Hence:
diff --git a/vl.c b/vl.c
index d759fde..11827ba 100644
--- a/vl.c
+++ b/vl.c
@@ -6296,6 +6296,7 @@ void do_loadvm(const char *name)
goto the_end;
}
ret = qemu_loadvm_state(f);
+ first_cpu->interrupt_request = 0;
qemu_fclose(f);
if (ret < 0) {
term_printf("Error %d while loading VM state\n", ret);
Okay to commit?
--
mailto:av1474@comtv.ru
next reply other threads:[~2008-06-17 5:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 5:19 malc [this message]
2008-06-17 7:58 ` [Qemu-devel] Re: loadvm and APIC Jan Kiszka
2008-06-17 18:07 ` malc
2008-06-17 21:51 ` Fabrice Bellard
2008-06-18 9:00 ` Jan Kiszka
2008-06-18 20:12 ` malc
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=Pine.LNX.4.64.0806170850540.9835@linmac.oyster.ru \
--to=av1474@comtv.ru \
--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).