跳至主要内容

How to Convert a VMware Pre-allocated Virtual Disk to a Growable Virtual Disk

受不了动辄几百G的虚机，记给自己看，只是在网络上搬运，来源在这里：http://www.virtuatopia.com/index.php/How_to_Convert_a_VMware_Pre-allocated_Virtual_Disk_to_a_Growable_Virtual_Disk。

he vmware-vdiskmanager tool

The VMware Disk Management Tool is a command line tool which is installed by default with VMware Server. The executable file is named vmware-vdiskmanager and is located in \Program Files\VMware\VMware Server on Windows hosts, and /usr/bin on Linux systems.
The tool accepts a number of command-line arguments, a full listing of which can be obtained by running vmware-vdiskmanager with no options.
vmware-vdiskmanager

Virtual Disk Types

The type to which a virtual disk is to be converted is specified using the -t flag, together with the target disk type. This is represented by a number as outlined in the following table:
Type Identifier
Description
0
Growable (single .vmdk file)
1Growable (multiple 2GB files)
2Pre-allocated (single file)
3
Pre-allocated (multiple 2GB files)
4Pre-allocated ESX
5Compressed for streaming

Performing the Virtual Disk Type Conversion

The vmware-vdiskmanager command requires a number of arugments perform a virtual disk type conversion. The syntax for a type conversion is as follows:
vmware-vdiskmanager -r <oldfilename>.vmdk -t <type> <newfilename>.vmdk
where <oldfilename>.vmdk is the name of the virtual disk image file to be converted, <type> is the number from the above table indicating the target virtual disk type, and <newfilename>.vmdk is the name of the new, converted file.
For example, to convert a virtual disk image file called win2008-1_2.vmdk to a growable disk called new.vmdk the following command would need to be executed:
vmware-vdiskmanager -r  win2008-1_2.vmdk -t 0 new.vmdk

  Creating disk 'new.vmdk'
  Convert: 100% done.
Virtual disk conversion successful.
Once the conversion is completed, the virtual machine will need to be configured to use the converted disk, or the new disk renamed to have the name of the original disk.

评论

发表评论

此博客中的热门博文

解决墙国Google Home无法联网问题

趁黑五特价入手了个Google Home，经过漫长的等待昨天终于等到。回到家里兴高采烈的安装了Home应用，设置好开始开心的调戏Google，播放音乐什么的都很正常。 第二天上班回到家里，发现Hey Google后，不是提示Sorry something went wrong, try again in a few seconds."就是"There was a glitch. Try again in a few seconds."，很是恼火。没可能哥花50刀就买一个蓝牙音箱回来吧，再说了，连不上网甚至连蓝牙也打不开。 本着一贯的研究精神，开搞。据说Google Home是自带DNS,OpenWRT路由上设置了全局SS，但是Google Home还是会用tcp的模式去访问不存在的DNS Server地址8.8.4.4和8.8.8.8，于是乎加了个防火墙规则，不管你Google Home什么请求，都乖乖给我走SS通道去。 修改OpenWRT的/etc/firewall.user文件，增加以下iptables规则： iptables -t nat -A PREROUTING -s 192.168.1.0/24 -p udp --dport 53 -j DNAT --to 192.168.1.0 iptables -t nat -A PREROUTING -s 192.168.1.0/24 -p tcp --dport 53 -j DNAT --to 192.168.1.0 iptables -I PREROUTING -t nat -p udp -d 8.8.4.4 --dport 53 -j REDIRECT --to-ports 1053 iptables -I PREROUTING -t nat -p udp -d 8.8.8.8 --dport 53 -j REDIRECT --to-ports 1053 嘿嘿，来一句"Hey Google. Make me relax“,满屋子都是优美的声音，听着写代码真爽:).
3 条评论
阅读全文

解决华为手机访问Google Play:从服务器检索信息时出错。[DF-DFERH-01]

虽然路由器已经设置了梯子，但是用华为手机访问Google Play时，还是提示： 从服务器检索信息时出错。[DF-DFERH-01]。 虽然在手机上把梯子设置成全局模式，连接Google Play后再断掉梯子连接可以升级应用，但实在是麻烦。 放狗搜了一把，网上包括菊厂官方谈坛所说的什么删除Google账户清数据等等方法都是瞎掰。还好自己用的是LEDE(当然OpenWRT也可以)，直接把services.googleapis.cn对应的IP指向到216.58.197.195，问题解决。 sed -i '$a conf-dir=/etc/dnsmasq.d' /etc/dnsmasq.conf mkdir /etc/dnsmasq.d/ cat >>/etc/dnsmasq.d/custom.conf<<EOF address=/services.googleapis.cn/216.58.197.195 EOF
2 条评论
阅读全文

解决OpenWRT安装第三方包Incompatible with the architectures configured错误

 起因 起了把家里路由器更新到新版本OpenWRT的念头很久了，周末终于克服自己的懒病，下载了OpenWRT 19.07.4的安装包，更新Linksys WRT1900ACS路由器的系统。 修改了IP地址，把Wifi打开后，驾轻就熟地修改了相关的配置，增加了第三方源，准备开始安装你懂的SS和ChinaDNS等组件。没想到往常屡试不爽的opkg install命令返回了安装失败提示： Incompatible with the architectures configured 仔细比对了所有的配置，确认没有错误，但是安装新增的第三方包时总是报错。 解决方法 试了N多种方法，还是不行，正准备放弃装回原来ROM时，突然发现运行opkg print-architecture返回的CPU架构型号是 arch all 1 arch noarch 1 arch arm_cortex-a9_vfpv3-d16 10 比原来系统打印出来的架构型号多了一个d16,而第三方源的库里貌似没有arm_cortex-a9_vfpv3-d16这样一个型号的源,尝试修改/etc/opkg.conf文件，把原来CPU型号列表增加不带d16行。 arch all 1 arch noarch 1 arch arm_cortex-a9_vfpv3 8 arch arm_cortex-a9_vfpv3-d16 10 再运行opkg install，包装成功。
发表评论
阅读全文