similar to: [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6)

Hello, I just wrote a step-by-step tutorial how to install the latest Xen 4.0.1 hypervisor on Fedora 13 (x86_64) host from src.rpm packages, and the pvops dom0 kernel from git repository. Check it out: http://wiki.xensource.com/xenwiki/Fedora13Xen4Tutorial It also shows how to install various Xen PV guests using the native distro installers: - CentOS 5.5 - Fedora 13 - Ubuntu 10.04 LTS

Hello, I just wrote a step-by-step tutorial how to install the latest Xen 4.0.1 hypervisor on Fedora 13 (x86_64) host from src.rpm packages, and the pvops dom0 kernel from git repository. Check it out: http://wiki.xensource.com/xenwiki/Fedora13Xen4Tutorial It also shows how to install various Xen PV guests using the native distro installers: - CentOS 5.5 - Fedora 13 - Ubuntu 10.04 LTS

This is fresh install of CentOS v6 and Xen v4.1 on a new Dell server following the tutorial posted at: http://wiki.xensource.com/xenwiki/RHEL6Xen4Tutorial   Every thing went just fine, yet virbr0 won''t work and when I run brctl show I get the following error message:   [root@pe1950 ~]# brctl show bridge name     bridge id               STP enabled     interfaces virbr0         

This is fresh install of CentOS v6 and Xen v4.1 on a new Dell server following the tutorial posted at: http://wiki.xensource.com/xenwiki/RHEL6Xen4Tutorial   Every thing went just fine, yet virbr0 won''t work and when I run brctl show I get the following error message:   [root@pe1950 ~]# brctl show bridge name     bridge id               STP enabled     interfaces virbr0         

Just wondering why kernel-2.6.32.23-170.xendom0.fc12.src.rpm cannot make itself into F14. It seems pretty stable. Why it cannot be just a package available via "yum install" . Anyway Fedora''s Libvirt has the best compatibility with Xen 4.0.1. It''s not too late switch back to Xen with PVOPS kernel. XenLinux 2.6.34.7 aka Suse is really dangerous . It outperforms pvops

Hi As you may''ve seen from my last posts I''m struggling to get the setup on my subject line to work without flaws. I''ve tried compiling the Kernel from Source, I''ve also tried Fedora 14, which has a flaky pv_ops Dom0 kernel which DOESN''T work at all, but none of these seem to work. I''m a mid-time XEN user, I just love it and want to stay

Hi As you may''ve seen from my last posts I''m struggling to get the setup on my subject line to work without flaws. I''ve tried compiling the Kernel from Source, I''ve also tried Fedora 14, which has a flaky pv_ops Dom0 kernel which DOESN''T work at all, but none of these seem to work. I''m a mid-time XEN user, I just love it and want to stay

Hi all, With help from others, I''ve been able to get Olaf''s patch for enabling MTUs >1500 for vifX.y and tapZ devices working. I''ve been able to boot dom0, launch domU and live-migrate without having the bridge''s MTU degrade at any time. Would the Xen RPM maintainers (and others) mind taking a look at the following patches? Kernel part:

Hi, Does anyone know what version of XEN works fine with CentOS 6? I installed XEN on a CentOS 6 server, as per these instructions: http://www.crc.id.au/xen-on-rhel6-scientific-linux-6-centos-6-howto/ And the server now gives this error on reboot: PANIC: early exception 0e rip 10:0 error 10 cr2 0 These are the packages that was installed: Installed: kernel-xen.x86_64 0:2.6.32.45-1

1. Attempt to load Nexenta under 2.6.32.16-1.2.108.xendom0.fc13.x86_64 Xen 4.0.1-rc6-pre & 2.6.32.16-1.2.108.xendom0.fc13.x86_64 on top F13 [root@fedora13 NexentaStor-Community-3.0.2]# uname -a Linux fedora13 2.6.32.16-1.2.108.xendom0.fc13.x86_64 #1 SMP Fri Jul 23 17:09:30 MSD 2010 x86_64 x86_64 x86_64 GNU/Linux [root@fedora13 NexentaStor-Community-3.0.2]# xm create -c

