virt March 2017

virt@lists.centos.org

25 participants
16 discussions

Red Hat VirtIO SCSI pass-through controller
by Gena Makhomed 15 Mar '17

15 Mar '17

Hello, All! virtio-win.iso contains two different Windows drivers. these Windows Server 2012 R2 drivers have different hardware IDs: \vioscsi\2k12R2\amd64\vioscsi.inf "Red Hat VirtIO SCSI pass-through controller" PCI\VEN_1AF4&DEV_1004&SUBSYS_00081AF4&REV_00 PCI\VEN_1AF4&DEV_1048&SUBSYS_11001AF4&REV_01 \viostor\2k12R2\amd64\viostor.inf "Red Hat VirtIO SCSI controller" PCI\VEN_1AF4&DEV_1001&SUBSYS_00021AF4&REV_00 PCI\VEN_1AF4&DEV_1042&SUBSYS_11001AF4&REV_01 When I use "VirtIO SCSI controller" in virt-manager, and when I install Windows Server 2012 R2 - I can use only viostor driver and can't use vioscsi driver, Windows Server 2012 R2 can't load vioscsi driver (?) from virtio-win.iso and did not see virtual hard disks with vioscsi driver. Only viostor driver work normally. How I can use "Red Hat VirtIO SCSI pass-through controller" for Windows Server 2012 R2 virtual machine, what I need to configure in xml-config? current /etc/libvirt/qemu/windows.xml config: <controller type='scsi' index='0' model='virtio-scsi'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none' io='native' discard='unmap'/> <source file='/volume/kvm-windows-system'/> <target dev='vda' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </disk> Additional info: ================ virtio-win.iso version: virtio-win-0.1.126.iso from https://fedoraproject.org/wiki/Windows_Virtio_Drivers OS: CentOS Linux release 7.3.1611 (Core) QEMU: qemu-kvm-1.5.3-126.el7_3.5.x86_64 Windows Server 2012 R2 MSDN installation ISO image: en_windows_server_2012_r2_with_update_x64_dvd_6052708.iso sha1sum: 865494e969704be1c4496d8614314361d025775e size: 5397889024 bytes devcon.exe output inside Windows Server 2012 R2 Virtual Machine: PCI\VEN_1AF4&DEV_1001&SUBSYS_00021AF4&REV_00\3&13C0B0C5&0&40 Name: Red Hat VirtIO SCSI controller Hardware IDs: PCI\VEN_1AF4&DEV_1001&SUBSYS_00021AF4&REV_00 PCI\VEN_1AF4&DEV_1001&SUBSYS_00021AF4 PCI\VEN_1AF4&DEV_1001&CC_010000 PCI\VEN_1AF4&DEV_1001&CC_0100 Compatible IDs: PCI\VEN_1AF4&DEV_1001&REV_00 PCI\VEN_1AF4&DEV_1001 PCI\VEN_1AF4&CC_010000 PCI\VEN_1AF4&CC_0100 PCI\VEN_1AF4 PCI\CC_010000 PCI\CC_0100 PCI\VEN_1AF4&DEV_1001&SUBSYS_00021AF4&REV_00\3&13C0B0C5&0&50 Name: Red Hat VirtIO SCSI controller Hardware IDs: PCI\VEN_1AF4&DEV_1001&SUBSYS_00021AF4&REV_00 PCI\VEN_1AF4&DEV_1001&SUBSYS_00021AF4 PCI\VEN_1AF4&DEV_1001&CC_010000 PCI\VEN_1AF4&DEV_1001&CC_0100 Compatible IDs: PCI\VEN_1AF4&DEV_1001&REV_00 PCI\VEN_1AF4&DEV_1001 PCI\VEN_1AF4&CC_010000 PCI\VEN_1AF4&CC_0100 PCI\VEN_1AF4 PCI\CC_010000 PCI\CC_0100 PCI\VEN_1AF4&DEV_1004&SUBSYS_00081AF4&REV_00\3&13C0B0C5&0&38 Name: Red Hat VirtIO SCSI controller Hardware IDs: PCI\VEN_1AF4&DEV_1004&SUBSYS_00081AF4&REV_00 PCI\VEN_1AF4&DEV_1004&SUBSYS_00081AF4 PCI\VEN_1AF4&DEV_1004&CC_010000 PCI\VEN_1AF4&DEV_1004&CC_0100 Compatible IDs: PCI\VEN_1AF4&DEV_1004&REV_00 PCI\VEN_1AF4&DEV_1004 PCI\VEN_1AF4&CC_010000 PCI\VEN_1AF4&CC_0100 PCI\VEN_1AF4 PCI\CC_010000 PCI\CC_0100 -- Best regards, Gena

2 3

qemu-kvm-ev-2.6.0-28.el7_3.3.1 miss source rpm
by Chen Fan 06 Mar '17

06 Mar '17

Hi, Now I can update the qemu-kvm-ev to the latest version 2.6.0-28.el7_3.3.1 provided by qemu-kvm-ev repo, but I couldn't find the according source package in source repo. was forgot :)? where can I find it? -- Sincerely, Chen Fan

2 2

qemu-kvm-ev-2.6.0-28.el7_3.6.1 now available for testing
by Sandro Bonazzola 02 Mar '17

02 Mar '17

Hi, just pushed to testing a new build of qemu-kvm-ev, here's the ChangeLog: * Thu Mar 2 2017 Sandro Bonazzola <sbonazzo(a)redhat.com> - ev-2.6.0-28.el7_3.6.1 - Removing RH branding from package name * Mon Feb 13 2017 Miroslav Rezanina <mrezanin(a)redhat.com> - rhev-2.6.0-28.el7_3.6 - kvm-cirrus-fix-patterncopy-checks.patch [bz#1420493] - kvm-Revert-cirrus-allow-zero-source-pitch-in-pattern-fil.patch [bz#1420493] - kvm-cirrus-add-blit_is_unsafe-call-to-cirrus_bitblt_cput.patch [bz#1420493] - Resolves: bz#1420493 (EMBARGOED CVE-2017-2620 qemu-kvm-rhev: Qemu: display: cirrus: potential arbitrary code execution via cirrus_bitblt_cputovideo [rhel-7.3.z]) * Fri Feb 10 2017 Miroslav Rezanina <mrezanin(a)redhat.com> - rhev-2.6.0-28.el7_3.5 - kvm-memory-Provide-memory_region_init_rom.patch [bz#1420456] - kvm-pci-mark-ROMs-read-only.patch [bz#1420456] - kvm-vhost-skip-ROM-sections.patch [bz#1420456] - kvm-display-cirrus-check-vga-bits-per-pixel-bpp-value.patch [bz#1418234] - kvm-display-cirrus-ignore-source-pitch-value-as-needed-i.patch [bz#1418234] - kvm-cirrus-handle-negative-pitch-in-cirrus_invalidate_re.patch [bz#1418234] - kvm-cirrus-allow-zero-source-pitch-in-pattern-fill-rops.patch [bz#1418234] - kvm-cirrus-fix-blit-address-mask-handling.patch [bz#1418234] - kvm-cirrus-fix-oob-access-issue-CVE-2017-2615.patch [bz#1418234] - Resolves: bz#1418234 (CVE-2017-2615 qemu-kvm-rhev: Qemu: display: cirrus: oob access while doing bitblt copy backward mode [rhel-7.3.z]) - Resolves: bz#1420456 ([ppc64le]reset vm when do migration, HMP in src host promp "tcmalloc: large alloc 1073872896 bytes...") * Wed Feb 08 2017 Miroslav Rezanina <mrezanin(a)redhat.com> - rhev-2.6.0-28.el7_3.4 - kvm-Disable-usbredir-and-libcacard-for-unsupported-archi.patch [bz#1420428] - Resolves: bz#1420428 (Remove dependencies required by spice on ppc64le) In order to test it: # yum install centos-release-qemu-ev # yum-config-manager --enable centos-qemu-ev-test # yum install qemu-kvm-ev Or just yum update if you already have qemu-kvm-ev installed and test repository enabled. If you test it, please provide feedback. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

heads-up: required vsyscall=emulate boot option for c5/c6 images on recent kernels
by Tru Huynh 02 Mar '17

02 Mar '17

Hi, If the pristine centos:centos5 centos:centos6 images are not running on your brand new host running another linux distribution, you might be hitting this issue: https://github.com/CentOS/sig-cloud-instance-images/issues/62 https://bugs.alpinelinux.org/issues/6928 Cheers Tru -- Tru Huynh http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

NUMA placement failed, performance might be affected
by Chris Wik 01 Mar '17

01 Mar '17

I just did a yum update on a CentOS 7 / Xen 4.6 server which took me from kernel-3.18.34-20.el7.x86_64 -> kernel-3.18.44-20.el7.x86_64 After rebooting, the following notice is printed immediately upon xl create'ing a domain: libxl: notice: libxl_numa.c:499:libxl__get_numa_candidate: NUMA placement failed, performance might be affected Indeed performance is significantly degraded. This issue didn't happen on the older kernel. Any ideas where it came from or how it can be fixed? # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 63 model name : Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz stepping : 2 microcode : 0x36 cpu MHz : 3500.090 cache size : 15360 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 15 wp : yes 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 eagerfpu pni pclmulqdq monitor est ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm ida arat epb pln pts dtherm fsgsbase bmi1 avx2 bmi2 erms xsaveopt bugs : bogomips : 7000.18 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management: # xl info host : ****.localdomain release : 3.18.44-20.el7.x86_64 version : #1 SMP Tue Oct 25 11:42:52 UTC 2016 machine : x86_64 nr_cpus : 1 max_cpu_id : 15 nr_nodes : 2 cores_per_socket : 1 threads_per_core : 1 cpu_mhz : 3500 hw_caps : bfebfbff:2c100800:00000000:00007f00:77fefbff:00000000:00000021:000037ab virt_caps : hvm hvm_directio total_memory : 130958 free_memory : 28003 sharing_freed_memory : 0 sharing_used_memory : 0 outstanding_claims : 0 free_cpus : 0 xen_major : 4 xen_minor : 6 xen_extra : .3-7.el7 xen_version : 4.6.3-7.el7 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : Wed Feb 15 02:12:22 2017 -0600 git:c359c64-dirty xen_commandline : placeholder dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all cc_compiler : gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-11) cc_compile_by : mockbuild cc_compile_domain : centos.org cc_compile_date : Wed Feb 15 12:18:43 UTC 2017 xend_config_format : 4 Thanks in advance, Chris -- Chris Wik Anu Internet Services www.anu.net | www.cwik.ch

2 2

Xen-4.4 branch End of Life
by Johnny Hughes 01 Mar '17

01 Mar '17

The CentOS VIrtualization Special Interest Group wants to remind everyone that the End of Life for the Xen-4.4 branch (currently 4.4.4-19) will be March 31st, 2017. This is because the Xen Project will no longer support Xen-4.4 after that date, based on this link: https://wiki.xenproject.org/wiki/Xen_Project_Release_Features Xen-4.6 is still available and will be maintained until October 2018 (on both CentOS-6 and CentOS-7) and Xen-4.8 will be available soon. Thanks, Johnny Hughes

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt March 2017