similar to: CVE-2018-3639 qemu-kvm-ev-2.10.0-21.el7_5.4.1 is now available for testing

Hi all, as per subject, when a Windows guest using a Spice display is rebooted with a planned chkdsk, the consistency check is always skipped. It seems that the Spice display issues some "phantom" keystrokes, which are then intended by Windows as the "skip chkdsk at boot" signal. I tried to use a Spice display with no additional features (ie: USB redirection), but to no

On 19/10/2018 08:13, Gionatan Danti wrote: > Il 17-10-2018 09:15 Gionatan Danti ha scritto: >> Hi all, >> as per subject, when a Windows guest using a Spice display is rebooted >> with a planned chkdsk, the consistency check is always skipped. >> >> It seems that the Spice display issues some "phantom" keystrokes, >> which are then intended by

Il 17-10-2018 09:15 Gionatan Danti ha scritto: > Hi all, > as per subject, when a Windows guest using a Spice display is rebooted > with a planned chkdsk, the consistency check is always skipped. > > It seems that the Spice display issues some "phantom" keystrokes, > which are then intended by Windows as the "skip chkdsk at boot" > signal. > > I

CentOS Errata and Security Advisory 2018:1396 Low Upstream details at : https://access.redhat.com/errata/RHSA-2018:1396 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 9f9ad22755911ec809e885c80cd5b1441c43dc799bb54051be879331e7876eae libvirt-3.9.0-14.el7_5.4.x86_64.rpm

CentOS Errata and Bugfix Advisory 2018:1375 Upstream details at : https://access.redhat.com/errata/RHBA-2018:1375 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: e1d3e1d14aff3039268b7e988bdccb6d008d8e029fe30aa47ac30f37d5b9e748 rsyslog-8.24.0-16.el7_5.4.x86_64.rpm

CentOS Errata and Bugfix Advisory 2018:2004 Upstream details at : https://access.redhat.com/errata/RHBA-2018:2004 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: c6aeeb4cda6936df7be422eab0b9354004412c9f5ad69acf38ad3c042cb83af6 selinux-policy-3.13.1-192.el7_5.4.noarch.rpm

Hi folks, Firstly; apologies in advance for what is a head wrecker of keeping on top of the speculative mitigations and also if this is a duplicate email; my first copy didn't seem to make it into the archive. Also a disclaimer that I may have misunderstood elements of the below but please bear with me. I write this hoping to find out a bit more about the state of the relevant kernel

2018-05-24 13:38 GMT+02:00 Karanbir Singh <kbsingh at 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 at redhat.com > >> <mailto:kbsingh at redhat.com>>: > >> > >> On 23/05/18 06:56, Sandro

2018-05-24 3:18 GMT+02:00 Karanbir Singh <kbsingh at 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. > > > >

On Mon, Sep 14, 2020 at 8:42 AM Yedidyah Bar David <didi@redhat.com> wrote: > > On Mon, Sep 14, 2020 at 12:28 AM wodel youchi <wodel.youchi@gmail.com> wrote: > > > > Hi, > > > > Thanks for the help, I think I found the solution using this link : https://www.berrange.com/posts/2018/06/29/cpu-model-configuration-for-qemu-kvm-on-x86-hosts/ > > > >

CentOS Errata and Bugfix Advisory 2018:2005 Upstream details at : https://access.redhat.com/errata/RHBA-2018:2005 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 6242a85af5ed59c2ccdbd84bf879042d896e94d073020da1a93aadd268eee0ec spice-server-0.14.0-2.el7_5.4.x86_64.rpm

Hi, I have a KVM server running on Centos 7.5. [root at kvm2 ~]# cat /etc/redhat-release CentOS Linux release 7.5.1804 (Core) Qemu packages are from Centos repository. [root at kvm2 ~]# rpm -qa|grep qemu libvirt-daemon-driver-qemu-3.9.0-14.el7_5.7.x86_64 qemu-img-1.5.3-156.el7_5.5.x86_64 qemu-kvm-common-1.5.3-156.el7_5.5.x86_64 ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch

CentOS Errata and Bugfix Advisory 2018:1391 Upstream details at : https://access.redhat.com/errata/RHBA-2018:1391 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 7445111d2f078d2a8d3625f87a4d0c2d9d08ec972c2cd5fe4e84d41ceeabfd86 radvd-1.9.2-9.el7_5.4.x86_64.rpm Source:

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

Hi, According to virsh capabilities I only have the following cpu features: <cpu> <arch>x86_64</arch> <model>IvyBridge-IBRS</model> <vendor>Intel</vendor> <microcode version='32'/> <topology sockets='1' cores='4' threads='1'/> <feature name='ds'/>

2018-05-15 14:16 GMT+02:00 Sandro Bonazzola <sbonazzo at redhat.com>: > > > 2018-05-15 13:53 GMT+02:00 Nerijus Baliunas <nerijus at users.sourceforge.net > >: > >> On Tue, 15 May 2018 14:45:23 +0300 Gena Makhomed <gmm at csdoc.com> wrote: >> >> > >> Something wrong with $contentdir variable, >> > >> it points to altarch

I am using nested virtualization on a Google Cloud Compute instance. Things are generally working fine with libvirt using qemu+kvm, however I observed that <cpu mode='host-model'> is not exposing avx and avx2 instruction set to the guest Linux instance. Google Cloud platform claims the CPU model of the host compute instance is Broadwell, however libvirt capabilities maps it to

Hi Daniel, I have noticed that it will fail exactly as you said if <cdrom> is first in the boot order, if <hd> is first in the boot order the XML validates and it starts as usual. first in log except below is with cdrom set to first in boot order, second is with hd set first. 2018-08-09 11:39:28.625+0000: starting up libvirt version: 3.9.0, package: 14.el7_5.6 (CentOS BuildSystem

2017-12-11 18:11 GMT+01:00 Markus Stockhausen <stockhausen at collogia.de>: > Hi Sandro, > > I'm wondering if BZ1513362 (AIO stuck fixed in qemu-kvm-rhev-2.9.0-16.el7_ > 4.12) > will be worth to give the newer version a try. > Above version is not yet released, can't see it on ftp://ftp.redhat.com/pub/redhat/linux/enterprise/7Server/en/RHEV/SRPMS/ > >

2018-05-15 14:39 GMT+02:00 Nerijus Baliunas <nerijus at users.sourceforge.net>: > On Tue, 15 May 2018 14:18:08 +0200 Sandro Bonazzola <sbonazzo at redhat.com> > wrote: > > > >> I have freshly installed CentOS 7.5 on a Dell server, and > > >> /etc/yum/vars/contentdir > > >> contains 'altarch' too. CentOS 7.4->7.5 upgraded servers