Test booting a RamOS on a 4000 MB (3.9 GB) VHD (Not compressed):
Just saw on a1ive's grub2 official releases page there is a new version, released a few hours ago, I decided to download it and after create the respective x86 and x64 efi versions and the core.img file, I used it for this test.
Only to test the limits I ran this test.
I was able to Ramboot a 4000 MB VHD NTFS single partition, on same PC with 8 GB of Ram, in this case this is same normal (uncompressed) installation, and it booted fine.
To test this, I increased the VHD size in command line and latter just expanded the single NTFS partition and edited the grub.cfg, the VHD was not fragmented when cheked with Winconting.
menuentry "Boot /VHD/10x64-39.vhd - UEFI Grub2 SVBus RAMDISK - 3.9 GB" {
efiload /EFI/grub/ntfs_x64.efi
search --file --set=vhd_drive --no-floppy /VHD/10x64-39.vhd
map --mem --rt ($vhd_drive)/VHD/10x64-39.vhd
boot
}
menuentry "Boot /VHD/10x64-39.vhd -l UEFI Grub2 SVBus RAMDISK - 3.9 GB" {
efiload /EFI/grub/ntfs_x64.efi
search --file --set=vhd_drive --no-floppy /VHD/10x64-39.vhd
map --mem --rt -l ($vhd_drive)/VHD/10x64-39.vhd
boot
}
The first menuentry without -l booted fine.
The second menuentry with -l do not load to Ram.
I don't think it is a good idea to go further as the memory above 4 GB available on this PC, is 4 GB or 4096 MB.
Then I can conclude using a1ive's Grub 2 we can make use of all the memory available on the PC above 4 GB, without any issue.
alacran