You are not logged in.

#1 2016-02-13 08:02:53

folatt
Member
Registered: 2015-08-01
Posts: 96

[Solved] Need help getting Xen QEMU keymap right.

I have the following setup:

name = 'ArkOS_Dev'
bootloader = "pygrub"
#kernel = "/mnt/arch/boot/x86_64/vmlinuz"
#ramdisk = "/mnt/arch/boot/x86_64/archiso.img"
#extra = "archisobasedir=arch archisolabel=ARCH_201511"
memory = 2048
vcpus = 3
disk = [ "format=raw, vdev=xvda, access=rw, target=/dev/vm_volumes/root.ArkOS_Dev",
         "format=raw, vdev=xvdb, access=rw, target=/dev/vm_volumes/swap.ArkOS_Dev"
       ]
vif = [ 'mac=00:16:3e:49:2b:a1,bridge=xenbr0' ]
vfb = ['vnc=1,vnclisten=0.0.0.0,vncpasswd=secret,keymap=bepo']
root = "/dev/xvda rw"

As you can see, I have chose bepo as my keymap (for testing, I ultimately want to use Dvorak, which is not standard in Qemu's keymaps for whatever reason.).

According to the Arch wiki qemu should be started with the '-k' option if it wants to
https://wiki.archlinux.org/index.php/QE … o_not_work

So I rebooted and looked for the process that was running this program and found it.
However, the '-k' option is missing:

$ ps -ef | grep -e '-xen-domid 1'
root       496     1  0 Feb12 ?        00:00:11 /usr/lib/xen/bin/qemu-system-i386 -xen-domid 1 
-chardev socket,id=libxl-cmd,path=/run/xen/qmp-libxl-1,server,nowait -mon chardev=libxl-cmd,mode=control 
-nodefaults -xen-attach -name ArkOS_Dev -vnc 0.0.0.0:0,password,to=99 -display none -machine xenpv -m 2048

Last edited by folatt (2016-02-13 16:29:26)

Offline

#2 2016-02-13 16:28:25

folatt
Member
Registered: 2015-08-01
Posts: 96

Re: [Solved] Need help getting Xen QEMU keymap right.

Looks like this is a different problem altogether.

I was under the impression that if I made a symbolic link in /etc/xen/auto to /etc/xen/myPV like so:

$ sudo ln -s /etc/xen/ArkOS_Dev_PV.cfg /etc/xen/auto/.
$ ls -lah /etc/xen/auto/
total 4.0K
drwxr-xr-x 1 root root  32 Feb 11 19:36 .
drwxr-xr-x 1 root root 312 Feb 11 19:36 ..
lrwxrwxrwx 1 root root  25 Feb 11 19:36 ArkOS_Dev_PV.cfg -> /etc/xen/ArkOS_Dev_PV.cfg

And the xendomains.service would automatically create my DomU on every boot.

Apparently that's not how it works.

Offline

Board footer

Powered by FluxBB