Hi all, I'm happy to announce a new tutorial! https://alteeve.com/w/2-Node_Red_Hat_KVM_Cluster_Tutorial This tutorial walks a user through the entire process of building a 2-Node cluster for making KVM virtual machines highly available. It uses Red Hat Cluster services v3 and DRBD 8.3.12. It is written such that you can use entirely free or fully Red Hat supported environments.

Hi all, I'm happy to announce a new tutorial! https://alteeve.com/w/2-Node_Red_Hat_KVM_Cluster_Tutorial This tutorial walks a user through the entire process of building a 2-Node cluster for making KVM virtual machines highly available. It uses Red Hat Cluster services v3 and DRBD 8.3.12. It is written such that you can use entirely free or fully Red Hat supported environments.

On 8 March 2016 at 19:36, Digimer <lists at alteeve.ca> wrote: > On 08/03/16 02:32 PM, James Hogarth wrote: > >>>> https://bugzilla.redhat.com/show_bug.cgi?id=1315856 > >>> > >>> What's odd is how it works in Fedora using mock but not EPEL6 with mock > >> ... > >>> got to be down to how the build roots are constructed. >

I have seen over the past few months subjects on RHEL 6 and RHEL 5.6 Are these two different builds for Centos to chase or one in the same?

On 12-03-2015 17:39, Digimer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 12/03/15 04:29 PM, Gilbert Sebenste wrote: >> Hello everyone, >> >> A network engineer buddy of mine brought up for discussion with me >> that he'd like to do some throughput testing, but he's new to >> Linux/RedHat. Is there any software I can recommend to

On 8 March 2016 at 19:02, Digimer <lists at alteeve.ca> wrote: > On 08/03/16 01:51 PM, James Hogarth wrote: > > On 8 March 2016 at 17:22, Digimer <lists at alteeve.ca> wrote: > > > >> On 08/03/16 11:36 AM, James Hogarth wrote: > >>> On 8 March 2016 at 16:15, Digimer <lists at alteeve.ca> wrote: > >>> > >>>> On

Hi all, I was trying to rebuild mtr (http://vault.centos.org/6.7/os/Source/SPackages/mtr-0.75-5.el6.src.rpm) and I keep getting: ==== Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.gu9Ds0 + umask 022 + cd /root/rpmbuild/BUILD + '[' /root/rpmbuild/BUILDROOT/mtr-0.75-5.el6.x86_64 '!=' / ']' + rm -rf /root/rpmbuild/BUILDROOT/mtr-0.75-5.el6.x86_64 ++ dirname

On 8 March 2016 at 17:22, Digimer <lists at alteeve.ca> wrote: > On 08/03/16 11:36 AM, James Hogarth wrote: > > On 8 March 2016 at 16:15, Digimer <lists at alteeve.ca> wrote: > > > >> On 08/03/16 07:11 AM, James Hogarth wrote: > >>> On 8 March 2016 at 10:07, Leon Fauster <leonfauster at googlemail.com> > >> wrote: > >>>

On 8 March 2016 at 16:15, Digimer <lists at alteeve.ca> wrote: > On 08/03/16 07:11 AM, James Hogarth wrote: > > On 8 March 2016 at 10:07, Leon Fauster <leonfauster at googlemail.com> > wrote: > > > >> Am 08.03.2016 um 01:50 schrieb Digimer <lists at alteeve.ca>: > >>> I'm not surprised, given that it is in the repo. That's why I was

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/15 08:16 PM, Steven Tardy wrote: > >> On Feb 23, 2015, at 6:34 PM, Ashley M. Kirchner >> <ashley at pcraft.com> wrote: >> >> I have a Dell server that has two built-in ethernet devices. When >> I kickstart the machine, they are correctly identified as eth0 >> and eth1 (correctly meaning they