minikube-iso: set CONFIG_QFMT_V2=y for aarch64

[zjx20]

If the option CONFIG_QFMT_V2=y is not set, the kernel prompts an error when attempting to use the project quota feature of ext4 in a minikube VM or minikube k8s cluster:

[ 9289.548970] EXT4-fs (loop0): The kernel was not built with CONFIG_QUOTA and CONFIG_QFMT_V2

The reproduction steps are as follows:

minikube start --driver=qemu2
minikube ssh

# inside the minikube shell
sudo bash -c su
cd /root
touch loop.img
truncate -s 1g loop.img
losetup -fP loop.img
devname=$(losetup -a | grep /root/loop.img | awk -F":" '{print $1}')
echo $devname  # <-- should be /dev/loop0 or something similar
mkfs.ext4 -O project,quota $devname
mkdir -p /root/mountpoint
mount -o prjquota $devname /root/mountpoint  # <-- ERROR, cannot mount the device with the prjquota option

Then check dmesg and you will see the error message mentioned earlier:

Please also notice that this option has been enabled in the x86_64 image:

minikube/deploy/iso/minikube-iso/board/minikube/x86_64/linux_x86_64_defconfig

Line 491 in 5af9a51

CONFIG_QFMT_V2=y

[k8s-ci-robot]

Welcome @zjx20!

It looks like this is your first PR to kubernetes/minikube 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/minikube has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @zjx20. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[minikube-bot]

Can one of the admins verify this patch?

[spowelljr]

ok-to-build-iso

[minikube-bot]

Hi @zjx20, we have updated your PR with the reference to newly built ISO. Pull the changes locally if you want to test with them or update your PR further.

[spowelljr]

/ok-to-test

[minikube-pr-bot]

kvm2 driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 17991) |
+----------------+----------+---------------------+
| minikube start | 53.6s    | 52.0s               |
| enable ingress | 25.2s    | 25.5s               |
+----------------+----------+---------------------+

Times for minikube start: 53.1s 51.0s 56.1s 56.0s 52.0s
Times for minikube (PR 17991) start: 53.1s 51.2s 51.3s 53.0s 51.6s

Times for minikube ingress: 25.6s 22.7s 27.0s 26.6s 24.0s
Times for minikube (PR 17991) ingress: 26.7s 24.0s 26.1s 26.0s 24.7s

docker driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 17991) |
+----------------+----------+---------------------+
| minikube start | 24.1s    | 23.7s               |
| enable ingress | 21.0s    | 22.0s               |
+----------------+----------+---------------------+

Times for minikube (PR 17991) start: 25.5s 23.2s 21.9s 23.1s 24.6s
Times for minikube start: 22.6s 25.0s 25.1s 25.9s 22.1s

Times for minikube ingress: 20.3s 22.9s 20.3s 21.4s 20.3s
Times for minikube (PR 17991) ingress: 28.3s 20.3s 20.4s 20.8s 20.3s

docker driver with containerd runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 17991) |
+----------------+----------+---------------------+
| minikube start | 21.8s    | 22.4s               |
| enable ingress | 37.4s    | 34.1s               |
+----------------+----------+---------------------+

Times for minikube start: 21.2s 21.0s 21.2s 23.7s 22.0s
Times for minikube (PR 17991) start: 23.5s 21.0s 21.3s 24.0s 22.2s

Times for minikube ingress: 47.8s 30.8s 31.8s 29.8s 46.8s
Times for minikube (PR 17991) ingress: 32.3s 30.8s 45.8s 30.8s 30.8s

[minikube-pr-bot]

These are the flake rates of all failed tests.

Environment	Failed Tests	Flake Rate (%)
KVM_Linux_crio	TestAddons/parallel/MetricsServer (gopogh)	3.82 (chart)
KVM_Linux_crio	TestFunctional/parallel/ImageCommands/ImageListShort (gopogh)	4.43 (chart)
Docker_Linux_containerd_arm64	TestStartStop/group/old-k8s-version/serial/SecondStart (gopogh)	30.86 (chart)

To see the flake rates of all tests by environment, click here.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: spowelljr, zjx20

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [spowelljr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment