similar to: Any advantage of running 32bit dom0?

Hey, I was looking for step by step installation for RHEL5 as dom0 and RHEL5 as domU, but could not find it.I put some instructions, hope it will save some time for somebody. If you will find some errors please fix them :) I assume that you already have rhel 5 up and running (webserver as well).I will install guest system in paravirtualized mode (mine processor does not support full

I am currently running a Redhat Rel5 Dom0 with a solaris 11-66 xen domU as well as a Redhat REL4 domU. I am experiancing problems similary to those described the the Aug 2006 Release notes regarding ... Solaris domUs on non-Solaris dom0s 32-bit Solaris domUs should run on any 3.0.2-3 or later dom0. The majority of our testing has been on CentOS dom0s. 64-bit solaris dom0 and domU require updates

Hi list! Now when Fedora 10 is out, I thought of writing here what's needed to run Fedora 10 Xen domUs on CentOS 5 dom0. Fedora 10 does not have separate kernel-xen, but instead Xen domU support is included in the normal kernel-PAE.i686 and kernel.x86_64 (based on the pv_ops Xen support included in the mainline/vanilla Linux kernels). RHEL 5.3 beta (and final obviously too) includes

Original Dom0 setup had been done per Todd Deshane''s instruction:- http://deshantm.livejournal.com/29959.html Functionality of SNV89 PV and HVM DomUs tested fine as well as F8 and WinXP HVM guests. Once again, all done as advised at http://deshantm.livejournal.com/29959.html Next i attempted to follow :- https://help.ubuntu.com/8.04/serverguide/C/libvirt.html #

Hi: Reading Red Hat's Website and a printed manual of RH184 (Red Hat Virtualization course) I see that RHEL 5 only supports RHEL 4.5 and RHEL 5 as paravirtualized guests. So I asume this is the same situation for CentOS 5, right? What's the dependency between Xen versions for paravirtualized guests? I ask this questions because I got this experiences: 1. Running CentOS 5 as Dom0 - RHEL

All, similar to some mail threads found in this forum and some other xen-related threads, I had problems with the network performance of my test system: * software base of dom0/domU: RHEL5 (Xen 3.0.3, Redhat 2.6.18-8el5xen SMP kernel) * ibm x306 servers with 3Ghz P4 /MT support; coupled via Gigabit Ethernet switch * standard xen bridging network configuration * test tool: iperf * Xen

Hi all i have a rhel5 server with 3GB of RAM and 4 xen guests running: - 1 Windows 2003 + Citrix PS 4.5 with 1 GB - 2 Rhel5 guests with cluster suite and GFS with 640 MB of ram in each one - 1 rhel5 guest with 512 MB of RAM Total: 2.816 MB of RAM Dom0 "only have" 256 MB of ram. Is sufficient or do I need to assign more RAM on dom0? For guests, this ram is sufficient

["Standard" CentOS 5.5 Xen Virtualization installation.] I'm setting up a new box on AMD Opteron platform. I'm doing some preliminary baselines (no domUs running) with an inline Watt/VA meter. It appears to enable full power management Xen dom0 must have all cpus by not limiting in kernel statement nor in xendconfig.sxp. In previous installations I cut them back to 1 or 2.

I am using Xen 4.6.0-8.el7 on CentOS 7 with 3 Linux DomUs. I did have Xen 4.? on CentOS 6.5 on my previous system. I installed using yum install centos-release-xen. On shutting down the Hypervisor it used to wait for the DomUs to shut down gracefully (one can take a minute or more), then on starting up again it would restart the DomUs, all nice and controlled. For some reason the DomUs (CentOS

Hi folks, I am using Xen 2.0.7 with debian based dom0 and domUs on several machines. Every few days I find the clocks of dom0 and domUs on the same machine to differ between seconds and hours. I know this is mentionened every now and then on the list. What I want to know: Is this bug still officially not fixed? Is something done to fix it or is it left as is? I just have to know the state

Hi, I''m having some issues with having my domUs shutdown gracefully when my dom0 reboots. Heres my config.sxp. --- snippet --- (actions_after_crash restart) (actions_after_shutdown preserve) (auto_power_on False) (actions_after_reboot restart) (on_crash restart) (on_poweroff destroy) (on_reboot restart) (on_xend_start start) (on_xend_stop shutdown) ___________ When I reboot my

On Thu, Apr 7, 2016 at 5:46 PM, exvito here <ex.vitorino at gmail.com> wrote: > Hello all, > > I'm addressing the mailing list following the suggestion of gwd on > #centos-virt @freenode IRC. > > The subject says most of it. Here are the details : > > - Was running 4.4.x and configured such that /etc/xen/auto domUs would be > saved/restored on dom0

Hi, I''ve got a machine that''s hosting a number of virtual machines (58 + the dom0) and I''m having some weird issues with packet loss and high latency that happens when ksoftirqd spikes in CPU usage. The machine itself is CentOS 5 x86_64 running the stock Xen packages (3.1.2). It''s a dual quad-core w/ hyperthreading, 48 gigs of ram, and using Adaptec

Hi Francis. Personally I would gracefully shutdown all the VM?s first, before attempting to shutdown the xen hypervisor. Are you getting any fsck errors when restarting those VM?s? Kind Regards, Keith On 21 Jan 2016, at 08:48, Francis Greaves <francis at choughs.net> wrote: > I am using Xen 4.6.0-8.el7 on CentOS 7 with 3 Linux DomUs. I did have Xen 4.? on CentOS 6.5 on my previous

Try this: systemctl start xendomains.service systemctl enable xendomains.service On 21 January 2016 at 08:48, Francis Greaves <francis at choughs.net> wrote: > I am using Xen 4.6.0-8.el7 on CentOS 7 with 3 Linux DomUs. I did have Xen > 4.? on CentOS 6.5 on my previous system. I installed using yum install > centos-release-xen. > On shutting down the Hypervisor it used to

Package: xen-hypervisor-3.0-unstable-1-i386 Version: 3.0-unstable+hg11561-1 Severity: important I've installed xen-linux-system-2.6.17-2-xen-k7 (version 2.6.17-9) on a server, and planned to run 3 Xen domUs on it. Creating the domUs was no problem, and running two of them works well. Starting the third one however will crash the dom0 and forces it to reboot. The machine is a Athlon64 3800+

Hi all, I would like to know how to debug xen. To give some more informations, I would like to explain why I''d like to do this. I''ve compiled xen from source (3.1.x/unstable) and installed it on Debain etch. Furthermore I''ve installed 2 DomU, one HVM (Win2k3) and one EFW (Endian Firewall, RH-based 2.6.9-55 kernel). Both DomU''s are running fine for about 15

Hi, This is slightly OT as xen is not officially supported in EL6. But maybe someone else is running it on centos6 as well and could help me out here: I have problems allocating a static amount of memory for my xen dom0. It seems to reduce when new domUs are created, even though I *think* ballooning is disabled. Can someone advise me what I'm doing wrong? I have xen-4.1.1-3 installed from

Hello all, I'm addressing the mailing list following the suggestion of gwd on #centos-virt @freenode IRC. The subject says most of it. Here are the details : - Was running 4.4.x and configured such that /etc/xen/auto domUs would be saved/restored on dom0 shutdown/bootup. - Installation was based on "centos-release-xen" such that "yum upgrade" brough Xen to 4.6.1. After

Hello! I've noticed this problem two times now.. last time I fixed it by rebooting the (centos 5.1 x86 32b) xen host/dom0. Symptoms: - Already running domUs (debian 2.6.18-6-xen-686 32b PAE) continue running and working OK - Cannot start new domUs (debian 2.6.18-6-xen-686).. kernel bootup just hangs before running initrd. Same domU with the exact same xen domU cfgfile worked earlier.