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:
Not sure if this is a virt-install issue or a libvirt issue:
# ls -ltrd /mnt/tests/distribution/virt/install/RH6_x86_64_hvm_guest
drwxrwxrwx. 4 root root 4096 Aug 16 12:54 /mnt/tests/distribution/virt/install/RH6_x86_64_hvm_guest
# virt-install --name RH6_x86_64_hvm_guest --location nfs://bigpapi.bos.redhat.com:/vol/engarchive2/redhat/released/RHEL-6/6.0/Client/x86_64/os --nonsparse --hvm -s 9 -f /var/lib/libvirt/images/RH6_x86_64_hvm_guest_aaaa.img --debug --extra-args ks=http://lab2.rhts.eng.bos.redhat.com/cblr/svc/op/ks/system/guest-80-99.rhts.eng.bos.redhat.com --prompt --accelerate --os-variant=virtio26 --network bridge:br0 --serial file,path=/mnt/tests/distribution/virt/install/RH6_x86_64_hvm_guest/logs/console.log
This fails because the console log file has upper case letters: "/mnt/tests/distribution/virt/install/RH6_x86_64_hvm_guest/logs/console.log" , yet libvirtd is trying to write it to all lower-case file name:
<serial type='file'>
<source path='/mnt/tests/distribution/virt/install/rh6_x86_64_hvm_guest/logs/console.log'/>
</serial>
What's worse is , trying to write to a non-existent serial log file crashes libvirtd but there will be another BZ for that. This was for rhel6.0 not tested it on 6.1 or 6.2 yet.
Version-Release number of selected component (if applicable):
python-virtinst-0.500.3-7.el6.noarch
libvirt-0.8.1-27.el6.x86_64
How reproducible:
Very
Steps to Reproduce:
1. Do a vm install with virt-install and pass on --serial file,path=/PATH/TO/FILE where path includes uppercase letters.
2.
3.
Actual results:
Expected results:
Additional info:
(In reply to comment #2)
> Gurhan, can you repro with 6.2 and virsh define?
I tried to same with 6.2 (RHEL6.2-20110816.n.1 distro) and that works just fine:
<serial type='file'>
<source path='/mnt/tests/distribution/virt/install/GuestTwo_ser/no.log'/>
<target port='0'/>
<alias name='serial0'/>
</serial>
<console type='file'>
<source path='/mnt/tests/distribution/virt/install/GuestTwo_ser/no.log'/>
<target type='serial' port='0'/>
<alias name='serial0'/>
</console>