Tag Info

Hot answers tagged

14

Method 1: Using VMWare Converter: Turn off the virtual machine; Start the VMWare Converter application; Open the wizard; Select 'standalone virtual machine' as the source and destination system; Choose 'Select volumes and resize to save or add space'; Enter a new size and voilรก, you're done! Some say that the expand process is slow and that VMWare ...


7

See this article and this one, seems like what you're looking for. here's the process: Taking a snapshot of the source VM using vmware-cmd. Create a new VM and delete all vmdks in it Copy the vmdk files from your snapshot into your new using vmkfstools. Fix your configurations files accordinately. Hope this helps.


7

That's pretty much it in 4.x. vSphere 5.0 allows for pass-thru RDMs to be larger (about 60 TB), but still has the 2 TB limit in place for VMDKs and non-pass-thru RDMs. (reference). Pass-thru (physical) RDMs and non-pass-thru (virtual) RDMs are distinguished by what degree the SCSI commands are virtualized by vSphere. Pass-thru RDMs are sent all SCSI ...


5

Okay, there are several posters here saying that you need to know more before you attempt this... I totally disagree. It's actually really straightforward to stick a VM on a drive and boot it up at a client. I've done this with Windows Hyper V VMs. Lots of companies do this. I personally don't even bother going through the 'export/import' procedure - I ...


5

If you have qemu-img, you should be able to do all of this from a command line dealing just with image files. qemu-img convert source.vmdk -O raw /target/drive/ That will write out whatever raw format the vmdk was out to a physical drive. I have not been able to test this on my own, but I think that will work :)


5

VMDK's can be easily grown but not shrunk. Its best to start off smaller and grow as needed for storage management reasons. With VSphere 4 they have thin provisioning now so you can tell the server its 100 GB but on the backend it only provisions how much its really using. http://www.vmware.com/products/vsphere/mid-size-and-enterprise-business/features.html ...


4

The downside is the danger of actually running out of physical disk space and crashing all your VM's. Setting up really big "growable" virtual disks is a good way to optimize the use of your diskspace if you keep on top of the physical space available, and always make sure there is enough. However, if you don't it becomes a single point of failure that ...


4

There are now several tools available to achieve this task. Some of theme have some more functions like converting a running PC to a image and converting to other formats. One neat little tool is StarWind V2V Converter: Another one is Vmdk2Vhd from vmToolkit but I have no experience with this one. If you want to go for the big solution with more functions ...


4

I'd take a look at VMware Converter. It can import a Hyper-V machine the same way it imports physical servers. I'm not sure there's a way to import directly from the vhd. I've used Converter quite a bit, and it's pretty simple/quick process.


4

The VMDK file is the actual virtual disk, an ovf file is just a settings file (plain text), that VMWare products (like ESXi Server) and other virtualization software (like Virtualbox) can use when importing the VM. You may have an existing settings file (like a .vmx) which you can convert into ovf format using VMware's tool 'ovftool': ...


4

It's certainly possible to ship or send a virtual disk or a whole machine folder. I've done it with VDMK disks, merely copy it to a USB and move it, then import to a datastore. As for would SysAdmins/CTO's allow it? Well, it would depend on the company, not asking us, and I imagine Licensing would get a bit interesting. Would you be happy if someoneone gave ...


3

A bug related to this was fixed in qemu version 1.2.0. Ubuntu 12.04 has an older qemu version, but if you install qemu-img from source code user@ubuntu:/tmp$ sudo apt-get install libglib2.0-dev user@ubuntu:/tmp$ wget http://wiki.qemu.org/download/qemu-1.2.0.tar.bz2 user@ubuntu:/tmp$ tar xfj qemu-1.2.0.tar.bz2 user@ubuntu:/tmp$ cd qemu-1.2.0 ...


3

Best practices are to separate the pagefile, databases, and logs onto separate spindles. This means putting three separate VMDKs on three separate LUNs. For 100 users, you might not need to do this. That's not a ton, but you should still be using perfmon (or similar) to profile your server's storage/RAM requirements. If you are, you'll know how many IOPS you ...


3

If you used the Microsoft spreadsheet to calculate your luns, I would match that. If the spreadsheet calls for 4 luns or something like that, I would create a vmdk for each lun and would probably put each vmdk in their own lun. This would largely depend upon what kind of disk system / san you are running and a host of other factors.


3

