From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Vishal Chourasia <vishalc@linux.ibm.com>
Subject: Re: [linux-lvm] Trouble Booting Custom Kernel with QEMU: dracut-initqueue timeout waiting for /dev/sysvg/root
Date: Wed, 30 Aug 2023 16:31:40 +0200 [thread overview]
Message-ID: <3cc29b24-8283-478a-bce2-56c392556391@gmail.com> (raw)
In-Reply-To: <fa1ed1e4-9eae-f921-1506-87b46c13ad1f@linux.ibm.com>
Dne 30. 08. 23 v 8:40 Vishal Chourasia napsal(a):
> Hi All,
>
> I hope this email finds you well. I am currently facing an issue with
> booting a VM using a custom-compiled kernel and would appreciate your
> expertise on the matter.
>
Hi
Not really sure how this relates to 'lvm2' yet - your kernel 'stuck' seems to
be caused by the inability to switch to 'rootfs' - which should be located on
/dev/vda3 (according to your qemu exec line) - but kernel panics
reports that device does not have recognizable filesystem.
There seems to be no lvm2 involved at all so far.
> ### Problem Description
> I have downloaded the `Fedora-Server-KVM-38-1.6.x86_64.qcow2` image and
> successfully booted it using `qemu-system-x86_64`. However, when I try
> to boot this VM with a custom-compiled kernel using the `-kernel` flag,
> it fails to boot. The root filesystem is on LVM, and it seems the kernel
> needs to activate volume groups before mounting the root filesystem.
If you believe the filesystem is really on LVM and your /dev/vda3 is just a PV
- then your boot line is wrong - and you need to be using different naming -
possibly something like:
root=/dev/vgname/lvrootname rd.lvm.lv=vgname/lvrootname
dracut that needs to include lvm2 code and be able to activate such LV prior
switch to rootfs (having somewhere inside lvchange -ay vgname/lvrootname)
But it's not really clear how have you moved from your /dev/vda3 to
something on top of lvm2...
Regards
Zdenek
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2023-08-30 14:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 6:40 [linux-lvm] Trouble Booting Custom Kernel with QEMU: dracut-initqueue timeout waiting for /dev/sysvg/root Vishal Chourasia
2023-08-30 14:31 ` Zdenek Kabelac [this message]
2023-08-30 22:40 ` Vishal Chourasia
2023-08-31 10:14 ` Zdenek Kabelac
2023-09-07 7:30 ` Vishal Chourasia
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=3cc29b24-8283-478a-bce2-56c392556391@gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=linux-lvm@redhat.com \
--cc=vishalc@linux.ibm.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).