virt

virt@lists.centos.org

1612 discussions

Installing support for q35 chipset
by admin＠siegel-tech.net 25 Jun '18

25 Jun '18

Hello I have recently had to reinstall Centos 7.5 to on host computer. I have not be able to set-up qemu to support the q35 chip set. I have several virtual machines that require q35. This is not my first install, I have configured libvirt on many machines in the past, it just worked, it has not required any manual configuration. [root@sj aadmin]# /usr/libexec/qemu-kvm -machine help Supported machines are: none empty machine pc RHEL 7.0.0 PC (i440FX + PIIX, 1996) (alias of pc-i440fx-rhel7.0.0) pc-i440fx-rhel7.0.0 RHEL 7.0.0 PC (i440FX + PIIX, 1996) (default) rhel6.6.0 RHEL 6.6.0 PC rhel6.5.0 RHEL 6.5.0 PC rhel6.4.0 RHEL 6.4.0 PC rhel6.3.0 RHEL 6.3.0 PC rhel6.2.0 RHEL 6.2.0 PC rhel6.1.0 RHEL 6.1.0 PC rhel6.0.0 RHEL 6.0.0 PC I have add the jenkins repository. and installed the following packages, OVMF.noarch 20171011-4.git92d07e48907f.el7 @base edk2.git.x86_64 0-20180612.181.g2aedaaef8a @qemu-firmware-jenkins edk2.git-aarch64.noarch 0-20180612.181.g2aedaaef8a @qemu-firmware-jenkins edk2.git-arm.noarch 0-20180612.181.g2aedaaef8a @qemu-firmware-jenkins edk2.git-ovmf-x64.noarch 0-20180612.181.g2aedaaef8a @qemu-firmware-jenkins edk2.git-tools.x86_64 0-20180612.181.g2aedaaef8a @qemu-firmware-jenkins coreboot.git.x86_64 4.8-599.333.g1bf411c743 @qemu-firmware-jenkins coreboot.git-tools.x86_64 4.8-599.333.g1bf411c743 @qemu-firmware-jenkins qemu-common.x86_64 2:2.0.0-1.el7.6 @epel qemu-guest-agent.x86_64 10:2.8.0-2.el7 @anaconda qemu-img.x86_64 10:1.5.3-156.el7_5.2 @updates qemu-kvm.x86_64 10:1.5.3-156.el7_5.2 @updates qemu-kvm-common.x86_64 10:1.5.3-156.el7_5.2 @updates qemu-kvm-tools.x86_64 10:1.5.3-156.el7_5.2 @updates qemu-system-alpha.x86_64 2:2.0.0-1.el7.6 @epel qemu-system-arm.x86_64 2:2.0.0-1.el7.6 @epel qemu-system-cris.x86_64 2:2.0.0-1.el7.6 @epel qemu-system-lm32.x86_64 2:2.0.0-1.el7.6 @epel qemu-system-m68k.x86_64 2:2.0.0-1.el7.6 @epel qemu-system-microblaze.x86_64 2:2.0.0-1.el7.6 @epel qemu-system-mips.x86_64 2:2.0.0-1.el7.6 @epel qemu-system-moxie.x86_64 2:2.0.0-1.el7.6 @epel qemu-system-or32.x86_64 2:2.0.0-1.el7.6 @epel qemu-system-s390x.x86_64 2:2.0.0-1.el7.6 @epel qemu-system-sh4.x86_64 2:2.0.0-1.el7.6 @epel qemu-system-unicore32.x86_64 2:2.0.0-1.el7.6 @epel qemu-system-x86.x86_64 2:2.0.0-1.el7.6 @epel qemu-system-xtensa.x86_64 2:2.0.0-1.el7.6 @epel qemu-user.x86_64 2:2.0.0-1.el7.6 @epel seabios.git.x86_64 1.11.0-40.27.gd9a8b86 @qemu-firmware-jenkins I have installed the Virtualization Host group. Configured the nvram in the /etc/libvirt/qemu.conf, I even used the same copy from a previous installation. nvram = [ "/usr/share/OVMF/OVMF_CODE.secboot.fd:/usr/share/OVMF/OVMF_VARS.fd", "/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd:/usr/share/edk2.git/ovmf-x64/OVMF_VARS-pure-efi.fd" ] Thank you Aaron

1 1

Re: [CentOS-virt] Q: how can I request to add an upstream patch to resolve a core dump issue?
by Xiong, Huan 25 Jun '18

25 Jun '18

UPDATE: It turned out QEMU still dumped core with that patch applied. That said, I'm still interested to know how to report issues with QEMU from centos-virt repo. Thanks, Ray > -----Original Message----- > From: Xiong, Huan > Sent: 2018年6月22日 11:12 > To: 'centos-virt(a)centos.org' <centos-virt(a)centos.org> > Subject: Q: how can I request to add an upstream patch to resolve a core > dump issue? > > Hi, > > The latest version of QEMU (qemu-kvm-ev-2.10.0-21.el7_5.3.1) from centos- > virt repo doesn't have this patch: > > commit 68a9398261ca38979bbc2b7c89ed5bb044ccc9e6 > Author: linzhecheng <linzhecheng(a)huawei.com> > Date: Tue Nov 28 12:46:56 2017 +0800 > > qemu-thread: fix races on threads that exit very quickly > > I wonder how I can request to add it? I hit a core dump issue repeatedly, > which I believe is fixed by this patch. While I observed it on an aarch64 > machine, I think the issue is common on all arch types. > > I'd like to submit a bug report, but didn't find a category for centos-virt at > https://Bugzilla.redhat.com (I suppose I should file bug against upstream, > right?). The Virt-SIG wiki page seems to be outdated and doesn't contain > information on this. Any suggestions? > > Thanks, > Ray

2 2

Re: [CentOS-virt] Virt SIG meetings
by Sandro Bonazzola 25 Jun '18

25 Jun '18

2018-06-25 4:40 GMT+02:00 George Dunlap <George.Dunlap(a)citrix.com>: > > On Jun 20, 2018, at 9:28 PM, Sandro Bonazzola <sbonazzo(a)redhat.com> > wrote: > > > > Hi, > > is it me showing up at the wrong time or meetings didn't happen in the > past 2 rounds? > > I see one scheduled for next week, June 26th, 15:00 UTC. Will it happen? > > I’m in China, at a conference at the moment, so I may not be able to > attend. But Anthony should be around to share stuff from the Xen side. > Would you (Sandro) be willing to chair the session? > Yes, i can chair it > > The one two weeks ago, I think I just got caught up in something and > forgot; sorry. If you remember please feel free to ping me on IRC if I > haven’t brought it up. :-) > Ok :-) > > -George > > -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

Q: how can I request to add an upstream patch to resolve a core dump issue?
by Xiong, Huan 22 Jun '18

22 Jun '18

Hi, The latest version of QEMU (qemu-kvm-ev-2.10.0-21.el7_5.3.1) from centos-virt repo doesn't have this patch: commit 68a9398261ca38979bbc2b7c89ed5bb044ccc9e6 Author: linzhecheng <linzhecheng(a)huawei.com> Date: Tue Nov 28 12:46:56 2017 +0800 qemu-thread: fix races on threads that exit very quickly I wonder how I can request to add it? I hit a core dump issue repeatedly, which I believe is fixed by this patch. While I observed it on an aarch64 machine, I think the issue is common on all arch types. I'd like to submit a bug report, but didn't find a category for centos-virt at https://Bugzilla.redhat.com (I suppose I should file bug against upstream, right?). The Virt-SIG wiki page seems to be outdated and doesn't contain information on this. Any suggestions? Thanks, Ray

1 0

Virt SIG meetings
by Sandro Bonazzola 20 Jun '18

20 Jun '18

Hi, is it me showing up at the wrong time or meetings didn't happen in the past 2 rounds? I see one scheduled for next week, June 26th, 15:00 UTC. Will it happen? Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

Fwd: [CentOS-devel] SIG Day @ CERN, October 18th
by Sandro Bonazzola 20 Jun '18

20 Jun '18

Hi, Who's going to the SIG meetings for Virtualization SIG? ---------- Forwarded message ---------- From: Rich Bowen <rbowen(a)redhat.com> Date: 2018-06-06 20:12 GMT+02:00 Subject: [CentOS-devel] SIG Day @ CERN, October 18th To: "The CentOS developers mailing list." <centos-devel(a)centos.org> Dear SIG members, As you've no doubt seen, we have a CentOS Dojo scheduled at CERN on October 19th. CERN has also generously offered us a meeting room on the day before, Thursday, October 18th, for SIG meetings. If your SIG is interested in taking advantage of this opportunity, please contact me with: * SIG Name * Primary contact for coordination * List of those likely to be in attendance Thanks. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166 _______________________________________________ CentOS-devel mailing list CentOS-devel(a)centos.org https://lists.centos.org/mailman/listinfo/centos-devel -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

libvirtd hang on CentOS6 after latest updates
by Karel Hendrych 29 May '18

29 May '18

Hi, I am seeing frequent libvirtd hangs (clients not responding) after last CentOS6-Xen update : libvirt-libs-4.1.0-2.xen46.el6.x86_64 libvirt-daemon-4.1.0-2.xen46.el6.x86_64 libvirt-daemon-driver-network-4.1.0-2.xen46.el6.x86_64 libvirt-daemon-driver-nwfilter-4.1.0-2.xen46.el6.x86_64 libgcc-4.4.7-18.el6_9.2.x86_64 2:qemu-img-0.12.1.2-2.503.el6_9.5.x86_64 libvirt-daemon-driver-storage-core-4.1.0-2.xen46.el6.x86_64 libvirt-daemon-driver-secret-4.1.0-2.xen46.el6.x86_64 libvirt-daemon-driver-interface-4.1.0-2.xen46.el6.x86_64 libvirt-daemon-driver-nodedev-4.1.0-2.xen46.el6.x86_64 10:centos-release-xen-common-8-4.el6.x86_64 xen-licenses-4.6.6-12.el6.x86_64 xen-libs-4.6.6-12.el6.x86_64 libvirt-daemon-driver-libxl-4.1.0-2.xen46.el6.x86_64 libvirt-daemon-driver-xen-4.1.0-2.xen46.el6.x86_64 libvirt-daemon-driver-qemu-4.1.0-2.xen46.el6.x86_64 libvirt-daemon-driver-storage-gluster-4.1.0-2.xen46.el6.x86_64 libvirt-daemon-driver-storage-logical-4.1.0-2.xen46.el6.x86_64 libvirt-daemon-driver-storage-mpath-4.1.0-2.xen46.el6.x86_64 libvirt-daemon-driver-storage-disk-4.1.0-2.xen46.el6.x86_64 libvirt-daemon-driver-storage-scsi-4.1.0-2.xen46.el6.x86_64 libvirt-daemon-driver-storage-iscsi-4.1.0-2.xen46.el6.x86_64 libvirt-daemon-driver-storage-4.1.0-2.xen46.el6.x86_64 libstdc++-4.4.7-18.el6_9.2.x86_64 libvirt-daemon-config-nwfilter-4.1.0-2.xen46.el6.x86_64 libvirt-daemon-config-network-4.1.0-2.xen46.el6.x86_64 libvirt-daemon-driver-lxc-4.1.0-2.xen46.el6.x86_64 libvirt-client-4.1.0-2.xen46.el6.x86_64 linux-firmware-20171215-82.git2451bb22.el6.noarch 12:dhcp-common-4.1.1-53.P1.el6.centos.4.x86_64 12:dhclient-4.1.1-53.P1.el6.centos.4.x86_64 libvirt-4.1.0-2.xen46.el6.x86_64 10:centos-release-xen-46-8-4.el6.x86_64 10:centos-release-xen-44-8-4.el6.x86_64 tzdata-2018e-3.el6.noarch libgomp-4.4.7-18.el6_9.2.x86_64 kernel-4.9.86-30.el6.x86_64 xen-hypervisor-4.6.6-12.el6.x86_64 xen-runtime-4.6.6-12.el6.x86_64 xen-4.6.6-12.el6.x86_64 libvirt-daemon-xen-4.1.0-2.xen46.el6.x86_64 Remedy is to kill -9 libvirtd and start again. Issue can be replicated within few domU starts. Usually libvirtd hangs when domU is bringing up xen drivers or something around udev, like: xen_netfront: Initialising Xen virtual ethernet driver I've been looking into libvirtd strace and debug logs, so far most suspicious in libvirtd debug log is this: libvirtd.log:2018-05-22 08:32:44.760+0000: 25455: debug : udevRemoveOneDevice:1289 : Failed to find device to remove that has udev name '/sys/devices/vif-24-0/net/vif24.0/queues/tx-7' libvirtd.log:2018-05-22 08:32:44.761+0000: 25455: debug : udevRemoveOneDevice:1289 : Failed to find device to remove that has udev name '/sys/devices/vif-24-0/net/vif24.0/queues/tx-6' libvirtd.log:2018-05-22 08:32:44.761+0000: 25455: debug : udevRemoveOneDevice:1289 : Failed to find device to remove that has udev name '/sys/devices/vif-24-0/net/vif24.0/queues/tx-4' libvirtd.log:2018-05-22 08:32:44.762+0000: 25455: debug : udevRemoveOneDevice:1289 : Failed to find device to remove that has udev name '/sys/devices/vif-24-0/net/vif24.0/queues/tx-5' libvirtd.log:2018-05-22 08:32:44.763+0000: 25455: debug : udevRemoveOneDevice:1289 : Failed to find device to remove that has udev name '/sys/devices/vif-24-0/net/vif24.0/queues/tx-2' libvirtd.log:2018-05-22 08:32:44.764+0000: 25455: debug : udevRemoveOneDevice:1289 : Failed to find device to remove that has udev name '/sys/devices/vif-24-0/net/vif24.0/queues/tx-3' libvirtd.log:2018-05-22 08:32:44.765+0000: 25455: debug : udevRemoveOneDevice:1289 : Failed to find device to remove that has udev name '/sys/devices/vif-24-0/net/vif24.0/queues/rx-6' libvirtd.log:2018-05-22 08:32:44.766+0000: 25455: debug : udevRemoveOneDevice:1289 : Failed to find device to remove that has udev name '/sys/devices/vif-24-0/net/vif24.0/queues/rx-5' libvirtd.log:2018-05-22 08:32:44.767+0000: 25455: debug : udevRemoveOneDevice:1289 : Failed to find device to remove that has udev name '/sys/devices/vif-24-0/net/vif24.0/queues/rx-4' libvirtd.log:2018-05-22 08:32:44.767+0000: 25455: debug : udevRemoveOneDevice:1289 : Failed to find device to remove that has udev name '/sys/devices/vif-24-0/net/vif24.0/queues/rx-7' libvirtd.log:2018-05-22 08:32:44.768+0000: 25455: debug : udevRemoveOneDevice:1289 : Failed to find device to remove that has udev name '/sys/devices/vif-24-0/net/vif24.0/queues/rx-2' libvirtd.log:2018-05-22 08:32:44.769+0000: 25455: debug : udevRemoveOneDevice:1289 : Failed to find device to remove that has udev name '/sys/devices/vif-24-0/net/vif24.0/queues/rx-3' I could not get rid of this by reducing amount of driver queues (not sure if that applies to PV) Is someone out there seeing similar issues? Anyone perhaps interested in reviewing full debug log / strace ? Cheers Karel

