Json config and stubdomain

["Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1241 bytes --]

Hi,

Debugging stubdomain continuation...
When stubdomain is started, it has no json config created. This results
in multiple problems:
 - impossible to dynamically attach additional devices
 - starting a domain with more than one PCI device fails

The second one is especially interesting because it look so much
inconsistent: libxl__device_pci_add_xenstore when called for the first
device, it immediately calls libxl__create_pci_backend and do not touch
json config at all. But when called for the next device, it loads json
config, adds the device there and save it. So it looks like the first
PCI device will never be saved into json config (when added
dynamically).
In case of stubdomain, libxl__device_pci_add_xenstore is called during
stubdomain startup, so defining two or more PCI devices means domain
startup fail.

So, the question is, whether json config should be created and properly
maintained for stubdomain, or not created at all (assuming all the
configuration is already handled in the target domain json config)?

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel