Bug 2018062
Summary: | QEMU Guest agent installation needs to be added to the migration flow | ||
---|---|---|---|
Product: | Migration Toolkit for Virtualization | Reporter: | Ilanit Stein <istein> |
Component: | General | Assignee: | Tomáš Golembiovský <tgolembi> |
Status: | CLOSED MIGRATED | QA Contact: | Ilanit Stein <istein> |
Severity: | medium | Docs Contact: | Avital Pinnick <apinnick> |
Priority: | high | ||
Version: | 2.2.0 | CC: | ahadas, apinnick, fdupont, gekis, istein, ltsai, rjones, xiaodwan |
Target Milestone: | --- | ||
Target Release: | 2.4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-07-11 08:33:24 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: | |||
Bug Depends On: | 2028764 | ||
Bug Blocks: |
Description
Ilanit Stein
2021-10-28 06:52:41 UTC
Ilanit, either this bug needs to be changed to virt-v2v, or we will need another bug for virt-v2v to fix this. (This is assuming we do the easiest thing which is "yum install qemu-guest-agent" which I think we should). We currently install the package in the container image, but it doesn't really make sense, because this will only put the package files in the container image, without the .rpm file. Instead, should we use "yum download qemu-guest-agent" and put the .rpm file in a specific location? At the moment virt-v2v looks for any RPMs in the virtio-win ISO under /linux/el<N> (eg /linux/el8 for RHEL 8 guest) and installs those. So if you don't want to change virt-v2v, you need to arrange to put RPMs there. However that was apparently difficult. So what I'm suggesting instead is that we change virt-v2v so it does yum install qemu-guest-agent as part of the conversion process (or maybe as a firstboot step). We'll need a BZ assigned to RHEL / virt-v2v in order to do this. Thanks Rich. I've opened https://bugzilla.redhat.com/show_bug.cgi?id=2028764 to track this in RHEL / virt-v2v. I see the fix was merged to virt-v2v on el9 so I assume the issue still exists in MTV We intend to upgrade the forklift-virt-v2v container to el9 in 2.4 |