virt April 2016

virt@lists.centos.org

20 participants
32 discussions

Out of Office. (was: Out of Office. (was: Out of Office. (was: Problems with scsi-target-utils when hosted on dom0 centos 7 xen box)))
by Steve Clark 13 Apr '16

13 Apr '16

1 0

Out of Office. (was: Out of Office. (was: Problems with scsi-target-utils when hosted on dom0 centos 7 xen box))
by Steve Clark 13 Apr '16

13 Apr '16

1 0

Out of Office. (was: Problems with scsi-target-utils when hosted on dom0 centos 7 xen box)
by Steve Clark 13 Apr '16

13 Apr '16

1 0

CentOS7, Xen 4.6.1, kernel 3.18.25-19 strange performance problem
by T.Weyergraf 11 Apr '16

11 Apr '16

Hi all, i just stumbled over a strange performance issue with my Xen setup. I use centos-virt Xen since a long time on my workstation and usually never check performance. However, yesterday I booted into the 3.18.25-19 Dom0 kernel *without* Xen and found the system noticably more responsive. That triggered me into running a simple kernel compile benchmark and compare the results: Testsequence: echo 3 > /proc/sys/vm/drop_caches make distclean cp ../.config . #copies an existing valid config for compile make oldconfig time make -j <threads> bzImage Results: xen 4.6.1 - kernel 3.18.25-19 16 threads: real 1m41.983s user 16m37.247s sys 5m7.121s 32 threads: real 1m29.240s user 23m7.170s sys 6m31.497s kernel 3.18.25-19 16 threads: real 1m12.909s user 14m37.627s sys 1m36.521s 32 threads: real 1m0.530s user 18m45.569s sys 1m58.807s Some notes: - System is a HP z840 with 2*8core E5 v3 Xeon and 128gig Ram. Disk is an Intel 750 ssd (PCIe nvme) - While normally in Xen, I limit Dom0 Memory via dom0_mem, but for the tests, Dom0 was allowed to use full memory - While running the test, no guest was running except Dom0. System was booted to graphical desktop and was completely unloaded otherwise - (boot-)logs showed no issues with ACPI or hardware-support or whatsoever. I have not yet run any in-depth investigation or tried too many different settings, but I find the differences quite noteworthy. So, if anybody came across the same issues, has some hints or suggestions, feel free. I'll continue poking around and if there is interest, i'll post updates. Regards, Thomas

2 2

systemd-nspawn will replace lxc
by C. L. Martinez 11 Apr '16

11 Apr '16

Hi all, It seems RH will deprecate LXC (https://access.redhat.com/articles/1365153) and will go to docker way (or maybe I am totally wrong). Is this true?? Will be systemd-nspawn a lightweight replacement for LXC containers?? Thanks. -- Greetings, C. L. Martinez

1 0

(qemu-kvm-ev) parallel port forwarding to guest VM
by Subscriber 11 Apr '16

11 Apr '16

Hi Where can I find information on supported devices in qemu-kvm-ev? Does it support parallel port forwarding to the guest VM? Thx. P.S. cat /etc/redhat-release CentOS Linux release 7.2.1511 (Core)

2 1

High Guest CPU Utilization when using libgfapi
by qingwei wei 11 Apr '16

11 Apr '16

Hi, I am currently testing running Openstack instance on Cinder volume with libgfapi. This instance is the Windows instance and i found that when running random 4k write workload, the CPU utilization is very high, 90% CPU utilization with about 86% in privileged time. I also tested the workload with volume from NFS and the CPU utilization is only around 5%. For gluster fuse, the CPU utilization is also not as high as 90%, around 30-40%. Is there any reason why is that so? Appreciate on any comments and suggestions. Details. Workload generator: IOMeter Instance: Windows 2008R2 Openstack Host: CentOS 7 qemu-kvm version: qemu-kvm-ev-2.1.2-23.el7.1.x86_64 Workload: 4kb random write, 4 workers with each worker configure to have 4 outstanding IOs Gluster server and client version: 3.7.8 Gluster info Volume Name: g37test Type: Distribute Volume ID: 27947421-111b-4727-bcaf-bafe73debe07 Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 192.168.99.4:/mnt/ssd/g37test Options Reconfigured: performance.readdir-ahead: on nfs.disable: true performance.io-cache: off performance.quick-read: off server.allow-insecure: on storage.owner-uid: 165 storage.owner-gid: 165 Cw

1 0

CentOS 6
by Gene 08 Apr '16

08 Apr '16

Will Xen4Centos on CentOS 6 be supported all the way through its EOL (November 30th, 2020)? If not when will it stop being supported/updated under this SIG? Thanks. -Gene

2 1

New qemu-kvm-ev available for testing
by Sandro Bonazzola 08 Apr '16

08 Apr '16

Hi, qemu-kvm-ev-2.3.0-31.el7_2.10.1 has been tagged for testing. In order to test it, please enable centos-qemu-ev-test repository after installing centos-release-qemu-ev Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 2

xen-4.4.4-2.el6 packages added to virt6-xen-44-testing
by Johnny Hughes 07 Apr '16

07 Apr '16

All, I have upgraded xen-44 from Xen-4.4.3 to Xen-4.4.4 (and placed the resulting RPMs from xen-4.4.4-2.el6.src.rpm into virt6-xen-44-testing). These RPMs have all the latest updates that were rolled into the xen-4.4.3-14.el6.src.rpm packages (through XSA-172 updates). Here is how to test: 1. If you want this box to always have 'testing' enabled for xen-44 .. do this: Edit /etc/yum.repos.d/CentOS-Xen-44.repo and set 'Enabled=1' in the [centos-virt-xen-44-testing] and then do: yum update (In this case, the testing repo remains enabled) 2. If you would rather not turn on testing permanently, but just want to test these updates (and leave only the main repo enabled by default), then do this: yum --enablerepo centos-virt-xen-44-testing update ============== The above assumes you have followed George's instructions and have removed centos-release-xen and centos-rtelease-xen-46 and have installed centos-release-xen-44 to stay on the Xen-4.4 branch, and have not upgraded to Xen-4.6. Thanks, Johnny Hughes

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt April 2016