similar to: Xen 3.1 - 32 vs 64 bit hypervisor

Hi Centos Users What are the advantages of 64 Bit and respective 32 Bit installation of Centos? With PAE 32 Bit installation can address huge amount of RAM. As a desktop system, I prefer 32 Bit installation because of teething troubles in 64 Bit Linux world. When would you choose 64 Bit and when 32 Bit? We are running mostly application and web services. Is this true that with 32 Bit

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

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-2 Severity: minor The package description reads: This version of the hypervisor is built with PAE enabled, in order to support systems with more than 4GB of memory. If you have less than that you should probably choose the non -pae version. That's not entirely true. I tried installing the non-pae version on my ProLiant

Hi, had a few problems with using xen: First: built a xen from source (tgz) and make dist ... then made initrd with mkinitrd and modules=all in the mkinitrd.conf -> initrd.img was 14mb and set it up in the grub with module /initrd.... on boot it loads the initrd like: Loading ramdisk into ram .... done but then NO MODULES in the initrd are being loaded by the kernel, though initrd

I booted into X11 and have networking working and a kernel compile = running. SMP and PAE should be less than a day away. This completes = the proof of concept, I believe ;) I didn't cc LKML since I didn't want to spam them with graphics. Very = controversial graphics. Hopefully you appreciate the humor. Zach -------------- next part -------------- A non-text attachment was

Guys, could you please confirm that these patches from -mm: paravirt-remove-read-hazard-from-cow.patch paravirt-pte-clear-not-present.patch paravirt-lazy-mmu-mode-hooks.patch paravirt-combine-flush-accessed-dirty.patch paravirt-kpte-flush.patch paravirt-optimize-ptep-establish-for-pae.patch paravirt-remove-set-pte-atomic.patch paravirt-pae-compile-fix.patch paravirt-update-pte-hook.patch are

Guys, could you please confirm that these patches from -mm: paravirt-remove-read-hazard-from-cow.patch paravirt-pte-clear-not-present.patch paravirt-lazy-mmu-mode-hooks.patch paravirt-combine-flush-accessed-dirty.patch paravirt-kpte-flush.patch paravirt-optimize-ptep-establish-for-pae.patch paravirt-remove-set-pte-atomic.patch paravirt-pae-compile-fix.patch paravirt-update-pte-hook.patch are

Hi, I have just looked at the xen source, because I want to finish my work from yesterday and have the hypervisor-pae really build & packaged. It seems so that we have two possibilities to do this: 1) create another dpatch that would patch xen/Makefile in order to have other filenames for the hypervisor when the pae-flag is set. the advanced would be, that if we use diffrent filenames

Package: xen-hypervisor-3.0-i386-pae Severity: wishlist The description of the package should give hints as to why it is different from xen-hypervisor-3.0-i386. Mike -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686 Locale:

I just discovered that my xen hypervisor only believes that it has 3199 MB of memory, when there are 4GB inside the computer. I don''t know how long this has been this way, but I do not know how to try and force the hypervisor to realize how much memory it has. Any ideas how I can accomplish this? I am running CentOS 5 (RHEL 5), kernel 2.6.18-53.1.4.el5xen, x86_64, xen 3.0.3.

hi, I''m developing my own 32-bit (no PAE) paravirtualized kernel for xen with Mini-OS as a starting point. I am currently working on process page table support (equivalent of arch/i386/mm/pgtable-xen.c) and mostly following Linux for the moment. I noticed that linux-2.6.18-xen never pins an L1 table (a pte), yet __pgd_pin() walks the page directory and gives up write access on the kernel

I have a machine that has worked fine for years on CentOS5. kernel-PAE-2.6.18-164.15.1.el5 is the last "works fine" kernel, but kernel-PAE-2.6.18-194.3.1.el5 crashes at boot every time. I tried banging on the side of the monitor to no avail. All kidding aside, here are pictures of my monitor when booting 194 in case that is helpful.

Package: src:xen Severity: important Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-2 I recently upgrade from Squeeze to Wheezy on a system which had the xen-linux-system-686-pae metapackage (one of two which Provides: xen-linux-system). After dist-upgrade I had the new xen-utils-common and xenstore-utils (and a few others) but not the xen-utils-4.1 or xen-hypervisor-4.1-i386 or xen-hypervisor-amd64

Hi, I have several machines using xen-hypervisor-3.2-1-i386 from etch-backports and they recently got upgraded to 20 or 24G RAM. I have seen talk of a limit of a 16G RAM with 32bit PAE Xen and indeed this is what I am seeing. I am guessing there is still no way to get the 32bit hypervisor to see more than 16G RAM, and I must go to 64bit. Can I boot a 64bit hypervisor and still keep the same

Does anyone know if the Xen 3.1.0 kernels as distributed in the "open source" tarballs (x86_64 version) are vulnerable to the recently-announced vulnerability CVE-2007-4573? IF so, is there any plan to release patched tarballs anytime soon? Thanks Steve Timm -- ------------------------------------------------------------------ Steven C. Timm, Ph.D (630) 840-8525 timm@fnal.gov

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=395 The guest domain crashed during the routine daily tests that I ran. Machine: IBM ThinkCentre, 1GB of RAM with FC3 based setup. Xen build, PAE enabled using changeset: 7701:abbe3df33774 [root@thinkcentre-dom0 xen-unstable.hg]# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 3

Do people actually use HostbasedAuthentication? It needs several steps to enable and generally seems quite arcane by now. I wonder if this is something that could be trimmed away... -- Christian "naddy" Weisgerber naddy at mips.inka.de

Hi, I've installed a mail server using CentOS 4.4 Now, if i reboot the server remotely by ssh, when it cames up, i have no network. The interface is up and everything looks pretty fine. But i can't even ping other machines in the same intranet. If i reboot it locally at the console, the network cames just fine. Never seen nothing like this. The mind boggles :( Any ideas ? Warm

Hey all, I''m thinking about moving my 2.0.7 install over to 3.0.0 for eventual use in a production environment. Two questions: 1) Do people think 3.0.0 is ready for production - or is it just a testing/unstable playpen? 2) What do I have to change - just the xen-2.0.7.gz for do I have to recompile the dom0/domU kernels too? Cheers, Matthew Walster

On Thu, 16 Nov 2006 00:16:26 +0100 Adrian Bunk <bunk@stusta.de> wrote: > Paravirt breaks CONFIG_X86_PAE=y compilation: > > <-- snip --> > > ... > CC init/main.o > In file included from include2/asm/pgtable.h:245, > from > /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/include/linux/mm.h:40, > from >