Hi Jim, I''m having some problems with the libvirt libxl driver you''re working on. More specifically, it does not seem to be working for me, at least not in the form in which it comes out of the related Fedora package. If/When you have a minute, would it be possible to you to have a look here: https://bugzilla.redhat.com/show_bug.cgi?id=893699 https://bugzilla.redhat.com/show_bug.cgi?id=893699#c10 ? Even just knowing whether it is me that am doing something wrong, or from where to start looking for the issue would be a great help. :-) Any further information you (or anyone) need, or any other setup you (or anyone) think it would be worthwhile to test, just tell me, I''ll do my best to comply. Thanks and Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Dario Faggioli wrote:> Hi Jim, > > I''m having some problems with the libvirt libxl driver you''re working > on. More specifically, it does not seem to be working for me, at least > not in the form in which it comes out of the related Fedora package. > > If/When you have a minute, would it be possible to you to have a look > here: > https://bugzilla.redhat.com/show_bug.cgi?id=893699 > https://bugzilla.redhat.com/show_bug.cgi?id=893699#c10 ? >Thanks for the bug ref, I''ve made a comment there.> Even just knowing whether it is me that am doing something wrong, or > from where to start looking for the issue would be a great help. :-) >As mentioned in the bug, the libxl driver will not load if xend is running. It appears xend is not running on your system, so hopefully there is something in your libvirtd logs telling why the driver did not load. Regards, Jim> Any further information you (or anyone) need, or any other setup you (or > anyone) think it would be worthwhile to test, just tell me, I''ll do my > best to comply. > > Thanks and Regards, > Dario > >
On Thu, 2013-01-17 at 09:00 -0700, Jim Fehlig wrote:> Dario Faggioli wrote: > > Hi Jim, > > > > I''m having some problems with the libvirt libxl driver you''re working > > on. More specifically, it does not seem to be working for me, at least > > not in the form in which it comes out of the related Fedora package. > > > > If/When you have a minute, would it be possible to you to have a look > > here: > > https://bugzilla.redhat.com/show_bug.cgi?id=893699 > > https://bugzilla.redhat.com/show_bug.cgi?id=893699#c10 ? > > > > Thanks for the bug ref, I''ve made a comment there. >Thanks. I replied myself, trying to provide some more information about what''s going on...> As mentioned in the bug, the libxl driver will not load if xend is > running. It appears xend is not running on your system, so hopefully > there is something in your libvirtd logs telling why the driver did not > load. >I''m not even sure whether xend is running or not! :-( As I wrote there, even when I only see the xend status check, I have xm working, which shouldn''t happen without a proper xend running, right? Moreover, independently from whether I install the package or not, or whether I kill/start xend manually, it looks indeed like the libxl driver is not able to load itself. Where should I look for the libvirtd logs you''re mentioning? I''ve checked in /var/log/libvirt/* and in /var/log/messages, without finding anything interesting. Should I look somewhere else? Should I pass additional parameter to any of the involved components? Thanks again and Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Dario Faggioli wrote:> On Thu, 2013-01-17 at 09:00 -0700, Jim Fehlig wrote: > >> Dario Faggioli wrote: >> >>> Hi Jim, >>> >>> I''m having some problems with the libvirt libxl driver you''re working >>> on. More specifically, it does not seem to be working for me, at least >>> not in the form in which it comes out of the related Fedora package. >>> >>> If/When you have a minute, would it be possible to you to have a look >>> here: >>> https://bugzilla.redhat.com/show_bug.cgi?id=893699 >>> https://bugzilla.redhat.com/show_bug.cgi?id=893699#c10 ? >>> >>> >> Thanks for the bug ref, I''ve made a comment there. >> >> > Thanks. I replied myself, trying to provide some more information about > what''s going on... > > >> As mentioned in the bug, the libxl driver will not load if xend is >> running. It appears xend is not running on your system, so hopefully >> there is something in your libvirtd logs telling why the driver did not >> load. >> >> > I''m not even sure whether xend is running or not! :-( As I wrote there, > even when I only see the xend status check, I have xm working, which > shouldn''t happen without a proper xend running, right? >For those not following in the bug, the libxl driver executes ''/usr/sbin/xend status'' and refuses to load it xend is running. The problem here is that the status check causes xend to start! I can''t reproduce the issue, so perhaps it is specific to the fedora packages.> Moreover, independently from whether I install the package or not, or > whether I kill/start xend manually, it looks indeed like the libxl > driver is not able to load itself. >Since checking xend status starts the service and returns that it is running, the driver won''t load :).> Where should I look for the libvirtd logs you''re mentioning? I''ve > checked in /var/log/libvirt/* and in /var/log/messages, without finding > anything interesting. Should I look somewhere else? Should I pass > additional parameter to any of the involved components? >See /etc/libvirt/libvirtd.conf for a nice set of logging controls. Regards, Jim
On Mon, 2013-01-21 at 17:55 -0700, Jim Fehlig wrote:> > I''m not even sure whether xend is running or not! :-( As I wrote there, > > even when I only see the xend status check, I have xm working, which > > shouldn''t happen without a proper xend running, right? > > > > For those not following in the bug, the libxl driver executes > ''/usr/sbin/xend status'' and refuses to load it xend is running. The > problem here is that the status check causes xend to start! >Ok, that sounds strange, but it is also the only reasonable explanation. I''ll try to have a look and confirm this> I can''t > reproduce the issue, so perhaps it is specific to the fedora packages. >I guess it can well be. I''ll investigate this and report back to both the list and the bug.> > Moreover, independently from whether I install the package or not, or > > whether I kill/start xend manually, it looks indeed like the libxl > > driver is not able to load itself. > > > > Since checking xend status starts the service and returns that it is > running, the driver won''t load :). >Yep, now it makes sense. :-) Thanks a lot for your time and Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Tue, 22 Jan 2013, Jim Fehlig wrote:> For those not following in the bug, the libxl driver executes > ''/usr/sbin/xend status'' and refuses to load it xend is running. The > problem here is that the status check causes xend to start! I can''t > reproduce the issue, so perhaps it is specific to the fedora packages.It is specific to the Fedora package. I traced it to the xen-initscript.patch file in the Fedora source. From xen-3.1.0-2.fc8 onwards Fedora xend ignores the option passed to it and just does a start. It was from before I started doing things on the package, but idea seems to have been to strip out functions like stop, reload etc. and do them directly in the init script. I don''t think it is worth changing this much, but I think I will put back the status option to keep libvirt happy. Michael Young
On Tue, 2013-01-22 at 20:19 +0000, M A Young wrote:> On Tue, 22 Jan 2013, Jim Fehlig wrote: > It is specific to the Fedora package. I traced it to the > xen-initscript.patch file in the Fedora source. From xen-3.1.0-2.fc8 > onwards Fedora xend ignores the option passed to it and just does a start. >Oh... I see...> It was from before I started doing things on the package, but idea seems > to have been to strip out functions like stop, reload etc. and do them > directly in the init script. >Ok.> I don''t think it is worth changing this much, but I think I will put back > the status option to keep libvirt happy. >Well, yes, I think that makes sense. Not much value added in reworking xend support now, given it''s being deprecated, but if we can put things in a way that the libvirt libxl driver is able to load, that would be awesome. :-) Thanks and Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Tue, Jan 22, 2013 at 8:19 PM, M A Young <m.a.young@durham.ac.uk> wrote:> On Tue, 22 Jan 2013, Jim Fehlig wrote: > > For those not following in the bug, the libxl driver executes >> ''/usr/sbin/xend status'' and refuses to load it xend is running. The >> problem here is that the status check causes xend to start! I can''t >> reproduce the issue, so perhaps it is specific to the fedora packages. >> > > It is specific to the Fedora package. I traced it to the > xen-initscript.patch file in the Fedora source. From xen-3.1.0-2.fc8 > onwards Fedora xend ignores the option passed to it and just does a start. > It was from before I started doing things on the package, but idea seems to > have been to strip out functions like stop, reload etc. and do them > directly in the init script. > > I don''t think it is worth changing this much, but I think I will put back > the status option to keep libvirt happy. >The other option of course would be to have a parallel patch in Fedora''s libvirt package, which calls "/etc/init.d/xend status" instead of "/usr/bin/xend status" -- but that seems like it''s probably more fragile than just re-enabling the option in the Xen package. -George _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel