docs: update xenstore migration stream definition

In order to close a race window for Xenstore live update when using
the new unique_id of domains, the migration stream needs to contain
this unique_id for each domain known by Xenstore.

Signed-off-by: Juergen Gross <jgross@suse.com>
Acked-by: Anthony PERARD <anthony.perard@vates.tech>
This commit is contained in:
Juergen Gross authored and Jan Beulich committed 2025-04-08 09:36:21 +02:00
1 parent 930279d96c
commit 60649eafb5
1 file changed
+17 -1
+17 -1
View File
@@ -156,7 +156,7 @@ the domain being migrated.
```
0 1 2 3 4 5 6 7 octet
+-------+-------+-------+-------+-------+-------+-------+-------+
| conn-id | conn-type | |
| conn-id | conn-type | fields |
+-------------------------------+---------------+---------------+
| conn-spec
...
@@ -165,6 +165,9 @@ the domain being migrated.
+---------------+---------------+-------------------------------+
| data
...
+---------------------------------------------------------------+
| unique-id |
+---------------------------------------------------------------+
```
@@ -178,6 +181,16 @@ the domain being migrated.
| | 0x0001: socket |
| | 0x0002 - 0xFFFF: reserved for future use |
| | |
| `fields` | A collection of flags indicating presence |
| | of additional fields after the variable |
| | length `data` part. The additional fields |
| | will start after a possible padding for |
| | aligning to a 8 octet boundary. |
| | Defined flag values (to be or-ed): |
| | 0x0001: `unique_id` present (only needed for |
| | `shared ring` connection in live |
| | update streams). |
| | |
| `conn-spec` | See below |
| | |
| `in-data-len` | The length (in octets) of any data read |
@@ -193,6 +206,9 @@ the domain being migrated.
| `data` | Pending data: first in-data-len octets of |
| | read data, then out-data-len octets of |
| | written data (any of both may be empty) |
| | |
| `unique-id` | Unique identifier of a domain |
| | |
In case of live update the connection record for the connection via which
the live update command was issued will contain the response for the live
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.