RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2085347 - [RFE] kdump: support dump to virtiofs
Summary: [RFE] kdump: support dump to virtiofs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: kexec-tools
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: ltao
QA Contact: Jie Li
Sujata Kurup
URL:
Whiteboard:
Depends On:
Blocks: 1967958
TreeView+ depends on / blocked
 
Reported: 2022-05-13 04:39 UTC by Dave Young
Modified: 2023-06-05 01:35 UTC (History)
10 users (show)

Fixed In Version: kexec-tools-2.0.25-3.el9
Doc Type: Enhancement
Doc Text:
.`virtiofs` support for `kexec-tools` enabled This enhancement adds the `virtiofs` feature for `kexec-tools` by introducing the new option, `virtiofs myfs`, where `myfs` is a variable tag name to set in the `qemu` command line, for example, `-device vhost-user-fs-pci,tag=myfs` The `virtiofs` file system implements a driver that allows a guest to mount a directory that has been exported on the host. By using this enhancement, you can save the virtual machine's `vmcore` dump file to: * A `virtiofs` shared directory. * The sub-directory, such as `/var/crash`, when the root file system is a `virtiofs` shared directory. * A different `virtiofs` shared directory, when the virtual machine’s root file system is a `virtiofs` shared directory.
Clone Of:
Environment:
Last Closed: 2023-05-09 08:14:41 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-121929 0 None None None 2022-05-13 04:41:03 UTC
Red Hat Product Errata RHBA-2023:2463 0 None None None 2023-05-09 08:14:55 UTC

Comment 7 xiagao 2022-05-17 02:05:16 UTC 
I list some basic virtiofs usage, you can have a reference.

1. virtiofs as root filesystem
For this one, you can refer to the following test case in polarion.
https://polarion.engineering.redhat.com/polarion/#/project/RHELVIRT/workitem?id=RHEL-272816
As you know, there is an open bug for dracut to support virtiofs, so the steps are just a workaround.

2. vmcore can be seen on host side without nfs setup/extra copy
The following polarion case is for this scenario, I think you can first setup virtiofs according to this.
https://polarion.engineering.redhat.com/polarion/#/project/RHELVIRT/workitem?id=RHEL-182379


Besides, Virtiofs only support RHEL8.2 (kernel-4.18.0-149.el8.x86_64) and later.
And for RHEL9.0, virtiofsd pkg is needed.

Here are some docs you can refer to.
https://libvirt.org/kbase/virtiofs.html 
https://virtio-fs.gitlab.io/howto-qemu.html
Comment 10 Vivek Goyal 2022-05-17 13:25:37 UTC 
(In reply to xiagao from comment #7)
> I list some basic virtiofs usage, you can have a reference.
> 
> 1. virtiofs as root filesystem
> For this one, you can refer to the following test case in polarion.
> https://polarion.engineering.redhat.com/polarion/#/project/RHELVIRT/
> workitem?id=RHEL-272816
> As you know, there is an open bug for dracut to support virtiofs, so the
> steps are just a workaround.
> 
> 2. vmcore can be seen on host side without nfs setup/extra copy
> The following polarion case is for this scenario, I think you can first
> setup virtiofs according to this.
> https://polarion.engineering.redhat.com/polarion/#/project/RHELVIRT/
> workitem?id=RHEL-182379
> 
> 
> Besides, Virtiofs only support RHEL8.2 (kernel-4.18.0-149.el8.x86_64) and
> later.
> And for RHEL9.0, virtiofsd pkg is needed.
> 

In RHEL8 we are using C virtiofsd which is part of qemu. In RHEL9.0 we are using rust based virtiofsd which is a package of its own.

Development on C version of virtiofsd is more or less frozen. So let us focus on rust virtiofsd instead.

Right now rust virtiofsd is being packaged for fedora. 

So let us just take fedora VM, configure virtiofs and try to make kdump work. And upstream fixes in various components as needed.
Comment 11 ltao 2022-08-05 09:45:29 UTC 
The v1 patch for fedora has been posted [1].

[1]: https://lists.fedoraproject.org/archives/list/kexec@lists.fedoraproject.org/thread/F6TEX2GSSC4GAJ5ZVY5WMGS66T7V52S4/
Comment 26 ltao 2022-11-09 04:01:16 UTC 
(In reply to xiagao from comment #7)
> I list some basic virtiofs usage, you can have a reference.
> 
> 1. virtiofs as root filesystem
> For this one, you can refer to the following test case in polarion.
> https://polarion.engineering.redhat.com/polarion/#/project/RHELVIRT/
> workitem?id=RHEL-272816
> As you know, there is an open bug for dracut to support virtiofs, so the
> steps are just a workaround.
> 
> 2. vmcore can be seen on host side without nfs setup/extra copy
> The following polarion case is for this scenario, I think you can first
> setup virtiofs according to this.
> https://polarion.engineering.redhat.com/polarion/#/project/RHELVIRT/
> workitem?id=RHEL-182379
> 
> 
> Besides, Virtiofs only support RHEL8.2 (kernel-4.18.0-149.el8.x86_64) and
> later.
> And for RHEL9.0, virtiofsd pkg is needed.
> 
> Here are some docs you can refer to.
> https://libvirt.org/kbase/virtiofs.html 
> https://virtio-fs.gitlab.io/howto-qemu.html

Hi xiaogao,

Currently we only tested virtiofs support for kdump on qemu-kvm. However we don't know if virtiofs support other virtualization platforms and should be tested as well. For example, does virtiofs support PowerVM on ppc arch, and did you test it before?

Thanks,
Tao Liu
Comment 28 xiagao 2022-11-14 01:32:56 UTC 
(In reply to ltao from comment #26)
> (In reply to xiagao from comment #7)
> > I list some basic virtiofs usage, you can have a reference.
> > 
> > 1. virtiofs as root filesystem
> > For this one, you can refer to the following test case in polarion.
> > https://polarion.engineering.redhat.com/polarion/#/project/RHELVIRT/
> > workitem?id=RHEL-272816
> > As you know, there is an open bug for dracut to support virtiofs, so the
> > steps are just a workaround.
> > 
> > 2. vmcore can be seen on host side without nfs setup/extra copy
> > The following polarion case is for this scenario, I think you can first
> > setup virtiofs according to this.
> > https://polarion.engineering.redhat.com/polarion/#/project/RHELVIRT/
> > workitem?id=RHEL-182379
> > 
> > 
> > Besides, Virtiofs only support RHEL8.2 (kernel-4.18.0-149.el8.x86_64) and
> > later.
> > And for RHEL9.0, virtiofsd pkg is needed.
> > 
> > Here are some docs you can refer to.
> > https://libvirt.org/kbase/virtiofs.html 
> > https://virtio-fs.gitlab.io/howto-qemu.html
> 
> Hi xiaogao,
> 
> Currently we only tested virtiofs support for kdump on qemu-kvm. However we
> don't know if virtiofs support other virtualization platforms and should be
> tested as well. For example, does virtiofs support PowerVM on ppc arch, and
> did you test it before?

Needinfo xuma here as he is the virtiofs feature owner on ppc arch.

> 
> Thanks,
> Tao Liu
Comment 29 lijin 2022-11-16 06:56:03 UTC 
(In reply to xiagao from comment #28)
> > 
> > Hi xiaogao,
> > 
> > Currently we only tested virtiofs support for kdump on qemu-kvm. However we
> > don't know if virtiofs support other virtualization platforms and should be
> > tested as well. For example, does virtiofs support PowerVM on ppc arch, and
> > did you test it before?

We only test kvm, PowerVM is not tested.

> Needinfo xuma here as he is the virtiofs feature owner on ppc arch.
> 
> > 
> > Thanks,
> > Tao Liu
Comment 37 errata-xmlrpc 2023-05-09 08:14:41 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (kexec-tools bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2463
Note You need to log in before you can comment on or make changes to this bug.