Created attachment 1478739 [details] related kernel message Description of problem: VM hangs after migrating from physical to virtual Version-Release number of selected component (if applicable): Fedora 28, 4.17.14-202.fc28.x86_64 How reproducible: Always Steps to Reproduce: 1. Migrate server from to VM 2. boot server 3. server hangs after minutes Actual results: Hangs Expected results: Should not hang Additional info: threadirq was added for the kernel parameter I changed to irqpoll and it does not hang anymore
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs. Fedora 28 has now been rebased to 4.18.10-300.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
The problem is still there. Will attach the kernel message with the newer kernel.
Created attachment 1489574 [details] 4.18.10-200.fc28 threadirqs problem 4.18.10-200.fc28 threadirqs problem
Any news regarding the problem?
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs. Fedora 28 has now been rebased to 4.20.5-100.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
I tested with 4.20.8-100.fc28.x86_64 and the problem is still there.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I tested with Fedora 29, kernel 5.0.9-200.fc29.x86_64. The problem is still there.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs. Fedora 29 has now been rebased to 5.2.9-100.fc29. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 30, and are still experiencing this issue, please change the version to Fedora 30. If you experience different issues, please open a new bug report for those.
Still have problem with Fedora 30 (kernel 5.2.8-200.fc30.x86_64).
So you are trying to migrate from a physical machine to a VM? Is this using p2v?
I want to have a VM to test upgrading Fedora before I would upgrade the physical server. Sometimes there is upgrade problem and I would like to test before performing upgrade on the physical server. Not using p2v to migrate. Just backup files and restore back to a VM. So the kernel parameters are the same. I am not aware that threadirqs could not be used in a VM.
What you are doing would require rebuilding the initramfs most likely, as well as a few other things. It certainly is not expected to "just work". Outside of that, from a kernel perspective, it isn't too much of a valid test, as you are not running the same hardware or drivers. I might suggest keeping a VM similar, but without copying the kernel/initramfs/grub configs, and testing the upgrade there, or perhaps just a back up to another partition on the hardware that you could restore if there is a problem. I am going to close this for now, as what you are trying is not expected to work.
The testing VM is migrated without 'threadirqs'. It was upgrade from FC28 to FC29/FC30. The initramfs was rebuilt after a new kernel is installed. I tested the problem by appending 'threadirqs' to the grub at boot time.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs. Fedora 30 has now been rebased to 5.5.7-100.fc30. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31. If you experience different issues, please open a new bug report for those.
I do not have the problem hardware to run the test now. Closing ticket. But Fedora support did not actively check the problem for 1.5 years.