From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Olivier B." Subject: Re: XenParavirtOps wiki cleanup, comments needed Date: Mon, 25 Jul 2011 23:12:59 +0200 Message-ID: <4E2DDC5B.9070505@daevel.fr> References: <20110725202357.GN32373@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <20110725202357.GN32373@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hi, if "device hotplug" include block attach, then it works : I can add new block device in a running PVOps DomU. Le 25/07/2011 22:23, Pasi Kärkkäinen a écrit : > Hello, > > Jeremy/Konrad/others: What do you guys think of the stuff on XenParavirtOps page? > http://wiki.xen.org/xenwiki/XenParavirtOps > > I was planning to clean it up, and remove things like this: > > "Xen/paravirt_ops has not had wide use or testing, so any testing you do is extremely valuable." > "Xen/paravirt_ops is very much a work in progress, and there are still feature gaps compared to 2.6.18-xen." > > etc.. those don't sound like very up-to-date anymore :) > > What about the notes like these: > - "CPU hotplug" (I guess this is about vcpu hotplug?) > - "Device hotplug" > - "Device unplug/module unload" > > What's the status of those so I can update the page.. ? > > Thanks, > > -- Pasi > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel