similar to: Xen Roadmap proposal

The following series improves kexec in a Xen PVonHVM guest. It is available via git: git://github.com/olafhering/linux.git xen-kexec-XS_RESET_WATCHES-3.0 A new xenstored command XS_RESET_WATCHES has been added in xen-unstable.hg changeset 23839:42a45baf037d. The command removes all watches and transactions for the guest. The following patches make use of the new command to wipe all existing

Add xs_reset_watches function to shutdown watches from old kernel after kexec boot. The old kernel does not unregister all watches in the shutdown path. They are still active, the double registration can not be detected by the new kernel. When the watches fire, unexpected events will arrive and the xenwatch thread will crash (jumps to NULL). An orderly reboot of a hvm guest will destroy the

Hello, In http://wiki.xensource.com/xenwiki/Xen4.0 we mention the following: "Better performance and scalability: 128 vcpus per guest, 1 TB of RAM per host, 128 physical CPUs per host (as a default, can be compile-time increased to lots more)." But what''s the max supported amount of memory for a (64bit) guest? -- Pasi _______________________________________________

Guests other than domain 0 using the console output have previously been controlled by the VERBOSE define, but with no designation of which guest''s output was on the console. This patch converts the HVM output buffering to be used by all domains, line buffering their output and prefixing it with the domain ID. This is especially useful for debugging stub domains. Signed-off-by: Daniel De

hi I try to understand the code of xen memory there are gmfn, gpfn and pfn in the xen and in the /xen/include/xen/mm.h there are some explanation about them as follows: * 1. gpfn/gpaddr: A guest-specific pseudo-physical frame number or address. * 2. gmfn/gmaddr: A machine address from the p.o.v. of a particular guest. * 3. mfn/maddr: A real machine frame number or address. * 4.

Hi, I have a question about memory page tables in Xen. As far as I understood, every modification to page table will go through Xen(hypervisor). Is it so that all page tables are actually allocated in Xen(hypervisor) instead of guest OS(domain)? Also, is it the case that Xen(hypervisor) needs to maintain a page table for each process running in every domain? Thanks Haifeng

Hi list, I''ve read about recent efforts to push pv-on-hvm drivers to Linux mainline and I''m curious to know the cause for this. What''s the advantage over using pv_ops directly and booting the kernel paravirtualized? Are there plans to move Linux domUs closer to the KVM way (from an architectural point of view)? Hope you can help. Regards, Markus

Hi, Let me start a new thread for this. I contacted the Grub people, and they seem more interested in creating a native Xen port of Grub than piggybacking the Mini-OS environment usin kexec as I tried. But they need some documentation on the Xen "firmware" to assess the task at least. What could be given to them apart from hvc_xen.c and xen-blkfront.c in the Linux sources?

Hi, Let me start a new thread for this. I contacted the Grub people, and they seem more interested in creating a native Xen port of Grub than piggybacking the Mini-OS environment usin kexec as I tried. But they need some documentation on the Xen "firmware" to assess the task at least. What could be given to them apart from hvc_xen.c and xen-blkfront.c in the Linux sources?

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

Hi, We have found that exist a huge degradation in performance when doing I/O to a disk images contained in single files from a paravirtualized domain and from an HVM at the same time. The problem was found in a Xen box with Fedora 8 x86_64 binaries installed (Xen 3.1.0 + dom0 Linux 2.6.21). The test hardware was a rack mounted server with two 2.66 Ghz Xeon X5355 (4 cores each one, 128 Kb L1

The aim of this patch is to define a stable way in which PVH is going to do AP bringup. Since we are running inside of a HVM container, PVH should only need to set flags, cr3 and user_regs in order to bring up a vCPU, the rest can be set once the vCPU is started using the bare metal methods. Additionally, the guest can also set cr0 and cr4, and those values will be appended to the default values

In a recent conversation one of my coworkers raised a concern about memory limitations when running 32-bit guests on top of the 64-bit hypervisor. At this point the discussion is academic; I don''t know when/if we''ll ever be able to get system resources to test it, to see if the concerns that he expressed are real. So I decided to post this in hope of getting comments from the

Hi all, I was messing around with kexec and it seems to work just fine on KVM, but for Xen domU images, it doesn't work at all. Daniel, I saw some patches from you back in September 2012 for adding this support for Dom0, but they don't seem to have gone into the kernel (but other patches went into kexec-tools at that time.) You mention that domU support is "easy" after your

Hi all, I was messing around with kexec and it seems to work just fine on KVM, but for Xen domU images, it doesn't work at all. Daniel, I saw some patches from you back in September 2012 for adding this support for Dom0, but they don't seem to have gone into the kernel (but other patches went into kexec-tools at that time.) You mention that domU support is "easy" after your

Hi all, I was messing around with kexec and it seems to work just fine on KVM, but for Xen domU images, it doesn't work at all. Daniel, I saw some patches from you back in September 2012 for adding this support for Dom0, but they don't seem to have gone into the kernel (but other patches went into kexec-tools at that time.) You mention that domU support is "easy" after your

Hi all, I''ve been reading through the code regarding paging --> spending a lot of time in mm/*.*, as well as some of the other parts up a level or two, but I''m still unclear as to some key things. Here''s what I think I know: I think I know how a domain''s shadow page table is first allocated E.G. the hash_table is xmalloc''ed and when it is

Hello, I just setup a few virtual systems, and I came into some limitations using XEN. I''d like to share these, just to know if the limitations are in the system or in the user :) I am using a standard Debian 4.0 (etch) GNU/Linux distribiution. The system is an Intel Core 2 duo with virtualization inside. I use the amd64 flavour. Thus my kernel is

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