virt

virt@lists.centos.org

1610 discussions

Official CentOS 8 images.
by Richard Beauchamp 21 Oct '19

21 Oct '19

Hi, A few searches didn't find an answer so hoping this group can provide some clues. Looking to find out if there is a timeline/plans to get the official images for CentOS 8 up, both AMIs on Amazon Marketplace and qcow2 on https://cloud.centos.org/. I can build myself, but would prefer to rely on the official source, it's been very helpful resource for my projects so far. Happy to help out if things are tied up on time/resources... Thanks, Richard

1 0

Re: [CentOS-virt] [EXTERNAL] Re: AMI for CentOS 8 and 7.7
by Todd H. Poole 11 Oct '19

11 Oct '19

Hi all, Any update on when the official CentOS 8 AMI will be released? A few projects (ZFS[1] being the highest profile one) are currently blocked from shipping RHEL 8 and CentOS 8 RPMs because their build and test pipelines are waiting on an official CentOS 8 AMI to hit the marketplace[2]. [1]https://github.com/zfsonlinux/zfs/issues/9287#issuecomment-537999796 [2] https://aws.amazon.com/marketplace/seller-profile?id=16cb8b03-256e-4dde-8f3… Sincerely, Todd

1 0

AMI for CentOS 8 and 7.7
by Nils Meyer 03 Oct '19

03 Oct '19

Hi centos-virt, I hope I picked the correct mailing list. I was wondering whether there is a plan to get CentOS 8 and perhaps 7.7 AMI for use with AWS. Is there something I can do to help this process along? I can probably offer an AWS account with some funds. Or if there is any information out there on how the previous AMI were created I might be able to adapt it for CentOS 8. Thank you - Nils -- Nils Meyer - IT Consulting Bergkoppelweg 8, 22335 Hamburg E-Mail: nils(a)nm.cx UST Id: DE256495282 PGP Key Fingerprint DD56 65D0 A3FB 5E6B B98D F66E 5F12 ABF5 D8FE 47DF https://nm.cx/nils@nm.cx.asc https://www.xing.com/profile/Nils_Meyer7

3 3

oVirt conference 2019 - Rome - October 4th
by Sandro Bonazzola 16 Sep '19

16 Sep '19

The oVirt Italian community <https://www.facebook.com/groups/ovirt.italia/> and Extraordy <https://www.extraordy.com/> in collaboration with Red Hat <https://www.redhat.com/>, Oracle <https://www.oracle.com/>, and Storware <https://storware.eu/> are pleased to invite you at oVirt Conference 2019 in Rome on October 4th 2019! Tickets are available for free at https://www.eventbrite.it/e/biglietti-ovirt-conference-2019-innovate-the-da… oVirt is part of CentOS Virtualization SIG, it will be an occasion to get in touch with the upstream community. Thanks -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

live migration issues after libvirtd restart
by Oleksandr Panchuk 23 Aug '19

23 Aug '19

Hi, All There is following issue in latest libvirt-4.5.0-10.el7_6.12 package, which could prevent live VM migrations with web sockets enabled, when libvirtd were restarted prior to migration. Environment: # uname -a Linux inv-cp1-hv3-centos7 3.10.0-957.12.2.el7.x86_64 #1 SMP Tue May 14 21:24:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/redhat-release CentOS Linux release 7.6.1810 (Core) # rpm -qa | grep libvirt-4 libvirt-4.5.0-10.el7_6.12.x86_64 # rpm -qa | grep qemu-kvm qemu-kvm-common-ev-2.12.0-18.el7_6.5.1.x86_64 qemu-kvm-ev-2.12.0-18.el7_6.5.1.x86_64 qemu-kvm-tools-ev-2.12.0-18.el7_6.5.1.x86_64 Repro steps: 1. start VM with following screen configuration: <graphics type="vnc" listen="0.0.0.0" passwd="vnc_password" port="-1" auto-port="yes" websocket="-1"/> 2. check VM XML (migratable): #virsh dumpxml 1 > | grep vnc <graphics type="vnc" listen="0.0.0.0" passwd="vnc_password" port="-1" auto-port="yes" websocket="-1"/> 3. restart libvirtd # systemctl restart libvirtd.service 4. check VM XML config again #virsh dumpxml 1 > | grep vnc <graphics type="vnc" listen="0.0.0.0" passwd="vnc_password" port="-1" auto-port="yes" websocket="5700"/> 5. try to migrate this VM to hypervisor with already running VM and you will get following error error: internal error: Failed to reserve port 5700 It happens when on destination hypervisor there is VM running with web socket port 5700. This issue was fixed since libvirt-4.6.0 release. I've retested it with libvirt-4.9.0 and libvirt-5.0.0 from http://mirror.centos.org/centos/7/virt/x86_64/libvirt-latest/ repo. And it actually fixed here. Interesting to know when newer version of libvirt(at least 4.6.0 of 4.5.0 with fix) will be available in official centos updates repo? Thanks a lot, Oleksandr

2 1

Are XSA-289, XSA-274/CVE-2018-14678 fixed ?
by Yuriy Kohut 01 Jul '19

01 Jul '19

Hello, Are XSA-289 and XSA-274/CVE-2018-14678 fixed with Xen recent 4.8, 4.10 and kernel 4.9.177 packages ? Thank you

2 2

centos7.6 nvme support
by jack.chen 25 Jun '19

25 Jun '19

