• Iustin Pop's avatar
    Temporary fix for dual hvm/pvm instances · f23b5ae8
    Iustin Pop authored
    We have a problem with the current model of combining instance lists
    from multiple hypervisors: we don't allow duplicates, but "xm list"
    gives the same output for both pvm and hvm. This is a lack in the actual
    xen hypervisor implementation/split between pvm and hvm, but for now we
    implement a weak workaround: identical instance params will be allowed,
    and merged. This breaks because there is a delta in listing, and should
    be treated as temporary workaround only.
    Note that there are two cases for duplicate instance: the above one (xen
    is the same, whether pvm or hvm), and the other case, the real error,
    when we have two different hypervisors reporting the same instance name.
    The latter case needs to be handled better (not by refusing to list the
    instances in the backend).
    Reviewed-by: ultrotter
backend.py 58.3 KB