Re: Xen Version update policy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


The latest bunch of test packages are available here:

Hopefully, as of a few hours ago, this set should actually install.

Currently, networking won't work as they require brctl - which isn't in EL8. I've written patches for this, but they'll probably end up being part of a cleanup of everything in /etc/xen/scripts/

Problem is, they're probably too late for the 4.13.0 release - so I'll have to carry them myself for a while until they hit the git staging area within Xen.

I don't have a kernel capable of being a Dom0 as yet - so that's still at a roll your own or obtain elsewhere status.

The source for all this is here:

Yes, I take patches.

Steven Haigh

📧 netwiz@xxxxxxxxx     💻

On Fri, Dec 13, 2019 at 10:11, Christoph <mangel@xxxxxx> wrote:

if you need someone to test the centos8 pkgs, Im interested :)


Am 13.12.2019 01:31, schrieb Steven Haigh:
On 2019-12-13 04:54, Kevin Stange wrote:
I don't want to burden Steven Haigh any, but I wonder if there's a way we could combine some of our efforts to make both "Xen made easy!" and
the Virt SIG Xen easier to manage.

I've been thinking about this for a while. The problem has been the
workflows between myself and the SIG are so far apart, its hard to
look at how to merge them.

I have full CI between my own git and packages to the mirrors - which
is good, but has its down sides. I also don't have the restrictions of
the CentOS build system to deal with - which is great for my workflow

I'm prepping packages for CentOS 8 now - but its exposing quite a
number of problems around the main toolsets for Xen - and instead of
just adding my own patch and moving on (ala Fedora's Xen packages),
I'm trying to get fixes in upstream where possible.

My todo list currently includes:
1) Replace all #! that include env python to a specific python
version/binary. ie /usr/bin/python or /usr/bin/python3. The configure
portions of this are complete, but the scripts need to be altered to
have the detected python version populated.

2) There's no brctl in CentOS 8. The network scripts need to be
re-written to use 'ip' instead. To maintain compatibility, the network
scripts need to support both brctl and ip commands and use whichever
is present on the system.

3) UEFI support needs to be tested. The preferred UEFI boot method for
Dom0 is to use grub to then boot Xen - but this needs to be tested.

So while me moving to try and get these fixed upstream is great - it
should make everyone's job easier in the long term. Although I have
the same problem as the SIG - there's just not enough people to test /
patch stuff. The more we deep dive into 4.13, the further away I can
see the release happening :(
CentOS-virt mailing list

CentOS-virt mailing list

[Index of Archives]     [CentOS Users]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     []     [Xfree86]     [Linux USB]

  Powered by Linux