Thanks, Max. This was helpful, and it makes sense to me now that I better understand how snapshots work.
I decided to try a theory, and that was, since I've been unable to delete the snapshot due to the segfault, to try and resize the snapshot .vdi file with *vboxmanage* since I had already done so with the base disk. It worked! Now Windows sees the extra disk space, and I've successfully grown the partition. I also *then* tried to delete the snapshot - and voila! That worked too. Moral of the story: Even though what I did may not be very conventional or recommended, it's possible to: - Resize the base disk - *Then* resize the snapshot .vdi file - *Then* delete the snapshot Thank you! - David On Tue, Dec 22, 2015 at 2:01 PM, Maxime Dor <m...@kamax.io> wrote: > David, > > About the error when trying to remove the snapshot, this is most likely > caused because you increased the disk size of the base disk, instead of the > snapshot diff disk currently in use by the VM. > The fact that the VM does not see the increase space is most likely due to > that - the base disk is actually not being seen directly the VM, only the > diff disk. > Now, you modified the base disk upon which the diff disks are based to > provide a single view of the data to the VM. I'm surprised VirtualBox does > not complain earlier about it, and is the most probable cause of the seg > fault. > So: never change the disk size (any of the disks in the snapshot chain) > while snapshots are in use. Always do it on the base disk once you've > remove ALL the snapshots. > > > About the activation: cloning a VM resets some values that are typically > used to uniquely identify the hardware by Windows: > - Motherboard UUID, by default same UUID as the VM but can be changed > individually > - Disk UUID > - MAC addresses on network interfaces > > This would be enough to trigger a new Windows activation since it would > typically mean you changed hardware. > Cloning is always an issue with Windows and you'll need to take that with > Microsoft directly. > > Max > > > On 22/12/15 13:19, David White wrote: > > Stephan, > Thanks for the response. Hope your experiment went well. > > As an update for the group (hoping some devs see this), I have > successfully deleted one of the snapshots. The first error message, "hard > disk has more than 1 child disk", was due to me somehow having a couple > different copies of the actual Windows VDI disk file laying around. I can't > remember exactly what I did to fix it, but I recall reviewing everything > tied to the VM within Settings -> Storage, and also browsing to the VM's > path on the host machine and deleting all of the files that weren't > actually in use. > > I continue to get a *segmentation fault* whenever I try to delete the > first snapshot. > > I've upgraded to VirtualBox 5.0.12, and have also tried cloning the > machine again - but I quickly confirmed that Windows lost its activation > again on the clone. > > I've backed up the entire dump / log / crash file that Ubuntu > automatically sends out whenever an application ends unexpectedly, so if > someone wants to see that, or if I should submit a bug report, I can > provide it. > > By the way, here's my (now, 2) questions (1 of them resolved) on SuperUser: > > 1. > > http://superuser.com/questions/1011325/virtualbox-windows-10-guest-resizing-snapshots-and-losing-activation > 2. > > http://superuser.com/questions/1016721/virtualbox-segfault-when-deleting-snapshot > > - David > > On Tue, Dec 15, 2015 at 7:57 AM, Stephan Hockley < > <stephan.hock...@yahoo.com>stephan.hock...@yahoo.com> wrote: > >> David, >> >> I can not answer your question, but on two unrelated issues: I have never >> been able to get my Microsoft product keys to be recognized in VBox nor >> VMware Fusion, and second, I did a Win 10 update last weekend and lost >> ethernet on the host machine. In short, found a community post and >> restored it. >> >> You have prompted my curiosity and I believe I will create a Win 10 VM >> this week. >> >> Good luck with this issue, I've been busy as of late, and hoping to >> become more responsive to the VBox user community. >> >> Stephan >> >> >> >> On Tuesday, December 15, 2015 6:03 AM, David White < >> <dmwhite...@gmail.com>dmwhite...@gmail.com> wrote: >> >> >> I asked the following question on Superuser about a week ago, but my >> question hasn't gained any traction. >> >> I have a Windows 10 VM in VirtualBox (Ubuntu 14 host, VirtualBox 5.0.10 >> platform). It was originally a Windows 7 virtual machine, and Windows 7 was >> fully activated. >> A few days ago, I wanted to run some Windows Updates on the Windows 10 VM >> to install Threshold 2, but I was told that there wasn't enough disk space. >> No problem, I figured I would just resize the disk.... except, that's a >> problem. I increased the disk size from 45GB up to 60GB using vboxmanage, >> but neither Windows nor gparted running on a Live CD will recognize the >> increased storage space. >> I read some documentation that indicates there's a bug in VirtualBox that >> prevents a guest VM from recognizing increased storage space when snapshots >> are present. >> I have 2 snapshots (that I don't really care about) of the Windows 10, so >> I figured that my snapshots are preventing the virtual machine from seeing >> the increased disk size. >> When I go to delete the snapshots, I get either of the following results, >> depending on which snapshot it is that I'm trying to delete: >> >> - *For the 2nd snapshot / child snapshot - *Error message - Hard disk >> {path-to-disk file} has more than one child hard disk (2). *or...* >> - *For the "parent" snapshot*, VirtualBox takes a long time acting >> like it is merging the differences, and then fails (completely crashes). >> Ubuntu's message whenever an application crashes appears with "The >> application Oracle VM VirtualBox has closed unexpectedly" >> - This is the only line I see in /var/log/syslog: Dec 15 05:52:20 >> Develop-CENTS kernel: [ 2082.315873] DeleteSnap[6852]: segfault at 20 >> ip >> 00000000006e3eab sp 00007f8c97893888 error 4 in VBoxSVC[400000+45b000] >> >> So then I read that if I clone the VM, that would essentially get rid of >> the snapshots for me, and then I could increase the disk size on the cloned >> VM. >> That's what I did, and I then successfully installed Threshold 2. >> About a week later, as I was doing some work, I noticed that Windows was >> telling me that it wasn't activated. I went into the Settings, and the >> message I read indicated was that "Windows 10 isn't activated because the >> previous version of Windows was never activated." >> Fortunately, I had a backed up copy of the old VM (pre-clone, and >> pre-updating to Threshold 2). I turned that back on, and confirmed that >> Windows was indeed activated. >> So I'm up a creek. >> >> 1. Why the heck did Windows 10 lose its activation on the clone that >> I created? >> 2. Can I create a clone without Windows losing its activation? >> 3. If not, how can I delete these snapshots, which are preventing me >> from resizing the hard disk that Windows uses? >> >>
------------------------------------------------------------------------------
_______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
