Showing posts with label vmware. Show all posts
Showing posts with label vmware. Show all posts
2009-11-23
Restoring a Snapshot Fails with Insufficient Permissions Error
You can find some very useful hints here.
2009-09-04
VMware disks created by an unsupported version
When you get the following error on VMware:
One or more of the disks used by this virtual machine was created by an unsupported version of VMware Server. To power on or upgrade the virtual machine, either remove the unsupported disks(s) or use a version of VMware Server that supports this version of the disks. Below is a list of the disks and their reported versions.
You can perform the following:
1) Edit file.VMX
2) Modify virtualHWVersion = "n"; n might be 4 for example
3) Edit the smallest file.VMDK (the one without -flat)
4) Modify ddb.virtualHWVersion = "n", the same way as before
One or more of the disks used by this virtual machine was created by an unsupported version of VMware Server. To power on or upgrade the virtual machine, either remove the unsupported disks(s) or use a version of VMware Server that supports this version of the disks. Below is a list of the disks and their reported versions.
You can perform the following:
1) Edit file.VMX
2) Modify virtualHWVersion = "n"; n might be 4 for example
3) Edit the smallest file.VMDK (the one without -flat)
4) Modify ddb.virtualHWVersion = "n", the same way as before
2009-05-20
enlarge your disk - vmware virtual disk
assumptions: the disk is system volume (i.e. there's only C:).
Also, there's no snapshot: if there's any, they should be removed for this to work as described.
1) increase virtual disk file size:
vmware-vdiskmanager -x 20Gb vmdiskfile.vmdk
2) add it as hd to another vm.
note: once the other vm has booted, the "new" hd should already automagically have a letter assigned. if not, then there's probably a snapshot and the process won't work (point 7 won't, at least).
3) inside the booted vm open a dos window and run: diskpart
4) list volume
5) set volume=X
6) list volume, just to verify
7) extend
That's it. Shutdown, remove the disk and go back to the original vm.
Also, there's no snapshot: if there's any, they should be removed for this to work as described.
1) increase virtual disk file size:
vmware-vdiskmanager -x 20Gb vmdiskfile.vmdk
2) add it as hd to another vm.
note: once the other vm has booted, the "new" hd should already automagically have a letter assigned. if not, then there's probably a snapshot and the process won't work (point 7 won't, at least).
3) inside the booted vm open a dos window and run: diskpart
4) list volume
5) set volume=X
6) list volume, just to verify
7) extend
That's it. Shutdown, remove the disk and go back to the original vm.
Subscribe to:
Posts (Atom)
