I’m using (Xen) XCP-ng 8.3 to deploy VMs.
Recently found out the 10.2 kernel (6.12.0-211.47.1) lacks of support on the XCP-ng VM console resolution, it goes back to (800x600).
The previous 10.1 kernel (6.12.0-124.47.1) can go with (1360x768).
Same thing happens to the latest 9.8 kernel (5.14.0-687.29.1), XCP-ng VM console resolution can only support (800x600), while the previous 9.7 kernel (5.14.0-611.5.1), or 9.6 can support (1360x768).
I tried many things from what Claude/Devin suggests, didn’t work.
Anyone knows how to fix it? Thanks
I created an AlmaLinux Jira issue to track this as a possible kernel/DRM regression.
Jira:
The issue includes the kernel version differences between AlmaLinux 10.1/10.2 and 9.7/9.8, as well as the XCP-ng 8.3 console resolution regression from 1360x768 to 800x600.
Could you please check whether the same console resolution regression can be reproduced with CentOS Stream 10 on XCP-ng 8.3?
The RHEL Jira issue I opened was closed because the report was based on AlmaLinux rather than CentOS Stream/RHEL.
According to the AlmaLinux documentation, the recommended approach is to test the issue against CentOS Stream first and report it upstream if it is reproducible there.
If CentOS Stream 10 also falls back to 800x600 while an older kernel works at 1360x768, we should have enough information to reopen/file this properly as a CentOS Stream kernel regression in the RHEL Jira tracker.
If possible, it would also be useful to test CentOS Stream 9, since a similar regression was observed between AlmaLinux 9.7 and 9.8.
Just tested with the latest CentOS 10.2 (Kernel 6.12.0-264).
It has the exact same issue, XCP-ng Console can only go up to 800x600
Thanks for testing this on CentOS Stream 10.
Since the same issue is reproducible there with kernel 6.12.0-264, I created a new RHEL Jira issue to track it as a CentOS Stream kernel/DRM regression:
The previous issue was closed because it had only been reported against AlmaLinux at that time.
Now that the regression has also been reproduced on CentOS Stream 10, the issue has been filed again with the CentOS Stream reproduction details included.
