virt May 2015

virt@lists.centos.org

14 participants
17 discussions

Won't attend to next Virt SIG meeting
by Sandro Bonazzola 28 May '15

28 May '15

Hi, I won't be able to attend to next week meeting. oVirt updates are: - 3.5.3 RC2 rpms for the Hypervisor Node are available for testing, info on http://wiki.centos.org/HowTos/oVirt - initial draft of the centos-kvm-release and centos-ovirt-release rpms is under review at https://gerrit.ovirt.org/41403 ; missing public key for rpm gpg-check to be added there. - Need to figure out which kind of automated tests we can add to ci.centos.org on the packages entering testing phase. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Kubernetes 0.17.1 in virt7-testing
by Navid Shaikh 28 May '15

28 May '15

Hi, kubernetes-0.17.1-3 is in virt7-testing repo [1]. Please test and feedback. [1] http://cbs.centos.org/repos/virt7-testing/x86_64/os/Packages/ -- Navid Shaikh IRC: nshaikh

4 5

Flannel 0.2 in virt7-testing
by Navid Shaikh 27 May '15

27 May '15

Hi, flannel-0.2.0-7.el7 is in virt7-testing repo [1]. Please test and feedback. [1] http://cbs.centos.org/repos/virt7-testing/x86_64/os/Packages/ -- Navid IRC: nshaikh

1 0

Bridge Networking for Xen in Box proposal
by Gautam Malu 26 May '15

26 May '15

Hi, I am doing xen in box gsoc project. The aim of the project is to have custom installer ISO which delivers xen stack running on c7 along with necessary bridge networking configuration. But I am getting confused over how to package bridge networking settings, so that I can deliver that during installation itself. I can use bridge-utils and package ifcfg-* files as differnet package. But for that I need to have the network information like how many NIC are present in the system, and which NIC is active is it eth0 or wlan0. I can probably write a script to set up bridge networking, which can be used to start bridge networking and stop, and ship that script as a package. Any suggestions? Best regards, Gautam Malu

2 1

Re: [CentOS-virt] xl stack problems on CentOS6 XEN4
by Hildebrand, Nils (BIT II 9) 20 May '15

20 May '15

Hi George, I already outlined the drbd-stuff on xen-users (see attachement). Yes - elrepo is right on mark. Excerpt: "The script (/etc/xen/scripts/block-drbd) I am using is from drbd84-utils-8.9.2-1.el6.elrepo.x86_64 - and already seems to contain the "drbd or phy" case; both in the add and the remove branch. CentOS6 XEN4 is based on the Kernel 3.10.68-11.el6.centos.alt.x86_64 which has drbd 8.4.3 built in." Excurse: As for SLES 11 there are two possibilities: a) official: Buy the HAE license (quite expensive). There is a drbd-stack built into it (based on drbd 8.4) b) inofficial: Compile your own drbd-srpm. That will contain the needed block-drbd as well, as part of the drbd-xen rpm. Back to my problem: Your patch does not fit my sources: http://vault.centos.org/6.6/xen4/Source/SPackages/ I am currently on XEN 4.4.2-2 - your patch is for 4.5? Can you please backport your patch to 4.4.2-2? Kind regards Nils -----Ursprüngliche Nachricht----- Von: George Dunlap [mailto:george.dunlap@eu.citrix.com] Gesendet: Montag, 18. Mai 2015 18:47 An: Hildebrand, Nils (BIT II 9); centos-virt(a)centos.org Betreff: Re: xl stack problems on CentOS6 XEN4 [Switching to CentOS-virt, as I think that's probably actually a more appropriate venue] On 05/11/2015 02:52 PM, Hildebrand, Nils (BIT II 9) wrote: > I am currently in the process of replacing my SLES11 SP3 Dom0s with CentOS6 XEN4 (at the moment: proof of concept with a test-cluster). > > I want to use the new xl-stack, instead of the old xm-stack, too. > > So far I stumbled across a number of minor glitches which could be worked around, I got DomUs with CentOS6 and CentOS 5 PV up and running with drbd-disk-backend (primary/secondary mode). > > But now I am stuck at the problem that pygrub does not seem to know about drbd-devices. I've never used drbd myself, but poking around a little bit, it seems that the SLES has drbd pacakages, one of which includes block scripts for Xen (drbd-xen). Looking at CentOS 6, I don't immediately see any drbd packages. Are you using the packages from elrepo, perhaps? In particular, do you have the Xen block scripts in /etc/xen/scripts/block-drbd? -George

1 0

Linux kernel 3.18.12 and libvirt 1.2.15 for Xen4CentOS in virt6-testing
by George Dunlap 19 May '15

19 May '15

Thanks to work from Johnny, linux 3.18.12 with all the x4c blktap goodness have been built and are now in the virt6-testing repo. I've also uploaded libvirt 1.2.15. As you may have seen earlier today, virt6-testing also includes an updated 4.4.2 package with the latest security update (XSA-133). The kernel has had some basic testing (by myself, Johnny, and another community member), but libvirt is at the moment untested, so caveat emptor. With such a large change, I want to leave both up for a few weeks before pushing them into the main repo. Please test them and report any errors you find. As a reminder, you can use the virt6-testing repo by putting the following file into /etc/yum.repos.d: [virt-testing] name=VirtSIG-\$releasever - Xen Testing baseurl=http://cbs.centos.org/repos/virt6-testing/\$basearch/os/ gpgcheck=0 enabled=0 For the adventurous, there are (as yet untested) kernel and xen packages in virt7-xen-44-candidate as well. I'll be pushing those to testing once I've actually had a chance to do set up my testing environment. Peace, -George

3 4

KVM and USB
by ToddAndMargo 14 May '15

14 May '15

Hi All, On KVM, is there a way to pass USB Flash drives automatically to the guest without having to go into virt-manager and selecting the specific USB device? -T -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Computers are like air conditioners. They malfunction when you open windows ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 1

xen-4.4.2-2 push to main rxen4 repo
by Johnny Hughes 13 May '15

13 May '15

I have pushed the xen4.4.2-2 rpms that George built for XSA-133 to our master server. It should populate to all of mirror.centos.org in 30 mins and will go to the external mirrors within the next day. Thanks, Johnny Hughes

1 0

Xen Security Advisory 133 (CVE-2015-3456) - Privilege escalation via emulated floppy disk drive
by George Dunlap 13 May '15

13 May '15

