[Qemu-devel] RFC: QMP event notification for disk media eject

[Qemu-devel] RFC: QMP event notification for disk media eject

[Luiz Capitulino]

Hi there,

I need feedback on a new QMP event.

Problem
=======

There's no way for a management tool to detect that a guest OS has ejected the
media in a CDROM or Floppy disk drive (I'm discarding polling, because it's
undesirable at best).

The end result is that the management tool can get confused, this is happening
with libvirt when migration is involved: if the guest is saved/restored or
migrated, then libvirt will start the guest again with media still present.

NOTE: Most of the analysis here was done by Daniel Berrange.

Solution
========

We need a new QMP event to solve that. There are two possible events, a
general one and a very specific one.

There are 3 scenarios in which both events should be emitted:

 1. When guest OS ejects media
 2. When 'eject' monitor command is run
 3. When 'change' monitor command is run

BLOCK_MEDIA_CHANGE
------------------

This is the general event, it's emitted when any removable block device
is changed.

Ideally, the event should contain two pieces of info:

 - qdev device name
 - new file path (to allow distinguishing eject from change)

Example:

  { "event": "BLOCK_MEDIA_CHANGE", "data": { "qdev-id": "myid",
                                             "new-path": "/foo/bar/dir/distro.iso" },
                                             ... }

BLOCK_MEDIA_EJECT
-----------------

This event is only emitted when a CDROM or a floppy disk is ejected.

The event contains one info one:

 - device name

Example:

  { "event": "BLOCK_MEDIA_EJECT", "data": { "device-name": "ide1-cd0" }, ... }

[Qemu-devel] Re: RFC: QMP event notification for disk media eject

[Kevin Wolf]

Am 11.01.2011 14:11, schrieb Luiz Capitulino:
> Hi there,
> 
> I need feedback on a new QMP event.
> 
> Problem
> =======
> 
> There's no way for a management tool to detect that a guest OS has ejected the
> media in a CDROM or Floppy disk drive (I'm discarding polling, because it's
> undesirable at best).
> 
> The end result is that the management tool can get confused, this is happening
> with libvirt when migration is involved: if the guest is saved/restored or
> migrated, then libvirt will start the guest again with media still present.
> 
> NOTE: Most of the analysis here was done by Daniel Berrange.
> 
> Solution
> ========
> 
> We need a new QMP event to solve that. There are two possible events, a
> general one and a very specific one.
> 
> There are 3 scenarios in which both events should be emitted:
> 
>  1. When guest OS ejects media
>  2. When 'eject' monitor command is run
>  3. When 'change' monitor command is run
> 
> BLOCK_MEDIA_CHANGE
> ------------------
> 
> This is the general event, it's emitted when any removable block device
> is changed.
> 
> Ideally, the event should contain two pieces of info:
> 
>  - qdev device name

Is there a reason why you use the device name instead of the drive
name/blockdev ID here?

>  - new file path (to allow distinguishing eject from change)

How do you distinguish? Would this key be missing for ejects? An empty
string? Something else?

> Example:
> 
>   { "event": "BLOCK_MEDIA_CHANGE", "data": { "qdev-id": "myid",
>                                              "new-path": "/foo/bar/dir/distro.iso" },
>                                              ... }
> 
> BLOCK_MEDIA_EJECT
> -----------------
> 
> This event is only emitted when a CDROM or a floppy disk is ejected.
> 
> The event contains one info one:
> 
>  - device name
> 
> Example:
> 
>   { "event": "BLOCK_MEDIA_EJECT", "data": { "device-name": "ide1-cd0" }, ... }

I think it's called drive name in most other places.

Kevin

[Qemu-devel] Re: RFC: QMP event notification for disk media eject

[Luiz Capitulino]

On Tue, 11 Jan 2011 14:28:23 +0100
Kevin Wolf <kwolf@redhat.com> wrote:

> Am 11.01.2011 14:11, schrieb Luiz Capitulino:
> > Hi there,
> > 
> > I need feedback on a new QMP event.
> > 
> > Problem
> > =======
> > 
> > There's no way for a management tool to detect that a guest OS has ejected the
> > media in a CDROM or Floppy disk drive (I'm discarding polling, because it's
> > undesirable at best).
> > 
> > The end result is that the management tool can get confused, this is happening
> > with libvirt when migration is involved: if the guest is saved/restored or
> > migrated, then libvirt will start the guest again with media still present.
> > 
> > NOTE: Most of the analysis here was done by Daniel Berrange.
> > 
> > Solution
> > ========
> > 
> > We need a new QMP event to solve that. There are two possible events, a
> > general one and a very specific one.
> > 
> > There are 3 scenarios in which both events should be emitted:
> > 
> >  1. When guest OS ejects media
> >  2. When 'eject' monitor command is run
> >  3. When 'change' monitor command is run
> > 
> > BLOCK_MEDIA_CHANGE
> > ------------------
> > 
> > This is the general event, it's emitted when any removable block device
> > is changed.
> > 
> > Ideally, the event should contain two pieces of info:
> > 
> >  - qdev device name
> 
> Is there a reason why you use the device name instead of the drive
> name/blockdev ID here?

Good question, this is a copy & paste from Daniel initial request, so
he's the best person to answer that question.

> >  - new file path (to allow distinguishing eject from change)
> 
> How do you distinguish? Would this key be missing for ejects? An empty
> string? Something else?

Yes, I think it would be optional and thus only part of the change
command.

> > Example:
> > 
> >   { "event": "BLOCK_MEDIA_CHANGE", "data": { "qdev-id": "myid",
> >                                              "new-path": "/foo/bar/dir/distro.iso" },
> >                                              ... }
> > 
> > BLOCK_MEDIA_EJECT
> > -----------------
> > 
> > This event is only emitted when a CDROM or a floppy disk is ejected.
> > 
> > The event contains one info one:
> > 
> >  - device name
> > 
> > Example:
> > 
> >   { "event": "BLOCK_MEDIA_EJECT", "data": { "device-name": "ide1-cd0" }, ... }
> 
> I think it's called drive name in most other places.

Ok, please note that we won't implement both events, we have to choose
one or the other.

[Qemu-devel] Re: RFC: QMP event notification for disk media eject

[Daniel P. Berrange]

On Tue, Jan 11, 2011 at 03:45:49PM -0200, Luiz Capitulino wrote:
> On Tue, 11 Jan 2011 14:28:23 +0100
> Kevin Wolf <kwolf@redhat.com> wrote:
> 
> > Am 11.01.2011 14:11, schrieb Luiz Capitulino:
> > > Hi there,
> > > 
> > > I need feedback on a new QMP event.
> > > 
> > > Problem
> > > =======
> > > 
> > > There's no way for a management tool to detect that a guest OS has ejected the
> > > media in a CDROM or Floppy disk drive (I'm discarding polling, because it's
> > > undesirable at best).
> > > 
> > > The end result is that the management tool can get confused, this is happening
> > > with libvirt when migration is involved: if the guest is saved/restored or
> > > migrated, then libvirt will start the guest again with media still present.
> > > 
> > > NOTE: Most of the analysis here was done by Daniel Berrange.
> > > 
> > > Solution
> > > ========
> > > 
> > > We need a new QMP event to solve that. There are two possible events, a
> > > general one and a very specific one.
> > > 
> > > There are 3 scenarios in which both events should be emitted:
> > > 
> > >  1. When guest OS ejects media
> > >  2. When 'eject' monitor command is run
> > >  3. When 'change' monitor command is run
> > > 
> > > BLOCK_MEDIA_CHANGE
> > > ------------------
> > > 
> > > This is the general event, it's emitted when any removable block device
> > > is changed.
> > > 
> > > Ideally, the event should contain two pieces of info:
> > > 
> > >  - qdev device name
> > 
> > Is there a reason why you use the device name instead of the drive
> > name/blockdev ID here?
> 
> Good question, this is a copy & paste from Daniel initial request, so
> he's the best person to answer that question.