2 2

cloud-init log to file not enabled in ec2 image oregon ami-5490ed2c (1804_2)
by Steve Dainard 26 May '18

26 May '18

Hello, Looks like the cloud-init log settings that write out to /var/log/cloud-init-output.log have been removed in 1804_2, wondering if this was a mistake or if there was a reason for this? Thanks, Steve

1 0

Re: [CentOS-virt] CESA-2018:1655 Important: qemu-kvm-ev security update
by Sandro Bonazzola 24 May '18

24 May '18

2018-05-24 13:38 GMT+02:00 Karanbir Singh <kbsingh(a)redhat.com>: > On 24/05/18 11:53, Karanbir Singh wrote: > > On 24/05/18 11:18, Sandro Bonazzola wrote: > >> > >> > >> 2018-05-24 3:18 GMT+02:00 Karanbir Singh <kbsingh(a)redhat.com > >> <mailto:kbsingh@redhat.com>>: > >> > >> On 23/05/18 06:56, Sandro Bonazzola wrote: > >> > CentOS Errata and Security Advisory 2018:1655 Important > >> > > >> > Upstream details at: https://access.redhat.com/ > errata/RHSA-2018:1655 > >> <https://access.redhat.com/errata/RHSA-2018:1655> > >> > > >> > This is the qemu-kvm-ev side of the CVE-2018-3639 mitigation. > >> > > >> > qemu-kvm-ev-2.10.0-21.el7_5.3.1 > >> > <http://cbs.centos.org/koji/buildinfo?buildID=22813 > >> <http://cbs.centos.org/koji/buildinfo?buildID=22813>> has been > >> tagged for > >> > release yesterday morning and should land on mirrors this morning. > >> > Johnny, Brian, Karanbir, please cross check it's being published, > I > >> > would have expected it to be already on mirrors. > >> > > >> > Thanks, > >> > -- > >> > > >> > SANDRO BONAZZOLA > >> > > >> > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION > R&D > >> > > >> > Red Hat EMEA <https://www.redhat.com/> > >> > > >> > sbonazzo(a)redhat.com <mailto:sbonazzo@redhat.com> > >> <mailto:sbonazzo@redhat.com <mailto:sbonazzo@redhat.com>> > >> > > >> > <https://red.ht/sig> > >> > <https://redhat.com/summit> > >> > > >> > >> With all the noise around this specific package, i went and looked > and > >> its in the queue for push, should be in the packages for Thu 24th > >> > >> > >> Looks like it's not yet published. > >> Also altarch is still broken https://bugs.centos.org/view.php?id=14835 > >> > >> > >> > >> > >> > > > > yeah, this is down to how the various arch bits were pushed out of sync; > > we got cut both ways, either if we do x86_64 on its own or we dont, > > > > i am working on sig content right now, so let me go look at this as well > > > > > > the sign runs are now running cleanly for altarch as well, it looks like > the mirrors caught up in sync with those in the last day or so. its > going to run for a bit though, I'll keep an eye on things. > > w.r.t the CVE note - just want to point out that I've been told that > lacking the vendor supplied microcode this fix's in this code do not > really help much. And there is no vendor microcode as yet. Is that an > accurate state of play ? > AFAIK Intel released a beta microcode to OEMs so individual hardware vendors should be providing it through their support pages after testing with their hardware. > > > -- > Karanbir Singh <kbsingh(a)redhat.com> | London, UK > Project Lead, The CentOS Project > Consulting Engineer, https://openshift.io/ > > -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 0

