Importing a XEN config from server 1 with the name xen-vm works fine, doing the same from another XEN server with the same name for the domU results in a conflict.
why should this be expected? i mean, it's a different dom0 - the domU can be named to whatever the admin wants them to be named. if there is a unique key in the database, the unique key should be about the domU name and the related dom0 - it looks like it's currently only on the domU.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
VM can not be attached to Dom0.. because with Virtualization you can move a VM from one dom0 to another.
Hope this explains why the key can not be Dom0 + domU
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
version is 2.0 with patch 1 applied
Isnt this expected ?
Can you describe the details.
why should this be expected? i mean, it's a different dom0 - the domU can be named to whatever the admin wants them to be named. if there is a unique key in the database, the unique key should be about the domU name and the related dom0 - it looks like it's currently only on the domU.
VM can not be attached to Dom0.. because with Virtualization you can move a VM from one dom0 to another.
Hope this explains why the key can not be Dom0 + domU