Converting 64-bit to 32-bit?

[virtual-sa]

Hi all. I need your advice, and all opinions are welcomed. I'm in a tight spot. I have a 64-bit VM running on VMware Server 1.x and I need to migrate

it over to ESX 4, however our corporate headquarters purchased us (without asking me what we needed...) the 32-bit version of ESX 4, not the 64-bit

version.

Here's a little history: My employer needed to get a document management system, which we purchased. It is an industry-specific DMS, not a

mainstream one such as Sharepoint, Livelink, or other well-known systems, as I was recommending that they buy; however it is a MS SQL backend product at least. When we were getting ready to purchase the MS SQL Server media, I read up on the differences between the 32-bit version and the 64-bit version. I read a Microsoft whitepaper (http://download.microsoft.com/download/0/4/7/047da8d3-aa80-452a-9148-40a7e8a7048a/SQL64bitAdvantages.doc) which stated that the 64-bit edition offered better performance than the 32-bit version, so that is why I went down the 64-bit route.

Is there any undocumented way to get a 64-bit VM to convert and run successfully on ESX 4 32-bit? My other option would be to convert the MS

SQL Server database from 64-bit to 32-bit? Is that even possible???

[RParker]

the 32-bit version of ESX 4, not the 64-bit version.

Uh ESX is ONLY 64-bit. ESX 4.

Is there any undocumented way to get a 64-bit VM to convert and run successfully on ESX 4 32-bit?

ESX 3.x is 32-bit, and you can still run 64-bit VM's in both.

[golddiggie]

ESX 4 doesn't have a 32 bit version, it's only 64 bit, requiring true 64 bit hardware to even install.

These are the available edititions of ESX/ESXi

What are you set to use for hardware for the ESX/ESXi host server?

With ESX/ESXi 4 requiring true 64 bit hardware, as it does now (ESX/ESXi 3.5 was able to install/run on 32 bit hardware as well as 64 bit, but that's gone away), you'll be able to run both 32 and 64 bit servers as VM's.

I would be interested to see what made the corporate HQ twits think they were buying something that doesn't exist...

VMware VCP4

Consider awarding points for "helpful" and/or "correct" answers.

[virtual-sa]

Well, I am using the VMware vCenter Converter Standalone Client, version 4.0.1 build-161434. When I try to do a conversion it fails and says "The destination does not support 64-bit guests."

So, if ESX 4 supports 64-bit guests, then why am I receiving this message?

[RParker]

So, if ESX 4 supports 64-bit guests, then why am I receiving this message?

Did you enable VX-T extensions (virtualization) in the BIOS of the ESX host?

[virtual-sa]

Good question, my boss did the original setting up of the ESX installation, at least at first, so I do not know. The host is a Dell R710; is there a way to look thru the ESX vSphere app, or will I have to shut it down and go into the BIOS to verify? It will suck if it is the latter... someone is always working on something around here, so it's hard to take them all down for a reboot!

Please note coverage cannot be bound or altered without confirmation from an agency representative.

This email, including attachments, contains information that is confidential. This email, including attachments, constitutes non-public information intended to be conveyed only to the designated recipient(s). If you are not an intended recipient, please delete this email, including attachments, and notify me by return mail, email or reply. The unauthorized use, dissemination, distribution or reproduction of this email, including attachments, is prohibited and may be unlawful.

[admin]

From the ESX console OS:

esxcfg-info | grep HV

HV Support will be one of the following:

0 - "Non-HV machine"

1 - "HV not supported"

2 - "HV BIOS disabled"

3 - "HV enabled"

Here, HV stands for hardware-assisted virtualization, which may be VT-x or AMD-V.

[virtual-sa]

This explains a lot... :

1. esxcfg-info | grep HV

|----HV Support............................................2

|----HV Replay Capable.....................................false

|----Reason HV Replay Disabled.............................2

Please note coverage cannot be bound or altered without confirmation from an agency representative.

This email, including attachments, contains information that is confidential. This email, including attachments, constitutes non-public information intended to be conveyed only to the designated recipient(s). If you are not an intended recipient, please delete this email, including attachments, and notify me by return mail, email or reply. The unauthorized use, dissemination, distribution or reproduction of this email, including attachments, is prohibited and may be unlawful.

[admin]

When you do change the VT setting in the BIOS, be sure to power the machine completely off. Changes to this BIOS setting are not effective until all power to the CPU has been removed.

[golddiggie]

That's the bios setting then...

A correct response would be (confirmed on my ESXi 4u1 host):

|----HV Support................. 3

|----HV Replay Capable..... true

As mentioned just above, you'll need to fully power off the server after you make the bios setting change. Not just a restart/reboot but full shutdown (wait a few moments) and then power back up. Some people even go so far as to unplug the server to ensure it's off. I think that's a bit of overkill.

VMware VCP4

Consider awarding points for "helpful" and/or "correct" answers.

[Matt_B1]

When running the command on my host, I get the following.

|----HV Support............................................3

|----HV Replay Capable.....................................false

|----Reason HV Replay Disabled.............................1

What is HV Replay and what do I set to make it true if it is helpful?

[DSTAVERT]

You need to create your own post.

[golddiggie]

Good question, my boss did the original setting up of the ESX installation, at least at first, so I do not know. The host is a Dell R710; is there a way to look thru the ESX vSphere app, or will I have to shut it down and go into the BIOS to verify? It will suck if it is the latter... someone is always working on something around here, so it's hard to take them all down for a reboot!

The first part of that is probably the biggest issue you're facing right now... The person who set up the host probably didn't even bother to check the bios settings first, giving you these issues.

I know you can have 64 bit guests on the Dell R710, since I've done it. BUT, it has to be configured properly/correctly in order to do so.

How long before they start whining about needing the VM that you've been trying to convert over? You're looking at a short 'down-time' window to check the bios, correct the setting, and bring it all back online. IF there was a second host, with HA configured between them, you'd actually have zero down time of the VM's since you could vMotion them over to the other host in order to take one down.

VMware VCP4

Consider awarding points for "helpful" and/or "correct" answers.

[virtual-sa]

Good idea Gold... My second host only has 2 VMs on it presently, I think that I will take it down at 5pm my time and do the BIOS config change. I really appreciate you guys' feedback on this. I didn't even think about the BIOS settings being a possible factor, especially since my boss at corp always carries on and on about how sophisticated of an operation they have with their virtual environment there... and they haven't even been any help on this at all. Thanks again!

Please note coverage cannot be bound or altered without confirmation from an agency representative.

This email, including attachments, contains information that is confidential. This email, including attachments, constitutes non-public information intended to be conveyed only to the designated recipient(s). If you are not an intended recipient, please delete this email, including attachments, and notify me by return mail, email or reply. The unauthorized use, dissemination, distribution or reproduction of this email, including attachments, is prohibited and may be unlawful.

[golddiggie]

Having at least two hosts is a huge advantage. Being able to vMotion the running VM's over to it is even more so. I look forward to the day that I have 2 (or more) hosts running in my lab so that I can do proper maintenance and updates on all of them. Kind of difficult to do when you're running a vCenter Server as a VM on the only host. Plus, my AD DC is a VM on that same host... I'm hopeful that I'll be able to get at least a second host up and running before the end of this year, if not adding a SAN to the mix too.

VMware VCP4

Consider awarding points for "helpful" and/or "correct" answers.

[virtual-sa]

Does vMotion come with ESX 4 as part of the suite, or is it a separate product that has to be purchased individually? Yes, vMotion is definitely cool...

Please note coverage cannot be bound or altered without confirmation from an agency representative.

This email, including attachments, contains information that is confidential. This email, including attachments, constitutes non-public information intended to be conveyed only to the designated recipient(s). If you are not an intended recipient, please delete this email, including attachments, and notify me by return mail, email or reply. The unauthorized use, dissemination, distribution or reproduction of this email, including attachments, is prohibited and may be unlawful.

[golddiggie]

It's included with the suite/licenseing models... Depending (completely) on which license set they went with... Which bundle/edition did they get you or you're a part of?

If you have the license applied, look on the host's "Configuration" tab and select "Licensed Features"... It will list VMotion and Storage VMotion if you're licensed for them (as well as everything else)...

VMware VCP4

Consider awarding points for "helpful" and/or "correct" answers.

[RParker]

so it's hard to take them all down for a reboot!

OK it's like this. since it reports 64-bit guest are not supported the feature is NOT enabled.

Do you NEED 64-bit guest support (yes/no)?

If YES then you MUST reboot, change the option (under CPU settings) and reboot again.

There is NO alternative.