Bug 2085347

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

(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.

The v1 patch for fedora has been posted [1].

[1]: https://lists.fedoraproject.org/archives/list/kexec@lists.fedoraproject.org/thread/F6TEX2GSSC4GAJ5ZVY5WMGS66T7V52S4/

(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

(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

(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

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