From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: balducci@units.it
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] 3.1.0-rc{0,1} doesn't start
Date: Mon, 19 Nov 2018 14:16:07 +0000 [thread overview]
Message-ID: <20181119141606.GC2365@work-vm> (raw)
In-Reply-To: <16966.1542632079@dschgrazlin2.units.it>
* balducci@units.it (balducci@units.it) wrote:
> hi
>
> thanks for taking the time to reply
>
> Dr. David Alan Gilbert writes:
> > > I suspect that this might be some problem on my side, as I couldn't
> > > find any similar report (apart some old (qemu-2.8.50) threads, that
> > > didn't help)
> >
> > Not necessarily; can you tell me:
> > a) At what point does it fail - immediately when booting the guest?
> > Some time during the boot? Later?
> > b) What guest does it happen on?
>
> a) the error happens almost immediately; I mean: when I run qemu from an
> xterm, it doesn't even popup its window: it just dumps the error
> message to the terminal and stops
> b) the guest is an old windows XP OS; but, as I say above, all goes as
> if qemu doesn't even load the OS image (at least this is my
> impression)
Thanks.
> Meantime, I have tried to (quick&dirty) disable the error
> catching/asserting in i386/kvm.c:
>
> install:41> diff ./qemu-3.1.0-rc1/target/i386/kvm.c.MSR_HACK ./qemu-3.1.0-rc1/target/i386/kvm.c
> 2205c2205
> < if (ret < cpu->kvm_msr_buf->nmsrs) {
> ---
> > if (1==0) {
> 2211c2211
> < assert(ret == cpu->kvm_msr_buf->nmsrs);
> ---
> > assert(1==1);
> 2524c2524
> < if (ret < cpu->kvm_msr_buf->nmsrs) {
> ---
> > if (1==0) {
> 2530c2530
> < assert(ret == cpu->kvm_msr_buf->nmsrs);
> ---
> > assert(1==1);
>
> and that makes qemu start and work without apparent problems.
> Of course, that is a crude and risky (I guess) workaround...
Yes, the gotcha is that the call writes a whole bunch of MSRs
and when one fails all the ones after it don't get written either;
so you get lots of weird problems due to whichever other MSRs
are wrong.
Dave
> thanks again
>
> ciao
> -gabriele
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-11-19 14:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-18 16:40 [Qemu-devel] 3.1.0-rc{0,1} doesn't start balducci
2018-11-19 10:43 ` Dr. David Alan Gilbert
2018-11-19 12:54 ` balducci
2018-11-19 14:16 ` Dr. David Alan Gilbert [this message]
2018-11-19 18:35 ` Dr. David Alan Gilbert
2018-11-19 18:54 ` balducci
2018-11-19 18:56 ` Dr. David Alan Gilbert
2018-11-19 20:43 ` Cole Robinson
2018-11-19 21:55 ` Bandan Das
2018-11-19 23:00 ` Eduardo Habkost
2018-11-20 18:40 ` Paolo Bonzini
2018-11-20 18:48 ` Eduardo Habkost
2018-11-20 19:34 ` Paolo Bonzini
2018-11-21 4:05 ` Bandan Das
2018-11-21 13:59 ` Paolo Bonzini
2018-11-20 8:27 ` balducci
2018-11-21 4:28 ` Bandan Das
2018-11-21 7:48 ` balducci
2018-11-21 12:50 ` Eduardo Habkost
2018-11-26 4:17 ` [Qemu-devel] [PATCH] kvm: Use KVM_GET_MSR_INDEX_LIST for MSR_IA32_ARCH_CAPABILITIES support Bandan Das
2018-11-26 16:34 ` Eduardo Habkost
2018-12-11 10:54 ` Hu, Robert
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=20181119141606.GC2365@work-vm \
--to=dgilbert@redhat.com \
--cc=balducci@units.it \
--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).