xen-4.4.2-2, available from the virt6-testing repository, includes the fix for this issue. Note that Xen actually does attempt to disable the floppy disk for HVM domains by default, but due to a bug in qemu, the floppy disk only partially disabled; enough functionality to exploit this bug remains. This should be available from the normal xen4 repositories sometime this afternoon. -George ---------- Forwarded message ---------- From: Xen.org security team <security(a)xen.org> Date: Wed, May 13, 2015 at 12:16 PM Subject: [Xen-users] Xen Security Advisory 133 (CVE-2015-3456) - Privilege escalation via emulated floppy disk drive To: xen-announce(a)lists.xen.org, xen-devel(a)lists.xen.org, xen-users(a)lists.xen.org, oss-security(a)lists.openwall.com Cc: "Xen.org security team" <security(a)xen.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2015-3456 / XSA-133 version 2 Privilege escalation via emulated floppy disk drive UPDATES IN VERSION 2 ==================== Public release. ISSUE DESCRIPTION ================= The code in qemu which emulates a floppy disk controller did not correctly bounds check accesses to an array and therefore was vulnerable to a buffer overflow attack. IMPACT ====== A guest which has access to an emulated floppy device can exploit this vulnerability to take over the qemu process elevating its privilege to that of the qemu process. VULNERABLE SYSTEMS ================== All Xen systems running x86 HVM guests without stubdomains are vulnerable to this depending on the specific guest configuration. The default configuration is vulnerable. Guests using either the traditional "qemu-xen" or upstream qemu device models are vulnerable. Guests using a qemu-dm stubdomain to run the device model are only vulnerable to takeover of that service domain. Systems running only x86 PV guests are not vulnerable. ARM systems are not vulnerable. MITIGATION ========== Enabling stubdomains will mitigate this issue, by reducing the escalation to only those privileges accorded to the service domain. qemu-dm stubdomains are only available with the traditional "qemu-xen" version. CREDITS ======= This issue was discovered by Jason Geffner, Senior Security Researcher at CrowdStrike. RESOLUTION ========== Applying the appropriate attached patch resolves this issue. xsa133-qemuu.patch qemu-upstream-unstable, Xen 4.5.x, Xen 4.4.x xsa133-qemuu-4.3-4.2.patch qemu-upstream-unstable, Xen 4.3.x, Xen 4.2.x xsa133-qemut.patch qemu-xen-unstable, Xen 4.5.x, Xen 4.4.x, Xen 4.3.x, Xen 4.2.x $ sha256sum xsa133*.patch e7ca0106a9d4bfe472b3b52bbed8646b47305634ff16c3e17ed6185296a7e7ff xsa133-qemut.patch 0cbc0415ef63bc195a0338441f3770d9fe6741e894879e35d1a6609ad028e42f xsa133-qemuu.patch cf735c1ecb6a40ca57d408e5c01725eca5b9b0a14b1d31b4362dc3f036bdeb28 xsa133-qemuu-4.3-4.2.patch $ DEPLOYMENT DURING EMBARGO ========================= Deployment of the patches described above (or others which are substantially similar) is permitted during the embargo, even on public-facing systems with untrusted guest users and administrators. But: Deployment of the mitigation by enabling stubdomains is NOT permitted (except on systems used and administered only by organisations which are members of the Xen Project Security Issues Predisclosure List). Specifically, deployment on public cloud systems is NOT permitted. This is because this configuration change may be visible to the guest. Also, distribution of updated software is prohibited (except to other members of the predisclosure list). Predisclosure list members who wish to deploy significantly different patches and/or mitigations, please contact the Xen Project Security Team. (Note: this during-embargo deployment notice is retained in post-embargo publicly released Xen Project advisories, even though it is then no longer applicable. This is to enable the community to have oversight of the Xen Project Security Team's decisionmaking.) For more information about permissible uses of embargoed information, consult the Xen Project community's agreed Security Policy: http://www.xenproject.org/security-policy.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJVUzJdAAoJEIP+FMlX6CvZnJcH/iszFBI+ltmOGxfCtSmnnkdu 6GZUFCVimeVG2ZfDCe1Bvw63ZMeB8AMUr2KmFrg0pOfC7m1Mc/4UhczpqeY9G1i0 kPCcNiK37Ju0otFN1AODHaYGhu6pgfTM+QV1muFVXHf9QibmH+vEy7HEN34Mtv/2 gGRmxLJnkHFME2sISuqhDsxIMf5QWN28I412/QqK8/mJMuvCJHqbLs/fv9f0uj9g sgAVCb3gsqNS7SSK1v49PqK+lQV+BkPR8pi8ODdL301iZWfu8PbVpYa5A84LVQF0 4ZnlVfWqeKXF7GlsuviinhQIoUIvSktf9tg65fM48Thk0UUp+MyHVkh4GkT/+Eo= =rN8t -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users(a)lists.xen.org http://lists.xen.org/xen-users

1 0

The future of blktap in Xen4CentOS
by George Dunlap 11 May '15

11 May '15

On Tue, May 5, 2015 at 2:07 PM, Johnny Hughes <johnny(a)centos.org> wrote: > WRT a new kernel .. the 3.18.x kernel has been selected to be maintained > as an LTS until Jan 2017. I think we should start work on rebuilding > this kernel and using it in the x4c projects. > > https://lwn.net/Articles/636289/ > > Thoughts? > > I will grab this kernel and try to roll in all the patches, etc. and see > if I can make it work. I did a little bit of work on building the 3.18 kernel a couple of weeks ago, but it looks like the blktap2.5 kernel code we were using before has totally bitrotted. I see three ways forward: 1. Try to do a "deep port" of the functionality, continuing to maintain it going forward. 2. Start using the blktap3 code, which requires no kernel driver. 3. Drop blktap support, and ask people to use qdisk for vhd. Re #1, I'm not really excited about the idea of trying to keep porting those patches forward (and finding and fixing bugs in the forward-port each time). Re #2, this would require getting the blktap3 stuff working upstream and then backporting it. #3 would be by far the easiest. In parallel to the Xen for C7 work I've been doing, I've been working on getting upstream Xen to build against XenServer's blktap code, with then aim of moving to blktap3. If we want to go with #2, then a major kernel update will have to wait until that work is done. -George

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt May 2015