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:

  virt-install defaults to rtl8139 for network and spapr-vscsi
  for storage; both are pretty poor choices for ppc64 guests.

  virtio should be used instead.


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

  virt-install-1.2.1-6.el7.noarch
  libvirt-client-1.2.17-8.el7.ppc64le


How reproducible:
 
  Always.


Steps to Reproduce:

  I usually use something like

    virt-install \
      --name guest \
      --location http://... /
      --ram 2048 \
      --vcpus 8 \
      --accelerate \
      --os-variant rhel7.0 \
      --graphics none \
      --network network=default \
      --disk size=10,bus=scsi 

  to install guests.


Actual results:

  The guest uses rtl8139 for network and spapr-vscsi for storage.


Expected results:

  virtio is used for both network and storage.


Additional info:

  The same seems to happen when using virt-manager from a Fedora
  22 host instead. I guess the code responsible for picking
  defaults is shared.

It's libvirt who selects default devices and this upstream commint in libvirt 75036c69 fixes the way how libvirt selects the default network device for guest.

With the disk, there is no spapr-vscsi storage bus, this was a bug and was fixed by commit 745fa9fa in virt-manager.  The disk bus is scsi and there is a scsi controller spapr-vscsi with spapr-vio address type.

Closing as a duplicate of a virt-manager bug, that's already fixed in rhel-7.2.  If you would like to track the issue for libvirt, but I don't think it's necessary, you can create a new bug.

*** This bug has been marked as a duplicate of bug 1206097 ***