From: Andy Smith <andy@strugglers.net>
To: xen-users@lists.xenproject.org
Cc: xen-devel@lists.xenproject.org
Subject: Trying out vixen: vif-route issue
Date: Thu, 11 Jan 2018 23:36:28 +0000 [thread overview]
Message-ID: <20180111233628.GY3124@bitfolk.com> (raw)
In-Reply-To: <20180111222636.GW3124@bitfolk.com>
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
prev parent reply other threads:[~2018-01-11 23:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180111211652.GT3124@bitfolk.com>
[not found] ` <20180111215924.GV3124@bitfolk.com>
2018-01-11 22:26 ` [Xen-users] Trying out vixen: failure to start device model Andy Smith
2018-01-11 23:36 ` Andy Smith [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180111233628.GY3124@bitfolk.com \
--to=andy@strugglers.net \
--cc=xen-devel@lists.xenproject.org \
--cc=xen-users@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).