Monday, July 2, 2012
Real competition now
What was that pooled vRAM licensing? Never mind? Good idea.
Now update the goddamn vCenter Appliance and stop making software that requires MS Windows.
Tuesday, April 3, 2012
vConverter 5 P2V Windows XP "server"
Let's see if I remember all the steps for this P2V.
Source machine was a physical Windows XP "server" on one subnet; destination was a new vSphere 5 environment on a second subnet. No routing between the two subnets, just another physical Windows XP workstation with nics on both subnets that I could install vConverter on.
After fighting with SSL certs with vConverter (an issue with the source machine's external firewall), I opted to turn off ssl in vConverter:
For this case, I didn't have a ton of extra space on the vConverter machine, so I needed to shrink the physical 80G IDE partition down to 20G (12G in use). No problems here and the "optimize partition alignment" option gives me plenty of warm fuzzies.
I booted up the final vSphere version, finished vmware tools intstall and got set to extend the C partition back out for future growth.
No dice.
IDE vmdk's can not be extended.
No problem, says Google. Swap the disk adapter in vConverter. So I go back to the workstation image of the source and V2V again with lsilogic parallel.
BSOD.
V2V with Buslogic?
BSOD.
Plan D: Change the IDE disk to SCSI.
Source machine was a physical Windows XP "server" on one subnet; destination was a new vSphere 5 environment on a second subnet. No routing between the two subnets, just another physical Windows XP workstation with nics on both subnets that I could install vConverter on.
After fighting with SSL certs with vConverter (an issue with the source machine's external firewall), I opted to turn off ssl in vConverter:
- Path for XP [and probably Windows 2003] C:\Documents and Settings\All Users\Application Data\VMware\VMware vCenter Converter Standalone\converter-worker.xml (the path for 2008 Server / Windows 7 is hidden folder C:\ProgramData\VMware\VMware vCenter Converter Standalone\converter-worker.xml)
- Edit the <nfc> <useSsl> statement from true to false
- Restart the vConverter Worker service
For this case, I didn't have a ton of extra space on the vConverter machine, so I needed to shrink the physical 80G IDE partition down to 20G (12G in use). No problems here and the "optimize partition alignment" option gives me plenty of warm fuzzies.
I booted up the final vSphere version, finished vmware tools intstall and got set to extend the C partition back out for future growth.
No dice.
IDE vmdk's can not be extended.
No problem, says Google. Swap the disk adapter in vConverter. So I go back to the workstation image of the source and V2V again with lsilogic parallel.
BSOD.
V2V with Buslogic?
BSOD.
Plan D: Change the IDE disk to SCSI.
- Clone the IDE version of the XP "server" for backup.
- Grab the lsilogic drivers from www.lsi.com/support
- Your Windows XP 32bit version will be something like LSI20320-R_xp_50700_01034132IT_1201800_1005239.zip
- 64bit XP: LSIMPT_SCSI_WinXP_1.28.03.zip
- VMware's KB article mentions the different versions but doesn't specify the 1.28.03 is for 64bit XP only. We'll see if they update the doc with my comment.
- I created a virtual floppy on one guest in the environment and copied over these files onto the floppy for future use (I'm sure they'll be needed again).
- Create a new vHDD with lsilogic parallel on scsi0:1; size doesn't matter, thin.
- Attach the vFloppy to the XP VM (note: vFloppies can only be connected to a single VM at a time) and install the correct drivers. Shutdown the XP VM.
- This process assumes there are no snapshots.
- Double dream hands time:
- Open ssh on one of the esxi servers, login, su to root and change directory to the XP VM that we've been screwing with.
- ls -l to get the byte count of the ide vmdk
- vmkfstools -c <size in bytes> -d thin -a lsilogic <name of new temp vmdk>
- Copy a backup of the ide .vmdk disk descriptor file (*not* the large -flat.vmdk)
- Copy a backup of the vmx file
- cat <name of new temp vmdk> ; note the following parameters:
- ddb.geometry.cylinders = "#"
- ddb.geometry.heads = "#"
- ddb.geometry.sectors = "#"
- ddb.adapterType = "lsilogic"
- vi <ide vmdk> and change the settings listed above to the values from the <temp vmdk> that you just copied down; save & close.
- vi <vmx file> and you'll need to look around and change a few areas:
- For ide0:0 that is your virtual hard disk, change all values to start with scsi0:0
- For ide0:1 that is probably listed as your cdrom; update these values to ide0:0
- Look for a value scsi0:0.present = "false" and update this to "true"
- ide0:1.present should be updated to "false" (you might be able to delete this line)
- save & close
- Try turning on the XP VM. If all has gone according to plan, you should boot without issue. Do a little dance (see link above for inspiration).
- Delete the temp vmdk and the backup files from within your ssh session
- Shut the VM back down and extend the C: partition (while you're at it, delete the scsi0:1 disk)
- Extend the vHDD from the vSphere Client GUI
- Boot from your favorite partition changer iso. I'm partial (ha!) to gparted...it's not let me down yet.
- Start the XP VM up again and probably go through a disk check. This is normal.
Thursday, March 29, 2012
DB2 to Postgre vCSA change
The vCenter Server Appliance in the not-released-yet 5.0.1 (5u1) version will be switching from embedded DB2 to Postgre. ARG. Drink up
Is this because the transaction log settings and otherwise working with DB2 to truncate existing tables has been an issue? I sure can't find any detailed information online with the inner workings of the DB2 db. Hopefully smoother sailings than I've had so far.
Is this because the transaction log settings and otherwise working with DB2 to truncate existing tables has been an issue? I sure can't find any detailed information online with the inner workings of the DB2 db. Hopefully smoother sailings than I've had so far.
Tuesday, March 27, 2012
vDR email spam
Crazy crazy amounts of email spewing from a vDR 2.0 appliance. VMware says this is a known bug and you could turn off email alerts and/or reboot your appliance on a regular basis. Drink Up.
Come on guys, really? That's not acceptable. How about I limit the number of outgoing packets per day on port 25? It worked this morning... but long term I hope that VMware is fixing this bug.
iptables -A OUTPUT -p tcp --dport 25 -m limit --limit 10/day -j ACCEPT
Also I was trying to find a config file that would have the settings for the email reports, but perhaps this isn't kept in a config or xml file. find / -mtime -1 after I made changes in the UI didn't seem to point to any text files.
Come on guys, really? That's not acceptable. How about I limit the number of outgoing packets per day on port 25? It worked this morning... but long term I hope that VMware is fixing this bug.
iptables -A OUTPUT -p tcp --dport 25 -m limit --limit 10/day -j ACCEPT
Also I was trying to find a config file that would have the settings for the email reports, but perhaps this isn't kept in a config or xml file. find / -mtime -1 after I made changes in the UI didn't seem to point to any text files.
Wednesday, February 22, 2012
The VCP5 can smell fear
For me, it was the fact that I'd never actually gone through an AutoDeploy setup. I mean, Enterprise Plus license level only with large shops that are deploying massive hosts? Not used often. I use the ESX Deployment Appliance. The every-person's version of kickstart for ESXi systems. I love EDA.
Anyway. The test could sense that I had skimmed the AutoDeploy documentation. I'm sure it has sensed fear from others on different subjects. A respectable 400 considering that I probably missed all the autodeploy questions.
And I totally stole and modified the VCP button. VCP#22708 on 3,4&5. VCAP5-DCD next.
Anyway. The test could sense that I had skimmed the AutoDeploy documentation. I'm sure it has sensed fear from others on different subjects. A respectable 400 considering that I probably missed all the autodeploy questions.
And I totally stole and modified the VCP button. VCP#22708 on 3,4&5. VCAP5-DCD next.
Monday, February 13, 2012
hostdatastoresystem.createvmfsdatastore for object datastoresystem error
Well, from the ramblings of other blogs and the community forums, that ^ error string from the vSphere Client could mean just about anything could be wrong with your storage, your LUNs or your storage network.
In my case, after a long call with Dell EqualLogic and VMware, it turned out to be MTU size. In order to make my world right again, the MTU size on the Dell 6224 switches needed to be higher than the MTU size on the surrounding infrastructure. So: vSwitch, VMKernel and EqualLogic mtu: 9000. 6224's: 9126
Previous to that, there were logins and logouts on the iSCSI side, all sorts of errors seen in the vmkernel logs, but nothing...absolutely nothing...pointed in the direction of the MTU.
So, my short story that was actually really long is to show you, dear reader, that the first blog post that you find with this error message might not be your problem, it might not be the third or fifth solution you find. You might need to get help from someone else to check your configuration for something stupid that you've missed because you are less familiar with jumbo frames.
In my case, after a long call with Dell EqualLogic and VMware, it turned out to be MTU size. In order to make my world right again, the MTU size on the Dell 6224 switches needed to be higher than the MTU size on the surrounding infrastructure. So: vSwitch, VMKernel and EqualLogic mtu: 9000. 6224's: 9126
Previous to that, there were logins and logouts on the iSCSI side, all sorts of errors seen in the vmkernel logs, but nothing...absolutely nothing...pointed in the direction of the MTU.
So, my short story that was actually really long is to show you, dear reader, that the first blog post that you find with this error message might not be your problem, it might not be the third or fifth solution you find. You might need to get help from someone else to check your configuration for something stupid that you've missed because you are less familiar with jumbo frames.
Wednesday, February 1, 2012
ipcop 2.0.2
IPCOP2 still needs buslogic SCSI controller; and in order to use BusLogic, make sure you've chosen Other Linux 32bit.
And E1000 nics (but you should have known that).
Subscribe to:
Posts (Atom)
