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

[George Dunlap <dunlapg@xxxxxxxxx>]

On Thu, Jan 11, 2018 at 9:16 PM, Andy Smith <andy@xxxxxxxxxxxxxx> wrote:
> Hi,
>
> I'm attempting to experiment with Vixen as described in the recent
> XSA-254 update. Unfortunately I'm failing at the first hurdle and am
> probably doing something stupid.
>
> All the steps up until creating the guest seemed to work. I ended up
> with a generated config that looks like this:
>
> name       = "debtest1"
> memory     = 2560
> vcpus      = 2
> vif        = [ "mac=00:16:5e:00:02:39, ip=192.168.82.225, vifname=v-debtest1" 
> ]
> kernel     = "/opt/grub/lib/grub-x86_64-xen.bin"
> disk       = [ "phy:/dev/ssdvg/domu_debtest1_xvda,xvda,w",
>                "phy:/dev/ssdvg/domu_debtest1_xvdb,xvdb,w" ]
> builder='hvm'
> type='hvm'
> device_model_version='qemu-xen'
> device_model_override='/var/lib/xen/pvshim-sidecars/debtest1.dm'
> device_model_args_hvm=['-cdrom','/var/lib/xen/pvshim-sidecars/debtest1.iso']
> boot='c'
> serial='pty'
>
> When I try to create it I get:
>
> Parsing config from /etc/xen/debtest1-with-shim.conf
> libxl: error: libxl_dm.c:2189:device_model_spawn_outcome: domain 7 device 
> model: spawn failed (rc=-3)
> libxl: error: libxl_create.c:1504:domcreate_devmodel_started: device model 
> did not start: -3
> libxl: error: libxl_dm.c:2303:kill_device_model: Device Model already exited
> libxl: error: libxl.c:1575:libxl__destroy_domid: non-existant domain 7
> libxl: error: libxl.c:1534:domain_destroy_callback: unable to destroy guest 
> with domid 7
> libxl: error: libxl.c:1463:domain_destroy_cb: destruction of domain 7 failed
>
> I've never tried running anything HVM before so I'm probably just
> missing some qemu thing.
>
> The dom0 is Debian jessie and qemu-system-x86 package is installed.
>
> The rest of the Xen installation is a recompiled 4.8 from
> jessie-backports.
>
> Searching around for the error, I saw someone 4 years ago had some
> success with:
>
> device_model_version="qemu-xen"
> device_model_override="/usr/bin/qemu-system-x86_64"
>
> But I don't think that could be the answer as 1) it's later said
> that's no longer necessary, and 2) device_model_override is already
> being set above.
>
> Any ideas?

Thanks for the detailed report -- it looks like the conversion script
needs a bit of wider testing.

So debtest.dm listed there is a "wrapper script", that needs to know
where qemu-system-x86 lives.  The current version checks
/usr/lib/xen/bin/ and /usr/local/lib/xen/bin, but given the output in
your subsequent email, yours is probably in /usr/lib/xen-4.8/bin.

Fastest thing to do is
1. Find out for sure where qemu-system-i386 lives
2. Modify the debtest.dm script so that it checks the right path.

We'll try to have an improved script tomorrow.

 -George

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