Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding qemu arguments not working/broken #3895

Closed
vordenken opened this issue Apr 12, 2022 · 2 comments
Closed

Adding qemu arguments not working/broken #3895

vordenken opened this issue Apr 12, 2022 · 2 comments
Labels
interface Design, UX/UI issues
Milestone

Comments

@vordenken
Copy link

Describe the issue
I'm trying to launch a microOS VM and in order to configure it I add a qemu argument: -fw_cfg name=opt/org.opensuse.combustion/script,file=/var/combustion-script. For some reason this feature is completely broken at least on my machine. If I save it and reenter the menu, the entry is gone. If I add the entry and scroll up, it seems to be "accepted" because there is a up-arrow right next to it. If I add multiple arguments and save it, they are also somehow invisible because starting the VM no longer works (errors about the arguments pop up) but because they are invisible in the menu I can't remove them.

To reproduce:
Add new VM in UTM.
Go to the VM settings, choose "QEMU" and scroll to the bottom.
Add an argument
Press save
Open settings/qemu again -> Added argument is gone.
Try to run the VM -> UTM gets error because there's a argument that doesn't make sense.

Here is a screenshot:
The UTM menu doesn't show any entries but the VM fails because of them.

Bildschirmfoto 2022-04-12 um 16 50 27

Configuration

  • UTM Version: 3.1.5
  • OS Version: 12.3.1
  • Intel or Apple Silicon? Apple

Crash log
Nothing is crashing.

Debug log
Also nothing interesting here, only that my arguments are not right. (Because they are there multiple times but invisible in the menu)

Upload VM
Its the basic microOS aarch64 raw image. I had this problem also with fedora coreOS. Don't think this has to do with the vm.

@fmontagut
Copy link

fmontagut commented Apr 19, 2022

I also experienced the same behaviour. It happens only on new created VM, and only when you create the first row of custom settings. The way I have circumvented this issue is, clicking save, entering on settings->QEMU again, adding further lines and moving them up so your initially created line moves to the bottom and you can see it and you can delete it.

@adespoton
Copy link

My experience has been that the line gets saved, but you may not see it when you re-open the tab... scrolling down and up a few times causes it to show up.

@osy osy added the interface Design, UX/UI issues label Apr 23, 2022
@osy osy added this to the v3.2 milestone Apr 23, 2022
@osy osy closed this as completed in 9050fe3 Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
interface Design, UX/UI issues
Projects
None yet
Development

No branches or pull requests

4 participants