similar to: Virt SIG roadmap

Hi all On 07/07/2015 10:30 PM, Johnny Hughes wrote: > On 07/07/2015 12:20 PM, Johnny Hughes wrote: [.... loads of stuff deleted .... ] >> OH .. I see, I did not get the firmware files, but their git pointer info :) >> >> I will rebuild and repost. >> > Please try the packages that are now in the same location. > >

Hi all, Looking to move from VMware to Xen4CentOS. We currently run Centos7 as our servers main distort. All the documentation I?ve found on the Xen4CentOS only refers to Centos6. Do any of you know if it currently or is being developed to work with Centos7? thanks in advance

Greeting, We are about to update the centos-release-xen package to point to Xen 4.8 rather than 4.6. I'll push the update next week. As a reminder, you can "pin" your installation to Xen 4.6 by installing centos-release-xen-46 and then removing centos-release-xen. And for the more adventurous, that update will come with a new package centos-release-xen-410 to install Xen 4.10.

I normally use the network-script parameter in the '/etc/xen/xend-config.sxp' configuration file to configure network bridges. However, the latest release of Xen4CentOS (which comes with Xen 4.4.1) has xend disabled by default. Can I continue to use network-script without xend? If not what is the recommended method for automatically configuring network bridges with the latest release of

On 07/07/2015 12:00 PM, Johnny Hughes wrote: > On 07/07/2015 10:36 AM, Akemi Yagi wrote: >> On Mon, Jul 6, 2015 at 8:43 PM, Johnny Hughes <johnny at centos.org> wrote: >>> On 07/05/2015 11:35 AM, T.Weyergraf wrote: >>>> Hi folks >>>> >>>> As mentioned in the subject, kernel-3.18.12-11 is missing firmware files >>>> required to

On Mon, Sep 7, 2015 at 11:02 PM, T.Weyergraf <T.Weyergraf at virtfinity.de> wrote: > First of all, I fully agree, that forked repos are undesirable. However, to > the casual observer (like me), there are hardly any ressources for Xen on > CentOS 7. There are some beta packages, as announced in the start if this > thread, with the latest update being 4.4.2 on 4th of august. I

All, I have compiled an experimental 3.18.12 kernel from the 3.18 LTS kernel branch from kernel.org for the Xen4Centos 6 tree. http://people.centos.org/hughesjr/xen-kernel/x86_64/ This should be considered extremely experimental at this point and is unsigned. I have tested it on 2 generic servers and it worked fine on both of those with sata and gigabit ethernet. Please test this and provide

The new process for auto updates of grub upon kernel install is in the xen4centos testing repo. In order to test these as updates to an existing system, you can do this: 1. download the test repo file: http://dev.centos.org/centos/6/xen-c6-RC1/xen-c6-RC1.repo 2. Put it in /etc/yum.repos.d/ 3. Issue this command: yum --disablerepo=Xen4CentOS upgrade xen\* centos-release-xen (that should

Hi So far, I did some preliminary testing using nested virt: host(L0): Fedora 25, kernel-4.9.11-200, kvm+qemu Guest(L1): CentOS 7 Xen-4.6.3-7, kernel-4.9.11-22 So far, at least the L1 setup had no issues. I'll need to pull L1 guest-storage from backup to test some L2 guests. Likewise, I try to allocate two blades at work for tests on real metal. Our standard-tests include starting

Hello, It seems currently when you "yum update" CentOS 6.6 Xen host you end up getting python-virtinst from c6 base repo: python-virtinst-0.600.0-24.el6.noarch and not from Xen4CentOS repo, because the version there is "older": 0.600.0-19. .. which means the centos/xen-specific patch in python-virtinst is "lost". (default to tap2 instead of tap1, to make blktap2

Do we want to move the Xen4CentOS kernel to new LTS 3.10.x from the current 3.4.x Kernel? If so, can we start testing the that kernel build? Is someone from Xen.org working on porting the xen specific patches that are required in the 3.10.x kernel from the ones we have in the 3.4.x tree in Xen4CentOS? The only one I know we need is the blktap module. I have created a new spec that builds a

I think this may have been asked before, but what would it take to get debuginfo packages built for the Xen4CentOS kernels? If it's just a patch for kernel.spec file that nobody has gotten around to, what is the best starting place for making that patch? Thanks, Sarah

Subject: Re: [CentOS-virt] Xen4CentOS kernel panic on dom0 reboot On Wed, Mar 5, 2014 at 10:17 AM, David Vrabel <david.vrabel at citrix.com>wrote: > > On 05/03/14 15:09, Karl Johnson wrote: > > > I've been using Xen4CentOS for the last 3 months. It's working fine and > > > dom0/domUs are stable but the server does a kernel panic when doing a > > >

By default, /var/lib/xenstored is mounted tmpfs in centos 5 but this doesn't appear to be true for Xen4CentOS. This can cause performance issues as mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=446089 I'm not sure if this should be part of xencommons, but if not, adding a tmpfs mount should probably be documented on the quick start wiki page. Thanks, Sarah

Thanks all for the advice. It seems there is an issue with Dracut booting from these hosts when LVM is used. dracut: Scanning devices sda2 for LVM logical volumes VolGroup/lv_swap VolGroup/lv_root dracut: inactive '/dev/VolGroup/lv_swap' [1.94 GiB] inherit dracut: inactive '/dev/VolGroup/lv_root' [230.69 GiB] inherit dracut: PARTIAL MODE. Incomplete logical volumes will be

I installed CentOS6 with the xen4centos set of packages; then I tried to install KVM (for performance comparison), I got the following error in YUM: --> Processing Dependency: /usr/share/gpxe/e1000-0x100e.rom for package: 2:qemu-kvm-0.12.1.2-2.415.el6_5.4.x86_64 Package gpxe-roms-qemu is obsoleted by ipxe-roms-qemu, but obsoleting package does not provide for requirements I manually

Hi list, what solution do you use for virtualizzation? thanks in advance.

Howdy, I recently went through a frustrating experience trying to get Xen 4 running on a CentOS 7 system. After a fresh install, fully updating the system, rebooting, then trying to install Xen4CentOS it would fail to boot into the 4.9 kernel, sitting there with a blinking cursor indefinitely. I thought it was a failure with grub, but it turns out this was set in the grub config:

Hello, I am running two dom0s, one on CentOS 5 with Xen 4.1.2 (from Gitco) and the other one on CentOS 6 with Xen 4.2.4 (from Xen4CentOS). I host one LVM based domU on both from the same template (CentOS 6 PV) with the same Xen config (see below). However, the domU on Xen 4.1 reports itself as Xen PV while the domU on Xen4CentOS reports itself as Xen HVM. == First domU == virt-what and cPanel