On 08/11/2017 02:27 PM, Wei Liu wrote:
On Fri, Aug 11, 2017 at 12:37:04PM -0600, Jim Fehlig wrote:
On 08/11/2017 05:45 AM, Wei Liu wrote:
On Thu, Aug 10, 2017 at 03:42:24PM -0600, Jim Fehlig wrote:
On 08/08/2017 09:09 AM, Wei Liu wrote:
Ian and Stefano
Oleksandr discovered that the p9fs array in libxl_domain_config is name
p9 instead of p9s. This causes problem for his work to rework device
Given that p9fs was added only during last release and the only known
external toolstack libvirt can't possibility use that, maybe we can
rename p9 to p9s. Opinions?
ATM the libvirt libxl driver doesn't use it, but it could by supporting
libvirt's <filesystem> device
I think that means all the parameters go directly to QEMU. Without
proper plumbing via libxl driver there won't be anything in the xenstore
hence it isn't useable by Xen guest, right?
I'm not sure why they have to go directly to QEMU. My naive thinking was to
map the <filesystem> XML elements/attributes to libxl_device_p9 struct. E.g.
/domain/devices/filesystem/source@file would map to libxl_device_p9->path,
Right, that would require adding code somewhere in libvirt.git, right?
What I'm trying to figure out is if there could be code is libvirt that
uses the p9 array defined in libxl. It seems to me the answer is no.
Correct, not at this time. Perhaps in the near future :-).
Xen-devel mailing list