Bug 1412090
Summary: | Virt-v2v will use the latest kernel instead of the default kernel. | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | kuwei <kuwei> | ||||
Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 7.3 | CC: | juzhou, kuwei, mxie, mzhan, ptoscano, tzheng, xiaodwan | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Unspecified | ||||||
Whiteboard: | V2V | ||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2017-02-16 17:00:49 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
kuwei@redhat.com
2017-01-11 08:57:25 UTC
Hi Kun Wei, can you please provide the full log of the virt-v2v invocation, running it with -v -x? Created attachment 1239401 [details]
v2v.log
Yup, I can confirm this. It looks like this was changed in upstream commit 16e817456cf7e5162ba053c92f1a4df24a4160d5: - before, the list of kernels was iterated from the first kernel to the last, returning the first good kernel (i.e. not for the old hypervisor, and that supports virtio when requested); this matched what the old virt-v2v did (lib/Sys/VirtConvert/Converter/Linux.pm, _configure_kernel function) - after, the list of kernel is sorted first by virtio, then by kernel version, and then by non-debug flavour, picking the resulting first kernel in both cases, the starting list of kernels contains all the valid kernels available in the bootloader, with the one marked as default as first element. It is thus clear than then sorting of kernels done now basically ignores whatever is the default kernel: any kernel with the same features (with virtio, non-debug) but with the higher version will be used instead. Possible options are: 1) decide the best kernel must be used anyway, no matter the previous default 2) keep the same default, if that kernels has the features needed (i.e. with virtio, non-debug, non-xen) 3) something else I'm currently missing I agree this does appear to be a silent change in the old virt-v2v behaviour. However what I'm missing here: Does changing to the latest kernel cause any demonstrable problem? The bug report just says the new default kernel is different, but doesn't say (AFAICT) that this caused a problem. I don't believe this is a real bug until it causes some problems, so I am closing it for now. Please reopen if there is a real problem identified. |