Hi! First of all thanks to everybody who have participated in the process of creating or developing Xen, I''m using it on some systems and writing a thesis on it, and it''s really a pleasure to work with it! Anyway, I have a small question, regarding the Xen HTTP interface... Unfortunately I wasn''t able to find any information about it, around... How is it supposed to work? What happens now if I try to connect to it with a browser is that I see a white page with two slashes on it, linking to the page itself... Is this the normal behaviour or am I missing something? Any hint would be greatly appreciated! Guido _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
http://www.libvirt.org/ Has a bunch of code that interacts with that interface. Other than that, there''s not really a reference other than the Python code itself. Regards, Anthony Liguori Guido Trotter wrote:> Hi! > > First of all thanks to everybody who have participated in the process of > creating or developing Xen, I''m using it on some systems and writing a thesis on > it, and it''s really a pleasure to work with it! > > Anyway, I have a small question, regarding the Xen HTTP interface... > Unfortunately I wasn''t able to find any information about it, around... How is > it supposed to work? What happens now if I try to connect to it with a browser > is that I see a white page with two slashes on it, linking to the page itself... > Is this the normal behaviour or am I missing something? > > Any hint would be greatly appreciated! > > Guido > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi,> Anyway, I have a small question, regarding the Xen HTTP interface... > Unfortunately I wasn''t able to find any information about it, around... > How is > it supposed to work? What happens now if I try to connect to it with a > browser > is that I see a white page with two slashes on it, linking to the page > itself... > Is this the normal behaviour or am I missing something? > > Any hint would be greatly appreciated!try http://localhost:8000/xend/ I also wonder why this is nowhere documented, but it seems to be running by default, I can''t remember having turned that on. It''s probably turned on with the config option (xend-http-server yes) in xend-config.sxp. Would be interesting if some developer could comment on this - will this be removed soon that it''s not worth documenting? Or is it so new that it''s not yet documented? ( in the latter case I''d start a wiki page to document this, in the former this would be waste of time, I guess) The wiki page XenIntro reads: "In the past,the start() method of SrvDaemon eventually started an http socket (8000) on which it listened to http requests. Now it does not open an http socket on port 8000 anymore." But I see this in Xen 3.0. So I am a bit unsure if this is what you get on the URL mentioned above, or which "past" they mean there :) Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Henning Sprang schrieb:> Hi, > >> Anyway, I have a small question, regarding the Xen HTTP interface... >> Unfortunately I wasn''t able to find any information about it, around... >> How is >> it supposed to work? What happens now if I try to connect to it with a >> browser >> is that I see a white page with two slashes on it, linking to the page >> itself... >> Is this the normal behaviour or am I missing something? >> >> Any hint would be greatly appreciated! > > try http://localhost:8000/xend/ > > I also wonder why this is nowhere documented, but it seems to be running by > default, I can''t remember having turned that on. > It''s probably turned on with the config option > (xend-http-server yes) > in xend-config.sxp. > > Would be interesting if some developer could comment on this - will this be > removed soon that it''s not worth documenting? Or is it so new that it''s not > yet documented? ( in the latter case I''d start a wiki page to document this, > in the former this would be waste of time, I guess) > > The wiki page XenIntro reads: > > "In the past,the start() method of SrvDaemon eventually started an http > socket (8000) on which it listened to http requests. Now it does not open an > http socket on port 8000 anymore." > > But I see this in Xen 3.0. So I am a bit unsure if this is what you get on > the URL mentioned above, or which "past" they mean there :) > > HenningI did try turning it on via (xend-http-server yes), but I also only get one line of html. Nothing else. Nada. So the http server is responding alright. But it doesn''t deliver anything worthwile... It doesn''t even seem to speak full http yet. If you do telnet localhost 8000 GET / you get nothing. Andrej _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>try http://localhost:8000/xend/>I also wonder why this is nowhere documented, but it seems to be >running by default, I can''t remember having turned that on. on my systems (SLES 10 and Ubuntu+Xen 3.1.0) it is of by default! >It''s probably turned on with the config option (xend-http-server yes) >in xend-config.sxp. It is, I just tried it and if you also uncomment "(xend-address '''')" you are able to connect from remote! In the sources I figured out before that somewhere there is s.th. like a http-server, but because it was not documented anywhere I didn''t knew what to do with it! -- Chau y hasta luego, Thorolf _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Andrej, Please read again:> [...] > > try http://localhost:8000/xend/ > [...] > > It doesn''t even seem to speak full http yet. If you do > > telnet localhost 8000 > GET / > [...]You''ll want to say GET /xend/ Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi again,> > [...] > > > try http://localhost:8000/xend/ > > [...] > > > > It doesn''t even seem to speak full http yet. If you do > > > > telnet localhost 8000 > > GET / > > [...] > > You''ll want to say GET /xend/Ooops, sorry. I just realized, with telnet it really doesn''t work. With a webbrowser it does, though. No idea why. Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Henning Sprang wrote:> I also wonder why this is nowhere documented, but it seems to be running by > default, I can''t remember having turned that on. > It''s probably turned on with the config option > (xend-http-server yes) > in xend-config.sxp. > > Would be interesting if some developer could comment on this - will this be > removed soon that it''s not worth documenting? Or is it so new that it''s not > yet documented? ( in the latter case I''d start a wiki page to document this, > in the former this would be waste of time, I guess) >It''s going away. libvirt has the best implementation of the protocol (outside of Xend) that I know of. It changes frequently and is not something that''s very fun to keep up with. We''re moving to an XML-RPC based interface. The interface will be standardized and documented in future versions of Xen (hopefully in the very near future). See http://wiki.xensource.com/xenwiki/Xend/XML-RPC Regards, Anthony Liguori> The wiki page XenIntro reads: > > "In the past,the start() method of SrvDaemon eventually started an http > socket (8000) on which it listened to http requests. Now it does not open an > http socket on port 8000 anymore." > > But I see this in Xen 3.0. So I am a bit unsure if this is what you get on > the URL mentioned above, or which "past" they mean there :) > > Henning > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Anthony Liguori wrote:> > It''s going away. libvirt has the best implementation of the protocol > (outside of Xend) that I know of. It changes frequently and is not > something that''s very fun to keep up with.The last "it" is libvirt? Hmm, so If I need a web interface today, I can chose between one that is going away soon and one that is not yet stable to use? libvirt.org gives me timeouts...> > We''re moving to an XML-RPC based interface. The interface will be > standardized and documented in future versions of Xen (hopefully in the > very near future). > > See http://wiki.xensource.com/xenwiki/Xend/XML-RPCSounds interesting. And the "S-Expression/HTTP protocol" stuff is what I explained to guido, and will be gone with the next release? Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Henning Sprang wrote:> Anthony Liguori wrote: > >> It''s going away. libvirt has the best implementation of the protocol >> (outside of Xend) that I know of. It changes frequently and is not >> something that''s very fun to keep up with. >> > > The last "it" is libvirt?No, I was referring to the current HTTP/S-Expression protocol.> Hmm, so If I need a web interface today, I can > chose between one that is going away soon and one that is not yet stable > to use? >If you need a web services interface, you''re best bet is to start using libvirt today. libvirt will encapsulate the change from S-Expression/HTTP to XML-RPC.> libvirt.org gives me timeouts... >You probably don''t have the HTTP transport enabled (the default is to just enable the domain socket transport). If you post your problem on the libvirt list, we''ll help you through it.>> We''re moving to an XML-RPC based interface. The interface will be >> standardized and documented in future versions of Xen (hopefully in the >> very near future). >> >> See http://wiki.xensource.com/xenwiki/Xend/XML-RPC >> > > Sounds interesting. And the "S-Expression/HTTP protocol" stuff is what I > explained to guido, and will be gone with the next release? >Not with the next release. It will stay around for at least a couple more releases until there is a standardized and documented XML-RPC interface. Regards, Anthony Liguori> Henning >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Mar 01, 2006 at 10:19:02PM +0100, Henning Sprang wrote:> libvirt.org gives me timeouts...it was down on Wednesday, it''s back up, tell me if you still have troubles. Daniel -- Daniel Veillard | Red Hat http://redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users