Archive for June, 2010
Although lately I’m quite busy with my Project, this will not preventing me from sharing another useful tips with you here. Actually there are a lot of tips I want to share but, unfortunately and inevitably, I can’t do it right now for some reason. So, to cut a long story short, today I will show you how you can directly connect, open and manage your vSphere 4.0 U1 virtual machine(VM) without using vSphere client with vmware-vmrc.exe.
First, lets talk about the advantages by directly connecting to VM console using vmware-vmrc.exe and why you need it. I understand we do have MS remote desktop(windows) or vnc(linux,ssh) which can accomplish this. But have you thought about how you want to let user to suspend or reset their VM easily without need to login first to vShpere client?. What about connecting iso images from client PC?. What ever the reason is, if you are concerning about to give user access to your vSphere environment and do want to limit it then, vmware-vmrc.exe can help you. Read more1 comment
I’ve been asked recently by forumer in VMware Communities, “How can we create a Virtual Machine(VM) from ESX Service Console(SC) or Can’t we?“. When I looked back since the first day I’ve started working with ESX, not a single time I’ve created new VM through SC. I’ve agreed, we can do a lot of things via CLi such as :
- vmware-cmd –> Manage VM, start, stop, snapshot, register/unregister, connect devices & etc
- vmkfstools –> Create, clone, resize, convert VM virtual disk & etc
But that’s all! What about completely build new VM from SC like the one we did from vi-client?. Unless I missed out something, the answer is “NO” and seem imposible to me. Nevertheless, I’m writing this to show you how can we create the new VM using script that I build from scratch.
Note : I’m not very good in Shell script but this wasn’t going prevented me from achieving this objective. Read more6 comments
Now vSphere make our job more easier when it come to the conversion of thin provision disk to pre-allocated thick for vmdk stored inside NFS datastore. So I list out some good points on why this conversion is important especially when Fault Tolerance is require for NFS VM :
- First, as we know by default NFS have their own thin provisioning method and we couldn’t change this to thick during VM creation (vi-client)
- Second, when you create new NFS VM, the Fault Tolerance and clustering option turned to grey or disabled.
- Thick provision or eagerzeroethick is one of the requirement of FT
- Lazyzeroed disk will automatically converted to eagerzeroedthick but this will not happen for thin provision disk.
In order for us to enable FT for the VM successfully, we must convert the NFS VM vmdk from thin to thick first and we can do this from vi-client as below: Read moreNo comments
Well I just noticed, among thoses active members in VMware Communities, I’m one of them. No wonder, I’ve had no time for other things and as a result, I recieved a sarcarstic comment last night from my daughter & my darling . But, what I’ve to do? John Trayer’s Blog really make me want to throw my precious time more towards VMware Communities.No comments
Yes, minor version number increased but who care, as long this one is better than previous (no email alert, broken snapshot, slow integrity check, hung backup task & etc) and benefit to the users, I’m glad to test it out. As listed in the source, now we are not only restrict from doing file level restore for Windows VM, but we also can do the same thing to Linux VM. However, whether it’s support LVM or not, you have to try it. .Hopefully with this release, VDR is seriously ready to attack SMB market.
VDR 1.2 feedback
- Enablement of Fault Tolerance Functionality for Intel Xeon 56xx Series processors— vSphere 4.0 Update 1 supports the Intel Xeon 56xx Series processors without Fault Tolerance. vSphere 4.0 Update 2 enables Fault Tolerance functionality for the Intel Xeon 56xx Series processors.
- Enablement of Fault Tolerance Functionality for Intel i3/i5 Clarkdale Series and Intel Xeon 34xx Clarkdale Series processors— vSphere 4.0 Update 1 supports the Intel i3/i5 Clarkdale Series and Intel Xeon 34xx Clarkdale Series processors without Fault Tolerance. vSphere 4.0 Update 2 enables Fault Tolerance functionality for the Intel i3/i5 Clarkdale Series and Intel Xeon 34xx Clarkdale Series processors.
- Enablement of IOMMU Functionality for AMD Opteron 61xx and 41xx Series processors— vSphere 4.0 Update 1 supports the AMD Opteron 61xx and 41xx Series processors without input/output memory management unit (IOMMU). vSphere 4.0 Update 2 enables IOMMU functionality for the AMD Opteron 61xx and 41xx Series processors.
- Enhancement of the esxtop/resxtop utility— vSphere 4.0 Update 2 includes an enhancement of the performance monitoring utilities, esxtop and resxtop. The esxtop/resxtop utilities now provide visibility into the performance of NFS datastores in that they display the following statistics for NFS datastores: Reads/s, writes/s, MBreads/s, MBwrtn/s, cmds/s, GAVG/s(guest latency).
- Additional Guest Operating System Support— ESX/ESXi 4.0 Update 2 adds support for Ubuntu 10.04. For a complete list of supported guest operating systems with this release, see the VMware Compatibility Guide.
Just finished played with New Proxmox Mail Gateway 2.5 using Linux kernel 2.6.27 today. Actually I’m in the middle of searching for another mail gateway to replace my Endian Firewall and I believe Proxmox is really up to my expectation (simplify).
A bit about ProxMox Mail Gateway :
- Latest Version : 2.5
- Kernel : Debian 2.6.27-2-proxmox
- Installer : iso, VMware appliance, OpenVZ template
- Download : http://www.proxmox.com/cms_proxmox/cms/upload/bittorrent/VM-Proxmox-Mail-Gateway-2.5.zip
- Free Clamav anti-virus Read more No comments