VM's should be allowed #236
Replies: 3 comments 1 reply
|
The policy exists because of historical precedent.
A "continue anyway" option does not solve the issue, because the problem is not there. That said, you can continue using it. However, the policy regarding using Nitrux as a guest OS in a VM will not change. |
|
@UriHerrera thanks for commenting. Very detailed but I was hoping for a more flexible stance, I have to say.
Sorry to disagree but currently, there is a problem, otherwise I wouldn't have raised it for discussion.
Well, I made the effort and looked again. Instead of clicking the 'ok' button on the 'Nitrux is going to reboot now' dialog, I sidestepped to workspace two and left the shutdown dialog still open. That kind of worked but that then meant that there weren't any installer options ....
Then I suppose that I will have to change instead?
This is all a bit of a pity as Nitrux seems to be quite an interesting project:
|
|
@UriHerrera It's been quite an interesting last 3 weeks and you have done some great work. Your guidance and annotated screen grabs were very useful. I was able to get Nitrux running quite nicely using some of qqX's built-in features:
I can understand your decision to pull Hyper-V support as I imagine you probably had a lot of inexperienced people trying to boot Nitrux on Windows as a lightweight VM Steam platform ... From my perspective though, being able to run up Nitrux and put it through a few basic paces has been of great value. I have quite enjoyed having a look at a full running example of KDE's Maui project. My experience with Garuda's Hyprland distro was helpful with working out where Hyprland finished and Maui started, although it was a bit tricky in places I have to say. Using the Qemu NBD mount system, I was able to install and test several different types of script, and in the light of which I made several changes to my work. I was also able to manually install qqX onto the Nitrux VM: The main interfaces loaded up correctly and almost all the dependencies were already there. I was quite surprised to see Qemu was pre-installed and waiting. I was able to auto-download distros and assemble the VMs, but what I wasn't able to do was actually run them. The one critical package that was missing was Debian's spice-client-gtk The other missing package was genisoimage. Having this would have meant being able to install and run Windows the other way round, ie on top of Nitrux. So, all of the above can be achieved using standard Qemu command line invocations. There is no obligation for anyone referring to this discussion to use the qqX VM manager in the slightest. For this reason, and for the reason of it being very Nitrux focused, it felt a bit pointless replicating the whole of this discussion on the qqX pages. It seems to be more a Nitrux VM discussion, to me (??) I have placed pop-up comments in qqX for users wanting give Nitrux a quick spin and given them a link to this discussion, for those wanting more details, eg: elif [[ "${VM_InstanceName,,}" == *nitrux* ]]; then
printf "\n\n TO RUN, side step to workspace 2 - See https://github.com/orgs/Nitrux/discussions/236 for more details."Currently this in release candidate stage. If you would like me to change this, please let me know. Cheers, Alex. |





Uh oh!
There was an error while loading. Please reload this page.
I wanted to test how a program that I have written might work with Nitrux.
I got the message that Virtual machines might not work too well. Also the bit about Spice and drivers .
But, the thing is, I was using SDL not Spice, and the VM system that I use allows drivers to be be side loaded ...
So, Nitrux shut me down and I wasn't even allowed to see if I could get the OS to work.
I think there should be a 'continue anyway' option. If there's not, how can anyone even try to check if new programs will work.
All reactions