search for: ptwr_emulate

Hello, I''m getting many "Error getting mfn" on a xen4.1.3 with dom0 3.4.11 x86_32. I thought it could be related to xen/mmu: Release just the MFN list, not MFN list and part of pagetables. http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git;a=commit;h=785f62314984ea3af9dd830b020289ba2509ae69 (XEN) Freed 212kB init memory. (XEN) mm.c:908:d0 Error getting mfn 2009b (pfn

Xen 3.2.1-rc1 64 bit Dom0: 2.6.16.33 PAE DomU: 2.6.18.8 (from a pull a few weeks ago) If you need the symbols, there from the same Xen I linked to in my post from a few days ago... (XEN) mm.c:3498:d4 ptwr_emulate: could not get_page_from_l1e() (XEN) Unhandled page fault in domain 4 on VCPU 0 (ec=0003) (XEN) Pagetable walk from 00000000c08187f0: (XEN) L4[0x000] = 00000004dfa38027 000000000000063c (XEN) L3[0x003] = 00000004e0071027 0000000000000003 (XEN) L2[0x004] = 00000004df8cd067 00000000000007a7 (XEN)...

Hi, I just upgraded to the latest SID after reinstalling my test server. Then, after a while, during the boot process, Xen seems to hang, then my server reboots. It's difficult for me to see anything, since I'm using a KVM over IP, using a quite slow link (from China to UK, using a FreeNX box that connects through a Java KVM over IP to the server), and I don't think it'd be easy

...ting a DomU, I get on the console: Checking if this processor honours the WP bit even in supervisor mode... <1>BUG: unable to handle kernel paging request at virtual address c0f5672c and in xm dmesg: (XEN) mm.c:612:d18 Non-privileged (18) attempt to map I/O space 003fc2f2 (XEN) mm.c:3267:d18 ptwr_emulate: could not get_page_from_l1e() (Se details in attachement) It does not happen all times, if the DomU boots, then it will run fine for ages. If it crashes, it is always at boot time at that place. So workaround is to ''xm create'' until it boots... I can reproduce the problem in b...

Hi Keir: I am sorry trouble you again. I want to emulate instruction "push %ebp" in Xen. I found the function emulate_privilege_op does not satisfy this requirement. Then I resort to x86_emulate. I construct the x86_emulate_ctxt and reuse the "ptwr_emulate_ops". code like this: extern const struct x86_emulate_ops ptwr_emulate_ops; in do_general_protection { .... struct x86_emulate_ctxt ctxt; ctxt.regs = regs; ctxt.force_writeback = 1; // 0 is the same ctxt.addr_size = 32; ctxt.sp_size = 32; ret = x86_emulate(&ctxt, &ptwr_emulate...

...xenbr0: topology change detected, propagating Dec 20 13:18:12 kr kernel: xenbr0: port 5(vif25.0) entering forwarding state xm dmesg reports nothing unusual except these at the end: (XEN) mm.c:649:d22 Error getting mfn 3b6 (pfn 55555555) from L1 entry 00000000003b6025 for dom22 (XEN) mm.c:3341:d22 ptwr_emulate: fixing up invalid PAE PTE 00000000003b6025 But I've no idea when those messages have been created. I've disabled selinux in dom0. Other domUs are running fine, although I haven't tried rebooting them. Any ideas what could be wrong with the domU? Regards, Peter

This fixes various problems that cropped up with the vdso patches. - Patch 1 fixes an information leak to userspace. - Patches 2 and 3 fix the kernel build on gold. - Patches 4 and 5 fix Xen (I hope). - Patch 6 (optional) adds a trace event to vsyscall emulation. It will make it easier to handle performance regression reports :) [1]

This fixes various problems that cropped up with the vdso patches. - Patch 1 fixes an information leak to userspace. - Patches 2 and 3 fix the kernel build on gold. - Patches 4 and 5 fix Xen (I hope). - Patch 6 (optional) adds a trace event to vsyscall emulation. It will make it easier to handle performance regression reports :) [1]

This fixes various problems that cropped up with the vdso patches. - Patch 1 fixes an information leak to userspace. - Patches 2 and 3 fix the kernel build on gold. - Patches 4 and 5 fix Xen (I hope). - Patch 6 (optional) adds a trace event to vsyscall emulation. It will make it easier to handle performance regression reports :) [1]

...171:d0 Domain attempted WRMSR 00000410 from 00000000:00043bff to 00000000:00000003. (XEN) traps.c:2171:d0 Domain attempted WRMSR 00000410 from 00000000:00000000 to 00000000:00000003. (XEN) mm.c:707:d1 Error getting mfn 284a5 (pfn 1d38a5) from L1 entry 00000000284a5025 for dom1 (XEN) mm.c:3635:d1 ptwr_emulate: fixing up invalid PAE PTE 00000000284a5025 (XEN) mm.c:676:d1 Non-privileged (1) attempt to map I/O space 000000f8 (XEN) mm.c:676:d1 Non-privileged (1) attempt to map I/O space 000000f8 # xm info host : aragorn.vialila.lan release : 2.6.18-92.1.22.el5.centos.plusxe...

Hello, Recently many advanced memory mechanisms are introduced into Xen. One problem we found is the conflict between p2m query and setting. For example, backend drivers always map domU’s page to its own space, during the mapping procedure, situations as follow may happen, when mfn is obtained by gfn_to_mfn(), this mfn is likely to be paged out. first case: grant mapping

Hi All, I am not very familiar with xen details. Now I am thinking of building two privilged domain(domain 0 not driver domain) at boot time. The other question is that wether it is possible to create another domain 0 by domain-builder running in domain0? Does it make sense when domain 0 is shut down unexpectedly another domain 0 can run at once. Maybe it is absurd. I am looking forwards

Hi, I installed Xen 4.0.1 from source on Debian 5.0.8 and when boot my computer hardware reboots at like "Scrubbing Free RAM". I tryed to find some information here but none was helpfull to me. Anyone? I have 4GB memory and a AMD Turion II X2 M500 (

Hello, I have some diagnostic Info for you. Tried to get xen-4.0.1 working on another node of my cluster. Only difference: Newer revision of the Hardware. Exactly same Software Stack. Stack: Ubuntu Lucid 64bit, xen-4.0.1 from Source, selfbuilt linux-2.6.32.27 from xen/stable-2.6.32.x Nodes working: HP DL380G5 16GB (Intel X5460) Node not working: HP DL380G6 16GB (Intel X5550) Effect: Xen

Hello, I''m facing a strange issue with network card PCI passthrough on my openwrt test domU. - With network PCI passthrough, DNS lookup failed for some domains (exemple, google.com) but not for other (free.fr my ISP, or my domain jbfavre.org). I can ping an IP address without any problem. - Starting domU as a "normal" (ie without PCI passthrough), no problem. As far as I can

2011/7/19 Stefano Stabellini <stefano.stabellini@eu.citrix.com>: > CC''ing Tim and xen-devel > > On Mon, 18 Jul 2011, Jiageng Yu wrote: >> 2011/7/16 Stefano Stabellini <stefano.stabellini@eu.citrix.com>: >> > On Fri, 15 Jul 2011, Jiageng Yu wrote: >> >> 2011/7/15 Jiageng Yu <yujiageng734@gmail.com>: >> >> > 2011/7/15