Hi Phil,
thanks for the explanation. Honestly, I don't think that running the ISO on Cockpit should make any difference. These virtualization technologies (and Cockpit is using KVM AFAIK) should behave the same way. Thanks for the info, we will look on that.
Adding Katerina from Cockpit team just in case she would have better insight than me.
Best Regards, Jirka
Dne 26. 11. 22 v 18:56 Phil Reese napsal(a):
Hi Jirka,
I appreciate you took the time to reply! You probably have many letters of feedback!
To clarify, instead of using virsh and Virtual Machine Manager for making and using KVMs in Fedora, I primarily use the Cockpit tool It is described here: https://fedoramagazine.org/reconfiguring-virtual-machines-with-cockpit/ and whose web site is: https://cockpit-project.org/
Given that your project goal seems to be to make the install of Fedora easier, it would make sense to also have it work well with another tool whose purpose is to make Linux system admin and VM creation and management easier for the newer Linux user to handle.
When I mentioned VNC viewer I'm not referring to remote installations but rather a tool on the host system using Cockpit, which shows the console of a VM while it boots and/or installs the OS, via Anaconda. See pict below for more context
Thanks very much for your efforts to make Fedora a strong and easy to use distribution.
Phil
On 11/26/22 5:54 AM, Jiri Konecny wrote:
The second install using Cockpit was a bust. As has been with other F36 ISO installs in Cockpit. The major issue is that the many changed window sizes that the Anaconda process uses didn't work out well with the VNC viewer. The initial Language suggestion screen couldn't be used as the 'Next' box couldn't be clicked on, nor was it obvious that TAB stepped through all the options available (though I could be wrong, as I could only see the smallest top sliver of the blue box.)
Not sure what exactly you mean by "using Cockpit". Could you please explain this in bigger detail. Do you mean remote installations?
