similar to: Xen 3.0 Status update

During boot of dom0, I get the following. Box is remote, so I''m now waiting for proxy power button pusher ;-) tg3 init fails doing dma_alloc_coherent (I assume this is from tg3_init_one -> tg3_test_dma -> pci_alloc_consistent -> dma_alloc_coherent). Looks like an issue with the amount of memory in dom0. Is this known? thanks, -chris root (hd0,0) Filesystem type is ext2fs,

u.inuse.type_info is at the end of the pfn_info structure, and is u32 for both x86_32 and x86_64--in this location it can also be the last 32 bits of a page. several functions use bitopts.h functions to manipulate this member, and on x86_64 these functions use u64 instructions, which will overflow the page boundary, and possibly the end of memory as we see here: (XEN)

Here is a patch for clustered xAPIC and Unisys ES7000 support in Xen. To turn the features on add CONFIG_X86_CLUSTERED_APIC and CONFIG_ES7000 defines to xen/include/asm-x86/config.h Signed off by Aravindh Puthiyaparambil <aravindh.puthiyaparambil@unisys.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Folks, I''m happy to report that dates have been finalized for the next Xen Summit: November 14-16 2007; Santa Clara CA, USA Sun Microsystems have kindly agreed to host the event at their Santa Clara campus. The plan is to start at 1pm on Wednesday the 14th, then run until lunchtime on Friday. The next steps are to put together a program committee and send out a formal Call For

Folks, I''m happy to report that dates have been finalized for the next Xen Summit: November 14-16 2007; Santa Clara CA, USA Sun Microsystems have kindly agreed to host the event at their Santa Clara campus. The plan is to start at 1pm on Wednesday the 14th, then run until lunchtime on Friday. The next steps are to put together a program committee and send out a formal Call For

Hi Ian, Natasha and I are interested in helping with the io emulation work for fully virtualized HVM guests you mentioned in your March 12th email: http://lists.xensource.com/archives/html/xen-devel/2006-03/msg00394.html In the post, you mentioned the following tasks: - get minios running on x86_64 - port xenbus/netfront/blkfront to minios - compile qemu-dm into minios - redirect IO to qemu-dm

add a hypercall number for virtual device in unmodified guest There are 6 patches for para-driver support in vmx guest. This is the first one. Signed-off-by: Xiaofeng Ling <xiaofeng.ling@intel.com> Signed-off-by: Arun Sharma <arun.sharma@intel.com> diff -r 287d36b46fa3 xen/arch/x86/x86_32/entry.S --- a/xen/arch/x86/x86_32/entry.S Tue Aug 30 20:36:49 2005 +++

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

The patchset will add basic NUMA support to Xen (hypervisor only). We borrowed from Linux support for NUMA SRAT table parsing, discontiguous memory tracking (mem chunks), and cpu support (node_to_cpumask etc). The hypervisor parses the SRAT tables and constructs mappings for each node such as node to cpu mappings and memory range to node mappings. Using this information, we also modified the

If you execute cat /dev/urandom at the xm console of a guest domain, it will spew garbage forever. Attempts to run xm destroy on it simply hang. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, I thought I had a workaround for live migration crashing (I''ve been looking at the SLES 3.0.2 9742c code.), but I found that I was getting filesystem errors. I''m wondering if the problem is races in data being written to the backing storage. When migrating a domain, before the domain is started on the new host, you have to guarantee that all the domU vbd data is out of

Hi all, I am using Xen 2.0.7. I have Broadcom NetXtreme BCM5704 Gigabit Ethernet (rev 02) cards which support frames greater than 1500. However when I boot into Xen and try to set the MTU to anything higher than 1500 (e.g., 4000, 8000 etc) I get a segmentation fault. After this fault, every command fails with a segmentation fault. I saw a similar bug report posted here:

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

Add vscsiif.h Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com> Signed-off-by: Jun Kamada <kama@jp.fujitsu.com> Signed-off-by: Akira Hayakawa <hayakawa.akira@jp.fujitsu.com> ----- Jun Kamada _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, I''ve added some preliminary support for VT-d for paravirtualized guests. This must be enabled using an ''iommu_pv'' boot parameter (disabled by default). I''ve added some python bindigs to allow xend to assign PCI devices to IOMMU for PV guests. For HVM guests this is handled in ioemu. Not sure if it makes sense to handle both cases in one place. The

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen hvc console (console=hvc0) *