From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: Zachary Amsden <zamsden@redhat.com>
Cc: Glauber Costa <glommer@redhat.com>, Avi Kivity <avi@redhat.com>,
Nikola Ciprich <nikola.ciprich@linuxbox.cz>,
KVM list <kvm@vger.kernel.org>,
Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: regression - 2.6.36 -> 2.6.37 - kvm - 32bit SMP guests don't boot
Date: Sun, 6 Mar 2011 17:03:28 +0100 [thread overview]
Message-ID: <20110306160328.GA29429@nik-comp.lan> (raw)
In-Reply-To: <4D739FEF.7000502@redhat.com>
> I did read your mail, but I was working on an old tree... because of
> that transformation, this fix will unfortunately have to be back and
> forward ported by hand.
OK, sorry, I didn't mean to be adverse...
>
> Did you try just that change right applied on top of the patch
> (e48672fa25e879f7ae21785c7efd187738139593) implicated by bisect?
yes, with host running e48672fa25e879f7ae21785c7efd187738139593,
32bit SMP guest doesn't boot, when I add kvm_request_guest_time_update(vcpu),
it helps.
>
> It will be great to know if that change alone fixes the problem, if so,
> the fix you propose is probably the right one for upstream.
ok, so shell I submit patch adding kvm_make_request(KVM_REQ_CLOCK_UPDATE, vcpu)?
this fixes things for me for 2.6.37.
>
> Thanks,
>
> Zach
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava
tel.: +420 596 603 142
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------
next prev parent reply other threads:[~2011-03-06 16:03 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 23:42 regression - 2.6.36 -> 2.6.37 - kvm - 32bit SMP guests don't boot Nikola Ciprich
2011-02-24 10:17 ` Avi Kivity
2011-02-24 10:48 ` Nikola Ciprich
2011-02-24 10:52 ` Avi Kivity
2011-02-24 11:27 ` Nikola Ciprich
2011-02-24 12:26 ` Avi Kivity
2011-02-24 12:41 ` Nikola Ciprich
2011-02-24 12:51 ` Avi Kivity
2011-02-24 12:57 ` Nikola Ciprich
2011-02-25 10:48 ` Nikola Ciprich
2011-02-25 14:45 ` Zachary Amsden
2011-02-27 17:20 ` Nikola Ciprich
2011-02-28 13:51 ` Zachary Amsden
2011-02-28 14:32 ` Nikola Ciprich
2011-02-28 15:17 ` Zachary Amsden
2011-02-28 15:28 ` Nikola Ciprich
2011-02-28 15:56 ` Zachary Amsden
2011-02-28 17:13 ` Nikola Ciprich
2011-02-28 17:15 ` Nikola Ciprich
2011-03-03 1:56 ` Zachary Amsden
2011-03-03 7:06 ` Nikola Ciprich
2011-03-03 20:47 ` Zachary Amsden
2011-03-03 21:06 ` Nikola Ciprich
2011-03-03 21:58 ` Zachary Amsden
2011-03-03 22:01 ` Nikola Ciprich
2011-03-04 15:13 ` Zachary Amsden
2011-03-04 18:27 ` Nikola Ciprich
2011-03-04 19:09 ` Glauber Costa
2011-03-04 20:55 ` Nikola Ciprich
2011-03-04 21:41 ` Glauber Costa
2011-03-04 22:36 ` Nikola Ciprich
2011-03-04 22:59 ` Zachary Amsden
2011-03-05 1:17 ` Zachary Amsden
2011-03-05 7:21 ` Nikola Ciprich
2011-03-06 14:53 ` Zachary Amsden
2011-03-06 16:03 ` Nikola Ciprich [this message]
2011-03-04 22:57 ` Zachary Amsden
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=20110306160328.GA29429@nik-comp.lan \
--to=extmaillist@linuxbox.cz \
--cc=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
--cc=zamsden@redhat.com \
/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).