Well, looks like I spoke too soon when I said that Arch works 'fine' without
enabling '3D Acceleration'. Yes, I get to a graphical login screen on Arch
without that setting, but when I actually try to log in I never get to a usable
desktop state. In order to achieve that, I also have to enable t
That's good to hear. By now though, I fully expect this to be a VMWare bug (of
a graphical nature it seems), that VMware needs to fix.
For my Arch VM, I did not have '3D Acceleration' enabled; but I just checked,
and turning it on seems to work fine as well.
I have no idea what's going on with
I have no idea when this will be fixed (or not). However, I personally was able
to work around it by *enabling* '3D Acceleration" in the VM settings (under
display) for my Fedora 40 VM. You could try to see if that works for you.
--
___
users mailing l
Well, just because it got annoying, I tried out some different settings for the
VM in VMWare, to see if that changed anything. I tried out some different
'Guest Operating System (version)' settings, under 'options->general->guest
operating system->version', but that did not change anything.
The
Yes, I (now) get that the VM is starting, it's just that - because I did not
get to a login-prompt and the screen stayed black - I assumed that it was hung
during boot without further testing/verifying it. Thanks for suggesting the
ping/ssh part.
I normally have the VM set to 'multi-user.target
I'm running VMware Workstation 17.5.2 on Windows 11.
I don't have '3D Acceleration' enabled (like suggested in the reddit post you
linked to), it's already off, so that is not the solution for me.
I'm not sure how to go about booting into text-only mode; I've run 'sudo
systemctl set-default mu
Hi,
I'm also running VMWare Workstation, and am experiencing the exact same issue.
On Fedora 40, using the kernels 6.10.4, 6.10.5, and 6.10.6 result in an
unbootable vm, and the last Fedora 40 kernel that worked was 6.10.3.
Just to do some verification, I tried running an Arch Linux guest with
