2
1
With Hyper-V, I created a expandable VHDX file with Windows 10 installed inside, whose max-size just equals the size of the partition it stores. Blue screen came out saying "VHD_BOOT_HOST_VOLUME_NOT_ENOUGH_SPACE" when native-booting.
I know M$ requires that there must be free space on the partition in case VHDX expands to maximum. (Plus the space of the page-file, as is said in MSDN .)
It means if you claim that much space, it must be reserved, no matter allocated to a traditional partition, occupied by a fixed-sized VHDX, or just left on the disk for an expandable VHDX (though may shared by multiple ones).
However, I would like to take care of it myself to utilize the free space not yet used. Since the VHDX will be my system drive, it is hardly possible that I wouldn't notice it before it grows too large.
I wonder if there are any tricks to by-pass this error?
Schezuk
Posted 2016-11-26T07:56:16.523
Reputation: 23
Sorry for my late response. Should I edit it inside the VHDX? Outside the VHDX there is no Windows installed on the physical drive, but a Windows boot-loader contained in folder \Boot and folder \EFI, which will load the VHDX while native-booting. – Schezuk – 2016-11-28T02:43:45.080
configure this inside the registry of the Windows that is inside the VHD. – magicandre1981 – 2016-11-28T05:12:41.650
@magicandre1981 how can you configure the registry inside the VHD windows if you can't even boot it. – Reda Drissi – 2020-02-04T10:03:13.257
@RedaDrissi mount the VHD, run regedit, load hive and edit the value
– magicandre1981 – 2020-02-04T15:39:39.800@RedaDrissi does it work? – magicandre1981 – 2020-02-19T15:26:23.140
I managed to make wine work and settled for a container instead. I needed a .NET windows application on a linux host and for my use case wine was enough. So I didn't try it. But if I ever try it I'll post my feedback here. – Reda Drissi – 2020-02-19T16:08:36.080