Hi, > > To be done: monitor support. I think the best way to handle this is to > > introduce a new command to query vnc server state, which returns a list > > of vnc servers but otherwise works like "query-vnc". Alternative > > approach would be to add a optional 'id=' parameter to query-vnc, but > > then you'll need a new list-vnc command. > > > > Opinions on this? > > I don't think it makes a whole lot of difference really. Either way > mgmt apps like libvirt will need updating to deal with the new monitor > commands.
One thing that comes do mind is that if we do a completely new command we can easily fix any shortcomings of the existing query-vnc command. The listening address could be changed to be a *list* of addresses, allowing to notify libvirt about multiple listening sockets. One ipv4, one ipv6 being a use case. If someone has more issues / suggestions I'd be happy to hear about them. cheers, Gerd
