From: Kashyap Chamarthy <kchamart@redhat.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
kvm@vger.kernel.org, dgilbert@redhat.com
Subject: Re: [nVMX] With 3.20.0-0.rc0.git5.1 on L0, booting L2 guest results in L1 *rebooting*
Date: Fri, 20 Feb 2015 20:45:09 +0100 [thread overview]
Message-ID: <20150220194509.GD30563@tesla.home> (raw)
In-Reply-To: <20150220161415.GA22152@potion.brq.redhat.com>
On Fri, Feb 20, 2015 at 05:14:15PM +0100, Radim Krčmář wrote:
> 2015-02-19 23:28+0100, Kashyap Chamarthy:
> > On Thu, Feb 19, 2015 at 10:10:11PM +0100, Kashyap Chamarthy wrote:
> > > On Thu, Feb 19, 2015 at 05:02:22PM +0100, Radim Krčmář wrote:
[. . .]
> > Then, I did another test:
> >
> > - Rebooted into Kernel 3.20.0-0.rc0.git5.1.fc23.x86_64 on physical
> > host (L0).
> > - In L1, checked out the KVM tree, applied your patch and built
> > Kernel[*] from the current KVM tree and booted into the newly built
> > one, here too, I'm thrown into a dracut shell
>
> Weird, but considering that boot fails on L0 as well, I think it that
> basing off a different commit could help ...
What I missed to do was to build initramfs:
$ cd /boot
$ dracut initramfs-3.19.0+.img 3.19.0+ --force
Then I can boot. However, networking was hosed due to this bug[1] in
`dhclient` (Andrea Arcangeli said it's fixed for him in newest Kernels,
but unfortunately it's still not fixed for me as I noted in the bug.
Anyway, for the nVMX bug in question, I actually built a Fedora scratch
Kernel build[2], with your fix, which was successful[3]. I will test
with it once I get the networking fixed on the physical machine,
hopefully, early next week.
> > [*] Exactly, I built it this way:
> >
> > # Clone the tree
> > $ git://git.kernel.org/pub/scm/virt/kvm/kvm.git
> >
> > # Make a new branch:
> > $ git checkout -b nvmx_test
> > $ git describe
> > warning: tag 'for-linus' is really 'kvm-3.19-1' here
> > for-linus-14459-g49776d5
>
> Hm, it should say v3.19 -- does it stay the same if you do
> `git fetch && git checkout origin/master`?
>
> If it still does, please try to apply it on top of `git checkout v3.18`.
> (The one that one failed too.)
>
> > # Make a config file
> > $ make defconfig
>
> It would be safer to copy the fedora config (from /boot) to .config and
> do `make olddefconfig`.
That's actually what I did on my later compiles.
For now, as noted above, will test with the Fedora Kernel scratch build
I made.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1194809 -- `dhclient`
crashes on boot
[2] http://koji.fedoraproject.org/koji/taskinfo?taskID=9004708
[3] https://kojipkgs.fedoraproject.org//work/tasks/4708/9004708/build.log
--
/kashyap
next prev parent reply other threads:[~2015-02-20 19:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 20:40 [nVMX] With 3.20.0-0.rc0.git5.1 on L0, booting L2 guest results in L1 *rebooting* Kashyap Chamarthy
2015-02-17 6:02 ` Jan Kiszka
2015-02-17 11:24 ` Kashyap Chamarthy
2015-02-17 18:00 ` Bandan Das
2015-02-17 18:07 ` Jan Kiszka
2015-02-18 10:20 ` Kashyap Chamarthy
2015-02-18 16:42 ` Paolo Bonzini
2015-02-19 12:07 ` Kashyap Chamarthy
2015-02-19 15:01 ` Radim Krčmář
2015-02-19 16:02 ` Radim Krčmář
2015-02-19 16:07 ` Radim Krčmář
2015-02-19 21:10 ` Kashyap Chamarthy
2015-02-19 22:28 ` Kashyap Chamarthy
2015-02-20 16:14 ` Radim Krčmář
2015-02-20 19:45 ` Kashyap Chamarthy [this message]
2015-02-22 15:46 ` Kashyap Chamarthy
2015-02-23 13:56 ` Radim Krčmář
2015-02-23 16:14 ` Kashyap Chamarthy
2015-02-23 17:09 ` Kashyap Chamarthy
2015-02-23 18:05 ` Kashyap Chamarthy
2015-02-24 16:30 ` [PATCH] KVM: nVMX: mask unrestricted_guest if disabled on L0 Radim Krčmář
2015-02-24 16:39 ` Jan Kiszka
2015-02-24 18:32 ` Bandan Das
2015-02-25 15:50 ` Kashyap Chamarthy
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=20150220194509.GD30563@tesla.home \
--to=kchamart@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@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