Freezing on Linux virtualbox at wallpaper with no ui

[bluejeans]

I've tried both with and without the virtualbox video option on startup. Vmware loads everything fine. Same settings in both programs. What could be going on? Although it isn't really stable in vmware either, doing something like disabling the animated background can hang everything. It seems to be more stable if I ignore the license popups (As in don't click) and use games/apps then.

[Mandrake]

I was never able to get it to install past 36% in VirtualBox either. I tried creating a presized disk of 90GB, playing aound with all the settings, giving it as many cores, memory, video, 3D, etc. as possible - nothing would get it to complete before hard locking VB.

So, I just booted with the image, killed the installer and played around with the live image a few times, then took the plunge. It's been great

[LeoNigro]

In VirtualBox (in Windows) do you have the Operating System set to "Debian 12 Bookworm"?
I even have a vm set up as "Ubuntu (64-bit)" that seems to work fine.

I don't know what the deal is with VirtualBox on some machines.
It's always worked so great on all my different Windows 10 machines, that I never thought that it would be an issue.

[Mandrake]

Well, that could be the difference I guess... I run ZorinOS on my home PC, although I have Windows 10 and 11, and several different distros of linux running inside of their own VBoxes. Mint, MX, Debian, Arch, Tuxedo, Lite, Pi for x86, etc.

So, I'm not sure what the issue is, other than it's a huge image that takes a while to install it's just flaking out for some weird reason over time.

I have another theory as well I'm going to try. I noticed until I updated COS, that it would give the nefarious error "...attempt to read or write outside hd0...' fail to boot and I'd have to reboot several times to get in. Once updated, I've yet to have the issue reappear.

This is a weird grub glitch that can happen sometimes and the way to avoid it is to make a 1GB /boot partition, then use the rest for / (and put a swap in if you want). I've had it happen in the past on other distros and large drives.

So, this weekend I'm going to try doing that on the VB install just to see if it makes a difference.

It's a thought anyway!

[LeoNigro]

Okay, so it would seem that the issue here is the ZorinOS linux distro hosting the Commodore OS linux distro.
I'm not sure what can be done.

Let us know how you go with the partition changes.