Referring to NTPRO Download Chrome OS VMware image post, I’m managed to get Chrome OS running on vSphere update 1 as screen below:
Please make sure you have selected Other 2.6x Linux 32bit as per your guest OS.
You may had experienced the snapshot problem when the snapshot delta virtual disk had become huge which is more than 20GB and is not able to be truncated by removing all the snapshot. Usually the problem occur when the snapshot is no longer available from snapshot manager, but you can see the delta files available from the command prompt or physical folder that contain the Virtual machine images. I experienced the 2nd time now which I am not able to remove the snapshot on a particular virtual machine from snapshot manager and command prompt. The production virtual machine was powered off due to disk full on the specify datastore. This virtual machine contain a previous snapshot which taken 2 weeks before and yet to be truncated. The delta disk had grown up to >20 GB and fully fill up the available space within the data store.
Due to some reconfiguration work we performed on our Virtual Infrastructure, we had required to relocate some of the VM to a different datastore. These VMs which required to be moved had been attached with Raw Device Mapping (RDM). Previously I thought the offline storage migration will not move the RDM over to the datastore as RDM is referring to the raw device from the SAN storage.Actually I was planned to convert the RDM to VMDK which I planned to manual transfer the files I need from RDM to the new virtual disk I created.
I had a tough time this week to deal with the snapshot issue with one of the VM. The VM is containing an important snapshot that previously taken for system restoration. When I browsed through the snapshot manager from vCenter, the system show my VM was running without any snapshots. Here was the kicked start of my problem and excited journey until I managed to recover it this morning.
I tried to SSH to the ESX host and browse to the specified datastore, and I found the snapshot file which end with file extension .vmsn were available in the correct location. No matter how many times I tried and rebooted my Virtual center, the snapshot were not visible to the snapshot manager still.
I read through some articles and forums which suggested to clone the snapshot by using vmkfstools -i option, but it didn’t success in my case here, and I continue my research and here I found a useful blog post from 1 of the blogger Oliver O’Boyle who experienced similar issue previously.
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.
