https://bugzilla.novell.com/show_bug.cgi?id=343180 Summary: XEN keymap problem. Product: openSUSE 10.3 Version: Final Platform: i586 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: nice@titanic.nyme.hu QAContact: qa@suse.de Found By: Other I installed Vindows Vista on Xen by vm-install ran from YaST with the following settings (/etc/xen/vm/windowsvista): ############################################### name="windowsvista" ostype="windowsvista" uuid="cf93a3e0-c33f-50c4-dd3f-b68691418a40" memory=1024 vcpus=1 on_crash="destroy" on_poweroff="destroy" on_reboot="restart" localtime=1 builder="hvm" extid=0 device_model="/usr/lib/xen/bin/qemu-dm" kernel="/usr/lib/xen/boot/hvmloader" boot="c" disk=[ 'file:/mnt/xen/vista.bin,hda,w', 'phy:/dev/cdrom,hdc:cdrom,r', ] vif=[ 'mac=00:16:3e:1a:4d:7d,model=rtl8139,type=ioemu', ] stdvga=0 vnc=1 vncunused=1 apic=0 acpi=1 pae=1 usb=1 usbdevice='tablet' serial="pty" ############################################### I tried to manage this qemu-dm assisted fully virtualized host either via VNC or SDL (changing the config file above), but I realized that the host's keyboard map was incomplete and incorrect. Let's see a sort example from the file /var/log/xen qemu-dm.29632.log: ############################################### Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 501 Warning: no scancode found for keysym 501 Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 507 ############################################### I figured out that the problem could by corrected by make qemu-dm use some of the keymaps under /usr/share/xen/qemu/keymaps by passing a -key CODE parameter to it. Or am I wrong? I also figured out that I can make xend to pass this parameter to qemu-dm by adding a keymap='CODE' line to the /etc/xen/vm/VM file. So I added the line keymap='hu' to the vm config file, and qemu-vm's command line really changed: milleniumfalcon:/var/log/xen # cat /proc/8046/cmdline | sed y/'\x0'/' '/ /usr/lib/xen/bin/qemu-dm -d 2 -vcpus 1 -boot c -localtime -serial pty -acpi -usb -usbdevice tablet -k hu -domain-name windowsvista -net nic,vlan=1,macaddr=00:16:3e:1a:4d:7d,model=rtl8139 -net tap,vlan=1 -vncunused -vnclisten 127.0.0.1 milleniumfalcon:/var/log/xen # cat /proc/8046/cmdline | sed y/'\x0'/' '/ The keyboard got a bit better but there are still missing keys, "ű" for example. I tried other keymaps with similar results. What may be wrong with these keymaps? Are they defectivein a way? I have no idea. Thist bug report is primarily about the possible errors int these keymap files, but I have other related quetions too: It wold be good to make it possible to change the keymap setting in vm-install if it is necessary at all. Furthermore I do not know where virt-manager gets the information about VMs from. Once I moved every file from /etc/xen/vm to the root directory, restarted virt-manager and in spite of the lack of VM description files it still remebered my guest VM. I also do not know, what keeps the files /etc/xen/vm/VM and /etc/xen/vm/VM.xml in synchron. So, if i add a keymap to the file /etc/xen/vm/VM then that VM will use that keymap if I start if by the xm command. But what happens if i start that VM from virt-manager? Do I also need to add the keymap to the file /etc/xen/vm/VM.xml? Or to a third file? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.