Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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 failed with install with SLES 12, the hvm kernel path dir is not right for SLES 12.
Version-Release number of selected component (if applicable):
# rpm -q virt-install virt-manager-common
virt-install-1.2.1-8.el7.noarch
virt-manager-common-1.2.1-8.el7.noarch
How reproducible:
always
Steps to Reproduce:
1. prepare a SLES 12 iso and install vm
# virt-install --name gsun_sles12_le -l /home/gsun/SLES-12-Server-DVD-ppc64le-GM-DVD1.iso --ram=2048 --vcpus=2 --hvm --debug --graphics vnc --wait -1 --prompt --accelerate --os-variant=virtio26 --network=network:default,model=spapr-vlan --serial pty --console pty --disk path=/home/gsun/sles12le_virtio.qcow2,size=8,bus='virtio' --extra-args "serial console=tty0 console=hvc0 netsetup=dhcp" --noreboot --os-variant sled12
it will fail at:
Retrieving file content... | 22 kB 00:00:00
[Fri, 09 Oct 2015 23:07:48 virt-install 14681] DEBUG (urlfetcher:196) local hasFile: Couldn't find /var/lib/libvirt/boot/virtinstmnt.ROJaT9/boot/ppc64le/loader/linux
[Fri, 09 Oct 2015 23:07:48 virt-install 14681] DEBUG (urlfetcher:196) local hasFile: Couldn't find /var/lib/libvirt/boot/virtinstmnt.ROJaT9/boot/loader/linux
The right kernel path should be "/boot/linux" not "/boot/loader/linux"
2.
3.
Actual results:
fail
Expected results:
success
Additional info:
Upstream commit:
commit 4578a4ec0f7c17d0a3b00a213f5e2dc07cb37f0b
Author: Pavel Hrdina <phrdina>
Date: Mon Nov 2 13:43:59 2015 +0100
virt-install: use correct path for linux and initrd for SLES on ppc64
Install DVD of SLES for ppc64 has different path where linux and initrd
are located. Add those paths to kernel_paths to search also there, in
case we are installing SLES on ppc64 host.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1270430
Signed-off-by: Pavel Hrdina <phrdina>
I can reproduce it with virt-manager-1.2.1-8.el7.noarch:
Steps:
# virt-install --name testvm --memory 1024 --disk /var/lib/libvirt/images/testvm.img,size=5 -l /var/lib/libvirt/images/SLE-12-Server-DVD-ppc64le-GM-DVD1.iso
WARNING Graphics requested but DISPLAY is not set. Not running virt-viewer.
WARNING No console to launch for the guest, defaulting to --wait -1
Starting install...
Retrieving file content... | 22 kB 00:00:00
ERROR Couldn't find hvm kernel for SUSE tree.
then upgrade to latest , the installation can be started successfully.
So move the bug from ON_QA 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-2016-2269.html