-
-
Notifications
You must be signed in to change notification settings - Fork 480
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
feat: ensure FreeBSD support is a good as it can be #926
Comments
Could not init `pa' audio driver |
I think that the problem is that I'm using pipewire...
|
as root I get a different error :
|
I am not seeing this as an issue. It doesn't replicate. Mario, your system looks in serious need of security updates. You are running qemu 7.2.5 while the current version on Ubuntu 23,10 is now at 8.0.4 ... You shouldn't being running things in root either. Certainly not quickemu. Update your computer. Test that a VM of Ubuntu 23.10 will work on your Ubuntu HOST. Then try FreeBSD. Also try the DVD version too. |
I don't know why,but I had two qemu-system-x86_64 executable versions installed and the default one was the older. ziomario@Z390-AORUS-PRO-DEST:~/Scaricati/OS$ quickemu --vm freebsd-14.0-disc1.conf Quickemu 4.9.1 using /usr/local/bin/qemu-system-x86_64 v8.0.4
Can I ask for some improvements to be added by default ? For example :
|
Ctrl Alt G is part of the SDL window. You can also try Spice. Shift F12. It's the way you SSH into the display server ... It's the same with all VM's. There's no obligation to use qqX but using this as a front end makes this all a lot easier. You can easily switch displays and lots of other things. I am currently finishing up on a system that allows you to easily customise your boot scripts too. Out probably next week. If not before. |
---> Ctrl Alt G is part of the SDL window. You can also try Spice. Shift F12. It's the way you SSH into the display server ... It's the same with all VM's. Maybe I didn't explain well. Even if I press SHIFT F12,it's annoying the same,because everytime I want to switch from the host os to the guest,I should press those keys. Instead,using "-usb -device usb-kbd -device usb-tablet" the mouse makes some kind of passthrough between them,without the obligation to press those keys. ---> There's no obligation to use qqX but using this as a front end makes this all a lot easier. You can easily switch displays and lots of other things. It makes no sense to configure qemu with "Display: qxl-vga" if the driver does not work within FreeBSD. I'm sure that a different display (supported by qemu and FreeBSD) will enable startx and a decent windows manager like xfce to work well. Inside FreeBSD there is the driver called "xf86-video-vmware" ; If I remember well,qemu also supports the vmware driver. If you want to recompile qemu and enable virGL on your quickemu by default,I wil do the rest,I mean I will try to configure it within FreeBSD. |
Are you look at barrier? That maybe solve you annoyance |
Yes,I know barrier. But do you want that I pass from the annoyance A to the annoyance B ? Barrier should be configured everytime I (we) want to create a new vm. More than one problem for me,I'm trying to explain to you how you can make the life easier to everyone who wants to use your tool. For example,I've added the parameters below to the file : freebsd-14.0-disc1.sh and voila',there is no more need to press any key to pass the mouse from the host to the guest. Just try and see if it works. If it works,please add these values by default in the appropriate place of your tool. Don't think to what I can do to tweak your script,think what YOU can do to make a better product : just add these :
and remove this :
|
@Marietto2008 Learning something from you today, possibly. I didn't know it was actually possible to bypass the separated window thing. I was always under the impression that this is one of the key elements to VM isolation and sand-boxing. But we are running type 2 VM's here and host pass-through is enabled to some extent, I suppose. You may be able to solve your current problem by using the .sh file that quickemu spits out into the VM folder. This file tends to cause a lot of confusion as Quickemu doesn't actually use it. But if you place a copy of it next to your .conf file and chmod +x, you can edit the device spec as per qemu invocation and boot from there. I have noticed that you have been involved VM work on Arm processors. https://github.com/mobile-virt/arm-xen-kvm The last bit of my work on custom scripts is getting Debian Arm ISO working with qqX. Then I need to make a Wiki, also explaining about how to do similar with RiscV, which I have already managed to do. You may be able to help, a bit later on, I think. 🤣 Quickemu is just a front end for Qemu. It does have it's flaws. We are currently working on how to make it the code better. If you would like to contribute, there's a lengthy discussion that sprang up on the issue here: TuxVinyards/qqX#4 |
Yeah,after a long training to learn how to virtualize any OS available for the x86_64 cpus using almost all the tools available,I have switched to the arm cpus to continue to have fun. Qemu-kvm is the first choice,but later I discovered how fun is to play with bhyve under FreeBSD and xen under arm 32 and arm 64. Actually I'm trying to boot FreeBSD as a domU when dom0 is Devuan,on my old ARMv7 Chromebook. Unfortunately it seems that xen is bugged and can't boot FreeBSD. No problems for Linux. I've bought the Raspberry p 4B because I want to do the same experiment there. Maybe I will be luckier with Arm 64 bit. I'm also working on a more interesting project. I've bought some old smartphones with Android preinstalled. These phones are special because we can bypass the bootloader protection and we can virtualize FreeBSD with kvm or xen,leaving 1 core for Android and the rest will go to FreeBSD. I love FreeBSD,I want to put it everywhere :D |
Coming back to your quickemu,I tried to point your attention to these two points below,but you have ignored them,but I find it interesting to talk about them : ---> It makes no sense to configure qemu with "Display: qxl-vga" if the driver does not work within FreeBSD. I'm sure that a different display (supported by qemu and FreeBSD) will enable startx and a decent windows manager like xfce to work well. Inside FreeBSD there is the driver called "xf86-video-vmware" ; If I remember well,qemu also supports the vmware driver. ---> If you want to recompile qemu and enable virGL on your quickemu by default,I wil do the rest,I mean I will try to configure it within FreeBSD. Those are two great improvements for your quickemu that will make the life easier for the FreeBSD users. Do you want to collaborate in this area ? Infact quickemu tells me that VirGL is off by default. I think you should use the qemu installed on the users PC and recompile it to enable it by default : Display: SDL, qxl-vga, GL (on), VirGL (off) |
Quickemu doesn't normally use qxl-vga when booting the VMs. It must be something to do with the way Wimpy / @flexiondotorg has set things up to work with FreeBSD. Unfortunately Wimpy seems to be being pulled in too many directions these days .... This why I said about a using a custom boot and about the discussion that some of us are currently having about ways to move forward. Your point is noted about QXL. Although, when I tried, evidence in screenshot, QXL loaded and seemed to work fine for me (?)
The basic idea that Wimpy had was to make a simple front end script that used standard everyday builds and got most things working. I haven't the foggiest idea whether VirGL is enabled or not 🤣 I am just using the standard Ubuntu build. I haven't had any problems so far. |
---> Your point is noted about QXL. Although, when I tried, evidence in screenshot, QXL loaded and seemed to work fine for me (?) It worked for you under FreeBSD 14.0-RELEASE ? ---> I am just using the standard Ubuntu build. I'm talking about the specific configuration for FreeBSD 14-RELEASE,that's different than the one for Ubuntu. |
So 13.3 and lower are not affected? @Marietto2008 |
Trying... |
@Marietto2008 You should be able to use any commands with quickemu As in README.md So if you have qemu builded with support, here shouldn't be problem. But freebsd 14 is evidently bugged.. |
So,for 14-RELEASE,maybe this works :
in any case,again,don't ask me to add a new parameter by my side. If the goal of your tool is to offer pre made configurations for a fast usage,you should add it by YOUR side. |
sure just solution meanwhile will be resolved upstream PS: I am thinking about anyone reading this trying freebsd... PPS: I am pretty sure that you don't need quickemu at all... PPPS: Not really "my" tool, but I am contributing 😉 |
---> PPS: I am pretty sure that you don't need quickemu at all... I can use it if it will work as I want... |
Not touched quickemu to much yet so I am not familiar with. But I have to learn it anyway so I will investigate more... PS: But since we can't merge any PR without @flexiondotorg. It isn't only on me and @TuxVinyards |
So work good or is frozen? |
But you didn't answer my question (or I missed that?) Is it affecting more versions (BSDs), or only freebsd 14.0? You tried older/different BSD or not? |
I didn't try if qxl works with 13.2,but who cares if vmware-svga works better ? :D |
The display resolution can be set using `--width` and`--height` for macOS and *BSD. - close quickemu-project#926 - close quickemu-project#1202
The display resolution can be set using `--width` and`--height` for macOS and *BSD. - close quickemu-project#926 - close quickemu-project#1202
The text was updated successfully, but these errors were encountered: