> Is there anyone tackling this problem now?( or going to? ) > Otherwise, any hint would help me. I don't think anybody has tried to handle this. The problem I think is that the mapping would have to be stored and if the hypervisor doesn't support this maintaining this data in a coherent fashion will be non-trivial. In any case the design for such a patch should be discussed here first and with the openvz maintainers to make sure the effort isn't wasted.

On Fri, Jul 24, 2009 at 06:23:21PM +0400, Anton Protopopov wrote: > > > > > Is there anyone tackling this problem now?( or going to? ) > > > Otherwise, any hint would help me. > > > > I don't think anybody has tried to handle this. The problem I think > > is that the mapping would have to be stored and if the hypervisor > > doesn't support this maintaining this data in a coherent fashion > > will be non-trivial. In any case the design for such a patch should > > be discussed here first and with the openvz maintainers to make sure > > the effort isn't wasted. > > > > Openvz supports setting names for containers, see description on --name > parameter in vzctl(8). But you (or libvirt) actually need to specify > an unique container id anyway. We should make use of this --name parameter then - I guess it didn't exist when we first wrote the driver. It is useful to users to have separate ID vs Name parameters - and in fact the current reusing of 'ID' for the name, causes a little confusion in virsh's lookup routines because it can't tell whether the parameter its given is a name or an ID, since they are identical.

Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/:| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org:| |: http://autobuild.org -o- http://search.cpan.org/~danberr/<http://search.cpan.org/%7Edanberr/>:| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|