|
From: | Marc-André Lureau |
Subject: | Re: [Qemu-devel] [PATCH 07/12] block: save the associated child in BlockDriverState |
Date: | Fri, 21 Jun 2013 15:30:38 +0200 |
There is already an interface for eject/change, which is the monitor.
> What exactly are you trying to do here (I guess I'll understand more
> when I get to the later patches)?
>
> Getting to the bottom BlockDriverState to be able to eject & change it.
> (it could also be named the "parent", but other parts of the code
> suggest the "child" name)
To signal an eject or medium change, the SPICE client should simply ask
libvirt to do so. It is fine to change "from" spicebd: "to" spicebd:,
the guest would still perceive it as a change.
I'm not sure how libvirt communicates the change back to the SPICE
client, and whether it is asynchronous or synchronous.
BTW, note that IDE or virtio-blk do not support removable media, and are
not able to pass eject or media change notifications. SCSI devices
(such as usb-bot, usb-uas and virtio-scsi) can.
Then draw it. :) But from the above description it looks like it is not
> Can you draw the relationships between all the BlockDriverStates in a
> spicebd: drive?
>
>
> Hopefully, but I have only tested with raw images (w/wo snapshot).
necessary, it should simply be "raw" on top of "spicebd". Parsing
formats should be done on the client side, perhaps by invoking qemu-nbd
and tunnelling the NBD data on the SPICE channel.
[Prev in Thread] | Current Thread | [Next in Thread] |