Created attachment 526012 [details] Console output. Description of problem: When trying to install F16 pv guest on RHEL5, installation ends on starting anaconda without any other progress. Version-Release number of selected component (if applicable): Host kernel-xen-2.6.18-238.el5xen xen-3.0.3-134.el5 Guest: kernel-3.1.0-0.rc6.git0.3.fc16.x86_64 anaconda-16.17-1.fc16.x86_64 How reproducible: Always Steps to Reproduce: 1. Run virt-install on f16 tree with -nographics options. 2. 3. Actual results: Console output ends with Starting Anaconda version 16.17. Expected results: Installation works. Additional info:
The installation starts correctly for me like this: --------v-------- LOCATION=... NAME=... virt-install --connect=xen --name="$NAME" --ram=1024 --arch=x86_64 --vcpus=4 \ --os-type=linux --os-variant=fedora12 --paravirt \ --location="$LOCATION" --file=/var/lib/xen/images/"$NAME".img \ --network=bridge:xenbr1 --nographics \ --extra='text serial lang=en_US.UTF-8 keymap=us' # make sure your terminal decodes UTF-8 and that your font has line-drawing # glyphs xm console "$NAME" --------^-------- (Idea shamelessly stolen from bug 740378.) Perhaps anaconda should detect that no graphical console (no framebuffer) is available at all, and auto-select the "text serial lang=C" options. Originally I passed lang=C (and no keymap), but even though anaconda starts with "lang=C", the bootloader installation fails ultimately: cannot open locale definition file `C': No such file or directory and the guest can't be started afterwards. The "lang" option must take its value from "/usr/share/system-config-language/locale-list" (part of the "system-config-language" package). I checked that file on my F14 laptop, and to my horror, it has no English setting with a *non*-UTF-8 charmap (ie. latin1 or ASCII). Insisting on UTF-8 over a serial console is a horrible bug. As a workaround, I passed 'lang=en_US.UTF-8 keymap=us', and changed my xterm (ctrl + right click) to use TrueType fonts, and UTF-8, before issuing "xm console". ... Hm, the bootloader failed to install even with lang=en_US.UTF-8, even though anaconda (or whatever else) wasn't complaining anymore about the locale definitions.
boot loader installation failure: probably bug 725185 (hinted at by http://koji.fedoraproject.org/koji/buildinfo?buildID=266733 changelog)
If you're going to do a serial console install, you must specify the "console" argument as well. That's in the documentation. Having given that, can you just not specify a lang= and see if that works? Alternatively, just give lang=en. If you give a language with "utf8" in it, anaconda's going to insist on using it.
Bug 751741 may be the same issue. When looking at that bug (using xl rather than virt-install) I found that the boot line "serial text console=hvc0" worked and I think in later tests I decided that "serial console=hvc0" was enough.
Yes, it is the same...
*** Bug 751741 has been marked as a duplicate of this bug. ***
This issue does not occur with released f16 tree.