search for: physpages

From: Heiko Carstens <heiko.carstens at de.ibm.com> From: Christian Borntraeger <borntraeger at de.ibm.com> This patch changes the s390 memory management defintions to use the pgste field for dirty and reference bit tracking of host and guest code. Usually on s390, dirty and referenced are tracked in storage keys, which belong to the physical page. This changes with virtualization:

plain text document attachment (xx-paravirt-mm.patch) Memory management for paravirt_ops. Signed-off-by: Steven Rostedt srostedt@redhat.com Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com> Index: clean-start/arch/x86_64/mm/fault.c =================================================================== --- clean-start.orig/arch/x86_64/mm/fault.c +++

plain text document attachment (xx-paravirt-mm.patch) Memory management for paravirt_ops. Signed-off-by: Steven Rostedt srostedt@redhat.com Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com> Index: clean-start/arch/x86_64/mm/fault.c =================================================================== --- clean-start.orig/arch/x86_64/mm/fault.c +++

Hi all, I'm playing with virsh, and I succeed to mange easily some KVM nodes. But I have issues to size RAM of openvz guests. virsh set by default the the memory to 256M on each guest instead of that I specify in the XML I have to modify by end the variable PHYSPAGES on each /etc/vz/conf/id_of_my_vz.conf Please follow the XML dump and the steps that I did. Cheers,Aurelien Log ---- 1) Define openvz guest domain 103 #virsh -c openvz:///system define vztest.xml Domain 103 defined from vztest.xml 2) Start the guest #virsh -c openvz:///system start...

...131072 0 dummy 0 0 0 0 0 numproc 63 237 999999 999999 0 physpages 79977 262204 0 262144 0 vmguarpages 0 0 131072 2147483647 0 oomguarpages 30261 44087...

Andre, Are you going to have time to MFC things from -current for auto-tuning -stable before 9.2? I fear (maybe unnecessarily?) that we are about to ship yet another release that can't do basic 10gigE when sufficient memory exists. If you don't have time, then let me know and I'll see what I can do. -- Alfred Perlstein VP Software Engineering, iXsystems

Hi all, I've been working on a port of paravirt_ops for the x86_64 architectures for a couple of days. Here's the result so far. I'm posting it soon for early cooments. The more, the better. It's obviously based on the previous work for i386, with the needed modifications. By now, I'm able to boot a bare metal kernel, but there are still some known issues, that are in my TODO

Hi all, I've been working on a port of paravirt_ops for the x86_64 architectures for a couple of days. Here's the result so far. I'm posting it soon for early cooments. The more, the better. It's obviously based on the previous work for i386, with the needed modifications. By now, I'm able to boot a bare metal kernel, but there are still some known issues, that are in my TODO

This patch series introduces a backend for kvm to run on IBM System z machines that uses the mainframe's sie virtualization capability. This work runs 64bit guests on z800/z890/z900/z990/z9/z10 class machines with a 64bit linux host. Userspace will follow once we're done brushing it over. The patch queue consists of the following patches, which can be applied in sequence on top of kvm.git

This patch series introduces a backend for kvm to run on IBM System z machines that uses the mainframe's sie virtualization capability. This work runs 64bit guests on z800/z890/z900/z990/z9/z10 class machines with a 64bit linux host. Userspace will follow once we're done brushing it over. The patch queue consists of the following patches, which can be applied in sequence on top of kvm.git