Date: Fri, 9 Dec 2016 09:32:17 -0700 From: Nathan Friess <nathan.friess@gmail.com> To: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= <roger.pau@citrix.com> Cc: freebsd-xen@freebsd.org Subject: Re: 11-RELEASE acting as vbd backend Message-ID: <584ADC91.8050909@gmail.com> In-Reply-To: <20161209144630.dfga5mozh72veo4g@dhcp-3-221.uk.xensource.com> References: <247e5b6c-2713-27cf-f8fa-61e55c9e2025@gmail.com> <20161206100414.pi7ep2zbkduhuol7@dhcp-3-221.uk.xensource.com> <39e43ae4-6388-c698-c3c2-43cbc1f7b93c@gmail.com> <20161209144630.dfga5mozh72veo4g@dhcp-3-221.uk.xensource.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 16-12-09 07:46 AM, Roger Pau Monné wrote: > Hello, > > Sorry for the delay, there was a huge can of worms behind this. I have a > solution, but it requires patching both Xen and the FreeBSD kernel. Please bear > with me, I will send those patches once ready. It sounds like you might know this already, but I did some more digging and here is what I can see so far... The important command is "xl devd". Running that under truss, it is trying to open /dev/xen/xenbus and that was the cause of the No such file error. It looks like the 10.3 tools used to open /dev/xen/xenstore instead. I can get around this by exporting XENSTORED_PATH="/dev/xen/xenstore". Now xl devd is stuck at: libxl: error: libxl_event.c:639:libxl__ev_xswatch_register: create watch for path /local/domain/7/backend: Invalid argument So it seems like an API issue with asking the kernel or dom0 to set a watch for new backend devices. Whenever the patches are ready I can test them on my system. Nathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?584ADC91.8050909>