On Sun, 01 Jun 2008 08:29:46 +0200, Bo Berglund <boberglund@xxxxxx>
>>I just tried the potentially very useful VHD Resize app. v220.127.116.11
>>It appeared to create a perfect copy of a Win311 VHD, increasing the
>>size from 200 to 300Mb.
>>When I ran it, it fell over with a "Missing Operating System" error on
>>initial boot up.
Same here. Had to kill VPC2007 to recover, but after I started VPC2007
again the guest bootup recommenced and it started. See below.
>>Glad I created a copy first.
No need, VHDResizer makes a *copy* of your original drive with the new
bigger size. So you must then make sure to use the *copied* VHD file
in your guest. Did you do that?
>>Incidentally I wasn't able to update the VHD in situ. It went through in
>>a flash and reported a successful outcome, but on bootup the disk size
>>was still 200Mb.
Just to make sure I tested VHDResizer 1.0.42 on a Win2000 4G VHD drive
and set the copy to 8G. The results are:
1) The expanded VHD is a *copy* of the original.
2) A new guest based on this VHD will not start! :-(
3) After *killing* VPC2007 and then starting VPC2007 again the new
guest starts automatically and this time it boots OK. (go figure)
4) Inside the guest the diskmanager reports the same 4G C: partition
size as before, but now with an extra 4G "unused space".
So the bottom line is that now one needs yet another tool to adjust
the partition size of the new VHD disk so it expands (without data
loss) the single partition to use the full drive capacity.
I don't see why the VHDResizer cannot also adjust the partition size
given that it *knows* the format of a VHD disk. *That* would make it a
useful tool indeed.
Also it should at the end switch the file names so that the original
disk becomes name.bak and the new disk name.vhd. This way the guest
will be able to start up again with less hassle.
Bo Berglund (Sweden)