search for: xc_linux_sav

...))) (config (vm (name sky) (memory 128) (image (linux (kernel /boot/vmlinuz-2.6.10-xenU) (root ''/dev/hda1 ro'') (args 4))) (device (vbd (uname phy:sda) (dev hda1) (mode w))) (device (vif (mac aa:00:00:20:ef:69))))))" /tmp/test)[DEBUG] Conn_sxpr< err=0 [1107253673.485081] xc_linux_save start 9 xc_linux_save start 9 xend.log [2005-02-01 10:27:28 xend] INFO (XendMigrate:370) Save BEGIN: [''save'', [''id'', ''16''], [''state'', ''begin''], [''domain'', ''9''], ['...

..."xm save" from Dom-0. But this command waits forever. I tried to follow the flow of the .py files (XendCheckpoint.py etc.). These seem to be called when I run ''xm save''. But beyond a point I am not sure what the python scripts do. I also see some libxc files such as xc_linux_save.c, but I am not sure who is using it (Dom-0 or Xen or the XenU). Can someone help me by explaining me what happens behind the scene when "xm save" is called ? Is there any good documentation explaining which actions are done by which layers (eg: python layer, C layer etc). Also, does...

...6; if(p2m[pfn] == INVALID_P2M_ENTRY) p2m[pfn] = p2m_batch[nr_mfns++]; - pte &= 0xffffff0000000fffULL; + pte &= ~MADDR_MASK_X86; pte |= (uint64_t)p2m[pfn] << PAGE_SHIFT; if(pt_levels == 2) Index: 2007-02-07/tools/libxc/xc_linux_save.c =================================================================== --- 2007-02-07.orig/tools/libxc/xc_linux_save.c 2007-02-01 17:41:07.000000000 +0100 +++ 2007-02-07/tools/libxc/xc_linux_save.c 2007-02-12 09:05:24.000000000 +0100 @@ -495,7 +495,7 @@ static int canonicalize_pagetable(unsign...

...[DEBUG] stream_init> unbuffer... [DEBUG] stream_init< err=0 [DEBUG] Conn_init> read stream... [DEBUG] stream_init>mode=r flags=1 compress=0 [DEBUG] stream_init> unbuffer... [DEBUG] stream_init< err=0 [DEBUG] Conn_sxpr> (xfr.err 0)[DEBUG] Conn_sxpr< err=0 [1130244324.172538] xc_linux_save start 8 xc_linux_save start 8 [1130244324.174077] Saving memory pages: iter 1 0% Saving memory pages: iter 1 0%Error when writing to state file (5) Error when writing to state file (5) 2790 [WRN] XFRD> Transfer errors: 2790 [WRN] XFRD> state=XFR_STATE err=1 2790 [INF] XFRD> Xfr se...

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

...Tue Jul 11 11:29:25 2006 -0600 > @@ -30,9 +30,11 @@ GUEST_SRCS-y += xc_load_bin.c > GUEST_SRCS-y += xc_load_bin.c > GUEST_SRCS-y += xc_load_elf.c > GUEST_SRCS-y += xg_private.c > -GUEST_SRCS-$(CONFIG_IA64) += xc_ia64_stubs.c > GUEST_SRCS-$(CONFIG_MIGRATE) += xc_linux_restore.c xc_linux_save.c > GUEST_SRCS-$(CONFIG_HVM) += xc_hvm_build.c > + > +# This Makefile only adds files if CONFIG_IA64 is y. > +include ia64/Makefile > > CFLAGS += -Werror > CFLAGS += -fno-strict-aliasing I''m not sure this is the best way. We''ll need to do the same...

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