Mark Wymer wrote: > Hi, (hope this is the correct forum) > I've just installed Opensolaris 2009.06 with no obvious problems. I then > installed VirtualBox 3, again, with no obvious problems. When I tried to > install Windows XP in a virtual machine I had all sorts of problems. Hunting > around I noticed that VB was starting the amd64 version! I checked various > bits and noticed that the OS seems to think it's instruction set is for the > AMD64 not the i386 that I've got. Am I a) missing something or b) > over-reacting and misreading the output from the following:- > > root at gandalf:~# uname -a > SunOS gandalf 5.11 snv_111b i86pc i386 i86pc Solaris > > root at gandalf:~# prtdiag -v | head -8 > System Configuration: System manufacturer P5KC > BIOS Configuration: American Megatrends Inc. 0804 10/30/2007 > > ==== Processor Sockets ==================================== > > Version Location Tag > -------------------------------- -------------------------- > Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz LGA775 > > root at gandalf:~# isainfo > amd64 i386 > > root at gandalf:~# isainfo -k > amd64 > > Is there anything else I should be looking at or any way to force the OS into > i386 'mode'?
You have an Intel Core 2 DUO processor which supports 64-bit instructions. Intel actually uses much of the same 64-bit instruction architecture that AMD *first* used, and hence, it is called AMD64. So, what you see is expected and correct. With that said, when you create the VirtualBox guest images, you'll notice that it offers you a 64-bit choice for each operating system. If you want to force VirtualBox to run your operating system guests as 32-bit, just select the OS option that doesn't say "64-bit". Cheers, -- Shawn Walker
