All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Fabio Fantoni <fabio.fantoni@m2r.biz>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: xen 4.6 regression: xl create fails if domU have custom vifname
Date: Fri, 28 Aug 2015 08:56:45 +0100	[thread overview]
Message-ID: <20150828075645.GA17809@zion.uk.xensource.com> (raw)
In-Reply-To: <55E012BE.9000100@m2r.biz>

On Fri, Aug 28, 2015 at 09:50:22AM +0200, Fabio Fantoni wrote:
> Il 27/08/2015 16:46, Wei Liu ha scritto:
> >On Thu, Aug 27, 2015 at 04:41:46PM +0200, Fabio Fantoni wrote:
> >>Today trying xen 4.6.0-rc2 with all things needed for future production
> >>server I found a regression: xl create fails if domU have custom vifname.
> >>xl create test.cfg
> >>Parsing config from test.cfg
> >>libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus:
> >>/etc/xen/scripts/vif-bridge add [14581] exited with error status 1
> >>libxl: error: libxl_device.c:1085:device_hotplug_child_death_cb: script: ip
> >>link set vif14.0-emu name frc-0-0-emu failed
> >This is the culprit.
> >
> >Did you do a clean install?
> >
> >You need to remove udev files in /etc. I should have mentioned this in
> >testing instructions.
> >
> >Wei.
> 
> Sorry for my mistake I didn't remember to check /etc because the testing deb
> (with make debball) delete /etc files only if specified as considered config
> files.

No worries. It's my fault for not mentioning it in test instructions.
This is something likely to trip people over.

> Removing the udev file solves the problem.

Thanks for confirming.

Wei.

      reply	other threads:[~2015-08-28  7:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27 14:41 xen 4.6 regression: xl create fails if domU have custom vifname Fabio Fantoni
2015-08-27 14:46 ` Wei Liu
2015-08-28  7:50   ` Fabio Fantoni
2015-08-28  7:56     ` Wei Liu [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=20150828075645.GA17809@zion.uk.xensource.com \
    --to=wei.liu2@citrix.com \
    --cc=fabio.fantoni@m2r.biz \
    --cc=ian.campbell@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.