From: John Nemeth <jnemeth@cue.bc.ca>
To: Wei Liu <wei.liu2@citrix.com>, John Nemeth <jnemeth@cue.bc.ca>
Cc: xen-devel@lists.xenproject.org
Subject: Re: Xen 4.6 script calling conventions
Date: Mon, 4 Jul 2016 01:07:51 -0700 [thread overview]
Message-ID: <201607040807.u6487pPx021118@server.cornerstoneservice.ca> (raw)
In-Reply-To: <20160702114043.GF32594@citrix.com>
On Jul 2, 12:40pm, Wei Liu wrote:
} On Tue, Jun 28, 2016 at 06:00:49PM -0700, John Nemeth wrote:
} > I'm trying to package Xen 4.6 (specifically Xen 4.6.3) for
} > use with NetBSD. I have it mostly done; however, when I try to
} > create a domU, libxl goes into an infinite loop calling the scripts.
} > If I try to create a domU with no network or disk, it works fine
} > (albeit of rather limited use). Have there been changes between
} > Xen 4.5 and Xen 4.6 in the calling convention for the scripts? Is
} > there documentation on what is expected somewhere? Please CC me on
} > any responses. Here is my domU config file:
}
} Can you give this patch a try? I don't have netbsd system at hand to
} test it.
Thanks. It pretty much did the trick. I just had to make
one minor change to your patch.
} I suspect netbsd doesn't support stubdom because that pile of code is a
} bit Linux centric, but it wouldn't hurt to prepare for it.
No, NetBSD doesn't do stubdom. However, I would certainly
like to NetBSD's support for Xen become equal to Linux's support
(or better :-) ), so anything that makes that easier is a good
thing.
}-- End of excerpt from Wei Liu
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-04 8:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 1:00 Xen 4.6 script calling conventions John Nemeth
2016-06-29 15:46 ` Dario Faggioli
2016-07-02 11:40 ` Wei Liu
2016-07-04 8:07 ` John Nemeth [this message]
2016-07-04 11:18 ` Wei Liu
2016-07-04 11:45 ` Roger Pau Monné
2016-07-04 11:57 ` Roger Pau Monné
2016-07-04 12:04 ` Wei Liu
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=201607040807.u6487pPx021118@server.cornerstoneservice.ca \
--to=jnemeth@cue.bc.ca \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@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).