RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1723261 - [RFE]Virt-v2v should delete floppy device during v2v conversion
Summary: [RFE]Virt-v2v should delete floppy device during v2v conversion
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virt-v2v
Version: unspecified
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: beta
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-24 04:17 UTC by liuzi
Modified: 2022-04-18 14:18 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-18 14:18:12 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:
knoel: mirror+

Attachments (Terms of Use)

Description liuzi 2019-06-24 04:17:39 UTC 
Description of problem:
Virt-v2v should  delete floppy device during v2v conversion

Background:
From Bug 1637250 - block drivers: remove floppy driver,we know that our customers no longer need the floppy device.so virt-v2v should delete floppy device during the conversion.


Actual results:
when convert guests with floppy device,virt-v2v will convert device floppy successfully.

Expected results:
virt-v2v should delete floppy device during conversion .

Additional info:
Comment 1 Richard W.M. Jones 2019-06-24 10:42:26 UTC 
I agree, it's about time we ignored floppy devices when we see them on input.  I
will however first ask a question on virt-devel to see if anyone can anticipate
any problem.
Comment 3 Pino Toscano 2019-06-24 11:24:54 UTC 
virt-v2v already does not write to the OVF the removable devices found in the original guest.
Am I missing anything?
Comment 4 Richard W.M. Jones 2019-06-24 16:11:02 UTC 
(In reply to Pino Toscano from comment #3)
> virt-v2v already does not write to the OVF the removable devices found in
> the original guest.
> Am I missing anything?

Right, although there are two things:

(1) For other output types (currently libvirt XML and -o json) we do write them.

(2) Not even parsing the floppy device from the source might, I suppose,
affect target bus assignment, although it's rather unlikely.
Comment 5 Richard W.M. Jones 2019-06-24 16:16:01 UTC 
The bug which proposed removing floppy disks from RHEL 8 was bug 1664997.
On that bug, downsides of this decision were discussed.  Summarising:

Martin Tessun noted:

I believe floppies are currently used for the following tasks:
- Windows driver disks
- Windows sysprep information
- cloud-init data
- Kickstart information for RHEL

These seem to be irrelevant to v2v because they're basically about
installing virtio drivers or installing the OS itself.

Erwan Gallen noted some places where floppies are used in OpenStack, but
as far as I can see they are irrelevant to v2v.

Fabian Deutsch noted that CNV does not provide any way to add floppies.
Comment 6 Pino Toscano 2019-06-24 16:22:50 UTC 
(In reply to Richard W.M. Jones from comment #4)
> (1) For other output types (currently libvirt XML and -o json) we do write
> them.

- for libvirt XML, it can be easy to not write them
- for -o json, I'd still write it, as it is basically a JSON representation of the guest (it is up to the consumers to do something with it)

> (2) Not even parsing the floppy device from the source might, I suppose,
> affect target bus assignment, although it's rather unlikely.

Right, and because of that I'd still parse all the devices available: this way v2v still has the complete overview of the hardware of the guest.
Comment 11 RHEL Program Management 2021-03-15 07:37:00 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 12 Richard W.M. Jones 2021-03-15 10:28:37 UTC 
My apologies, this bug was closed by an automated process that we have no control
over, and it should not have been.  I am reopening it.
Comment 14 RHEL Program Management 2021-12-31 07:27:01 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 15 Richard W.M. Jones 2021-12-31 09:18:38 UTC 
I have to apologise - this bug was closed in error by a process we have no
control over which closes bugs claiming they are "stale" when they are not.
We have tried to have this process removed, with no success.  I am reopening
it and setting the "stale" date far into the future.
Comment 17 Laszlo Ersek 2022-04-18 14:18:12 UTC 
Just put quite a bit of work into virt-v2v making sure floppies (together with other removable media drives) were correctly mapped (bug 2074805). We might remove floppies if we can demonstrate the current code causes actual problems or misunderstandings, but for now I'm going to close this as WONTFIX.
Note You need to log in before you can comment on or make changes to this bug.