[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Xen failing to create domain



That log file had the answer. I didn't even know that existed.

/usr/lib/xen/bin/qemu-system-i386: error while loading shared libraries: libiscsi.so.7: cannot open shared object file: No such file or directory

I updated libiscsi and now have libiscsi.so.8 instead. I just used downgrade to go back to libiscsi-1.17.0-2 and that fixed it.
Although, why does it need iSCSI? I'm not using any iSCSI disks.

Anyway, thank you very much!

On Wed, Oct 3, 2018 at 1:57 AM George Dunlap <dunlapg@xxxxxxxxx> wrote:
On Wed, Oct 3, 2018 at 4:07 AM Duncan X Simpson <virtualdxs@xxxxxxxxx> wrote:
>
> I've been running a router in an HVM domU for a year or so, and it just failed on me. When I try to xl create /etc/xen/chr.hvm.cfg, I get:
>
> Parsing config from /etc/xen/chr.hvm.cfg
> libxl: error: libxl_dm.c:2339:device_model_spawn_outcome: Domain 2:domain 2 device model: spawn failed (rc=-3)
> libxl: error: libxl_create.c:1501:domcreate_devmodel_started: Domain 2:device model did not start: -3
> libxl: error: libxl_dm.c:2453:kill_device_model: Device Model already exited
> libxl: error: libxl_domain.c:1003:libxl__destroy_domid: Domain 2:Non-existant domain
> libxl: error: libxl_domain.c:962:domain_destroy_callback: Domain 2:Unable to destroy guest
> libxl: error: libxl_domain.c:889:domain_destroy_cb: Domain 2:Destruction of domain failed
>
> I hadn't updated between when that happened and the last time I booted that domU. I tried updating my system (pacman -Syu), but no change. Any ideas?

Can you attach your config file, and
/var/log/xen/qemu-dm-${vnmame}.log?  (Where ${vmname} is the name of
your VM of course.)

For good measure, could you attach the output of `dmesg` and `xl dmesg` as well?

Thanks.

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.