Promote Qemu priority from "experimental" to "preferred"

[kloseliebej]

Fixes #15316

Promoted to "preferred" because qemu is similar to kvm which is preferred, but open to other options.

Testing:

1. Unit tests passed
2. Tested locally using command "minikube start", though not seeing the options, probably because I don't have a M1 chip.

[linux-foundation-easycla]

• ✅ login: kloseliebej / name: Yiwei Li (bfa81b4)
• ❌ The commit (560a840). This user is missing the User's ID, preventing the EasyCLA check. Consult GitHub Help to resolve.For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

Welcome @kloseliebej!

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 @kloseliebej. 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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kloseliebej
Once this PR has been reviewed and has the lgtm label, please assign prezha for approval by writing /assign @prezha in a comment. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[minikube-bot]

Can one of the admins verify this patch?

[afbjorklund]

Should start out as registry.Default

[kloseliebej]

Changed it to "default", though not sure how to fix this error

[medyagh]

@kloseliebej thanks for this contribution, the reason it is not working for you in the logs shows, because you have an existing cluster with a different driver, that you would need to delete first

[medyagh]

@kloseliebej thanks for this contribution, the reason it is not working for you in the logs shows, because you have an existing cluster with a different driver, that you would need to delete first

[medyagh]

Changed it to "default", though not sure how to fix this error

Seems like your first commit was pushed before signing the CLA so your would need to rebase and and force push your commit history :)

[spowelljr]

Completed in #15556