| 30 Nov 2025 |
 mou | but your config mentioned MBR in comments, so it might be different situation for you | 14:09:13 |
 not-jack | this is the default config for single disk ext4 | 14:10:19 |
| not-jack | so i think we're in the same situation | 14:11:48 |
| mou | As i understand logic of the boot process, the important part is decide are you using UEFI. If yes, you have to have GPT partition table (not mbr) and old MBR requirement to have bootloader in first 512K of the drive is no longer reuirement. So this reservation for grub is not needed | 14:15:35 |
| not-jack | aha, so it's legacy for backwards compat with grum | 14:16:46 |
| not-jack | * aha, so it's legacy for backwards compat with grub | 14:16:48 |
| mou | It is not grub specific. It is applicable to any bootloader for MBR partitioned drive. All bootloader put their initialization code into first 512K right after partition table | 14:17:51 |
| not-jack | * aha, so it's legacy for backwards compat with grub MBR | 14:19:33 |
| mou | But i did not refreshed my knowledge in this area for last decade, so i might mix things up. So, if you want to be sure, do additional check. | 14:19:34 |
| not-jack | the check will be seeing if i can boot! | 14:19:50 |
| mou | Here is more in depth explanation of the logic. https://superuser.com/questions/1566558/is-a-boot-sector-considered-to-be-a-partition | 14:22:28 |
| not-jack | thanks, that helps :) | 14:26:46 |
 spewdins | For those using disko for vm’s disk sizes…
I wonder. Are you declaratively setting your vm .qcow2 for example, from the host system? Or from inside the vm. | 17:03:16 |
| not-jack | When using disko-install, i get no space left on device | 19:59:11 |
| not-jack | I've tried remounting the store with more space, but that doesn't seem to do anything | 20:00:00 |
| not-jack | Anyone have tips? | 20:00:07 |
