VFIO setup wont work (in ujust)

[Split7fire]

Describe the bug

Long story short:
ujust setup-vfio wont work until you manually append "kvm.report_ignored_msrs" to kargs. By default Bluefin-dx-nvidia have no such a karg, so this line of code never execute

bluefin/just/bluefin-system.just

Line 162 in 43e996a

if [[ ${VIRT_TEST} == *kvm.report_ignored_msrs* ]]; then

What did you expect to happen?

I expected ujust to just append needed modules to karg.

Output of bootc status

Current staged state is native ostree
Current booted state is native ostree
Current rollback state is native ostree

Output of groups

vlad wheel docker lxd incus-admin libvirt

Extra information or context

No response

[ledif]

Thanks for the report. This should be fixed with #2140.

[Split7fire]

Thanks for the report. This should be fixed with #2140.

Thanks, but I noticed one another bug: I can't use kvmfr0 (from lookinglass). because my user have no privilege to read /dev/kvmfr0.
Any advice?

[ledif]

Did you run ujust configure-vfio and select the "Enable kvmfr module" option? That should have run the /usr/libexec/bluefin-dx-kvmfr-setup script for you that should set the correct permissions and SELabels for /dev/kvmfr0.

What is the output of ls -l /dev/kvmfr0?

[Split7fire]

Did you run ujust configure-vfio and select the "Enable kvmfr module" option? That should have run the /usr/libexec/bluefin-dx-kvmfr-setup script for you that should set the correct permissions and SELabels for /dev/kvmfr0.

What is the output of ls -l /dev/kvmfr0?

Yeah, sure. It fails at last line:

bluefin/system_files/dx/usr/libexec/bluefin-dx-kvmfr-setup

Line 108 in 43e996a

rpm-ostree initramfs --enable

It fails with initramfs already enabled or something like that.
But everything before it went fine. Open new issue for that?

[ledif]

The initramfs already enabled message isn't really an error -- more of a notice. If everything else worked fine, then it can be ignored in my opinion.

[Split7fire]

The initramfs already enabled message isn't really an error -- more of a notice. If everything else worked fine, then it can be ignored in my opinion.

Yeah, agreed. But

I can't use kvmfr0 (from lookinglass). because my user have no privilege to read /dev/kvmfr0.

still persist

[m2Giles]

Did you enable kvmfr as well? The script should setup your user as owner with a udev rule and setup the SELinux requirements.

What is the output ls -lZ /dev/kvmfr0?

[Split7fire]

Did you enable kvmfr as well? The script should setup your user as owner with a udev rule and setup the SELinux requirements.

Yes, sure.

What is the output ls -lZ /dev/kvmfr0?

crw-rw----. 1 root qemu system_u:object_r:device_t:s0 239, 0 янв 12 09:51 /dev/kvmfr0

[m2Giles]

Edit the rule in /etc/udev/rules.d

Change where it says root to your username.

[Split7fire]

Edit the rule in /etc/udev/rules.d

Change where it says root to your username.

Ok, it considered as workaround? Will it survive updates?

[m2Giles]

Yes, it will not be wiped in an update.

The script created the file with user as root and not your username.

[Split7fire]

Yes, it will not be wiped in an update.

The script created the file with user as root and not your username.

So, it is expected behavior?

Edit the rule in /etc/udev/rules.d

Change where it says root to your username.

Now looking glass working, thanks for assistance.