I tried Wine, Wine in Bottles etc all fails. Never talk about it again.
I set up a virtual machine and that fails.
So let’s start with what works, using a QEMU as the virtual machine with a second graphics card and pass-through.
Why should anyone doing this start at what seems like the “extreme end” of solutions?
Because near ever other solution is going to fail to load software that seeks to detect a graphics card, which is pretty much anything serious.
Here are some issues with other approaches as that apply to using Rocky 9 with Wayland.
QEMU running Wayland using the default virtual is S L O W. I’m mean really slow. Like it refreshes in 1 cms squares per second. Completely unusable. Maybe if Spice is working that might be different but I haven’t managed to find a complete guide to doing that.
If you flip to X11 the performance is more normal. A bit slow but near usable.
Bug – The screen %, I’m working on 125% on UHD is reset in the switch between X11 and Wayland.
This set up won’t allow you to load software like SketchUp.
Currently, I’ve got 2 graphics cards, Radeon old and new, with one on a stub waiting for Windows. Both go to HDMI posts in the same monitor. Mouse and keyboard control go to the VM and Windows once started.
If I really need to get back to Linux I can pull out the USB and reset it to Linux. I think this can be done in software.
This is likely the best example of how to do this…
This is the best write up on how to do the gpu pass-through.
To go with this you need a method to share a folder between the 2 systems, I’m guessing SAMBA but it does look like there might be other options. And some as you go trouble shooting advice.
And I think it is valid to provide some other than “nano” advice on editing config files.
I’m using “#kate /etc/default/grub” etc that’s could be useful to people that are intimidated by nano etc.
I think it should be a Wiki page. It’s a bit of a PITA using lots of different instructions that are for different versions of Linux and make them work on Rocky without the knowledge in your head about the difference between this and that in the instructions.
I would say that it is a good idea to install Cockpit before you start and be able to run the journal so you can see errors as they occur.
This is probably the last piece of the puzzle to configure.
Really needs someone Rocky to write this up but I’m happy to help with that. I can at least qualify what is written as working on my system.
I’d say it would be something that would be interesting to write up as written all on the terminal and options for using the GUI. For example you can get the PCI information from the UI using About System/Devices/PCI
Basically it would be interesting to see the topic written up specifically for Rocky 9 KDE (narrow) but expanded with methods that are both terminal and GUI.