Your customer want you to add a new volume in one of the VM Windows server but can not affort down time? No worry, you can do that easily with ESX.
Below is step by step guide with screen captured from the VM (my test machine is running on Windows 2003 Enterprise):
Tip: It is best to do a snapshot before you start this task, incase anything goes wrong.
1) This is my test VM machine. It is having one disk at beginning.
Read more »
Your customer want you to add a new volume in one of the VM SLES server but can not affort down time? No worry, you can do that easily with ESX.
Below is step by step guide with screen captured from the VM (my test machine is running on SLES10 SP2):
Tip: It is best to do a snapshot before you start this task, incase anything goes wrong.
1) This is my test VM machine. It is having one disk at beginning.
Read more »
Posted on October 6th, 2008 in Tips | 1 Comment »
As you may aware, we all had difficulty before this to select the boot option or BIOS setup mode during a VM startup or reboot. That is because the virtual center console delay respond and others reason, we always miss the option we need. Now, we do not require to press or reset the VM for multiple time. It can be easily force to enter BIOS mode for a VM on next reboot.
1st, right click the VM you would like to configure and select edit settings. Click on the option tab and choose on the boot option. At your right hand site, you will see the force BIOS setup. Check the box to force the VM entry to BIOS setup screen and click ok. The setting is done after that. On the next reboot, the VM will automatically go in to BIOS setup mode and you can configure the boot option priority as you need.
Read more »
1st of all, the reason of being utilize blade system in the market are looking at the point of servers consolidation, reduce power consumption and reduce the TCO require to purchase in term of hardware compare to the 1U, 2 U and 4 U servers. When we do compare the reason of having blade, you will always notice it was comparable between 2U and 1U servers in the x86 family and data center environment. In large scale deployment, you will always see that the Blade allow you to scale and spend in the sense with more stand alone machine you can have with the limitted rack space and power you do have in your DC. These seems to make sense for us to start moving to blade, BUT it also have some risk which will become major issue later on.
Before you can use blade, you require higher power consumption per rack to support approximately 30 to 32 blades per racks on 42 servers rack. At the same time, the cooling unit design in you DC require to be customize to ensure your blade chassis is working in perfect condition. Once you have this, then you may able to start think about Blade.
Read more »
Today, something weird happen. 1 of my VM guest which is windows 2003 server suddenly hung up. When I try to reset it, the Console screen show blank after the bios screen. I try to attach the VMDK to another newly created VM and it still not functioning. To verify the vmdk is not corrupted, I mount the vmdk to another windows 2003 VM and I found that the VMDK is functioning.
After that, I try to check most of the setting and log file from putty and virtual center. Here is my finding. Due to some unknown reason, the .vmx file setting and the configuration on the virtual center show really different. I had to force restart the virtual center service, and reconfigure some of the resources setting in virtual center to ensure it had not reserve or limit any resources on CPU and memory, and I power up the VM again. This round, the VM able to power up and functioning. Originally, It shouldn’t reserve any resource as I had not configured that. For some unknown reason, the resources limit had been configured by the ESX itself. This had happened in the pass but it had not cause any issue.
Read more »
