Test B) try fix the display On 5900x Zen3 system, ubuntu 26.04 LTS , kernel 7.0.0-38-generic :
I get in via SSH, but screen is black. amdgpu failed with error -22 and no DRM device is created. Try: BIOS: Re-Size BAR Suppor = Disabled BIOS: PCIEX16 Bifurcation from 1x8/1x8 to "Auto" Reboot (still no display with XEN), SSH: # journalctl -b -k --no-pager | grep -i 'amdgpu.*failed with error' amdgpu 0000:0a:00.0: probe with driver amdgpu failed with error -5 AI suggested: GRUB_CMDLINE_XEN_DEFAULT="dom0=pvh" With this option system just bootloops to POST > GRUB > Black .. and in 5sec again.. And "nomodeset" also no game. I am out of ideas, RX9070XT just is not working with booting to XEN - so I have no screen on this system. ### ### ### Test C1) try get any log/debug , managet Supermicro MB, AMD EPYC Zen5 CPU with 48threads, ubuntu 26.04 LTS , kernel 7.0.0-38-generic GRUB_CMDLINE_XEN_DEFAULT="dom0_max_vcpus=12 watchdog=true console=vga loglvl=all guest_loglvl=all sync_console" GRUB_CMDLINE_LINUX_DEFAULT="nvme.poll_queues=24 ignore_loglevel loglevel=7 systemd.show_status=1 nomodeset" update-grub , reboot I see XEN kernel lines then black screen... nothing.. On this system Dom0 kernel lines and CLI login prompt actually show up without "nvme.poll_queues" parameter. Waited 3 min, still black scree, SSH times out. ctrl+alt+del (booting without XEN to fix GRUB defaults) Test C2) last try Same as C1, but also adding "vga=text-80x25,keep" to GRUB_CMDLINE_XEN_DEFAULT update-grub , reboot well finally... I get XEN boot lines.. But it gets stuck at: 239.629381 xor: automatically using best checksumming function avx 239.810270 async_tx: api initialized (async) The IPMI screen capture is attached. SSH times out. Smasing esc, enter, Ctrl+a Ctrl+c Ctrl+Alt+F1/F2/F3 No response from screen. ctrl+alt+del - and system reboots ### ### ### D) Now I remember with "vga=text-80x25,keep" and "sync_console" days before - tried to troubleshoot with AI-help. I had output that got stuck at line that loaded BTRFS successfully. So I disabled BTRFS on that system but then it got stuck on something else seemingly random. At that time I did not yet know the problem was the combination of "dom0_max_vcpus" and "nvme.poll_queues" Maybe someone with more knowledge about XEN debugging could reproduce the BUG on their lab system? Im at the limits of my capability here - The Ryzen system has GPU issue with XEN and I cant use the Supermicro system at any time. ** Attachment added: "IPMIscreencap.7z" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2170270/+attachment/6008530/+files/IPMIscreencap.7z -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2170270 Title: Xen Dom0 fails to boot with "nvme.poll_queues=24" and "dom0_max_vcpus=6 dom0_vcpus_pin" To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2170270/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
