On Linux Mint 22.3 Cinnamon Framework 13 x86-64 when running:

```bash
qemu-system-x86_64 -cdrom debian-live-13.6.0-amd64-standard.iso
```

I face:

```
Invalid physical address chosen!
Physical KASLR disabled: no suitable memory region!
System is deadlocked on memory
```

```
kernel BUG at kernel/entry/common.c:375!
```

how to solve this issue?
Aug 17, 1:56pm

The error you're encountering (Invalid physical address chosen!, Physical KASLR disabled, and kernel BUG) is often related to Kernel Address Space Layout Randomization (KASLR) and memory allocation issues in QEMU when booting a Linux kernel. This can happen due to incompatibilities between the QEMU version, the kernel version, or insufficient memory allocation for the VM.

Here are the most effective solutions to try, in order of likelihood to resolve your issue:

1. Disable KASLR in the Kernel Command Line

KASLR is a security feature that randomizes the kernel's memory layout. Some older or misconfigured QEMU versions may not handle it correctly. Disable it by passing the kaslr=off option to the kernel.

How to do it:

  • When booting the Debian live ISO, press Tab or e (depending on the bootloader) to edit the boot parameters.
  • Add kaslr=off to the end of the kernel command line.
  • Boot the system.

Example: If the boot line looks like:

text
linux /live/vmlinuz-6.1.0-18-amd64 initrd=/live/initrd.img-6.1.0-18-amd64 boot=live

Change it to:

text
linux /live/vmlinuz-6.1.0-18-amd64 initrd=/live/initrd.img-6.1.0-18-amd64 boot=live kaslr=off

2. Allocate More RAM to the VM

The error System is deadlocked on memory suggests the VM may not have enough memory. Try increasing the RAM allocated to the VM.

How to do it: Add the -m flag to allocate more memory (e.g., 4GB):

bash
qemu-system-x86_64 -cdrom debian-live-13.6.0-amd64-standard.iso -m 4G

3. Use a Newer Version of QEMU

Older versions of QEMU may have bugs related to KASLR or memory management. Ensure you're using the latest version of QEMU available for Linux Mint 22.3.

How to check/upgrade:

bash
qemu-system-x86_64 --version

If it's outdated, upgrade QEMU:

bash
sudo apt update && sudo apt upgrade qemu

4. Enable NX (No-Execute) Bit in QEMU

Some kernels require the NX bit to be enabled for proper memory protection. Add the -cpu flag to enable it:

bash
qemu-system-x86_64 -cdrom debian-live-13.6.0-amd64-standard.iso -cpu host,nx

5. Try a Different Machine Type

Some machine types in QEMU handle memory differently. Use a more modern machine type like q35 or pc:

bash
qemu-system-x86_64 -cdrom debian-live-13.6.0-amd64-standard.iso -machine q35

6. Check for Known Issues with Debian 13.6.0

Debian 13.6.0 is a very recent release (as of August 2026). There may be known issues with QEMU compatibility. Check the Debian release notes or QEMU bug tracker for workarounds.

7. Use -no-acpi Flag

Some ACPI-related issues can cause kernel panics. Disable ACPI to test:

bash
qemu-system-x86_64 -cdrom debian-live-13.6.0-amd64-standard.iso -no-acpi

8. Test with a Different ISO

If the issue persists, try booting a different live ISO (e.g., Ubuntu or an older Debian version) to rule out ISO-specific problems.

9. Debug with QEMU Logging

Enable QEMU logging to get more details:

bash
qemu-system-x86_64 -cdrom debian-live-13.6.0-amd64-standard.iso -d int,cpu_reset -D /tmp/qemu.log

Check /tmp/qemu.log for clues.

Most Likely Fix

Start with disabling KASLR (kaslr=off) and allocating more RAM (-m 4G). These are the most common solutions for this error. If that doesn't work, try the other steps in order.

Aug 17, 1:56pm

This is a shared conversation and may include unverified content that doesn't reflect Mistral AI's views. Login to resume chatting.

Vibe can make mistakes. Check answers. Learn more