Re: [Xen-users] Starting xenstored in a driver domain

[Michael Collins <mike@xxxxxxxxxxx>]

While your patch did work, it removed some default functionality from 
the script while running in dom0.  I wrote up the following and have 
patched it into my scripts on both my dom0 and driver domu.
It just checks to see if /proc/xen/capabilities exists and is empty, if 
so it only creates the domid and mac external-ids.
If it's not empty, it then reverts to its normal behavior adding the 
mac, vm-uuid and vm-name external-ids.
This way, the same script can operate on both dom0 and driver domu 
without any changes.

Thanks for pointing me in the right direction!

Mike


On 12/4/2017 9:50 AM, George Dunlap wrote:
> On Mon, Dec 4, 2017 at 3:40 AM, mike@xxxxxxxxxxx <mike@xxxxxxxxxxx> wrote:
> > So I figured out that I don't need a running instance of xenstored on the
> > driver domain, since xenstore-read works for the driver domains own trees in
> > xenstore.  Are the xenstore-read errors in vif-openvswitch because that
> > script is written to be run on dom0 only?  Do I need to create a new vif
> > script that is specific to driver domains?
> It sounds like that's a bug in the vif-openvswitch script -- it
> shouldn't rely on reading data from the domain's "private" xenstore
> area (available to domain 0 but not to a driver domain).
>
> Can you try the attached patch and see if it helps?
>
>   -George

Attachment: vif-openvswitch.patch
Description: Text document

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-users