Compile failure on Fedora 29. u2mfn missing.

[Public Email Account]

I am getting errors when attempt to compile using qubes-builder.

This is the output

#BEGIN OF LOG

make: Leaving directory '/home/user/rpmbuild/BUILD/kernel-4.19.34/linux-4.19.34'

+ rm -f source

+ find . '!' -type d -printf '%P\n'

++ dkms status u2mfn

++ tail -n 1

++ tr -d :,:

++ cut -f 2 -d ' '

+ u2mfn_ver=

+ rm -rf /home/user/rpmbuild/BUILD/u2mfn

+ cp -r /usr/src/u2mfn- /home/user/rpmbuild/BUILD/u2mfn

cp: cannot stat '/usr/src/u2mfn-': No such file or directory

error: Bad exit status from /var/tmp/rpm-tmp.RyLsDj (%prep)

RPM build errors:

    Bad exit status from /var/tmp/rpm-tmp.RyLsDj (%prep)

make[2]: *** [/home/qubesbuilder/qubes-builder/qubes-src/builder-rpm/Makefile-legacy.rpmbuilder:71: dist-package-build] Error 1

make[2]: Leaving directory '/home/qubesbuilder/qubes-builder'

make[1]: *** [Makefile.generic:180: packages] Error 1

make[1]: Leaving directory '/home/qubesbuilder/qubes-builder'

make: *** [Makefile:231: linux-kernel-dom0] Error 1

#END OF LOG

I found this thread which looks like it has relevant information

https://groups.google.com/forum/#!msg/qubes-users/yBeUJPwKwHM/D407feX6CAAJ

u2mfn appears to be missing. I am using Fedora 29. I do not have the ability to use Qubes to compile Qubes because I dont have Qubes. This is why Im trying to compile Qubes.

Can someone recommend how to get the needed files on Fedora required for qubes-builder that I might be missing?

Thank you

Sent with ProtonMail Secure Email.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

This isn't about your host Fedora system. qubes-builder use isolated
chroot environment for the build and this is where u2mfn module is
missing. Check beginning of the log to see what have happened, the
module should be installed as part of qubes-kernel-vm-support package.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlzCSRkACgkQ24/THMrX
1yzV6AgAiBg+VYm99fzFKTanKMs+enzYxgDsqob+hbANMVHS2xQ8htf5sBnGgNdr
eeKXmQXx8gj5lRsCvQcTY4u0zqsqsH7oI/LmB7spfy8MzCfli/ewbHti6WGuDgRI
RpfhSOvD+rTnIKq0QgsVw8LBBR5IXj7+qQAKCeg7gblttT44JLRxnlTGAO6Qywdv
DXL0mPDuE9mPlOq96Gf7e2d3t7Tn1qxBXz7H5AB7vfh9koTFCnQl8ypqzvnM93ow
LTOkoqX0Oyck+v3LVMC9WBoFZ5RJyE0+62nJKh99lmjxbk+cKBeBXQCQmlQxxC+K
+/7ZtSwfRDW9PLBH0s7VlTLWURrzkA==
=TZSt
-----END PGP SIGNATURE-----

[Public Email Account]

> This isn't about your host Fedora system. qubes-builder use isolated
> chroot environment for the build and this is where u2mfn module is
> missing. Check beginning of the log to see what have happened, the
> module should be installed as part of qubes-kernel-vm-support package.
>

Im glad you mention chroot.
It seems like it fails because it is not detect the u2mfn version so
it is looking for u2mfn- folder which does not exist. In the filepath
/qubes-builder/chroot-dom0-fc29/usr/src I have a folder named
"u2mfn-4.0.23" not "u2mfn-"
If the build script was working properly it would append the version
to the end of u2mfn- and be able to find it correctly.

If I am correct the file
/qubes-builder/chroot-dom0-fc29/usr/sbin/qubes-prepare-vm-kernel
appears to have the command that detects u2mfn version.
On line 30 of this file I see
u2mfn_ver=`dkms status u2mfn|tail -n 1|cut -f 2 -d ' '|tr -d ':,'`

