Xen users - Oct 2005 - xen 2.0 migrate bug?

I just accidentally trashed a domU by overwriting it with another domU _of
the same name_ from another xen host. I meant to do the migrate but did
not expect it to replace the domU on the destination host. (I forgot that
the two domUs had the same name.)

Worse, the resources from the domU that got stomped on are still marked as
allocated so I need to reboot the whole box in order to restart it. :-(

I would humbly suggest that "stomping on" (e.g. overwriting) a running
domU of the same name violates the principle of least suprise, and
consequently should be rejected. If it is a needed "feature", then I
apologize (and perhaps suggest that a -o flag for overwrite could be
usefull).

This was with xen-2.0-testing code downloaded sept 28th.

----------------------------------------------------------------------
tbrown@BareMetal.com   | Don''t go around saying the world owes you a
living;
http://BareMetal.com/  | the world owes you nothing; it was here first.
web hosting since ''95  | - Mark Twain


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> I just accidentally trashed a domU by overwriting it with 
> another domU _of the same name_ from another xen host. I 
> meant to do the migrate but did not expect it to replace the 
> domU on the destination host. (I forgot that the two domUs 
> had the same name.)
Yeah, that''s not so user friendly.

As it happens, I already have this on the bug list -- this happened by
accident during the Xen tutorial at Linux Kongress while people were
having fun passing a VM around between their laptops. The VNC display of
the VM (which was running an animated fractal viewer) was being
projected on to a big screen :-)

Ian

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users