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: Thu, 19 Feb 2015 23:28:32 +0100 [thread overview]
Message-ID: <20150219222832.GA22611@tesla.redhat.com> (raw)
In-Reply-To: <20150219211011.GE28728@tesla.redhat.com>
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:
[. . .]
> > Can you try if the following patch works?
>
> Sure, will test a Kernel built with the below patch and report back.
Hmm, I'm stuck with a meta issue.
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:
. . .
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 exist
. . .
I saved the report from /run/initramfs/rdsosreport.txt here[2].
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
[1] git://git.kernel.org/pub/scm/virt/kvm/kvm.git
[2] https://kashyapc.fedorapeople.org/temp/kernel-boot-failure.txt
[*] 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
# Make a config file
$ make defconfig
# Compile
$ make -j4 && make bzImage && make modules
# Install
$ sudo -i
$ make modules_install && make install
--
/kashyap
next prev parent reply other threads:[~2015-02-19 22:28 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 [this message]
2015-02-20 16:14 ` Radim Krčmář
2015-02-20 19:45 ` Kashyap Chamarthy
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=20150219222832.GA22611@tesla.redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.