Re: port-xen/48220: xentools-4.1: xl has problems with file/vnd based disks

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

The following reply was made to PR port-xen/48220; it has been noted by GNATS.

From: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: port-xen-maintainer%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost,
        netbsd-bugs%NetBSD.org@localhost, toby.karyadi%gmail.com@localhost
Subject: Re: port-xen/48220: xentools-4.1: xl has problems with file/vnd
 based disks
Date: Thu, 19 Sep 2013 23:27:46 +0200

 On Thu, Sep 19, 2013 at 08:40:01PM +0000, Toby Karyadi wrote:
 >  >   use xl, then you should be using xentools42 (and xenkernel42).
 >  Actually I'm trying to submit patches for xentools41 to fix the problems 
 >  with xl that I mentioned. I'm hoping that it would provide a smoother 
 >  migration from 3.3 to 4.*. I thought xentools42 doesn't support HVM domU 
 >  just yet, is that no longer true? Trying xentools42 is my next step.
 
 HVM domU works with xen 4.2
 
 >  >   
 >  >   } 2) Once problem 1) is fixed, xl also has another bug that caused
 >  >   } xenbackendd to not call the 'block' script to properly undo the
 >  >   } vnd device.
 >  >   
 >  >        If you are using xl then you should not be running xenbackendd.
 >  >   That is only for use with xm.  Using the combination of xl and
 >  >   xenbackendd can mess things up.  This would be another reason to
 >  >   use xentools42 since the startup scripts have been redone to get
 >  >   this correct.
 >  >   
 >  If you look at rc.d/xencommons for 4.1, it actually does start 
 >  xenbackendd. On the other hand, xend should not be started. 
 >  Unfortunately xencommons and xend rc scripts uses the same rcvar 'xend', 
 >  so if you specify xend=yes in /etc/rc.conf you'll start both xencommons 
 >  and xend. The work around is to have xencommons and xend files under 
 >  /etc/rc.conf.d where the xencommons file should contain xend=yes where 
 >  the xend file should contain xend=no.
 
 At this time, xl is not recommended on xen 4.1, that's why xend is still
 started. xl is known to have various problems and limitations
 (i.e. features present in xm which have not been intgrated in xl,
 like shutdown -a)
 
 -- 
 Manuel Bouyer <bouyer%antioche.eu.org@localhost>
      NetBSD: 26 ans d'experience feront toujours la difference
 --