From mboxrd@z Thu Jan  1 00:00:00 1970
From: Radim =?utf-8?B?S3LEjW3DocWZ?= <rkrcmar@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 17:14:15 +0100
Message-ID: <20150220161415.GA22152@potion.brq.redhat.com>
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>
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: Kashyap Chamarthy <kchamart@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:42428 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753762AbbBTQOY (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 20 Feb 2015 11:14:24 -0500
Content-Disposition: inline
In-Reply-To: <20150219222832.GA22611@tesla.redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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:
>=20
> [. . .]
>=20
> > > Can you try if the following patch works?
> >=20
> > Sure, will test a Kernel built with the below patch and report back=
=2E
>=20
> Hmm, I'm stuck with a meta issue.
>=20
> I checked out the KVM tree[1] on L0, applied your patch and built[*] =
the
> Kernel, and booted into it. Boot fails and drops into a dracut shell =
on
> because:
>=20
>  . . .
>  dracut-initqueue[3045]: Warning: Cancelling resume operation. Device=
 not found.
>  [ TIME ] Timed out waiting for device
>  dev-ma...per910\x2d\x2d02\x2droot.device.
>  [DEPEND] Dependency failed for /sysroot.
>  [DEPEND] Dependency failed for Initrd Root File SyWarning:
>  /dev/disk/by-uuid/4ccddb2d-4d63-4fce-b4d4-9b2f119a30cc does not exis=
t
>  . . .
>=20
> I saved the report from /run/initramfs/rdsosreport.txt here[2].
>=20
>=20
> Then, I did another test:
>=20
>   - 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 bui=
lt
>     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 ...

> [1] git://git.kernel.org/pub/scm/virt/kvm/kvm.git
> [2] https://kashyapc.fedorapeople.org/temp/kernel-boot-failure.txt
>=20
> [*] 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

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`=
=2E
(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`.

>   # Compile
>   $ make -j4 && make bzImage && make modules
>  =20
>   # Install
>   $ sudo -i
>   $ make modules_install && make install
>=20
> --=20
> /kashyap