There isn't any reason I chose one over the other, libvirt
certainly doesn't care - we can hook into either option.
I assume the best thing is to use the same identifier
that we already use in BLOCK_IO_ERROR event, for sake
of consistency.

Daniel

[Qemu-devel] Re: RFC: QMP event notification for disk media eject

[Anthony Liguori]

On 01/11/2011 07:11 AM, Luiz Capitulino wrote:
> Hi there,
>
> I need feedback on a new QMP event.
>
> Problem
> =======
>
> There's no way for a management tool to detect that a guest OS has ejected the
> media in a CDROM or Floppy disk drive (I'm discarding polling, because it's
> undesirable at best).
>
> The end result is that the management tool can get confused, this is happening
> with libvirt when migration is involved: if the guest is saved/restored or
> migrated, then libvirt will start the guest again with media still present.
>
> NOTE: Most of the analysis here was done by Daniel Berrange.
>
> Solution
> ========
>
> We need a new QMP event to solve that. There are two possible events, a
> general one and a very specific one.
>
> There are 3 scenarios in which both events should be emitted:
>
>   1. When guest OS ejects media
>   2. When 'eject' monitor command is run
>   3. When 'change' monitor command is run
>
> BLOCK_MEDIA_CHANGE
> ------------------
>
> This is the general event, it's emitted when any removable block device
> is changed.
>
> Ideally, the event should contain two pieces of info:
>
>   - qdev device name
>   - new file path (to allow distinguishing eject from change)
>
> Example:
>
>    { "event": "BLOCK_MEDIA_CHANGE", "data": { "qdev-id": "myid",
>                                               "new-path": "/foo/bar/dir/distro.iso" },
>                                               ... }
>    

I think this is short sighted as block devices are not simply expressed 
in terms of new-path.  You would need to do something like:

{ 'blockdev': {'file': '/foo/bar/dir/distro.iso', 'cache', 'off', ...}}

And that adds a lot of complexity that I'm not sure is really 
justified.  Tray status is really what you're interested in.  The user 
cannot directly change the media, only the management tools can so why 
would the management tools need to be notified about something that they 
did?

Regards,

Anthony Liguori

> BLOCK_MEDIA_EJECT
> -----------------
>
> This event is only emitted when a CDROM or a floppy disk is ejected.
>
> The event contains one info one:
>
>   - device name
>
> Example:
>
>    { "event": "BLOCK_MEDIA_EJECT", "data": { "device-name": "ide1-cd0" }, ... }
>    

Re: [Qemu-devel] Re: RFC: QMP event notification for disk media eject

[Markus Armbruster]

Anthony Liguori <anthony@codemonkey.ws> writes:

> On 01/11/2011 07:11 AM, Luiz Capitulino wrote:
>> Hi there,
>>
>> I need feedback on a new QMP event.
>>
>> Problem
>> =======
>>
>> There's no way for a management tool to detect that a guest OS has ejected the
>> media in a CDROM or Floppy disk drive (I'm discarding polling, because it's
>> undesirable at best).
>>
>> The end result is that the management tool can get confused, this is happening
>> with libvirt when migration is involved: if the guest is saved/restored or
>> migrated, then libvirt will start the guest again with media still present.
>>
>> NOTE: Most of the analysis here was done by Daniel Berrange.
>>
>> Solution
>> ========
>>
>> We need a new QMP event to solve that. There are two possible events, a
>> general one and a very specific one.
>>
>> There are 3 scenarios in which both events should be emitted:
>>
>>   1. When guest OS ejects media
>>   2. When 'eject' monitor command is run
>>   3. When 'change' monitor command is run
>>
>> BLOCK_MEDIA_CHANGE
>> ------------------
>>
>> This is the general event, it's emitted when any removable block device
>> is changed.
>>
>> Ideally, the event should contain two pieces of info:
>>
>>   - qdev device name
>>   - new file path (to allow distinguishing eject from change)
>>
>> Example:
>>
>>    { "event": "BLOCK_MEDIA_CHANGE", "data": { "qdev-id": "myid",
>>                                               "new-path": "/foo/bar/dir/distro.iso" },
>>                                               ... }
>>    
>
> I think this is short sighted as block devices are not simply
> expressed in terms of new-path.  You would need to do something like:
>
> { 'blockdev': {'file': '/foo/bar/dir/distro.iso', 'cache', 'off', ...}}
>
> And that adds a lot of complexity that I'm not sure is really
> justified.  Tray status is really what you're interested in.

