virt November 2016

virt@lists.centos.org

9 participants
8 discussions

Start a nNew thread

Libvirt packages update
by Jean-Marc Liger 03 Jan '17

03 Jan '17

Hi, As libvirt provided in CR repo is now 2.0.0, libvirt packages for Xen need to be updated. Regards, Jean-Marc Liger

3 2

Running i386 guests under CentOS7 amd64 kvm host
by C. L. Martinez 01 Dec '16

01 Dec '16

Hi all, Maybe it is a stupid question, but I a totally lost. When I try to configure an ubuntu i386 guest under CentOS7 amd64 kvm host (fully patched) using virt-manager, I can't select what architecture I want to use. If I try to change guest.xml using "virsh edit", I can do it, but guest doesn't starts ... Is it not possible to run i386 guests under CentOS7 amd64 kvm hosts?? Thanks. -- Greetings, C. L. Martinez

4 10

Virt SIG page
by Sandro Bonazzola 30 Nov '16

30 Nov '16

Hi, I would suggest to review https://wiki.centos.org/SpecialInterestGroup/Virtualization and update it a bit. I think it's a bit outdated. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Fwd: Still no C4-8xl for Centos6-HVM AMI
by John Peacock 30 Nov '16

30 Nov '16

I asked back in September about getting the Centos6-HVM AMI updated to support the C4-8XL instance type. Karanbir responded https://lists.centos.org/pipermail/centos-virt/2016-September/005222.html but I still see no evidence this has happened. This is a major thorn in our side and has prevented us from going completely to the C4 instance type , which we need for performance (both CPU and network). Thanks in advance John -- JOHN PEACOCK senior software build and release engineer tel 877-887-3031 mobile 240-429-9334 email john.peacock(a)sparkpost.com

1 0

Re: [CentOS-virt] Request to join Centos Virt SIG
by Sandro Bonazzola 21 Nov '16

21 Nov '16

On Mon, Nov 21, 2016 at 3:45 PM, Eyal Edri <eedri(a)redhat.com> wrote: > Hi, > > My name is Eyal and I've been a member of the oVirt infrastructure team > [1] from its inception date a few years ago. > > In our team we're constantly using Centos repos to test oVirt on our CI > systems [2] and I would want to join the SIG group to be able to hear on > upcoming releases and help oVirt consume them in alignments with the > release schedule. > > Welcome aboard Eyal, ack to join Virt SIG for oVirt on my side. Eyal experience with oVirt CI is really welcome! > > [1] infra-docs.readthedocs.org > [2] jenkins.ovirt.org > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Virtualization & IaaS DevRoom at FOSDEM (closes Nov 18th)
by Lars Kurth 14 Nov '16

14 Nov '16

Hi all, as last year the Virtualization & IaaS DevRoom is happening at FOSDEM again next year, and the CFP is available at http://www.ovirt.org/blog/2016/10/call-for-proposal-fosdem-2017/ I hope to see many of you there again in 2017. Best Regards Lars

1 0

Re: [CentOS-virt] CentOS-virt Digest, Vol 111, Issue 2
by Jinesh Choksi 07 Nov '16

07 Nov '16

On 05/11/2016 12:00, centos-virt-request(a)centos.org wrote: > would making these changes not break the existing automation that folks > might have in place ? Hi Yes, that was my concern as well. I was asking the question since I wanted to find out whether it was possible that a refresh of the CentOS-7 x86_64 AMI would enable the new functionality. I was not requesting for the functionality to be enabled. Regards, Jinesh

1 0

CentOS-7 x86_64 AMIs and consistent network device naming
by Jinesh Choksi 04 Nov '16

04 Nov '16

Hello, Re: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-Be… Are there any upcoming plans for turning off the use of legacy interface names in the next official CentOS 7.x AMI? Currently, both the official RHEL 7.3 GA AMI and the latest available official CentOS-7 x86_64 AMI use legacy interface names via either: - "net.ifnames=0" kernel boot parameter or - "ln -vs /dev/null /etc/udev/rules.d/80-net-setup-link.rules" As I'm setting up some automation which will use the official CentOS 7 AMI, I'm wondering whether to switch on the new naming scheme manually and pre-empt the switch over or wait until the official AMIs switch over. Also, will the next CentOS 7 AMI start using NetworkManager instead of the traditional ifcfg-* scripts? Regards, Jinesh

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt November 2016