Re: [XenAccess-devel] Error connecting to xend
Status: Beta
Brought to you by:
bdpayne
From: Steve B. <st...@at...> - 2006-06-28 16:13:29
|
Bryan D. Payne wrote: > This looks like libvirt cannot connect to the Xend deamon. I believe > that libvirt requires the xend-http-server to be enabled (which is no > longer the default setting for Xen). Try adding or uncommenting the > following line from /etc/xen/xend-config.sxp: > > (xend-http-server yes) > > After the edit you will need to restart xend: > > service xend restart > > I believe that this will fix your problem. I should probably add > something about this to the README file :-) Let me know how it works > out for you. That worked like a charm, thank you! I can now successfully use your module-list and process-list examples, and sure enough they match what is reported inside the VM using lsmod and ps. Very slick. However, your process-data example only partially works for me (note I modified it to take the pid as a command line argument): [root@localhost examples]# ./run ./process-data 1 Memory descriptor addresses for pid = 1: start_code = 0xffffffff end_code = 0xc035ac8c start_data = 0xc035ac8c end_data = 0x00000001 start_brk = 0xdead4ead brk = 0xffffffff start_stack = 0xffffffff arg_stack = 0xc035aca4 arg_end = 0xc035aca4 env_start = 0x0000008e env_end = 0x00000017 ERROR: cannot translate this address failed to map memory: Success Notwithstanding the fact that I'm no kernel guy so I can't make sense of the above output from the printaddr() function (but it does look a little odd to me), I see that the attempt to "/* grab the memory...and print it out */" fails (with an error code of "Success"?). Do you have any thoughts on this? As an unrelated question, do you think XenAccess would also work on Linux running in an HVM domU? My testing so far has been in a paravirtualized domU. Thanks for your help, - Steve Stephen Brueckner, ATC-NY |