The feature you are asking for is called "snapshots in a process tree" in VMWare terms and "snapshot branching" everywhere else and is a feature of the VMWare Workstation product line: Note that vSphere / ESX(i) products do not have this feature. Technically, there is support for linked clones in vCenter for use with the VMWare View VDI solution. ...


3

The lowest tier out there for vmware hosting is vCloud Express. A big jump in features but not price would be vCloud Datacenter. Links go to list of providers. Regarding "highly overpriced:" You get what you pay for. Higher price generally means higher SLA, redundancy, performance, features, etc.


3

A bit late, but for reference I have successfully: Attach clonezilla to the virtual machine Boot the virtual machine with clonezilla disk Save an image of the disk to an external USB drive (also attached to the virtual machine) Restore the image to a physical disk using clonezilla


2

I believe they might be using incompatible "differentiating" algo and storage format. You probably will have to examine official specification, or google for software that does it. Also, as an ugly hack, u can discard/merge these snaps, and use several v-machines (or just backup it as a file, if your snaps just have some initial state saved)


2

Have you tried booting into a BartPE cd (i.e. UltimateP2V ) and using Ghost? You'll probably run into driver problems once it gets on the hardware but, those are easy enough to deal with (in theory, lol). If you want to create your own P2V (V2V, V2P, etc) disk check out Mike Laverick's write up (its the best): ...


2

http://www.vmdkhosting.com offers uploading of VMDK/VMware images, or shipment of USB drive(s), and exclusively support VMware. It appears they do not allow storage appliances though (Nexenta, FreeNAS). So if you are just uploading a normal VM they are probably your best bet.


2

Mount the VMDK using VMware's Disk Mount utility, then copy the file you want, then unmount it. See this page: http://www.vladan.fr/mounting-your-vmdk-disks-directly-to-your-windows-box-how-to/


2

If you're running any recent version of esx(i) you can do a storage vmotion and convert it from thick to thin as it goes. If you're on 4.x this is built in to the gui, if it's a previous version it either involves getting a plug-in or using powershell. You will need two datastores with the second at least large enough to store the entire vmdk plus ...


2

qemu for mac can convert from raw image to vm. Check this forum post: http://qemu-forum.ipi.fi/viewtopic.php?f=6&t=4508#p13682 It's for converting from vdi to vmdk, so you'll need only the second part - from raw to vmdk. You can use dd to get a raw image out of the hdd - just connect it to your mac, and the use: dd bs=512 if=/dev/rXX# ...


2

A vmx file is simply a descriptor for the vmware virtual machine. The VMDK is what you will need to convert. Gareth's first link is a good tutorial on how to convert a VMDK->AMI, but you WILL have to change your kernel, and then you will have to bundle the image. The whole process is described on this link: ...


2

You should be able to use the VMWare Disk Manager to inrease the size of your image. -x [GB|MB] Expands the virtual disk to the specified capacity. You must specify the new, larger size of the virtual disk in Gigabytes or Megabytes. You cannot change the size of a physical (raw) disk. Caution: Before running the virtual disk manager ...


2

Just posting as an answer, so you can accept ;-) The LUN from the storage array represents a VMFS datastore. The VMDKs represent the virtual disks of the VMs. After expanding a LUN on the array, you first need to grow the datastore before being able to extend the VMDK. Clearly (from the output of df): 85630910464 = 80G. So the VMFS still had the old size.


2

For 100 users, my VMWare-based Exchange systems look like this... [VMDK] - 72GB thin-provisioned for operating system [VMDK] - 40GB thin-provisioned for Exchange Logs [VMDK] - 200GB+ thin or thick-provisioned for Exchange Database Don't get carried away with trying to outsmart your hypervisor's scheduler. I highly doubt that your setup would be much of a ...


2

Looks like physically copying thin-provisioned disks is a bad idea. VMFS does strange things with thin-provisioned disks, things that cp or mv can't cope with. Corruption ensues. Don't do it. vmkfstools handles them much better (and safer).


2

Don't forget network attached storage type protocols (eg. NFS, CIFS). That is, if your SAN/NAS supports serves them up. Obviously a VM providing either of those would kinda defeat the purpose. Linux guests can use multiple VMDKs for an LVM, which is not exactly spanning and not exactly RAID.


2

The list of shares and the share permissions are stored in the registry. The file and folder ACL's are stored in the MFT. So would this work? Yes it would work, but probably not by the method you're planning. A better method would be to convert the disk to a VMDK from within the guest, then disconnect the iSCSI target, then attach the VMDK to the guest, ...



Only top voted, non community-wiki answers of a minimum length are eligible