RE: [Xen-devel] detecting a 'block-configure' via xenbus

["James Harper" <james.harper@xxxxxxxxxxxxxxxx>]

> On 16/11/08 09:02, "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
wrote:
> 
> > Under Debian Lenny's Xen 3.2.1, when I execute such a command, Dom0
> > writes to the backend values 'params' and 'type', twice, but doesn't
> > update the 'sectors' value to match the new device, or initiate a
state
> > change. Given that, the best I can come up with is to watch
'params',
> > and initiate the state change in DomU to re-initialise the backend
> > connection and hopefully get an updated sectors value...
> 
> block-configure has only ever worked for CDROM virtual media changes
> (i.e.,
> change ISO file) for HVM guests, via full qemu CDROM drive emulation.
It
> appears nothing else was ever implemented, so this has no chance of
> working
> without further blkback/blktap changes.
> 
> I noticed that the SuSE kernel does have a new blkback source file
cdrom.c
> which I don't think has ever been proposed for inclusion in
xen-unstable.
> Perhaps that is a protocol extension worth looking at?
> 

It reportedly works with the Citrix product, is the protocol definition
itself open? A xenstore-ls shows what looks like some SCSI modepage data
in the tree which I hadn't seen before too.

James

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel