search for: xc_linux_build

...ol_evtchn, unsigned long flags, - unsigned int vcpus); + unsigned int vcpus, + unsigned int store_evtchn, + unsigned long *store_mfn); int xc_plan9_build (int xc_handle, diff -ur xen-unstable/tools/libxc/xc_linux_build.c xen-unstable-working/tools/libxc/xc_linux_build.c --- xen-unstable/tools/libxc/xc_linux_build.c 2005-05-24 13:10:24.000000000 +1000 +++ xen-unstable-working/tools/libxc/xc_linux_build.c 2005-05-31 17:44:08.000000000 +1000 @@ -50,7 +50,8 @@ unsigned long shared_info_frame...

...ot;/home/xin/work/xmp/xen32-smp/dist/install/usr/lib/python/xen/xend/serve r/relocate.py", line 30, in ? File "/home/xin/work/xmp/xen32-smp/dist/install/usr/lib/python/xen/xend/XendC heckpoint.py", line 15, in ? ImportError: /usr/lib/python/xen/lowlevel/xc.so: undefined symbol: xc_linux_build [root@xin ~]# _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I am getting the following error when I try to bring up Mini-OS on x86_64 Xen (unstable: 9994). It is dying in xc_linux_build() causing xend to fault and restart. Any clue why this happening? Has something changed in the builder that Mini-OS needs to be aware of? PS: I tried reverting changeset 9993 (Allow linking of mini-os with application-specific object code), but still got the same error Thanks, Aravindh Puthiyapa...

xentop "-b" options are duplicateded(--batch and --vbds). from xen-unstable 10623 Please fix it. http://xenbits.xensource.com/xen-unstable.hg?cs=856caf975abd Thanks, Atsushi SAKAI _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Here are two patches that let xm create, save and restore extract and preserve elfnotes read by the domain builder. This is handy for a few things. In particular, I''d like it so that xm can decide whether or not guest domains support fast resume (if save fails, or for checkpointing). _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

This patch adds a parallel set of APIs to the domain builders to allow images and ramdisks to be passed via buffer, rather than via file. This allows usage of the underlying domain building routines in "file-challenged" enviroments. Specifically, xc_linux_build_mem is the buffer oriented version of the file-oriented xc_linux_build. Likewise, xc_hvm_build_mem is the buffer oriented analog of the file based xc_hvm_build. This patch also implements a suggestion by Mark Williamson to have the internal APIs always directly use uncompressed buffers. -b Sig...

...that > > dsi->v_start is 0 which throws things off. But this is totally valid so > > I am not sure what checks need to be introduced to stop this from > > happening. Should the bounds check for the array be reintroduced? > > The problem is almost certainly a wrap in > xc_linux_build.c:setup_guest(). v_end is taken from parseelfimage() and > then incremented to make room for initrd, page tables, etc. If that > wraps round to zero then the size check will pass and things will > generally be screwed. > > We probably need to take care whenever we increment v_end to...

hi, it would be extremely useful for me if someone with knowledge of how the current tools and drivers use Xenstore would be kind enough to update the Wiki with current information. I have been spending quite a lot of time trying to get my domU connected to a block device in dom0 using a home-brewed domain creation tool, and I am still at the ''Timeout connecting to device!''

...nd_recv(xcs_ctrl_fd, &msg) || msg.result != XCS_RSLT_OK) { >- dolog(LOG_ERR, "xcs vind failed. Possible bug."); >+ dolog(LOG_ERR, "xcs virq bind failed. Possible bug."); > goto out_close_data; > } > >diff -r e69cbfee4011 -r 8fe8a99b1c2a tools/libxc/xc_linux_build.c >--- a/tools/libxc/xc_linux_build.c Tue Aug 30 08:47:51 2005 >+++ b/tools/libxc/xc_linux_build.c Tue Aug 30 16:14:53 2005 >@@ -335,7 +335,8 @@ > unsigned int control_evtchn, > unsigned long flags, > unsigned in...

To allow xenguest consumers to also make use of the extra protection added as a result of xsa-25. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> diff -r 5af4f2ab06f3 -r daec50a41570 tools/libxc/xenguest.h --- a/tools/libxc/xenguest.h +++ b/tools/libxc/xenguest.h @@ -177,6 +177,13 @@ int xc_dom_linux_build(xc_interface *xch unsigned int console_evtchn, unsigned

Last year we had a discussion[1] about how the hypercall ABI unfortunately contains fields that change width between 32- and 64-bit builds. This is a huge problem as we come up on the python management stack for ppc64, since the distributions ship 32-bit python. A 32-bit python/libxc cannot currently manage a 64-bit hypervisor. I had a patch but was unable to test it, and some other things were

Hi there! I was wondering what the general opinion on autotoolizing xen is? I am volunteering to do so, if there is interest in updating the build system to use autoconf, automake and/or libtool. Is one configure script for all of xen enough or do you want to be able to configure all/some tools separately? I know that Anthony is no fan of libtool... are there more reservations about some

We (Michael Fetterman, George Dunlap and I) have been working over the last while on a full replacement for Xen''s shadow pagetable support. This mail contains some design notes, below; a patch against xen-unstable, giving a snapshot of the current state of the new shadow code, is at http://www.cl.cam.ac.uk/~tjd21/shadow2.patch Comments on both are welcome, although the code is not