Strange VirtualBox Behavior

WetGeek

This isn't earth-shaking, but it's got me wondering, and I'm hoping that someone here has had this problem, and figured it out. I'm out of ideas.

Trying to print some labels for a batch of tomato-basil soup I'm canning, I wasn't able to use my server, because the label software threw an error about a bad connection between the server and the printer. Everything checked out, so I wanted to try using the workstation across the room.

Problem is, the workstation doesn't have a swappable bay for 2.5" SSDs, as the server does. So I can't boot it directly into Windows, which is what the label printer software requires. My only choice is to create a Windows VM on that machine. (It currently doesn't have any of those at all.)

But when I tell VirtualBox I'm creating a Windows VM, all of the version choices have "(32-bit)" after them. It occurs to me that I need to create a 64-bit version of Windows 10 instead. (Do they even make a 32-bit version of that?)

So I figured I'd try telling it that I'm making a 64-bit Linux VM. That should at least get me a correct BIOS, and after all, I've installed Linux on Windows machines many times, so why not install Windows on a Linux machine? But would you believe it? Every version of Linux was listed with "(32-bit)" after it.

I replaced Budgie with Plasma on this machine a few weeks ago, so it's a fairlyt fresh Solus installation. This workstation is fully updated, as of Saturday. I've deleted VirtualBox and reinstalled it, with the same results. I know the workstation isn't running anything 32-bit. Anyone have a clue?

stalebrim

WetGeek Turn virtualization on from your BIOS.

tomscharbach

WetGeek Make/model and basic specs of the workstation? Is it your old Precision? Windows is usually spot on about selecting the right edition of Windows to install, so it sounds like VB installed as a 32-bit installation somehow. Crazy-making.

WetGeek

stalebrim Turn virtualization on from your BIOS.

I'll check that, but back when this was a Budgie machine, it did have a Windows VM on it. So I'm pretty sure that setting is already correct. Easy to check, though. Thanks for your suggestion.

WetGeek

tomscharbach Is it your old Precision?

No, but that's not a bad idea. It's an HP desktop. Solus doesn't run on 32-bit machines, so I didn't think it would install a 32-bit version of VirtualBox by default. That sure would explain it, though. How to check?

tomscharbach

WetGeek How to check?

Got me. You are the VB expert, at least relative to me.

tomscharbach

WetGeek I don't know if this will help, or not, but it might give you a hint to track down something:

Axios

I think vb does either least thats the way it is in software center they dont list a 32bit and 64bit
VB

WetGeek

tomscharbach it might give you a hint to track down something

Thanks! It shows only 32-bit in everything, but it's probably about the same problem. I'll check it out.

WetGeek

tomscharbach it might give you a hint to track down something

That's the recommendation to turn on virtualization in the BIOS. Stalebrim suggested that a while ago, and I haven't had a chance to check it yet. I'll do that now, just to check off that box.

WetGeek

Don't anyone fret too much over this. The workstation is now just an old HP that I happened to have on hand when my original workstation died. I was no longer in a mood to replace its motherboard, so I decided to donate it.

I've been meaning to upgrade that for a while now, and this seems like a great time to do that. I just ordered a DELL Optiplex 9020 that will be here Friday, so although I'm still curious about this issue, it probbaly won't be an issue beyond Friday.

And I can tell it's tomato-basil soup just by looking at the jars.

tomscharbach

WetGeek And I can tell it's tomato-basil soup just by looking at the jars.

Or maybe your magic marker ... 😆

WetGeek It shows only 32-bit in everything, but it's probably about the same problem.

You could try the suggestions in this article, I suppose.

Axios

got have both these on Intel Virtualization Technology and Intel VT-d Feature

WetGeek

WetGeek Stalebrim suggested that a while ago, and I haven't had a chance to check it yet. I'll do that now, just to check off that box.

Mystery solved. Apparently that Windows VM was on the original workstation that did support virtualization. On this little HP, the UEFI HP Setup does't even contain that setting. It's from 2015, and I'm now pretty sure I simply transferred the original workstation's 500GB SSD into this machine when I swapped it out. That's why the Windows VM icon showed up on the screen. I rarely used it, though, and apparently not on this computer.

No worries, though. That Optiplex is gonna be lots of fun. No regrets here.

stalebrim

WetGeek You're welcome. Better luck with the Dell!

mw42815

so what OS is on the HP machine ? Linux or Windows ? I am confused. Are you saying that the HP is a 32 bit only machine. I believe there are several Linux "distro" out there that support 32 bit . I believe you can still download a image of Windows 8.1 or Windows 10 that is 32 bit on the Microsoft website. google Windows ISO image 32 bit . i found a 32 bit Windows 10 ISO file that is 4 gig in size . good luck

stalebrim

mw42815 There's apparently no support for hardware virtualization on that particular HP machine. The machine likely is 64-bit.

WetGeek

mw42815 Are you saying that the HP is a 32 bit only machine.

No, I'm saying that its 2015 i5 processor didn't support hardware virtualization, apparently.

mw42815

here is the link i found .

https://www.microsoft.com/en-gb/software-download/windows10ISO

WetGeek

mw42815 here is the link i found

Thanks, but I already have a copy of that on my NAS.