I made a try to fix this issue where not detect version.
I changed the line to be
u2mfn_ver=`4.0.23`
then I reran "make qubes". This still fails because that file with
my correction gets overwritten to original version of qubes-prepare-vm-kernel
everytime "make qubes" gets ran.

Does anyone have recommendation?

Thank you

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sun, Apr 28, 2019 at 02:10:13AM +0000, 'Public Email Account' via qubes-devel wrote:
>
> > This isn't about your host Fedora system. qubes-builder use isolated
> > chroot environment for the build and this is where u2mfn module is
> > missing. Check beginning of the log to see what have happened, the
> > module should be installed as part of qubes-kernel-vm-support package.
> >
>
> Im glad you mention chroot.
> It seems like it fails because it is not detect the u2mfn version so
> it is looking for u2mfn- folder which does not exist. In the filepath
> /qubes-builder/chroot-dom0-fc29/usr/src I have a folder named
> "u2mfn-4.0.23" not "u2mfn-"
> If the build script was working properly it would append the version
> to the end of u2mfn- and be able to find it correctly.
>
> If I am correct the file
> /qubes-builder/chroot-dom0-fc29/usr/sbin/qubes-prepare-vm-kernel
> appears to have the command that detects u2mfn version.
> On line 30 of this file I see
> u2mfn_ver=`dkms status u2mfn|tail -n 1|cut -f 2 -d ' '|tr -d ':,'`
>
> I made a try to fix this issue where not detect version.

If the above doesn't list the proper version, it means u2mfn module
isn't properly registered in dkms. It should be done at module
installation time (by qubes-kernel-vm-support package), but if it
failed, you can do that manually:

chroot chroot-dom0-fc29 dkms add -m u2mfn -v 4.0.23

> I changed the line to be
> u2mfn_ver=`4.0.23`
> then I reran "make qubes". This still fails because that file with
> my correction gets overwritten to original version of qubes-prepare-vm-kernel
> everytime "make qubes" gets ran.

You can avoid full rebuild by building selected components -
specifically skipping those you've already built. "make help" will
display the full list, so you can start with linux-kernel, which is the
failing one:

make linux-kernel artwork gui-common gui-daemon ...

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlzFDtgACgkQ24/THMrX
1ywL6wf/TBAY7Y5imX6Lz6ZIqS6KxbXZjT27s2cosOEOH/XlsqrEcWniQAQ7RxnG
2AWL7hQfE+zT8kVCl+fhN/rqKq0/d7uummPtNxqvXXp6J5K87UHvXu7axbmaaPRa
DpGqNM06ONrO3SyOfklLStRJteY6F/kHvkHXKlcBiCziQtXKFTU7tCGQbWe4Z5Mf
UomDLFrflgZ9hfxfl9fw+5JvFNtPnMRogk5aAVaBU6dtcIrTCZpaJRSigussr7VI
uSae1VXLlH7rmmFbECW4YDxYS5VxxyP7ntuHHvu7FpTm7XpMKVgYKVgfsPWh+pQ+
AQOT/FKBrHQykxUMyKEowog9GnVA6Q==
=oF0M
-----END PGP SIGNATURE-----

[Public Email Account]

> If the above doesn't list the proper version, it means u2mfn module
> isn't properly registered in dkms. It should be done at module
> installation time (by qubes-kernel-vm-support package), but if it
> failed, you can do that manually:
>
> chroot chroot-dom0-fc29 dkms add -m u2mfn -v 4.0.23
>

Thank you this was very helpful and fixed the issue. If I did this command
to early it would reset the adding of u2mfn to dkms. To get this command to
work I had to wait until the file
qubes-builder/chroot-dom0-fc29/usr/sbin/qubes-prepare-vm-kernel was generated
then I ran command chroot chroot-dom0-fc29 dkms add -m u2mfn -v 4.0.23

[Public Email Account]

I think part of the issue was that I was trying to build Qubes 4.1 which seems to be unstable.
Building Qubes 4.0 has much more stable.
I still ran into some issues but found a solution for them.
I posted information on qubes-users with solution.