On Fri, 2014-03-28 at 21:49 +0100, Axel Beckert wrote: > Hi Ian. > > Ian Campbell wrote: > > Subject: Please support operation on systems without xend installed > > The support is probably already there, at least in 4.4. From the man > page of xen-create-image: > > --no-xen-ok Don't complain if xen seems not installed or xend is > not running. (Needed for the testsuite.) > > Can you check if that helps also in your case, i.e. use 4.4 and run it > with that option?
Our automated test infra uses Wheezy which only has 4.3. We've worked around it for now (by filling the appropriate file with dummy content) so we can live with that until Jessie. > > Upstream Xen has made Xen a configure time option which defaults to off > > which > ^^^ > > I suspect that should be "Xend". Correct. Oops. > > will release with Xen 4.4 in the new year. Also the new ARM port will not > > include xend even as an option (the above log is actually from the ARM test > > because the test infrastructure currently forces xend on for x86). BTW apart > > from this issue xen-tools seems to work perfectly fine on armhf. > > So I'll likely make this check off by default or remove it completely. Sounds good. Another option would be to validate its content iff it exists. > > I also observed a few secondary issues: > > > > The callers of fail() appear for the most part to expect the final "\n" to > > be > > appended to the log but logprint() does not do so (the callers of logprint > > appear to get this right and pass "\n" themselves where necessary). > > > > The overall xen-create-image command appears to succeed despite erroring out > > early (no domain is actually created). > > Does this relate to 4.4 or 4.3.1? I've only tried 4.3.1 from Wheezy. > There have been quite some changes > in 4.4 with regards to proper error handling and passing. > > If you just had a look at 4.3.1 here, please check 4.4, too. If the > issue is still there, please file a new, separate, bug report. (I'll > consider this bug report for being about adaptions to deprecated > features of Xen as these are the primary issues in this report.) I can't easily try 4.4 on the systems I have in my hands right now, but if/when I get a chance I'll indeed open a fresh report if needed. > > If xend is installed then the warning/advice to add a network-script setting > > to xend-config.sxp is contrary to both upstream Xen and the Debian Xen > > maintainer's advice, which is to use /etc/network/interfaces to configure > > host > > level networking, see /usr/share/doc/xen-utils-4.1/README.Debian and > > http://wiki.xen.org/wiki/HostConfiguration/Networking. Under xl this is the > > only possible way to configure networking. > > Yeah, noticed that when setting up the two Xen Dom0s for DebConf 13 > which were installed with Wheezy from scratch and not dist-upgraded > from Squeeze. :-) > > Will likely remove that warning completely. Thanks. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
