ZFS boot menu - Physical KASLR disabled

G’day,

I am installing Ubuntu ZFS on Root in a Hyper V VM (I don’t have a choice regarding the host OS) and I am receiving a “Invalid physical address chosen! Physical KASLR disabled: no suitable memory region!” error.

I can’t seem to find any current documentation on this at all and I am wondering if it a specific ZFS Boot Menu/Debootstrap install quirk as using the standard ubuntu installer on EXT4 works fine.

Probably out of the scope of the forum but I thought it was worth an ask

Cheers

Hi all,

I have tried this with the ubuntu server installer and have the same issue, it’s leading me to think that there must be some kind of issue between ZBM and hyper V which is really weird.

Cheers,

Fwiw, I could never get ZBM working right in KVM VMs under Ubuntu 22.04 (last time I tried in virtual) either. Worked fine on bare metal, but never would successfully boot in a VM on the same hardware.

Good to know I might give it a miss, thanks for letting me know :slight_smile:

Is ZFS on Root with GRUB worth looking into?

Whilst I was trying to resolve the issue I bumped into the openzfs documentation for installing Ubuntu on Root with GRUB and it suggested setting a unique serial number on each virtual disk using libvirt or qemu. I have no idea how to do that with Hyper V or if that was my issue but I thought it was interesting.