virt

virt@lists.centos.org

2 participants
1613 discussions

New VDSM and QEmu-KVM versions available for testing
by Sandro Bonazzola 03 Jul '15

03 Jul '15

Hi, the following packages from oVirt 3.5.4 RC1 have been pushed to testing repositories: - qemu-kvm-ev-2.1.2-23.el7_1.4.1 - vdsm-4.16.21-1.el7 You're welcome to test them[1] and provide feedback. [1] http://wiki.centos.org/HowTos/oVirt Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 2

Introduction
by Danilo Falcão 01 Jul '15

01 Jul '15

Hi guys I'm Danilo Falcão (fcon), a Sys Admin from Brazil and living in Germany. Recently I have joined Fedora QA & Infrastructure and now the CentOS project to work with Lokesh (lsm5) building RPMS for Docker and related packages. In the past years I've been working a lot with Virtualization (XEN and KVM mostly) and since Docker appeared I became a big fan of it. I'm also a Bash scripter and a Python Fabric lover. If there's anything I can help you guys with, just holla at me @ Freenode or drop an e-mail :) Cheers, Danilo

1 0

RHEL/CentOS 7.x KVM kernel instability & unreliability
by Vlastimil Holer 23 Jun '15

23 Jun '15

Hello, I'm managing smaller private virtualization infrastructure, currently based on CentOS 7.x. In the past we were running mostly on Debian 7 (kernel 3.2.x) and CentOS 6.x without problems. After we have upgraded to CentOS 7.x, I have experienced occasional physical host crashes when I did e.g. suspend or resume more virtual machines OR random virtual machine checkpoint was invalid and VM could not be resumed. I did few intesive tests on same hardware with: - CentOS 6.6 ... worked fine - CentOS 7.1 with 1. CentOS distribution kernel ... failed 2. Binary RHEL 7.1 distr. kernel ... failed 3. vanilla 3.10.80 kernel ... failed (plus various firmware releases and BIOS configurations) So far I could reliably run only CentOS 7.x with latest 4.0.5 kernel from ElRepo. 7.x kernel is based on 3.10.x, which failed for me as well. So I think there was some bug in KVM, which led to memory corruption. The result was either kernel oops or broken checkpoint and kernel oops occured later. I have opened bug on Red Hat https://bugzilla.redhat.com/show_bug.cgi?id=1231964 but since it's a private bug, I have created duplicate bug on CentOS http://bugs.centos.org/view.php?id=8949 There is described how to reproduce the problem including stress test script. I would appreciate if anybody can confirm it happens for him as well. Best regards, Vlastimil Holer

1 0

Kvm intel dual gigabit ethernet nic pass thru.
by mechy2k2000 22 Jun '15

22 Jun '15

Hello I am having a weird issue with a PCI-X Intel dual gigabit ethernet nic. While I am partially successful in pass thru with kvm, I have a weird issue with my pfsense freebsd vm. It see the two nics but gives them the same Mac address. I'm not sure if this is a pfsense bug or what. The nic works for everything but this Mac address issue. Long story short, I guess what I'm asking is there any options I should use when passing thru dual and quad Intel ethernet adapter right now I am using hostpci0: 1:00.0, driver=vfio Thanks Rafeal

1 0

CentOS 6 domU console issue
by Gene 20 Jun '15

20 Jun '15

Howdy, I'm having an issue with the console for CentOS 6 domUs. When I boot the domU I can see the console just fine. After grub has made its selection I get these errors: xenconsole: Could not open tty `': No such file or directory libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited with error status 2 After that the boot process continues fine and I'm able to sign into the console of the domU instance. However, when I close the console my command prompt doesn't work properly anymore, keypresses aren't printed to the screen. This problem is nearly identical to this issue: http://lists.xen.org/archives/html/xen-devel/2014-01/msg02259.html However, for my situation xenconsoled is running. Has anyone else encountered this issue? $ rpm -aq | egrep xen\|centos-release centos-release-xen-6-4.el6.centos.x86_64 xen-licenses-4.4.1-5.el6.x86_64 xen-hypervisor-4.4.1-5.el6.x86_64 xen-4.4.1-5.el6.x86_64 xen-libs-4.4.1-5.el6.x86_64 xen-runtime-4.4.1-5.el6.x86_64 centos-release-6-6.el6.centos.12.2.x86_64 -Gene

1 1

Custom installer ISO for C7+xen
by Gautam Malu 19 Jun '15

19 Jun '15

