Hide Forgot
Description of problem: Kickstart installation of RHEL-7.0-20131117.n.0 in a qemu-kvm VM fails with "** (anaconda:1224): WARNING **: could not open X-Display **" Version-Release number of selected component (if applicable): Fedora-19 host anaconda 19.31.36-1 qemu-kvm-1.4.2-12.fc19 How reproducible: Run kickstart installation Steps to Reproduce: 1. 2. 3. Actual results: Fails with aforementioned error trying to open X-Display, even thought kickstart installation restricts to text mode. Expected results: Kickstart intsllation succeeds. Additional info:
Occured with RHEL-7.0-20131125.n.0
Unable to reproduce the problem using RHEL-7.0-20131127.1.
(In reply to David Cantrell from comment #3) > Unable to reproduce the problem using RHEL-7.0-20131127.1. David, I can reproduce this with every RHEL-7 nightly newer than RHEL-7-20130920.n.0, which still WFM. Even RHEL-7-beta does not WFM.
Created attachment 836073 [details] RHEL-7-beta kickstart failing RHEL-7-beta kickstart file which fails for me.
Please attach /tmp/anaconda.log, /tmp/syslog, and /tmp/X.log from the installation environment.
No logs provided, closing the bug. If you can provide the information requested in comment #6, feel free to reopen the bug.
I am seeing this also. I am trying to gather logs
In my case this is not under KVM, but on a Dell XE2 performing a PXE boot with a kickstart that is trying to do a text mode install. install url --url=http://yumhost/distro/rhel/7.0b/x86_64/os text skipx lang en_US.UTF-8 keyboard us reboot authconfig --enablemd5 --enableshadow firewall --disabled selinux --disabled bootloader --location=mbr timezone --utc US/Eastern network --device=eth0 --bootproto=dhcp --hostname=euler zerombr clearpart --all --initlabel partition /boot --size 128 partition pv.00 --size 1 --grow volgroup VolumeGroup00 pv.00 logvol / --vgname VolumeGroup00 --size 1 --name=rootlv --grow %packages ....
Looks like the X error is a red herring. Removing 'text' and 'skipx' and the X message goes away ... however the real anaconda stack trace shows: ...pyanaconda/nm.py, line 200, in nm_device_property raise UnknownDeviceError(name, e) ...nm.py, line 274, in nm_device_hwaddress ...network.py, line 515, in add_connection_for_ksdata This seems like maybe my network line is wrong ... I will test
Yes, that was the problem. The eth0 device is now em1 due to the biosdevname change. It is past that error now.
It looks like my problem here is really a dup of: https://bugzilla.redhat.com/show_bug.cgi?id=1046307