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.

Bug 1085856

Summary: RHEL.7 guest (RHEL7.0-20140403.3) hang when installation
Product: Red Hat Enterprise Linux 7 Reporter: CongLi <coli>
Component: qemu-kvmAssignee: Ademar Reis <areis>
Status: CLOSED WORKSFORME QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: acathrow, coli, juzhang, lersek, michen, scui, shuang, virt-maint, xhan, xutian, xwei
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-28 17:54:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
serial log
none
installation screenshots
none
autotest debug file none

Description CongLi 2014-04-09 14:10:04 UTC
Created attachment 884511 [details]
serial log

Description of problem:
RHEL.7 guest (RHEL7.0-20140403.3) hang when installation

From the serial log, guest stuck at '2014-04-09 03:49:04: [[32m  OK  [0m] Started Dump dmesg to /var/log/dmesg.'.
vm will be killed when installtion time more then 50 mins.

2014-04-09 03:49:04: [[32m  OK  [0m] Listening on D-Bus System Message Bus Socket.
2014-04-09 03:49:04: [[32m  OK  [0m] Reached target Sockets.
2014-04-09 03:49:04: [[32m  OK  [0m] Reached target Basic System.
2014-04-09 03:49:04:          Starting firewalld - dynamic firewall daemon...
2014-04-09 03:49:04:          Starting Dump dmesg to /var/log/dmesg...
2014-04-09 03:49:04:          Starting Terminate Plymouth Boot Screen...
2014-04-09 03:49:04:          Starting System Logging Service...
2014-04-09 03:49:04:          Starting Wait for Plymouth Boot Screen to Quit...
2014-04-09 03:49:04: [[32m  OK  [0m] Started Dump dmesg to /var/log/dmesg.
2014-04-09 04:38:47: Ncat: Broken pipe.
2014-04-09 04:38:47: (Process terminated with status 1)

Version-Release number of selected component (if applicable):
compose: RHEL7.0-20140403.3

host:
kernel-3.10.0-119.el7.x86_64
qemu-kvm-1.5.3-60.el7.x86_64

guest:
kernel-3.10.0-119.el7.x86_64

How reproducible:
1 / 11

Steps to Reproduce:
1. Install a RHEL.7 guest of tree RHEL7.0-20140403.3:
/usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/virt/qemu/qemu \
    -S  \
    -name 'virt-tests-vm1'  \
    -sandbox off  \
    -M pc  \
    -nodefaults  \
    -vga cirrus  \
    -chardev socket,id=qmp_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1-20140408-203357-WrKiq4jr,server,nowait \
    -mon chardev=qmp_id_qmpmonitor1,mode=control  \
    -chardev socket,id=serial_id_serial0,path=/tmp/serial-serial0-20140408-203357-WrKiq4jr,server,nowait \
    -device isa-serial,chardev=serial_id_serial0  \
    -chardev socket,id=seabioslog_id_20140408-203357-WrKiq4jr,path=/tmp/seabios-20140408-203357-WrKiq4jr,server,nowait \
    -device isa-debugcon,chardev=seabioslog_id_20140408-203357-WrKiq4jr,iobase=0x402 \
    -device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=03 \
    -drive id=drive_image1,if=none,cache=none,snapshot=off,aio=threads,file=/usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/virt/shared/data/images/RHEL-Server-7.0-64-virtio.qcow2 \
    -device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=1,bus=pci.0,addr=04 \
    -device virtio-net-pci,mac=9a:96:97:98:99:9a,id=idwiJG2s,netdev=idOl08hZ,bus=pci.0,addr=05  \
    -netdev tap,id=idOl08hZ,vhost=on,vhostfd=28,fd=27  \
    -m 2048  \
    -smp 2,maxcpus=2,cores=1,threads=1,sockets=2  \
    -cpu 'Opteron_G2',+kvm_pv_unhalt \
    -drive id=drive_unattended,if=none,snapshot=off,aio=threads,media=cdrom,file=/usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/virt/shared/data/images/rhel70-64/ks.iso \
    -device ide-cd,id=unattended,drive=drive_unattended,bootindex=3,bus=ide.0,unit=0 \
    -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1  \
    -kernel '/usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/virt/shared/data/images/rhel70-64/vmlinuz'  \
    -append 'ksdevice=link ks=cdrom:/dev/sr0:/ks.cfg nicdelay=60 console=ttyS0,115200 console=tty0 root=live:http://download.englab.nay.redhat.com/pub/rhel/rel-eng/latest-RHEL-7/compose/Server/x86_64/os/LiveOS/squashfs.img'  \
    -initrd '/usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/virt/shared/data/images/rhel70-64/initrd.img'  \
    -vnc :0  \
    -rtc base=utc,clock=host,driftfix=slew  \
    -boot order=cdn,once=d,menu=off  \
    -no-kvm-pit-reinjection \
    -no-shutdown \
    -enable-kvm
2.
3.

Actual results:
guest hang when installtion

Expected results:
installation successful

Additional info:
1. cpuinfo:
processor	: 1
vendor_id	: AuthenticAMD
cpu family	: 15
model		: 67
model name	: Dual-Core AMD Opteron(tm) Processor 1216
stepping	: 3
cpu MHz		: 2400.000
cache size	: 1024 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
apicid		: 1
initial apicid	: 1
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good nopl extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy
bogomips	: 4822.38
TLB size	: 1024 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc

Comment 2 CongLi 2014-04-09 14:19:01 UTC
Created attachment 884514 [details]
installation screenshots

Comment 3 CongLi 2014-04-09 14:20:51 UTC
Created attachment 884521 [details]
autotest debug file

Comment 5 Laszlo Ersek 2014-04-10 12:10:03 UTC
Please
- run kernel, systemd and plymouth with full debug logging (use appropriate parameters on the kernel command line),
- when the hang hits, exercise various Magic SysRq keys; for example:

'd'     - Shows all locks that are held.
'l'     - Shows a stack backtrace for all active CPUs.
't'     - Will dump a list of current tasks and their information to
          your console.
'w'     - Dumps tasks that are in uninterruptable (blocked) state.

If the above doesn't enable the anaconda / systemd / plymouth developers to determine the cause, we can look in a vmcore, saved with "virsh dump --memory-only" (exact package versions will be necessary).

For example, I have no clue why netcat runs at all.

Comment 7 juzhang 2014-04-11 01:34:36 UTC
Hi Cong,

Can you have a look comment5 and comment6 and reply it?

Best Regards,
Junyi

Comment 9 Ademar Reis 2014-05-28 17:54:48 UTC
Closing it because it happened once during the development of RHEL7 and couldn't be repdroduced with a more recent image. If you ever reproduce it again with the GA, please reopen.