If you have the feature added/running it doesn’t work very well side by side with other Virtual Machines like VirtualBox. Hyper-V is, essentially, Microsoft’s implementation of running virtual machine in your Windows. If you have one of those settings configured as mentioned, this is the reason why you are only seeing 32-bit guest operating systems available when create a new virtual machine. You either have Hyper-V turned on, or have Intel Virtualization Technology disabled in BIOS. It was showing 64-bit operating systems as one of those options in VirtualBox but you don’t know why there are only 32-bit versions listed below. So we know your machine is on 64-bit and perhaps at some point. You are not restricted in running 32-bit of Windows. This isn’t “normal” and you can fix it to enable VirtualBox to support 64-bit OS. … bumping.If the host machine is 64-bit and you are using VirtualBox to host and running your virtual machine, don’t be puzzled if your VirtualBox is showing you that it can only support for 32-bit of operating system. In the mean time, I am going to go ahead and close this old thread. #Virtualbox 64 bit not available amd windows 10#Does the Windows 10 VM work on other hosts? You assert that it won't get past the Windows logo without acceleration why do you think that it will work with acceleration? In other words, I am not sure you are chasing the same problem.Īs this thread is old and solved, and as I am a moderator I am going to suggest you open a new thread on the topic that you will own.īe sure to tell us about your machine (including make/model), its graphics subsystem, and which kernel you are running. I believe this is all moot with recent versions of VirtualBox. Thinking back, the problem was that a working 32 VM stopped working because the defaults inside VirtualBox changed, and the GUI was not updated to support it. Fortunately, this computer (HP Envy) does have VT-x I have not thought about this issue in a long time. When I started this thread, three years ago, I had a different computer. #Virtualbox 64 bit not available amd 32 bit#The latest version of VirtualBox would again run my 32 bit XP VM without barfing due to lack of Vt-x. Hand editing the XML file that defined my XP VM and adding a tag disabling long mode to the CPU section of the file did the trick. There did not seem to be a GUI hook in the Oracle VM management tool to disable LongMode. It would seem that, missing that tag, the latest version of VirtualBox defaults to enabling LongMode which, in turn, requires Vt-x. #Virtualbox 64 bit not available amd windows 7#The Windows 7 VM, created by the latest incarnation of VirtualBox, had the tag and set it to false. In the older versions of the XML file that defined the XP Virtual Machine, there had been no LongMode tag. I was wrong, it is (was, actually, I finished my migration to Windows 7) a 32 bit machine.Īpparently, newer versions of VirtualBox have a VM configuration option called LongMode (I am not certain as to the capitalization, I am not in front of my machine). I had thought that the XP was 64 bit and would not start leading me to believe II had lost Vt-x capability. I could not build a Windows 7 x86_64 machine, only a 32 bit. My confusion was that my XP VM would not start complaining about a lack of Vt-x support. It turns out that my machine does not support Vt-x It never has.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |