Interesting article posted in VMware’s blog recently and at least twice the same issue happened to me on HP Blade with power saving enabled in the bios. Nevertheless, there was no noticeable performance impact by turning off this feature though.

source

Just want to share my latest experience fixing one of p2v VM done by my customer. The guest OS is a redhat 5.3 64bit with xen kernel. Since converter 5 now able to preserve LVM volume, nothing much we have to worry about other than mptscsih driver. Well, for the second time below command successfully fixed the “kernel panic” due to driver issue upon the completion of p2v.

$new-kernel-pkg –mkinitrd –depmod –install 2.6.18-128.el5

Of course, the above command will replace your existing xen kernel but the good things is, you will now able to power on your VM like usual.

ariyossss

Well, although it is just a draft, so many ah bengs out there felt uneasy with the idea of BCPM drafted by MOSTI. For me, if this is going to raise my stake, professionalism of I.T industry in Malaysia, why not! In the real world, every one have to accept, if not many, there were some Gov critical project’s been done before by this ah bengs. The quality is the main concerns here and their dirty shits are every where. And you know what… those qualified professionals normally become a scape goats for this ah bengs when problem happened… Am sick of this..

Source

It’s been a week now since me and my colleagues went for vForum event which has been held in Singapore. Although I ONLY managed to join a few technical sessions, it was absolutely an outstanding event. I can see from my colleagues face that they are really passionate and some of them even have got chance to visit all VMware Partner Booths such as Hitachi, Dell Drobo, Veeam & etc. But seriously, I felt something was missing in the event. Probably it’s because there was nothing new has been shared by VMware partners or perhaps, the were too many uncles/auntie in the event

p/s: Don’t forget to attend today vSeminar at Bandar Utama (url).

As I’ve mentioned it here, now VMware have come with the patch which will resolve the issue. Test it out..

The complete bulletin of of ESX 4.1 Update 2 has been released. As per VMware, you cannot consider any ESX 4.1 as Update 2 unless you completely upgrade it with this bulletin. Source Sighh … Time to upgrade my customers ESX.