Re: [Xen-users] Trying out vixen: failure to start device model

Re: [Xen-users] Trying out vixen: failure to start device model

[Andy Smith]

[Cc'ing xen-devel as this bit seems like a bug in pvshim]

On Thu, Jan 11, 2018 at 09:59:24PM +0000, Andy Smith wrote:
> libxl: debug: libxl_dm.c:2094:libxl__spawn_local_dm: Spawning device-model /var/lib/xen/pvshim-sidecars/debtest1.dm with arguments:
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   /var/lib/xen/pvshim-sidecars/debtest1.dm
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -xen-domid
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   9
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -chardev
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-9,server,nowait
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -no-shutdown
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -mon
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   chardev=libxl-cmd,mode=control
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -chardev
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   socket,id=libxenstat-cmd,path=/var/run/xen/qmp-libxenstat-9,server,nowait
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -mon
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   chardev=libxenstat-cmd,mode=control
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -nodefaults
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -no-user-config
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -name
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   debtest1
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -vnc
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   127.0.0.1:0,to=99
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -display
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   none
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -kernel
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   /opt/grub/lib/grub-x86_64-xen.bin
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -serial
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   pty
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -device
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   cirrus-vga,vgamem_mb=8
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -boot
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   order=c
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -smp
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   2,maxcpus=2
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -device
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   rtl8139,id=nic0,netdev=net0,mac=00:16:5e:00:02:39
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -netdev
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   type=tap,id=net0,ifname=vif9.0-emu,script=no,downscript=no
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -machine
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   xenfv
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -cdrom
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   /var/lib/xen/pvshim-sidecars/debtest1.iso
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -m
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   2552
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -drive
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   file=/dev/ssdvg/domu_debtest1_xvda,if=ide,index=0,media=disk,format=raw,cache=writeback
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   -drive
> libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm:   file=/dev/ssdvg/domu_debtest1_xvdb,if=ide,index=1,media=disk,format=raw,cache=writeback
> libxl: debug: libxl_dm.c:2098:libxl__spawn_local_dm: Spawning device-model /var/lib/xen/pvshim-sidecars/debtest1.dm with additional environment:
> libxl: debug: libxl_dm.c:2100:libxl__spawn_local_dm:   XEN_QEMU_CONSOLE_LIMIT=1048576
> libxl: debug: libxl_event.c:636:libxl__ev_xswatch_register: watch w=0x1b46a58 wpath=/local/domain/0/device-model/9/state token=2/2: register slotnum=2
> libxl: debug: libxl_event.c:573:watchfd_callback: watch w=0x1b46a58 wpath=/local/domain/0/device-model/9/state token=2/2: event epath=/local/domain/0/device-model/9/state
> libxl: debug: libxl_exec.c:398:spawn_watch_event: domain 9 device model: spawn watch p=(null)
> libxl: debug: libxl_event.c:673:libxl__ev_xswatch_deregister: watch w=0x1b46a58 wpath=/local/domain/0/device-model/9/state token=2/2: deregister slotnum=2
> libxl: error: libxl_dm.c:2189:device_model_spawn_outcome: domain 9 device model: spawn failed (rc=-3)
> libxl: error: libxl_create.c:1504:domcreate_devmodel_started: device model did not start: -3

I looked in the generated /var/lib/xen/pvshim-sidecars/debtest1.dm
and noted:

 63 for path in /usr/local/lib /usr/lib; do
 64     $path/xen/bin/qemu-system-i386 "${newargs[@]}" ||:
 65 done
 66 echo >&2 'could not exec qemu'

My qemu-system-i386 is at /usr/bin/qemu-system-i386 (Debian jessie,
qemu-system-x86 package) so is never going to be found by that.
Maybe pvshim-converter.pl should give up if it can't find
qemu-system-i386?

Anyway, as a quick test I created
/usr/local/lib/xen/bin/qemu-system-i386 as a symlink to
/usr/bin/qemu-system-i386 and now it gets further before dying with
a different error, so the above seems like it was a problem.

Parsing config from /etc/xen/debtest1-with-shim.conf
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-route add [31567] exited with error status 1
libxl: error: libxl_device.c:1225:device_hotplug_child_death_cb: script: /etc/xen/scripts/vif-route failed; error detected.
libxl: error: libxl_create.c:1461:domcreate_attach_devices: unable to add nic devices
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-route remove [31751] exited with error status 1
libxl: error: libxl_device.c:1225:device_hotplug_child_death_cb: script: /etc/xen/scripts/vif-route failed; error detected.

Cheers,
Andy

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Trying out vixen: vif-route issue

[Andy Smith]

Hi,

On Thu, Jan 11, 2018 at 10:26:36PM +0000, Andy Smith wrote:
> Parsing config from /etc/xen/debtest1-with-shim.conf
> libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-route add [31567] exited with error status 1
> libxl: error: libxl_device.c:1225:device_hotplug_child_death_cb: script: /etc/xen/scripts/vif-route failed; error detected.
> libxl: error: libxl_create.c:1461:domcreate_attach_devices: unable to add nic devices
> libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-route remove [31751] exited with error status 1
> libxl: error: libxl_device.c:1225:device_hotplug_child_death_cb: script: /etc/xen/scripts/vif-route failed; error detected.

I seem to have got it working. The vif-route thing was this:

https://lists.xen.org/archives/html/xen-users/2015-08/msg00005.html

i.e. /etc/xen/scripts/vif-route in HVM mode is *still* being called
with both "online" and "add", and fails with the latter, leading to
"unable to add nic devices". I used Martti's suggested workaround
and things seem to work now.

In dom0 I have an extra v-debtest-emu interface that is shutdown.
What is that for? Do I need it? If not, can it be gotten rid of
somehow? It can't be doing too much if it's shutdown with no
addresses on it.

There is something odd going on with my pvgrub2 kernel which was
compiled with a ram disk. The first thing that happens is I get:

error: file `/ramdisk' not found.

Press any key to continue...

Then I can either press a key or else wait about 5 seconds, either
way pvgrub2 continues to boot, presents the menu I put in its ram
disk and the options correctly chain to whatever they are meant to
(only tested grub2 inside guest so far). The /ramdisk message
doesn't appear in PV mode so I don't know what that is about yet.

qemu process still hangs around after guest is shut down.

Cheers,
Andy

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel