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.

Description of problem:

When building the virt-p2v appliance for RHEL 7.1[*], I discovered
that the network device doesn't come up.  This is caused by
systemd so-called "predictable" device naming changing the
device name from what Anaconda previous set up.

[*] http://oirase.annexia.org/virt-p2v/RHEL-7.1/

Version-Release number of selected component (if applicable):

virt-p2v 1.28.1-1.18.el7

How reproducible:

100%

Steps to Reproduce:
1. virt-p2v-make-kickstart http://download.eng.rdu2.redhat.com/released/RHEL-7/7.1/Server/x86_64/os/
2. sudo livecd-creator p2v.ks
3. Boot the resulting appliance:
  qemu-kvm -cpu host -m 2048 -hda /tmp/any-disk-image -cdrom /tmp/livecd-p2v-2015xxxxxx.iso -boot d

Actual results:

No network.

Expected results:

Network should be initialized.

Additional info:

The following patch fixes things:

https://github.com/libguestfs/libguestfs/commit/63cd28974e363e9f4b1ea56b39661ad3218a8f13

Tingting, can you add QA ack for this please?

Unfortunately this bug will be hard to reproduce, although easy to
verify.  To verify you just need to boot the virt-p2v ISO and
check that the network works.

Tested with:
libguestfs-1.28.1-1.37.el7.x86_64
virt-v2v-1.28.1-1.37.el7.x86_64
livecd-p2v-201505191242.iso	

Tried about 10 times,Boot virt-p2v iso,the network works well and there is a dialog about "Network Connections".

Refer to the above comments,move the bug to VERIFIED.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2183.html