Hello: I create a centos7.6 virtual machine which use 3.10.0-957 kernel，using pci passthrough to support nvme device； and I found interrupt can not distribute to target CPU which in smp_affinity set，the problem solved when I update kernel to 5.0.20,is anyone can tell me how to solve this problem without updating kernel?? thanks advance!!

2 1

Speculative attack mitigations
by Jonathan Archdale - Blacknight 12 Jun '19

12 Jun '19

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 patches for the various speculative attack mitigations in the current 4.9.177-35 kernel used in the centos-virt tree. For reference; I am running a Dell R620, using an E5-2620 v2 CPU, using 4.9.177-35 from the xen-410 tree in the EL6 branch ; though I am still using xen 4.6 at this time. I have been told in the irc channel that the kernel is not built against a specific version of xen so this should make no odds. As per https://www.dell.com/support/home/ie/en/iebsdt1/drivers/driversdetails?driv… - bios version 2.70 (installed) contains mitigations for CVE-2018-3639 (variant 3a route system register read) and CVE-2018-3640 (variant 4, speculative store bypass). I am also running the latest available intel microcode for the CPU; as imported via 'module /GenuineIntel.bin' and 'ucode=2' in my grub.conf to import (as taken from https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files) # uname -r 4.9.177-35.el6.x86_64 # cat /proc/cmdline ro root=UUID=0e51d8dc-6409-4715-83f4-f86fa24083e2 rd_NO_LUKS KEYBOARDTYPE=pc KEYTABLE=uk LANG=en_US.UTF-8 rd_NO_MD nodmraid SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_NO_LVM rd_NO_DM rhgb quiet intel_idle.max_cstate=0 processor.max_cstate=0 l1ft=full mds=full,nosmt ssbd=force-on # grep -e flags -e "model name" -e microcode -e bugs /proc/cpuinfo | sort -u model name : Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz microcode : 0x42e flags : fpu de tsc msr pae mce cx8 apic sep mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc arch_perfmon rep_good nopl nonstop_tsc pni pclmulqdq monitor est ssse3 cx16 sse4_1 sse4_2 popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm fsgsbase erms xsaveopt dtherm ida arat pln pts bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds You will note that there is a lack of flags for ssbd, spec_ctrl, intel_stibp, flush_l1d, ibrs, etc. # for i in /sys/devices/system/cpu/vulnerabilities/* ; do echo -n "$i : "; cat $i ; done /sys/devices/system/cpu/vulnerabilities/l1tf : Mitigation: PTE Inversion /sys/devices/system/cpu/vulnerabilities/mds : Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown /sys/devices/system/cpu/vulnerabilities/meltdown : Vulnerable /sys/devices/system/cpu/vulnerabilities/spec_store_bypass : Vulnerable /sys/devices/system/cpu/vulnerabilities/spectre_v1 : Mitigation: __user pointer sanitization /sys/devices/system/cpu/vulnerabilities/spectre_v2 : Mitigation: Full generic retpoline, STIBP: disabled, RSB filling Despite having relevant microcode, I am still seeing the box as showing vulnerable to meltdown, speculative store bypass (ssbd), as well as MDS via MD_CLEAR mitigation. When I mount the debugfs, the flag for ibrs is missing - preventing me enabling it as a mitigation for ssbd (due to lack of relevant cpu flag): # mount -t debugfs none /sys/kernel/debug/ # ls -lahtr /sys/kernel/debug/x86/ibrs_enabled ls: cannot access /sys/kernel/debug/x86/ibrs_enabled: No such file or directory I have other R620's with the same CPUs running stock el6 kernels that are showing as fully patched to these issues. Could I please get some feedback from whoever builds out the kernels; if the mitigations/patches are in place in the 4.9.177-35 kernel for the various speculative mitigations? Specifically; CVE-2018-3639, CVE-2018-3640, CVE-2018-3646, CVE-2018-12126, CVE-2018-12130, CVE-2018-12127 and CVE-2019-11091. Many thanks for your response. Regards, Jonathan

2 1

CentOS 7 Xen 4.12 libvirt/virt-manager wrong path for qemu-system-i386
by Pasi Kärkkäinen 27 May '19

27 May '19

Hello, While testing Virt-SIG Xen 4.12 rpms on CentOS7 I noticed the following problem with libvirt/virt-manager when manually installing a new HVM guest from virt-manager GUI.. basicly the VM installation won't start, because libvirt/virt-manager is not able to start the VM, due to "missing" qemu-system-i386 binary: Unable to complete install: 'unsupported configuration: emulator '/usr/lib/xen/bin/qemu-system-i386' not found' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 2553, in _do_async_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 498, in start_install doboot, transient) File "/usr/share/virt-manager/virtinst/guest.py", line 434, in _create_guest domain = self.conn.createXML(install_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3725, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirtError: unsupported configuration: emulator '/usr/lib/xen/bin/qemu-system-i386' not found Quick'n'dirty fix is to create a symlink: ln -s /usr/lib64/xen/bin/qemu-system-i386 /usr/lib/xen/bin/qemu-system-i386 .. after creating that symlink the VM can be started just fine and works OK. We need to fix that default directory path for qemu-system-i386 to be correct out-of-the-box.. Thanks, -- Pasi

2 3

centos-virt CPU microcode updates?
by Karel Hendrych 16 May '19

16 May '19

Hi, is there any guide for CPU microcode updates on CentOS6, Xen 4.10, kernel 4.9 ? Thanks Karel

3 3

← Newer
1
2
3
4
5
6
7
8
9
...
161
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt