virtualbox.org

you will typically next
need to use a partition management tool inside the guest to adjust the main partition to fill
the drive.

We used the Windows Server 2003 Computer Management/Storage/Disk Management tool in the guest OS as specified by a blog page. That page stated we would see the extra space shown as available but not allocated in any partition. However, when we opened that tool it only showed the space previously alloted to the VHD.

Which of course it wouldn't since --resize does not support snapshots. (You would think that would have been mention at least in passing somewhere.)

But the VB Virtual Media Manager insisted that the VHD had been successfully resized. And still does even after the recovery operation I carried out.

joeller wrote:But the VB Virtual Media Manager insisted that the VHD had been successfully resized. And still does even after the recovery operation I carried out.

Of course it does. You have successfully adjusted the size of the base VHD. The problem with snapshots is that the size change is not propagated through the snapshot chain, so your current state sees nothing. In effect all you have done is manually corrupted the supposedly frozen base of the chain (though reports so far indicate that this corruption is harmless).

There is no way that changes could be propagated forward anyway, so resizing the base would never be the right thing to do. In theory the correct thing would be to resize the current state file, except that VBoxManage just errors out ("not supported") if you try that.

Two other interesting occurrences have happened as a result as this misadventure since last tuesday. When I left tuesdays, I had just finished restoring databases to our SQL Server Instance omn the VM and everythign was fine. When I came in on Monday, suddenly the VM entry in Virtual Box said it could not find certain fiels or UUIDs neither of which had to do with the files that had been used. When I examined the vbox file the whoel of the "<HardDisks>" element was missing. It was necessary to over write this file with the copy that had been made 6/29/2012 of the vbox file before Brad starting playing with it. Then everything was the say as it was when I left it on 7/3/2012.

the other interesting occurence, is that IE on the host can no longer locate web sites on the guest particularly the SSRS report server web site. The network setting on the VM shows as "host Only adapter" as it should be, with "promiscuous mode" set to "allow all", and "cable connected" checked. I have not figured a way to fix this as yet.

Base on you information about snapshots we plan to stop using them. and do our backups by exporting appliances. We plan to delete the snapshot using the procedure in section 1.9.1 on the new manual after we do an export (just in case). Do you forsee any issues that this could cause? Will this then allow our increase of the base machine to be visible insie the guest computer management tool?

Update: I see that the export process gets rid of snapshots. So I guess we will just have to make copies of the snapshots folder just in case.

mpack wrote: Also, note that I said "current user manual" - the feature explanation was expanded recently.

The latest version of the user manual (Version 4.1.18 copyright 2004-2012 Oracle Corporation, p 131 retrieved from http://dlc.sun.com.edgesuite.net/virtua ... Manual.pdf) still does not mention that resizing does not work on snapshotted hard drives. Are they planning on mentioning this at some point in the future? Or are they intending to upgrade the application it so that it does work on snapshotted hard drives?

joeller wrote: IE on the host can no longer locate web sites on the guest particularly the SSRS report server web site. The network setting on the VM shows as "host Only adapter" as it should be, with "promiscuous mode" set to "allow all", and "cable connected" checked. I have not figured a way to fix this as yet.

I don't know if you are still following this thread. However the issue related above is still a problem. This was not a problem before we worked with this. the other reason that this is a problem is that we cannot use our Business Intelligence Development Studio on the the host to design and deploy reports to the the Report Server on the VM any more. This is a major issue.

Nothing I have found shows any incorrect setting in our setup (although the chapter in the "current" manual on host only adapter does not match the current version of VirtualBox). In case You are not still following this thread, I will generate a new thread to cover this issue.