I figure the important bit is the notification that tray status changed.
If management software wants to know more, it can query when it gets the
event.

>                                                               The user
> cannot directly change the media, only the management tools can so why
> would the management tools need to be notified about something that
> they did?

Re: [Qemu-devel] Re: RFC: QMP event notification for disk media eject

[Luiz Capitulino]

On Tue, 11 Jan 2011 15:29:12 +0100
Markus Armbruster <armbru@redhat.com> wrote:

> Anthony Liguori <anthony@codemonkey.ws> writes:
> 
> > On 01/11/2011 07:11 AM, Luiz Capitulino wrote:
> >> Hi there,
> >>
> >> I need feedback on a new QMP event.
> >>
> >> Problem
> >> =======
> >>
> >> There's no way for a management tool to detect that a guest OS has ejected the
> >> media in a CDROM or Floppy disk drive (I'm discarding polling, because it's
> >> undesirable at best).
> >>
> >> The end result is that the management tool can get confused, this is happening
> >> with libvirt when migration is involved: if the guest is saved/restored or
> >> migrated, then libvirt will start the guest again with media still present.
> >>
> >> NOTE: Most of the analysis here was done by Daniel Berrange.
> >>
> >> Solution
> >> ========
> >>
> >> We need a new QMP event to solve that. There are two possible events, a
> >> general one and a very specific one.
> >>
> >> There are 3 scenarios in which both events should be emitted:
> >>
> >>   1. When guest OS ejects media
> >>   2. When 'eject' monitor command is run
> >>   3. When 'change' monitor command is run
> >>
> >> BLOCK_MEDIA_CHANGE
> >> ------------------
> >>
> >> This is the general event, it's emitted when any removable block device
> >> is changed.
> >>
> >> Ideally, the event should contain two pieces of info:
> >>
> >>   - qdev device name
> >>   - new file path (to allow distinguishing eject from change)
> >>
> >> Example:
> >>
> >>    { "event": "BLOCK_MEDIA_CHANGE", "data": { "qdev-id": "myid",
> >>                                               "new-path": "/foo/bar/dir/distro.iso" },
> >>                                               ... }
> >>    
> >
> > I think this is short sighted as block devices are not simply
> > expressed in terms of new-path.  You would need to do something like:
> >
> > { 'blockdev': {'file': '/foo/bar/dir/distro.iso', 'cache', 'off', ...}}
> >
> > And that adds a lot of complexity that I'm not sure is really
> > justified.  Tray status is really what you're interested in.
> 
> I figure the important bit is the notification that tray status changed.
> If management software wants to know more, it can query when it gets the
> event.

Which means you're in favor of the BLOCK_MEDIA_EJECT event, right?

> 
> >                                                               The user
> > cannot directly change the media, only the management tools can so why
> > would the management tools need to be notified about something that
> > they did?
> 

Re: [Qemu-devel] RFC: QMP event notification for disk media eject

[Markus Armbruster]

Luiz Capitulino <lcapitulino@redhat.com> writes:

> Hi there,
>
> I need feedback on a new QMP event.
>
> Problem
> =======
>
> There's no way for a management tool to detect that a guest OS has ejected the
> media in a CDROM or Floppy disk drive (I'm discarding polling, because it's
> undesirable at best).
>
> The end result is that the management tool can get confused, this is happening
> with libvirt when migration is involved: if the guest is saved/restored or
> migrated, then libvirt will start the guest again with media still present.
>
> NOTE: Most of the analysis here was done by Daniel Berrange.
>
> Solution
> ========
>
> We need a new QMP event to solve that. There are two possible events, a
> general one and a very specific one.
>
> There are 3 scenarios in which both events should be emitted:
>
>  1. When guest OS ejects media
>  2. When 'eject' monitor command is run
>  3. When 'change' monitor command is run
>
> BLOCK_MEDIA_CHANGE
> ------------------
>
> This is the general event, it's emitted when any removable block device
> is changed.
>
> Ideally, the event should contain two pieces of info:
>
>  - qdev device name
>  - new file path (to allow distinguishing eject from change)
>
> Example:
>
>   { "event": "BLOCK_MEDIA_CHANGE", "data": { "qdev-id": "myid",
>                                              "new-path": "/foo/bar/dir/distro.iso" },
>                                              ... }

What if a host block device that isn't currently connected to a qdev
goes through a media change?

What if the connected qdev doesn't have an ID?

> BLOCK_MEDIA_EJECT
> -----------------
>
> This event is only emitted when a CDROM or a floppy disk is ejected.
>
> The event contains one info one:
>
>  - device name
>
> Example:
>
>   { "event": "BLOCK_MEDIA_EJECT", "data": { "device-name": "ide1-cd0" }, ... }

What makes CD-ROM and floppy special?

Re: [Qemu-devel] RFC: QMP event notification for disk media eject

[Luiz Capitulino]

On Tue, 11 Jan 2011 15:13:40 +0100
Markus Armbruster <armbru@redhat.com> wrote:

> Luiz Capitulino <lcapitulino@redhat.com> writes:
> 
> > Hi there,
> >
> > I need feedback on a new QMP event.
> >
> > Problem
> > =======
> >
> > There's no way for a management tool to detect that a guest OS has ejected the
> > media in a CDROM or Floppy disk drive (I'm discarding polling, because it's
> > undesirable at best).
> >
> > The end result is that the management tool can get confused, this is happening
> > with libvirt when migration is involved: if the guest is saved/restored or
> > migrated, then libvirt will start the guest again with media still present.
> >
> > NOTE: Most of the analysis here was done by Daniel Berrange.
> >
> > Solution
> > ========
> >
> > We need a new QMP event to solve that. There are two possible events, a
> > general one and a very specific one.
> >
> > There are 3 scenarios in which both events should be emitted:
> >
> >  1. When guest OS ejects media
> >  2. When 'eject' monitor command is run
> >  3. When 'change' monitor command is run
> >
> > BLOCK_MEDIA_CHANGE
> > ------------------
> >
> > This is the general event, it's emitted when any removable block device
> > is changed.
> >
> > Ideally, the event should contain two pieces of info:
> >
> >  - qdev device name
> >  - new file path (to allow distinguishing eject from change)
> >
> > Example:
> >
> >   { "event": "BLOCK_MEDIA_CHANGE", "data": { "qdev-id": "myid",
> >                                              "new-path": "/foo/bar/dir/distro.iso" },
> >                                              ... }
> 
> What if a host block device that isn't currently connected to a qdev
> goes through a media change?
> 
> What if the connected qdev doesn't have an ID?

We could add the blockdev id too.

> > BLOCK_MEDIA_EJECT
> > -----------------
> >
> > This event is only emitted when a CDROM or a floppy disk is ejected.
> >
> > The event contains one info one:
> >
> >  - device name
> >
> > Example:
> >
> >   { "event": "BLOCK_MEDIA_EJECT", "data": { "device-name": "ide1-cd0" }, ... }
> 
> What makes CD-ROM and floppy special?

Those are the only devices that support the eject operation (or have a tray
status? Sorry for my bad terminology) and are the ones that we have a concrete
use case to handle.

We might want to be more general, but it does have a complexity cost and
its possible user cases are theoretical IMHO.