From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kashyap Chamarthy <kchamart@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
Message-ID: <20150220194509.GD30563@tesla.home>
References: <20150216204013.GI21838@tesla.redhat.com>
 <54E2D966.9070706@siemens.com>
 <20150217112426.GL21838@tesla.redhat.com>
 <54E4C0FD.4090906@redhat.com>
 <20150219120719.GJ11686@tesla.redhat.com>
 <20150219150159.GA19057@potion.brq.redhat.com>
 <20150219160221.GB19057@potion.brq.redhat.com>
 <20150219211011.GE28728@tesla.redhat.com>
 <20150219222832.GA22611@tesla.redhat.com>
 <20150220161415.GA22152@potion.brq.redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Jan Kiszka <jan.kiszka@siemens.com>, kvm@vger.kernel.org,
	dgilbert@redhat.com
To: Radim =?utf-8?B?S3LEjW3DocWZ?= <rkrcmar@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:47118 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754548AbbBTTpR (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 20 Feb 2015 14:45:17 -0500
Content-Disposition: inline
In-Reply-To: <20150220161415.GA22152@potion.brq.redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Fri, Feb 20, 2015 at 05:14:15PM +0100, Radim Kr=C4=8Dm=C3=A1=C5=99 w=
rote:
> 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=C4=8Dm=C3=A1=C5=
=99 wrote:

[. . .]

> > Then, I did another test:
> >=20
> >   - Rebooted into Kernel 3.20.0-0.rc0.git5.1.fc23.x86_64 on physica=
l
> >     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 b=
uilt
> >     one, here too, I'm thrown into a dracut shell
>=20
> 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:
> >=20
> >   # Clone the tree
> >   $ git://git.kernel.org/pub/scm/virt/kvm/kvm.git
> >=20
> >   # 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
>=20
> Hm, it should say v3.19 -- does it stay the same if you do
> `git fetch && git checkout origin/master`?
>=20
> If it still does, please try to apply it on top of `git checkout v3.1=
8`.
> (The one that one failed too.)
>=20
> >   # Make a config file
> >   $ make defconfig
>=20
> It would be safer to copy the fedora config (from /boot) to .config a=
nd
> do `make olddefconfig`.

That's actually what I did on my later compiles.

=46or now, as noted above, will test with the Fedora Kernel scratch bui=
ld
I made.

  [1] https://bugzilla.redhat.com/show_bug.cgi?id=3D1194809 --  `dhclie=
nt`
      crashes on boot
  [2] http://koji.fedoraproject.org/koji/taskinfo?taskID=3D9004708
  [3] https://kojipkgs.fedoraproject.org//work/tasks/4708/9004708/build=
=2Elog

--=20
/kashyap