Skip to content

CNV#70576: known issue in 4.18.13 and bug fix for same in 4.18.17 #100425

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 14, 2025
Merged

CNV#70576: known issue in 4.18.13 and bug fix for same in 4.18.17 #100425

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions virt/release_notes/virt-4-18-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -263,3 +263,27 @@ You can also disable free page reporting of memory ballooning for all new VMs. T

// cnv-56890 - threads
* In the web console, it is erroneously possible to define multiple CPU threads for a VM based on s390x architecture. If you define multiple CPU threads, the VM enters a `CrashLoopBackOff` state with the error `qemu-kvm: S390 does not support more than 1 threads`. (link:https://issues.redhat.com/browse/CNV-56890[CNV-56890])

[id="virt-4.18-asynch-releases_{context}"]
== Maintenance releases

Release notes for asynchronous releases of Red{nbsp}Hat {VirtProductName}.

[id="virt-4.18.17_{context}"]
=== Version 4.18.17

.Bug fixes

//CNV-70576: VM operations fail after update to 4.18.13 or below
* As of 4.18.17, updating from {VirtProductName} 4.17 to {VirtProductName} 4.18 no longer causes VM operations to fail. (link:https://issues.redhat.com/browse/CNV-69894[CNV-69894])

[id="virt-4.18.13_{context}"]
=== Version 4.18.13

.Known issues

//CNV-70576: VM operations fail after update to 4.18.13 or below
* VM operations fail after updating from {VirtProductName} 4.17.27 to 4.18.13 and earlier 4.18 releases. The `virt-handler` pod logs show the error `unable to create virt-launcher client connection: can not add ghost record when entry already exists with differing socket file location`. (link:https://issues.redhat.com/browse/CNV-69894[CNV-69894])
** To fix this issue, update to {VirtProductName} 4.18.17 or later. If you have a disconnected cluster, you might need to refresh your internal repositories first.
+
For more information, see link:https://access.redhat.com/solutions/7131692[{VirtProductName}: VM operations fail after upgrade to 4.18 from 4.17.27 or above] in the Red{nbsp}Hat Knowledgebase.