I'm getting "Error setting installer parameters" while attempting to set up a new VM in Virtual Machine Manager [SOLVED]
EDIT: tldr - I was having issues creating a VM using Virtual Machine Manager on Bazzite Linux. Several responders chimed in that it's likely because I'm using the flatpak version of VMM. I probably still could make it work on Bazzite somehow, perhaps w/ the help of distrobox, but instead I've fired up a VM on an old laptop running Linux Mint and everything is smooth sailing. Thanks to all who took some time to help me find a solution.
Original body:
Background: I'm looking to set up a virtual Debian server using Virtual Machine Manager, but I'm stuck on creating my first VM. I'm running Bazzite on my host machine if that makes any difference.
Steps to Reproduce the Issue:
- Launch Virtual Machine Manager.
- Click File > New Virtual Machine, which opens the "New VM - Step 1" window.
- Select "Local install media" and click Forward, which brings me to "New VM - Step 2."
- Click "Browse..." which opens the "Locate ISO media volume" window:
- Click "Browse Local," which opens the file browser.
- Choose ISO file (in my case, I'm using
debian-12.11.0-amd64-netinst.iso
) and click Select, which returns me to the "New VM - Step 2" window. - Because the OS is not detected automatically, I uncheck the "Automatically detect from the installation media / source" checkbox, start typing the word "debian" in the text box above it, and select Debian 12 from the pop-up selection menu.
- Click Forward.
Actual behavior:
Input Error - Error setting installer parameters. Validating install media '/run/user/1000/doc/c0a3c3fc/debian-12.11.0-amd64-netinst.iso' failed. Could not start storage pool: cannot open directory '/run/usr/1000/doc/c0a3c3fc': Permission denied.
Expected behavior: Create the VM and boot into the ISO that I selected in previous steps.
What am I doing wrong? Thanks!
yo_scottie_oh
Unknown parent • • •I copied the ISO file to my home directory but got the same result. Any other ideas?
EDIT: I got past this issue by opening up Flatseal and granting access to all system files for Virtual Machine Manager; however, now I'm getting stuck on another permission issue after I choose how much RAM, CPU, and disk space to allocate. Reference my response to @ormith@lemmy.world's comment.
dengtav
in reply to yo_scottie_oh • • •And check the permissions of the image it self, maybe thats the issue
Balinares
in reply to yo_scottie_oh • • •yo_scottie_oh
in reply to Balinares • • •Here are the results of some commands that I believe answer your questions. When I run the
ls
command against that directory, it says no such file or directory. Could this have something to do w/ the fact that Virtual Machine Manager is running as a flatpak? (as the other commenter @ormith@lemmy.world has hinted)Here's what I tried:
EDIT: I got past this issue by opening up Flatseal and granting access to all system files for Virtual Machine Manager; however, now I'm getting stuck on another permission issue after I choose how much RAM, CPU, and disk space to allocate. Reference my response to @ormith@lemmy.world's comment.
ormith
in reply to yo_scottie_oh • • •Try using flatseal to give it direct access to all files.
yo_scottie_oh
in reply to ormith • • •Thanks - this got me past the original issue. What I did is I opened up Flatseal and granted access to all system files for Virtual Machine Manager.
However, now I'm stuck at a different point. I can get past where I choose how much memory, CPU, and disk storage to allocate, but when I get to Step 5 and click Finish,
This happens:
This message is talking about permission denied, so I checked the file permissions, and I saw that the ISO file is owned by the qemu user:
I changed it to myusername:
When I tried the same steps again, I got stuck in the same place and rerunning
ls
showed that the ISO file's ownership has reverted back toqemu
.Any ideas?
ormith
in reply to yo_scottie_oh • • •No idea. Since the path is a /run/media one, what's the filesystem used there? Perhaps it's incompatible. Have you tried putting the iso in your home directory and going from there instead?
But perhaps it would work best if you just do what the documentation tells you not to do and rpm-ostree install virt-manager (and libvirt and friends, if needed)
Mordikan
in reply to yo_scottie_oh • • •HayadSont
in reply to yo_scottie_oh • • •Virtual Machine Manager's GitHub page for its flatpak includes the following lines:
So, in this case, have you either installed libvirtd on the host^[Technically, you could also install libvirtd as a sysext.] (i.e. have you installed it with
rpm-ostree
) OR have you installed the QEMU extension as per its own instruction?If neither, then you should at least do one of them and report back.
EDIT: While what's written above remains relevant beyond Bazzite, Bazzite's ujust scripts do provide handholds for a myriad of situations including this one:
ujust
script will likely install another instance of VM Manager. As such, the flatpak is no longer needed and would only cause confusion.] the flatpak of Virtual Machine Manager)ujust
, i.e. invoke theujust setup-virtualization
commandI suppose the
ujust
way handles a bunch of gotchas you'd otherwise have to tackle yourself. And, thus, is most likely preferred over all other methods.As a side note, please consider consulting Bazzite's excellent documentation first. We'll be more than happy to help out regardless, but I'm sure there are a bunch of gems you'll be missing out on otherwise.
ujust - Bazzite Documentation
docs.bazzite.gg