virt

virt@lists.centos.org

1610 discussions

Difference between qemu-kvm-ev and qemu-kvm-ma?
by Lance Albertson 15 May '18

15 May '18

I see with the introduction of CentOS 7.5 there's a new qemu-kvm-ma package on ppc64le (which is actually newer than qemu-kvm-ev currently). Does anyone know what the difference is between these two packages? We currently use qemu-kvm-ev and we've run into this bug [1] which got me wondering if we should be switching to that package on ppc64le. Thanks! [1] https://bugzilla.redhat.com/show_bug.cgi?id=1570533 -- Lance Albertson Director Oregon State University | Open Source Lab

5 14

Xen 4.6.6-9 (with XPTI meltdown mitigation) packages making their way to centos-virt-xen-testing
by George Dunlap 04 May '18

04 May '18

I've built & tagged packages for CentOS 6 and 7 4.6.6-9, with XPTI "stage 1" Meltdown mitigation. This will allow 64-bit PV guests to run safely (with a few caveats), but incurs a fairly significant slowdown for 64-bit PV guests on Intel boxes (including domain 0). If you prefer using Vixen / Comet, you can turn it off by adding 'xpti=0' to your Xen command-line. Detailed information can be found in the XSA-254 advisory: https://xenbits.xen.org/xsa/advisory-254.html Please test and report any issues you have. I'll probably tag then with -release tomorrow. 4.8 packages should be coming to buildlogs soon. -George

7 14

Xen DomU's randomly freezing
by Daz Day 30 Apr '18

30 Apr '18

Hi, I've tried hitting up the CentOS forums and thought I'd try here too as I don't seem to be getting any bites. We've been in the process of migrating all our hypervisors over to CentOS 7 using Xen. Once we had a few up and running we started to notice that the DomU's would randomly freeze. They become unresponsive to any network traffic, stop consuming CPU resources on the hypervisor and it's not possible to log in to the console locally using: virsh console <domain> We can sometimes get as far as typing a username and hitting return, but the DomU just hangs there. It doesn't seem to matter what Linux distro the DomU is running, it affects them all. The only way we can get them back is by destroying and recreating them (far from ideal!). After a bit of research and digging around, we eventually found these 2 nuggets: https://wiki.gentoo.org/wiki/Xen#Xen_domU_hanging_with_kernel_4.3.2B https://www.novell.com/support/kb/doc.php?id=7018590 They both advise adding the command line argument: gnttab_max_frames=256(the default is 32). We applied this change and all hypervisors rand stable for around a week until DomU's started freezing again (we've since tried even higher values, to no avail). More research later led me to https://bugs.centos.org/view.php?id=14258 and https://bugs.centos.org/view.php?id=14284 (which are essentially the same report). There hasn't really been any movement on these tickets unfortunately, but I have +1'd them. Have any others had issues with Xen and DomU's locking up in CentOS 7? Are there any other fixes/workarounds? If any additional info is needed that isn't already in the bug tickets or forum post, please let me know and I'll be happy to provide whatever is required (these freezes are happening at least once a day). Any help would be much appreciated and would mean my Ops guys could get a decent sleep! Cheers Darren

2 1

Proposal to CANCEL: 2018-05-01 Virtualization SIG meeting
by Sandro Bonazzola 25 Apr '18

25 Apr '18

Hi, I'm proposing to cancel next week meeting. It's labor day in many countries including Italy. Thanks, -- 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>

2 1

Contributing Hyper-V/Azure packages
by Stephen Zarkos 24 Apr '18

24 Apr '18

Hi All, I'm interested in contributing to Virt-SIG with packages focused on Hyper-V/Azure support, i.e. kernel packages with additional patches and build configurations tuned for Hyper-V. There are some advantages these packages can bring to CentOS users - - Access to the latest features and fixes - Reduced boot time - Smaller memory footprint Of course all the new features/fixes are already upstream in the mainline kernel, but the aim here would be to backport them for easy consumption. Any questions about this sort of contribution? I'd love to see this happen. Thanks! Steve

2 1

Re: [CentOS-virt] CentOS-virt Digest, Vol 128, Issue 1
by mql 20 Apr '18

20 Apr '18

Scott thanks ever so much for your response - yes that answers the question. Thanks, M > On 20 Apr 2018, at 13:00, centos-virt-request(a)centos.org wrote: > > Send CentOS-virt mailing list submissions to > centos-virt(a)centos.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.centos.org/mailman/listinfo/centos-virt > or, via email, send a message with subject or body 'help' to > centos-virt-request(a)centos.org > > You can reach the person managing the list at > centos-virt-owner(a)centos.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of CentOS-virt digest..." > > > Today's Topics: > > 1. Apparent discontinuity between advertised centos7 release > 1803_01 and content of centos-release file (mql) > 2. Re: Apparent discontinuity between advertised centos7 release > 1803_01 and content of centos-release file (Scott Dowdle) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 19 Apr 2018 18:11:59 +0100 > From: mql <email(a)ej73.com> > To: centos-virt(a)centos.org > Subject: [CentOS-virt] Apparent discontinuity between advertised > centos7 release 1803_01 and content of centos-release file > Message-ID: <A6EFFA5E-4C12-4D8C-8ED3-E64094153E9E(a)ej73.com> > Content-Type: text/plain; charset="us-ascii" > > > > Hello, > > I searched centos7 in the AWS marketplace for the at-time-of-writing-latest centos7 image: https://aws.amazon.com/marketplace/pp/B00O7WM7QW?qid=1524138193326&sr=0-1&r… > > I built a standard free tier t2.micro from this putative 1803_01 AMI. I see from the docs, this is thus a March 2018 compilation. > When I get CLI, I get this: > > [centos@ip-172-31-27-32 etc]$ cat centos-release > CentOS Linux release 7.4.1708 (Core) > > which suggests that the AMI I just launched was built on a version of centos compiled from upstream sources in August 2017. > Does the release of centos7 on the marketplace sport a release version which does not pertain to the machine's release? Unlike with releases published outside AWS, the Centos <https://wiki.centos.org/Cloud/AWS> cloud page does not specify version info as listed on AWS. > > Thanks v much IA, > > M > > > > > > > >

1 0

Apparent discontinuity between advertised centos7 release 1803_01 and content of centos-release file
by mql 19 Apr '18

19 Apr '18

Hello, I searched centos7 in the AWS marketplace for the at-time-of-writing-latest centos7 image: https://aws.amazon.com/marketplace/pp/B00O7WM7QW?qid=1524138193326&sr=0-1&r… I built a standard free tier t2.micro from this putative 1803_01 AMI. I see from the docs, this is thus a March 2018 compilation. When I get CLI, I get this: [centos@ip-172-31-27-32 etc]$ cat centos-release CentOS Linux release 7.4.1708 (Core) which suggests that the AMI I just launched was built on a version of centos compiled from upstream sources in August 2017. Does the release of centos7 on the marketplace sport a release version which does not pertain to the machine's release? Unlike with releases published outside AWS, the Centos <https://wiki.centos.org/Cloud/AWS> cloud page does not specify version info as listed on AWS. Thanks v much IA, M

2 1

Issues with live KVM migration
by Daznis 09 Mar '18

09 Mar '18

Hello, I have been trying to livemigrate one of our KVM machines that has a local storage device, but it's failing. With error: error: internal error: unable to execute QEMU command 'migrate': this feature or command is not currently supported . After a bit of indepths look. I found out that local disk migration is not enabled with qemu-kvm-ev package. I have also tried to save a bit on downtime by creating a disk snapshot and just copy it over to new node, but live disk snapshots are also disabled. virsh snapshot-create vrt1-int-fr --disk-only --atomic error: Operation not supported: live disk snapshot not supported with this QEMU binary

1 0

qemu-kvm-ev-2.9.0-16.el7_4.14.1 has been released
by Sandro Bonazzola 09 Mar '18

09 Mar '18

Hi, qemu-kvm-ev-2.9.0-16.el7_4.14.1 <http://cbs.centos.org/koji/buildinfo?buildID=22232> has been tagged for release and should land on mirrors.centos.org on Monday, March 12th 2018. Here's the ChangeLog: * Thu Mar 08 2018 Sandro Bonazzola <sbonazzo(a)redhat.com> - ev-2.9.0-16.el7_4.14.1 - Removing RH branding from package name * Thu Jan 18 2018 Miroslav Rezanina <mrezanin(a)redhat.com> - rhev-2.9.0-16.el7_4.14 - kvm-fw_cfg-fix-memory-corruption-when-all-fw_cfg-slots-a.patch [bz#1534649] - kvm-mirror-Fix-inconsistent-backing-AioContext-for-after.patch [bz#1535125] - Resolves: bz#1534649 (Qemu crashes when all fw_cfg slots are used [rhel-7.4.z]) - Resolves: bz#1535125 (Mirror jobs for drives with iothreads make QEMU to abort with "block.c:1895: bdrv_attach_child: Assertion `bdrv_get_aio_context(parent_bs) == bdrv_get_aio_context(child_bs)' failed." [rhel-7.4.z]) Regards, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

kernel 4.9.86-30 missing mpt2sas module
by T.Weyergraf 07 Mar '18

07 Mar '18

Hi I am attempting to setup Xen 4.10 with kernel 4.9.86-30 ( virt7-xen-410-testing, virt7-common-testing ) on CentOS7 After installing everything, the machine was unable to boot and hung in dracut stating it could not find its root device. The testsystem I use is a somewhat aged Dell M915 Blade (Quad opteron 61xx), using an MPT SAS controller for it's SAS boot drives. Stock CentOS 7 reports mpt2sas module being used to access the controller. That module is not present in the modules directory of the 4.9.86: 4.9.86-30: # pwd /lib/modules/4.9.86-30.el7.x86_64 # find . -name "*mpt2*" -print # stock 3.10.0-693: # pwd /lib/modules/3.10.0-693.el7.x86_64 # find . -name "*mpt2*" -print ./kernel/drivers/scsi/mpt3sas/mpt2sas.ko.xz The fun part is, that according to the shipped config, it should be there: # grep MPT2 /boot/config-4.9.86-30.el7.x86_64 CONFIG_SCSI_MPT2SAS_MAX_SGE=128 CONFIG_SCSI_MPT2SAS=m Any idea, what happened? I will try myself to build a new kernel from the corresponding source package to check, what went wrong. As a side note: anyone here, who tried that combo? I know, it's somewhat cutting edge, but as I am finally looking into some sort of modern Xen4CentOS setup to replace our aged setup in our infrastructure, i thought i'd rather settle with something as new as possible to avoid running into "not supported anymore soon" issues. Check hypervisor support matrix on frontpage https://xenproject.org/ Regards Thomas Weyergraf

3 2

← Newer
1
...
8
9
10
11
12
13
14
...
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