On Mon, Mar 02, Juergen Gross wrote:
> On 03/02/2015 04:14 PM, Olaf Hering wrote:
> >In this case the code which checks pdev usage in
> >libxl_device_vscsi_get_host can just be removed.
> Hmm, maybe issuing a warning would be a sensible thing to do?
This gets us back to square #1 with the questio
On 03/02/2015 04:14 PM, Olaf Hering wrote:
On Mon, Mar 02, Juergen Gross wrote:
On 03/02/2015 11:16 AM, Olaf Hering wrote:
+How to do live migration?
+ - pdev will likely be evaluated again on the target host if it came from
+ domU.cfg. But what about pdev from 'xl scsi-attach pdev vdev'? It
On Mon, Mar 02, Juergen Gross wrote:
> On 03/02/2015 11:16 AM, Olaf Hering wrote:
> >+How to do live migration?
> >+ - pdev will likely be evaluated again on the target host if it came from
> >+ domU.cfg. But what about pdev from 'xl scsi-attach pdev vdev'? Its
> >required
> >+ to adjust h:c:
On 03/02/2015 11:16 AM, Olaf Hering wrote:
Signed-off-by: Olaf Hering
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Keir Fraser
Cc: Tim Deegan
---
docs/misc/pvscsi.txt | 147 +++
1 file changed, 147 insertions(+)
diff --git a/docs/m
>>> On 02.03.15 at 11:16, wrote:
> +== Config Format ==
> +
> +The domU.cfg syntax is "vscsi=[ 'pdev,vdev[,option]' ]". pdev is the dom0
> device
> +in either /dev/$device or pHOST:CHANNEL:TARGET:LUN notation. vdev is the
> domU
Since /dev/... is OS (Linux) specific, I think the text should ex
Signed-off-by: Olaf Hering
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Keir Fraser
Cc: Tim Deegan
---
docs/misc/pvscsi.txt | 147 +++
1 file changed, 147 insertions(+)
diff --git a/docs/misc/pvscsi.txt b/docs/misc/pvscsi.txt
new file
