First this device is awesome and is invaluable (worth every penny) if you are doing development of any kind these days. Many of my deployments these days are to Windows based retail point of sale systems. Integrations mostly. I’ve been running a Windows Server 2008 R2 on my MacBook Pro using VMWare Fusion. This has been a boon. But I wanted more flexibility to support running the 6-7 different styles of deployment on different VM’s keeping them separate and self-contained. Nothing offered this kind of flexibility cost effectively.
Until Antsle. I picked one up on a Black Friday sale a few weeks ago and this is my first shameless plug. If you do any kind of web based work or even Windows development. This is the product for you!!
So, I ran into what I thought was my first problem. They have a number of Windows based templates available. I’m using the Windows Server 2008 R2 template. After getting the OS activated using our MSDN subscription keys and getting it updated there was not enough space to do any deployment work! So I went searching for ways to expand the volume used by windows. Which lives on a ZFS volume on the Antsle device. I also asked their support group (email@example.com) and they gave me some hints too.
This is what I did. Note, the following commands are run from an ssh session with the Antsle device.
- Got my Windows Antlet stable (apply product keys, get updates installed, etc)
- Look for the qcow2 file that houses the Antlet’s disk.
zfs list |grep <antletName>
This command lists the location of the Antlet’s disk in ZFS.
- Get info about what the Antlet’s virtual disk size.
qemu-img info <antlet-qcow2-path-and-filename>
This command lists the info known about the Antlet’s disk.
- Perform the Antlet disk resize
qemu-img resize <antlet-qcod2-path-and-filename> +<size>
This command expands the virtual size for the Antlet’s disk.
- Finally expand the Windows disk with Computer Management > Disk Management by using Extend Volume. You get this!