[Pkg-xen-devel] Bug#452721: Bug#452721: "xendomains" does not restore domains in same order as it would start them

[Diederik de Haas]

On Monday, 27 September 2021 19:13:04 CEST Andy Smith wrote:
> I think the "auto" directory is a pretty good and simple interface,
> so how about using it for save/shutdown as well? So, instead of just
> enumerating all running domids, enumerate all files in
> /etc/xen/auto/ in REVERSE order, parsing the name of the domain out
> of each one and doing the action on that name. When all files have
> been exhausted, THEN do the action on any remaining running domains.

I'm not familiar with the "auto" directory('s functionality), but I _assume_ 
that it's a directory which contains Xen domain config files which are 
automatically started up at boot time (in alphabetical sequence).
The user can choose to start other VMs if (s)he so chooses.

If that's correct, then I find it more logical to do *everything* in reverse.
The VM that was started first, should be saved/shutdown last and IIUC your 
proposal would not do that.
What makes the most sense to me is that the last started VM should be saved/
shutdown first, which would be one of the "remaining running domains". Once all 
the "remaining" ones have been saved/shutdown, THEN do the auto ones in 
reverse order.

Could the domain ID be used for that?
I haven't studied it 'in detail', but they seem sequential.

But my main point is that I think the proposed sequence should be adjusted.

Cheers,
  Diederik
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20210928/475d61e8/attachment.sig>