Re: [CentOS-virt] CESA-2018:1655 Important: qemu-kvm-ev security update
by Sandro Bonazzola 24 May '18

24 May '18

2018-05-24 3:18 GMT+02:00 Karanbir Singh <kbsingh(a)redhat.com>: > On 23/05/18 06:56, Sandro Bonazzola wrote: > > CentOS Errata and Security Advisory 2018:1655 Important > > > > Upstream details at: https://access.redhat.com/errata/RHSA-2018:1655 > > > > This is the qemu-kvm-ev side of the CVE-2018-3639 mitigation. > > > > qemu-kvm-ev-2.10.0-21.el7_5.3.1 > > <http://cbs.centos.org/koji/buildinfo?buildID=22813> has been tagged for > > release yesterday morning and should land on mirrors this morning. > > Johnny, Brian, Karanbir, please cross check it's being published, I > > would have expected it to be already on mirrors. > > > > Thanks, > > -- > > > > SANDRO BONAZZOLA > > > > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > > > > Red Hat EMEA <https://www.redhat.com/> > > > > sbonazzo(a)redhat.com <mailto:sbonazzo@redhat.com> > > > > <https://red.ht/sig> > > <https://redhat.com/summit> > > > > With all the noise around this specific package, i went and looked and > its in the queue for push, should be in the packages for Thu 24th > Looks like it's not yet published. Also altarch is still broken https://bugs.centos.org/view.php?id=14835 > > > -- > Karanbir Singh <kbsingh(a)redhat.com> | London, UK > Project Lead, The CentOS Project > Consulting Engineer, https://openshift.io/ > > -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 0

← Newer
1
...
7
8
9
10
11
12
13
...
162
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt