Skip to content
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

Update Readme.md to specify operating system compatibility in Virtual x86 #926

Merged
merged 2 commits into from
Sep 21, 2023
Merged

Update Readme.md to specify operating system compatibility in Virtual x86 #926

merged 2 commits into from
Sep 21, 2023

Conversation

spetterman66
Copy link
Contributor

Read the title to see what this PR is about :)

Readme.md Outdated
- Slax works.
- AntiX works
- Fedora 30 works.
- Zorin OS 12.6 works.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't really need to name every Linux distribution. How about just Fedora, the is based on Debian or Ubuntu anyway.

@spetterman66
Copy link
Contributor Author

spetterman66 commented Sep 20, 2023 via email

@spetterman66
Copy link
Contributor Author

better?

@copy
Copy link
Owner

copy commented Sep 20, 2023

Looks good now. That said, does Fedora 30 actually work?

@spetterman66
Copy link
Contributor Author

yes. see the screenshots i posted in the gitter discussion channel

@copy
Copy link
Owner

copy commented Sep 20, 2023

I can't reproduce it, does only the LXDE version work?

@spetterman66
Copy link
Contributor Author

spetterman66 commented Sep 20, 2023

What specifications have you allocated to the virtual machine? Give it 2048MB RAM, 128MB VRAM, and keep ACPI off (Because it's not required for correct operation). Use the boot arguments loglevel=7 earlyprintk=serial,keep for best verbosity (By pressing the tab key on the boot options screen), and to get info where it gets stuck at.

@spetterman66
Copy link
Contributor Author

spetterman66 commented Sep 20, 2023

As you can see in the screenshot below, Fedora 30 (i386, LXDE) works fine in Virtual x86. I have not tried other spins. (BTW, loading desktop, but it loaded cursor so it works :)
image

@copy
Copy link
Owner

copy commented Sep 20, 2023

Does it work correctly? I wouldn't expect any distro (not even bloated ones) to take more than a few minutes to boot.

@BelleNottelling
Copy link
Contributor

Does it work correctly? I wouldn't expect any distro (not even bloated ones) to take more than a few minutes to boot.

It looks like Fedora 30 just outright works (although very slowly unless you are using one of the optional desktop environments.

  • Fedora-Workstation-Live-i386-30-1.2.iso Booted to the live image about 8.5 min, but once it got to that point performance was awful and it's not even worth attempting, moving the mouse would be met with 30+ second long delays.
  • Fedora-LXDE-Live-i386-30-1.2.iso Got me to a complete LiveCD desktop in about 7 min and felt very usable in performance.
  • Fedora-LXQt-Live-i386-30-1.2.iso Took about 6min to get the LiveCD to the desktop and once again felt very usable.
  • Fedora-Xfce-Live-i386-30-1.2.iso Took about 10 min for the LiveCD to get to the desktop and again performance felt fine.

These were tested with 2048MB of RAM and 64MB of VRAM allocated in the VM. ACPI was disabled and in all cases I used the default live image option that I was presented with.

I'm guessing the very long boot time in that other screenshot was either because of the boot arguments that were used or potentially a slow host was being used. I am testing things with an i7 13700K so it's somewhat a best-case scenario for CPU performance.

@copy copy merged commit baa0966 into copy:master Sep 21, 2023
@copy
Copy link
Owner

copy commented Sep 21, 2023

Fedora-Workstation-Live-i386-30-1.2.iso Booted to the live image about 8.5 min, but once it got to that point performance was awful and it's not even worth attempting, moving the mouse would be met with 30+ second long delays.

Hmm, indeed. It's similarly slow in qemu-kvm, so let's assume v86 isn't at fault here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants