Debian in VirtualBox as 32bit? What's going on?

[Goatmilk]

I tried to install Debian 13 in VirtualBox, but couldn't get past this:

I'm pretty sure the iso-file I've chosen is 64bit - it even says so in the file's name (if I'm not totally mistaken reading amd64).

Can it be the trouble stems from this being a live CD iso? Should I pick another one? The download site at Debian's is a wee bit confusing.

VirtualBox doesn't seem to be the best one identifying versions, though. It had listed LMDE as Ubuntu, but there I could change it to Debian. I can't change it here with Debian itself, makes no difference whether I skip the unattendend installation or not.

 

[Brickwizard]

you have download the right one, perhaps you should try Mint LMDE7

 

[Goatmilk]

Maybe...

I've tried another one and installed it, but there seems to be a problem with that one, as well: it obviously wants its installation medium back.

Error message:
Media Change of type 'Debian GNU/Linux 13.1.0 Trixie - Official amd64 DVD Binary-1 with firmware 20250906-10:24' is requested.
Debian GNU/Linux 13.1.0 Trixie - Official amd64 DVD Binary-1 with firmware 20250906-10:24

A media change is required

I've apparently changed it when I mounted the Virtual Box Additions, and now I don't know how to get it back.

you have download the right one, perhaps you should try Mint LMDE7

I'm already trying MX Linux and LMDE 6. And there's always Windows 7...

 

[Goatmilk]

The culprit was a small line in its sources.list, where it had listed a cdrom at the top. #ed it out and now it works.

A bit slower than MX, though, maybe it hasn't gotten enough juice in its little vm.

Music files and videos are a bit choppy.

 

[Goatmilk]

Those are the error messages I could find:

owl@vbox:~$ sudo dmesg -l err
[sudo] password for owl:
[    0.070022] RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible!
[    1.443843] vmwgfx 0000:00:02.0: [drm] *ERROR* vmwgfx seems to be running on an unsupported hypervisor.
[    1.443849] vmwgfx 0000:00:02.0: [drm] *ERROR* This configuration is likely broken.
[    1.443852] vmwgfx 0000:00:02.0: [drm] *ERROR* Please switch to a supported graphics device to avoid problems.
[    8.897384] vboxsf: Unknown parameter 'tag'
owl@vbox:~$

Found advice in the webs suggesting to adjust the display settings in Virtualbox and change the graphic controller for the vm from VMSVGA to VBoxSVGA.

But, if I do that, VirtualBox tells me, "Invalid settings detected".

Any ideas?

​

 

[dos2unix]

There is a 32-bit version of VirtualBox, that will run on 64 bit systems, but it won't let you run 64-bit VMs.

 

[Goatmilk]

There is a 32-bit version of VirtualBox, that will run on 64 bit systems, but it won't let you run 64-bit VMs.

I don't think my version is a 32bit - it's Virtual Box Version 7.1.12 _ Debian r169651

It did run LMDE 6 (since deleted, couldn't really warm up to it); and it does run Debian 13, and both in 64bit.

Debian has a few errors, but it runs nonetheless.

edit: And doesn't it look noiiice?

Post in thread 'Post a screenshot of your Desktop'

Oct 23, 2025

VirtualBox only, for now...

• Goatmilk

 

[Brickwizard]

It did run LMDE 6 (since deleted, couldn't really warm up to it);

if LMDE [NOW 7] works for your hardware, but you don't like the Cinnamon desk top, then you can always change it to KED Plasma, XFCE or any other DE you prefer. Most common ones are available in the software repository

 

[Goatmilk]

I dabbled a bit with LMDE twice, and never really could get to it. It's like MX in another dress, and MX wins that comparison hands down.

Right now, the choices are down to MX Linux and Debian 13.

MX Linux is more comfortable (duh, used it for about a year, and if only for surfing...)
It's a lot snappier - which might simply be due to the fact that it is the main system, while Debian is squashed in the VB

Debian seems more to the point, seems cleaner and clearer and does not have all the bloat (MX this and MX that and MX whatever). It might take a while longer for a rookie like me to get along with it, but I have a feeling it might be worth it.

Pondering a new thread here, would like to put those two up for comparison.

 

[Goatmilk]

Well, I got rid of at least one of the warnings, the first one:
RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible!

Thanks to the advice of this nice website:

How to Fix the RETBleed Attack Warning in VirtualBox – FOSSGuides

fossguides.com

So all that's left is this:

owl@vbox:~$ sudo dmesg -l err
[sudo] password for owl:
[    6.715231] vmwgfx 0000:00:02.0: [drm] *ERROR* vmwgfx seems to be running on an unsupported hypervisor.
[    6.715237] vmwgfx 0000:00:02.0: [drm] *ERROR* This configuration is likely broken.
[    6.715241] vmwgfx 0000:00:02.0: [drm] *ERROR* Please switch to a supported graphics device to avoid problems.
[    9.118155] vboxsf: Unknown parameter 'tag'

Anyone? Pretty please?

 

[Trml]

While the settings will affect graphics performance, they have nothing to do with your 32bit issue.

I read Virtualbox will not run 64bit, if the basic CPU extension is not enabled. Check like so:

$ lscpu |grep Virtua
Virtualization:                          VT-x

If you don't see VT-x, enable it in UEFI/Bios.

 

[bob466]

Don't know about Debian 13 but I installed MX Linux in Virtualbox recently...runs well but it's 64bit.

 

[Goatmilk]

While the settings will affect graphics performance, they have nothing to do with your 32bit issue.

I read Virtualbox will not run 64bit, if the basic CPU extension is not enabled. Check like so:

$ lscpu |grep Virtua
Virtualization:                          VT-x

If you don't see VT-x, enable it in UEFI/Bios.

I did that, and it said VT -x

I also went and registered in the Debian forum to ask over there, but it seems to be a pesky problem.

I'm also not very familiar with VirtualBox; the only other virtual machines I've made are Windows XP and Linux LMDE6, and both ran fine.

I've decided to go later on and install Debian 12. It is tried and tested and if it comes up with the same troubles, the fault clearly doesn't lie with Debian 13 - and there might be much more info to be found, as it's been around for a while.

Well, in other words, I'm totally clueless.

As always...