Created attachment 524269 [details] Screenshot of vncviewer localhost:0 - none of the keys pressed are sent to anaconda. Description of problem: When I try to install F16 as DomU under Xen the installer (text) does not recognize any of the keys I am pressing. If I use the VNC F8 to send Ctrl-Alt-Del nothing happens. Version-Release number of selected component (if applicable): Whatever is in the F16-Alpha How reproducible: Steps to Reproduce: 1. cat > F16.xm kernel = "/tmp/vmlinuz" ramdisk="/tmp/initrd.img" #extra="askmethod" memory = 1024 name = "Fedora" vcpus=2 vif = [ 'mac=00:0F:4B:00:00:63,bridge=switch' ] disk = [ 'phy:/dev/vg_guest/FC16-64,xvda,w' ] vfb = [ 'vnc=1, vnclisten=0.0.0.0,vncunused=1'] 2. xm create -c F16.xm 3. vncviewer localhost:0 Actual results: No keyboard response. Expected results: Keyboard response Additional info: I did manage to install FC16 using workarounds. Mainly on the 'extra' line I added 'console=hvc0 test serial vnc' and I was able to hit keys in the text console (so the one provided by xm console), but still not in the VNC provided by the framebuffer. And the selection of the packages was done via vncviewer <guest-ip>:0. After the install was finished I poked around in the initrd and noticed that the xen-kbdfront was missing. But I couldn't figure out a way to insert the xen-kbfront during the install - either via unpacking the xz initrd img (tried the alpha version), nor disk images. Perhaps there is a link explaining how to create one?
Created attachment 524270 [details] Text output from 'xm console' with debug options. Screen output based off: #cat F16.xm kernel = "/tmp/vmlinuz" ramdisk="/tmp/initrd.img" extra="debug initcall_debug loglevel=10" memory = 1024 name = "Fedora" vcpus=2 vif = [ 'mac=00:0F:4B:00:00:63,bridge=switch' ] disk = [ 'phy:/dev/vg_guest/FC16-64,xvda,w' ] vfb = [ 'vnc=1, vnclisten=0.0.0.0,vncunused=1'] #xm create -c F16
There is a workaround for this which is to do: extra="vnc lang=en_US.UTF-8 keymap=us" Anyhow, I am more than happy to test say, an kernel and initrd.img that have an xen-kbdfront injected in it... Does F16 use the old RHEL5 method of manually loading some specific modules? Or does it nowadays use the udev mechanism?
I am having a hard time actually finding this version (17.0) in the rawhide or F16 initrd.img. This URL http://fedora.mirror.ac.za/linux/development/rawhide/x86_64/os/Packages/ shows that lorax-16.4.2 is going in rawhide/f16. Sooo when will 17.0 be in? It is rather impossible to test this without using an initrd image, so I can't very well do 'yum update' during an install when I can't use the keyboard.
lorax-16.4.5-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/lorax-16.4.5-1.fc16
*** Bug 740657 has been marked as a duplicate of this bug. ***
I figure the "test" extra arg in the comments above is "text" in reality.
lorax-16.4.6-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/lorax-16.4.6-1.fc16
lorax-16.4.6-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.