[libvirt] [tck PATCH] Update x86_64 image & virt-builder image to F31
Laine Stump
laine at redhat.com
Mon Dec 16 15:11:37 UTC 2019
On 12/13/19 11:51 AM, Daniel P. Berrangé wrote:
> i386 was dropped even as a secondary arch in F31 so must remain
> on F30
>
> Signed-off-by: Daniel P. Berrangé <berrange at redhat.com>
I did that locally a couple weeks ago, then forgot to send it. (except
that I missed the part to update the kernel images. I guess when F30
goes EOL we'll just drop i686 testing completely?)
Reviewed-by: Laine Stump <laine at redhat.com>
> ---
> conf/default.cfg | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/conf/default.cfg b/conf/default.cfg
> index 39d9b04..3493ad7 100644
> --- a/conf/default.cfg
> +++ b/conf/default.cfg
> @@ -49,7 +49,7 @@ images = (
> hvm
> xen
> )
> - osname = fedora-30
> + osname = fedora-31
> }
> )
>
> @@ -76,6 +76,7 @@ images = (
> #
> kernels = (
> # Fedora 30 i686 PAE has pv_ops, so one kernel can do both Xen and KVM guests here
> + # No i386 releases since F30
> {
> arch = i686
> ostype = (
> @@ -85,15 +86,15 @@ kernels = (
> kernel = http://dl.fedoraproject.org/pub/fedora-secondary/releases/30/Everything/i386/os/images/pxeboot/vmlinuz
> initrd = http://dl.fedoraproject.org/pub/fedora-secondary/releases/30/Everything/i386/os/images/pxeboot/initrd.img
> }
> - # Fedora 30 x86_64 has pv_ops, so one kernel can do both Xen and KVM guests here
> + # Fedora 31 x86_64 has pv_ops, so one kernel can do both Xen and KVM guests here
> {
> arch = x86_64
> ostype = (
> hvm
> xen
> )
> - kernel = http://dl.fedoraproject.org/pub/fedora/linux/releases/30/Everything/x86_64/os/images/pxeboot/vmlinuz
> - initrd = http://dl.fedoraproject.org/pub/fedora/linux/releases/30/Everything/x86_64/os/images/pxeboot/initrd.img
> + kernel = http://dl.fedoraproject.org/pub/fedora/linux/releases/31/Everything/x86_64/os/images/pxeboot/vmlinuz
> + initrd = http://dl.fedoraproject.org/pub/fedora/linux/releases/31/Everything/x86_64/os/images/pxeboot/initrd.img
> }
> # LXC containers need a virtual container filesystem somewhere
> # {
More information about the libvir-list
mailing list