Hi, I have made a installer script which builds a custom c7 installer iso, which delivers xen 4.4 stack over minimal c7 installation. I have already tested it out c7 and c6.6 but it should work with any fedora installation also. https://github.com/gautamMalu/centos-xen It uses virt7-xen-44-testing repo (http://goo.gl/b2w53S) so you will need access to internet during installation. It uses custom anaconda so you can use it with your own ks scripts. https://github.com/gautamMalu/XenInBox Here is link for pre-build iso https://www.dropbox.com/s/e2h2zh2mb0u629k/c7-xen.iso?dl=0 Please test it out, and provide your feedback. Best regards, Gautam Malu

1 0

Reminder: the CentOS Virt SIG meeting is at 14:00 today on #centos-devel
by Lars Kurth 16 Jun '15

16 Jun '15

1 0

Re: [CentOS-virt] [ovirt-users] oVirt 3.5.3 VDSM on CentOS Virt SIG
by Sandro Bonazzola 15 Jun '15

15 Jun '15

Il 15/06/2015 12:41, Daniel Helgenberger ha scritto: > Hello Sandro, > > frist thanks for the great news! > > On 15.06.2015 10:28, Sandro Bonazzola wrote: >> Hi, >> today oVirt 3.5.3 has been released[1] >> VDSM 4.16.20 and its dependencies has been tagged as release as well within the Virt SIG build repositories for CentOS Linux 7. >> In order to enable the needed repositories you need to create /etc/yum.repos.d/centos-virt-sig.repo with the following content: > > I tried and seem to be unable to find any adequate release notes for > VDSM. Can someone firect me there or what are the benefits of vdsm > 4.16.20 over 4.16.16? Here's the list of bugs fixed: http://www.ovirt.org/OVirt_3.5.3_Release_Notes#VDSM > > Thanks! > >> >> [virt7-kvm-common-release] >> name=virt7-kvm-common-release >> baseurl=http://cbs.centos.org/repos/virt7-kvm-common-release/x86_64/os >> enabled=1 >> gpgcheck=0 >> >> [virt7-ovirt-common-release] >> name=virt7-ovirt-common-release >> baseurl=http://cbs.centos.org/repos/virt7-ovirt-common-release/x86_64/os >> enabled=1 >> gpgcheck=0 >> >> [virt7-ovirt-35-release] >> name=virt7-ovirt-35-release >> baseurl=http://cbs.centos.org/repos/virt7-ovirt-35-release/x86_64/os >> enabled=1 >> gpgcheck=0 >> >> >> An initial submission for the repository rpm has been pushed[2] and is waiting for public GPG keys to be added. >> >> [1] http://lists.ovirt.org/pipermail/announce/2015-June/000175.html >> [2] https://gerrit.ovirt.org/41403 >> > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

oVirt 3.5.3 VDSM on CentOS Virt SIG
by Sandro Bonazzola 15 Jun '15

15 Jun '15

Hi, today oVirt 3.5.3 has been released[1]. VDSM 4.16.20 and its dependencies has been tagged as release as well within the Virt SIG build repositories for CentOS Linux 7. In order to enable the needed repositories you need to create /etc/yum.repos.d/centos-virt-sig.repo with the following content: [virt7-kvm-common-release] name=virt7-kvm-common-release baseurl=http://cbs.centos.org/repos/virt7-kvm-common-release/x86_64/os enabled=1 gpgcheck=0 [virt7-ovirt-common-release] name=virt7-ovirt-common-release baseurl=http://cbs.centos.org/repos/virt7-ovirt-common-release/x86_64/os enabled=1 gpgcheck=0 [virt7-ovirt-35-release] name=virt7-ovirt-35-release baseurl=http://cbs.centos.org/repos/virt7-ovirt-35-release/x86_64/os enabled=1 gpgcheck=0 An initial submission for the repository rpm has been pushed[2] and is waiting for public GPG keys to be added. [1] http://lists.ovirt.org/pipermail/announce/2015-June/000175.html [2] https://gerrit.ovirt.org/41403 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Bridges, VLANs, Bonding on CentOS 7
by Timo Schöler 11 Jun '15

11 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, some months ago I ran into a hassle with following, quite simple config that works on CentOS 6 and CentOS 5 extremeley well, for years. However, I have problems getting it running on CentOS 7. ,-- bond0.100 -- brbond0.100 -> (VMs) eth0 (eno1 on C7) --. | |--- bond0 ----|-- bond0.101 -- brbond0.101 -> (VMs) eth1 (eno2 on C7) --´ | `-- bond0.n ---- brbond0.102 -> (VMs) Any idea, what's the difference between C5/C6 and CentOS 7? Best, Timo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlV5UHYACgkQuSPmkPhAW0qvSgD/aSybtfIG6Uy1da+zdJNNK7Ol fH2XG6We/FjakF102yUA/Ahbqk525/kP0kiq1/u9C2O5prnpjY9wIrYYUt/LU9nG =lcgL -----END PGP SIGNATURE-----

2 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt