While working on pvscsi support for libxl I noticed that assigning a
resource exclusivly to just a single domU via libxl will be a major
effort. Up to now libxl could rely on the fact that a resource can be
either shared or the backend deals with the attempt to share.
There are two cases in pvscsi:
1) a single physical HST:CHN:TGT:LUN device must be assigned to just a
single domU. While the (xenlinux) backend driver allows to assign
the device to more than one domU the sharing can not work in
practice.
2) the xenlinux backend driver has two modes: emulation and raw. With
raw mode the SCSI commands coming from domU will be passed directly
to the physical device. I think its required to make sure that all
devices connected to a physical scsi host must operate either
entirely in raw mode or on emulation mode.
To handle both cases libxl could either assume that the admin is
responsible for proper configuration:
- just one domU per physical device
- if raw mode is enabled all devices on the physcial scsi host will be
assigned to just one domU
Or libxl gets functionality to verify that two cases above are really
enforced. Doing that means that there has to be some global lock under
which the system state in xenstore is parsed and the to be assigned domU
configuration is compared:
- are the physical devices already assigned
- is the raw mode properly configured
In xend the case #1 was not handled. There is some code for case #2, I
have to check how complete the enforcement in xend was.
I wonder what should be done in my changes for libxl.
Olaf
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
