On 10/14/2010 03:16 PM, Anthony Liguori wrote:
> On 10/14/2010 05:03 PM, Robert Relyea wrote:
>>> Remote device passthrough is just a special case of passthrough.
>>> It's got interesting characteristics in that unlike local device
>>> passthrough, if you preserve the connection to the remove devi
On 10/14/2010 05:03 PM, Robert Relyea wrote:
Remote device passthrough is just a special case of passthrough.
It's got interesting characteristics in that unlike local device
passthrough, if you preserve the connection to the remove device,
migration is still possible.
However, remote device
On 10/14/2010 11:52 AM, Anthony Liguori wrote:
> On 10/14/2010 01:37 PM, Robert Relyea wrote:
>> Anthony Liguori wrote:
>>
>>
>>> > And how does the smart card state get migrated during migration? How
>>> > do you keep it synced with QEMU?
>>> >
>>> > I don't understand the use-case behind this.
On 10/14/2010 01:37 PM, Robert Relyea wrote:
Anthony Liguori wrote:
> And how does the smart card state get migrated during migration? How
> do you keep it synced with QEMU?
>
> I don't understand the use-case behind this. Is this so that a local
> physical smart card can be passed thro
Anthony Liguori wrote:
> > And how does the smart card state get migrated during migration? How
> > do you keep it synced with QEMU?
> >
> > I don't understand the use-case behind this. Is this so that a local
> > physical smart card can be passed through to a guest from a Spice
> > client and wh
- "Anthony Liguori" wrote:
> On 10/12/2010 12:09 PM, Alon Levy wrote:
> > The smart card is not being migrated. It is running on the client
> machine,
> > which is not being migrated/shutdown (same as vncviewer isn't
> migrated).
> >
> >
>
> Ok, let's look at this compared to another si
On 10/12/2010 12:09 PM, Alon Levy wrote:
The smart card is not being migrated. It is running on the client machine,
which is not being migrated/shutdown (same as vncviewer isn't migrated).
Ok, let's look at this compared to another similar use-case: USB
passthrough of a webcam device that
- "Anthony Liguori" wrote:
> On 10/12/2010 11:43 AM, Alon Levy wrote:
> > - "Anthony Liguori" wrote:
> >
> >
> >> On 10/12/2010 11:03 AM, Alon Levy wrote:
> >>
> >>> - "Anthony Liguori" wrote:
> >>>
> >>>
> >>>
> On 10/12/2010 07:58 AM, Alon Levy wrote:
> >>
On 10/12/2010 11:43 AM, Alon Levy wrote:
- "Anthony Liguori" wrote:
On 10/12/2010 11:03 AM, Alon Levy wrote:
- "Anthony Liguori" wrote:
On 10/12/2010 07:58 AM, Alon Levy wrote:
This patch adds a new device, it is described in full in the
- "Anthony Liguori" wrote:
> On 10/12/2010 11:03 AM, Alon Levy wrote:
> > - "Anthony Liguori" wrote:
> >
> >
> >> On 10/12/2010 07:58 AM, Alon Levy wrote:
> >>
> >>> This patch adds a new device, it is described in full in the
> second
> >>>
> >> patch
> >>
> >>>
On 10/12/2010 11:03 AM, Alon Levy wrote:
- "Anthony Liguori" wrote:
On 10/12/2010 07:58 AM, Alon Levy wrote:
This patch adds a new device, it is described in full in the second
patch
intro and also in the documentation in docs. In brief it provides a
sta
- "Anthony Liguori" wrote:
> On 10/12/2010 07:58 AM, Alon Levy wrote:
> > This patch adds a new device, it is described in full in the second
> patch
> > intro and also in the documentation in docs. In brief it provides a
> standard
> > smart card reader device.
> >
> > The first patch is th
On 10/12/2010 07:58 AM, Alon Levy wrote:
This patch adds a new device, it is described in full in the second patch
intro and also in the documentation in docs. In brief it provides a standard
smart card reader device.
The first patch is the configure change and docs.
The second patch contains th
This patch adds a new device, it is described in full in the second patch
intro and also in the documentation in docs. In brief it provides a standard
smart card reader device.
The first patch is the configure change and docs.
The second patch contains the actual device, I couldn't figure out a go
On 10/06/2010 05:12 PM, Alon Levy wrote:
Actually, both are possible - but the later is the interesting use case (the
former is mainly for debugging). To elaborate: the device is meant to allow
a hardware reader to be available to the guest while still being available to
the client (which is runn
On 10/07/2010 02:39 AM, Alon Levy wrote:
- "Anthony Liguori" wrote:
On 10/06/2010 03:55 AM, Gerd Hoffmann wrote:
On 10/06/10 02:28, Alon Levy wrote:
Does this work with live migration? I can't see how it would.
No, it doesn't right now. It would
- "Anthony Liguori" wrote:
> On 10/06/2010 03:55 AM, Gerd Hoffmann wrote:
> > On 10/06/10 02:28, Alon Levy wrote:
> >>
> >>>
> >>> Does this work with live migration? I can't see how it would.
> >>>
> >>
> >> No, it doesn't right now. It would require cooperation with the
> client,
> >> to
On 10/06/10 21:00, Anthony Liguori wrote:
Better yet, mark the guest as unmigrateable and let the management tool
unplug the usb device before migration and replug it after migration.
Yep, that will work too.
cheers,
Gerd
- "Anthony Liguori" wrote:
> On 10/05/2010 07:28 PM, Alon Levy wrote:
> > - "Anthony Liguori" wrote:
> >
> >
> >> On 10/05/2010 04:32 PM, Alon Levy wrote:
> >>
> >>> This patch adds a new device, it is described in full in the
> second
> >>>
> >> patch
> >>
> >>>
- "Anthony Liguori" wrote:
> On 10/06/2010 03:55 AM, Gerd Hoffmann wrote:
> > On 10/06/10 02:28, Alon Levy wrote:
> >>
> >>>
> >>> Does this work with live migration? I can't see how it would.
> >>>
> >>
> >> No, it doesn't right now. It would require cooperation with the
> client,
> >> to
On 10/06/2010 03:55 AM, Gerd Hoffmann wrote:
On 10/06/10 02:28, Alon Levy wrote:
Does this work with live migration? I can't see how it would.
No, it doesn't right now. It would require cooperation with the client,
to tell it to reconnect to the target qemu (kind of like spice).
I think
On 10/05/2010 07:28 PM, Alon Levy wrote:
- "Anthony Liguori" wrote:
On 10/05/2010 04:32 PM, Alon Levy wrote:
This patch adds a new device, it is described in full in the second
patch
intro and also in the documentation in docs. In brief it provides a
sta
On 10/06/10 02:28, Alon Levy wrote:
Does this work with live migration? I can't see how it would.
No, it doesn't right now. It would require cooperation with the client,
to tell it to reconnect to the target qemu (kind of like spice).
I think until we have this migration should have pret
- "Anthony Liguori" wrote:
> On 10/05/2010 04:32 PM, Alon Levy wrote:
> > This patch adds a new device, it is described in full in the second
> patch
> > intro and also in the documentation in docs. In brief it provides a
> standard
> > smart card reader device.
> >
> > The first patch is th
On 10/05/2010 04:32 PM, Alon Levy wrote:
This patch adds a new device, it is described in full in the second patch
intro and also in the documentation in docs. In brief it provides a standard
smart card reader device.
The first patch is the configure change and docs.
The second patch contains th
This patch adds a new device, it is described in full in the second patch
intro and also in the documentation in docs. In brief it provides a standard
smart card reader device.
The first patch is the configure change and docs.
The second patch contains the actual device, I couldn't figure out a go
26 matches
Mail list logo
