similar to: Does xen use 2MB page?

hi,all has anyone set the eflags.TF of vm? I want to introdeuce a VM into single-step by setting the eflags.TF of vm, then I disassemble the bytes at RIP to figure out what''s going on . I have set the trap flag ,but I didn''t achieve what I want. First, I only get hlt,mov, rdtsc, clts, in, out . Second, the VM always crash. does anyone have experience and give

hi all, I have a doubt. about event channel of xen, a piece of code here " evtchn_bind_interdomain() { struct domain *ld= current->domain }", it is used to bind domain A and domain B but why it is always current->domain ? -- ---------------------------------------------------------- regards, yandong _______________________________________________ Xen-devel mailing list

I use the libguestfs to upload a file into the VM. But I found the date of the file in the VM is in the future(modify time is May 18, now is May 13), and this lead to the VM will auto fix it using fsck before boot. anyone can help or give me some tips? thank you very much. Best regards yandong

xen_changeset : Sun Apr 16 15:45:57 2006 +0100 9629:07408313ce33 /var/log/xend.log: [2006-04-19 20:42:09 xend] DEBUG (balloon:126) Balloon: free 1348; need 521; done. [2006-04-19 20:42:09 xend] DEBUG (XendCheckpoint:148) [xc_restore]: /usr/lib/xen/bin/xc_restore 11 20 42 133120 1 2 [2006-04-19 20:42:10 xend] ERROR (XendCheckpoint:227) xc_linux_restore start: max_pfn = 20800

branch xen-unstable xen branch xen-unstable job build-i386 test xen-build Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git Tree: xen git://xenbits.xen.org/xen.git *** Found and reproduced problem changeset *** Bug is in tree: xen git://xenbits.xen.org/xen.git Bug introduced: ae763e4224304983a1cde2fbb3d6e0c4d60b2688 Bug not present:

build p2m mapping according to m2p mapping. Signed-off-by: Xin Li <xin.b.li@intel.com> Signed-off-by: Yunhong Jiang <yunhong.jiang@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I am using Xen-4.4.0, libvirt-1.2.9 My ubuntu.cfg is: ubuntu10.cfg bootloader = "/usr/local/lib/xen/boot/hvmloader" builder="hvm" memory = 512 name = "ubuntu" vif = [ "type=ioemu,bridge=ovsbr0", "type=ioemu,bridge=ovsbr0","type=ioemu,bridge=ovsbr0","type=ioemu,bridge=ovsbr0",,"type=ioemu,bridge=ovsbr0"]

Hi I wanted to find out if there is way to list all the running processes in a guest VM from the hypervisor. Like the output of 'ps -ef' from inside the guest VM, but without logging in or ssh into it. Thanks dtsweval

Hi, I have server that has been running 5.x - 5.8 for a few years without issue and decided to move it to a fresh install of 6.2. First thing I noticed is a good part of the log has these mtrr messages finally ending with "mtrr_cleanup: can not find optimal value" and "please specify mtrr_gran_size/mtrr_chunk_size". I have been searching around and reading the kernel docs

As I know, you can use Libvmi API to access the memory of VM and then walk through the double-linked list of process to reconstruct the process list. it is easy, and libvmi has provide the example 在2015-04-20 22:52:02,hanyandong<hanyandong@iie.ac.cn>写道： > On 20.04.2015 06:22, dt sweval wrote: > > Hi > > I wanted to find out if there is way to list all the running processes

Since the latest update (may wrap here), xorg-x11-server-Xorg-1.15.0-26.el6.centos.0.1.x86_64 Sat 20 Jun 2015 04:16:01 PM EDT xorg-x11-server-common-1.15.0-26.el6.centos.0.1.x86_64 Sat 20 Jun 2015 04:15:58 PM EDT x264-0.0.0-0.4.20101111.el6.rf.x86_64 Wed 19 Nov 2014 04:56:05 PM EST xvidcore-1.2.2-1.el6.rf.x86_64 Wed 19 Nov 2014 04:55:49 PM EST . . . drop a lot of older

Hell all, I am doing some research work on protecting Xen''s data structures. I know there is a direct-map area(about 12M), in which we can get the physical address of the data structure from its virtual address. My question is : are the stack and the heap of Xen both located in this direct-map area? Since I need protect stack and heap data, so it is easy to identify their physical

Attached are the patches to support super page with EPT. We only support 2M size. And shadow may still work fine with 4K pages. The patches can be split into 3 parts. Apply order is as attached. tool.diff To allocate 2M physical contiguous memory in guest except the first 2M and the last 2M. The first 2M covers special memory, and Xen use the last few pages in guest memory to do special

Dear R forum, Please refer to my query regarding "Error with function". I forgot to mention that I am using "plyr" library. Sorry for inconvenience. Regards Katherine --- On Tue, 23/4/13, Katherine Gobin <katherine_gobin@yahoo.com> wrote: From: Katherine Gobin <katherine_gobin@yahoo.com> Subject: [R] Error with function To: r-help@r-project.org Date:

Dear R forum, I have a data.frame as given below: df = data.frame(tran = c("tran1", "tran2", "tran3", "tran4"), tenor = c("2w", "1m", "7m", "3m"))  Also, I define libor_tenor_labels = as.character(c("o_n", "1w", "2w", "1m", "2m", "3m", "4m",

Dear R forum Please refer to my query captioned Error with function. I had missed in bracket ")" in the return statement and hence I was getting the error. I has struggled for more than 2 hours to find out the problem and only then has posted to the forum. I sincerely apologize to all for consuming your valuable time. Thanks for the efforts at your end. Regards Katherine --- On

The memory permutation cause a slow down in case of a save/restore (bug 1143). It works better when the mixing is done with 2MB chunks. Signed-off-by: Jean Guyader <jean.guyader@eu.citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

CONFIG_PHYSICAL_ALIGN gives the physical address's alignment where the kernel is loaded. CONFIG_PHYSICAL_ALIGN's default value is different from i386 kernel with the x86_84 kernel. The i386's default CONFIG_PHYSICAL_ALIGN value is 1MB, but the x86_64's is 2MB. The problem is, if you compile x86_64 kernel, the value of CONFIG_PHYSICAL_ALIGN will be fixed, and the next time you

CONFIG_PHYSICAL_ALIGN gives the physical address's alignment where the kernel is loaded. CONFIG_PHYSICAL_ALIGN's default value is different from i386 kernel with the x86_84 kernel. The i386's default CONFIG_PHYSICAL_ALIGN value is 1MB, but the x86_64's is 2MB. The problem is, if you compile x86_64 kernel, the value of CONFIG_PHYSICAL_ALIGN will be fixed, and the next time you