virt

virt@lists.centos.org

1612 discussions

some ovirt packages missing?
by Sven Kieske 30 Sep '16

30 Sep '16

Hi, I just tried to setup ovirt-websocket-proxy. the package name in the upstream repo is e.g.: http://resources.ovirt.org/pub/ovirt-3.6/rpm/el7/noarch/ovirt-engine-websoc… I have the following repos enabled: yum repolist enabled Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.imt-systems.com * epel: mirror.imt-systems.com * extras: repo.de.bigstepcloud.com * updates: repo.de.bigstepcloud.com repo id repo name status base/7/x86_64 CentOS-7 - Base 9.007 centos-gluster37/7/x86_64 CentOS-7 - Gluster 3.7 139 centos-ovirt36/7/x86_64 CentOS-7 - oVirt 3.6 499 centos-qemu-ev/7/x86_64 CentOS-7 - QEMU EV 52 epel/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 10.626 extras/7/x86_64 CentOS-7 - Extras 390 updates/7/x86_64 CentOS-7 - Updates 2.504 repolist: 23.217 shouldn't this suffice to install the websocket proxy? -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +495772 293100 F: +495772 293333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen

2 1

Fwd: Centos 6 AMI does not support c4-8xlarge
by John Peacock 22 Sep '16

22 Sep '16

One of the things suboptimal with Marketplace images is that the author can limit which instance types are allowed with the AMI and there is no way to override that. We are using Centos 6.8 for our deployments, but we need to move to the c4.8xlarge type, but that is not a permitted option for the "CentOS 6 (x86_64) - with Updates HVM" AMI. Is there any way we could get that image refreshed to support the largest image type? We really need the 10G networking for our application. Thanks in advance John -- JOHN PEACOCK senior software build and release engineer tel 877-887-3031 mobile 240-429-9334 email john.peacock(a)sparkpost.com

3 4

Virtualization SIG membership
by Frantisek Kluknavsky 22 Sep '16

22 Sep '16

Hi, can I join the Virtualization SIG? I am interested in packaging docker with Lokesh Mandvekar. Thank you very much, Fero

1 0

Bridging wireless interface for KVM guests
by C. L. Martinez 16 Sep '16

16 Sep '16

Hi all, I am trying to configure wlan0 interface to use it with kvm guests. I know that I need to use ebtables statements due to it is not possible to link wlan0 interface with a bridge. I have followed Debian's tutorial: https://wiki.debian.org/BridgeNetworkConnections#Bridging_with_a_wireless_N… without luck. Someone have tried?? I am using CentOS 7 fully patched. Thanks.

2 1

Re: [CentOS-virt] Error doing PCI passthrough on CentOS 7.2
by C. L. Martinez 14 Sep '16

14 Sep '16

On Wed 14.Sep'16 at 7:17:45 -0600, Alex Williamson wrote: > On Wed, 14 Sep 2016 15:00:37 +0200 > Paolo Bonzini <pbonzini(a)redhat.com> wrote: > > > On 14/09/2016 14:35, Sandro Bonazzola wrote: > > > FYI > > > > > > > > > ---------- Forwarded message ---------- > > > From: *C. L. Martinez* <carlopmart(a)gmail.com <mailto:carlopmart@gmail.com>> > > > Date: Tue, Sep 13, 2016 at 11:29 AM > > > Subject: [CentOS-virt] Error doing PCI passthrough on CentOS 7.2 > > > To: centos-virt(a)centos.org <mailto:centos-virt@centos.org> > > > > > > > > > Hi all, > > > > > > I am trying to configure a kvm guest using pci passthrough to pass it a > > > wireless pci adapter (host is my personal laptop). But when I try to > > > start it: > > > > > > error: Failed to start domain obsdfw > > > error: unsupported configuration: host doesn't support passthrough of > > > host PCI devices > > > > What's the libvirt XML for the domain? > > > > > PCI passthrough is enabled: > > > > > > [ 0.000000] Command line: > > > BOOT_IMAGE=/vmlinuz-3.10.0-327.28.3.el7.x86_64 > > > root=UUID=48220e4e-228c-42d9-a0af-482c2fc7c008 ro crashkernel=auto rhgb > > > quiet intel_iommu=on > > > [ 0.000000] Kernel command line: > > > BOOT_IMAGE=/vmlinuz-3.10.0-327.28.3.el7.x86_64 > > > root=UUID=48220e4e-228c-42d9-a0af-482c2fc7c008 ro crashkernel=auto rhgb > > > quiet intel_iommu=on > > > > > > And supported according dmesg output: > > > > > > root@lapdev01# dmesg | grep IOM > > > [ 0.000000] Intel-IOMMU: enabled > > > > Is the VFIO module installed, and can you see IOMMU groups in "ls -lR > > /dev/vfio"? > > What's the host processor model? If this is the only line you see, > chances are your processor doesn't support VT-d, this line is just an > acknowledgment of the intel_iommu=on parameter, it doesn't indicate > that it's really enabled as it implies. The line you need to see is: > > DMAR: Intel(R) Virtualization Technology for Directed I/O > > Find your processor on http://ark.intel.com/ and look for VT-d > support. Thanks, > > Alex Oops .. You are right Alex. My processor doesn't support VT-d according to Intel. Many thanks for your help. -- Greetings, C. L. Martinez

1 0

Error doing PCI passthrough on CentOS 7.2
by C. L. Martinez 13 Sep '16

13 Sep '16

Hi all, I am trying to configure a kvm guest using pci passthrough to pass it a wireless pci adapter (host is my personal laptop). But when I try to start it: error: Failed to start domain obsdfw error: unsupported configuration: host doesn't support passthrough of host PCI devices PCI passthrough is enabled: [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.10.0-327.28.3.el7.x86_64 root=UUID=48220e4e-228c-42d9-a0af-482c2fc7c008 ro crashkernel=auto rhgb quiet intel_iommu=on [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.10.0-327.28.3.el7.x86_64 root=UUID=48220e4e-228c-42d9-a0af-482c2fc7c008 ro crashkernel=auto rhgb quiet intel_iommu=on And supported according dmesg output: root@lapdev01# dmesg | grep IOM [ 0.000000] Intel-IOMMU: enabled As you can see in the following output, VT-d extensions are supported also: root@lapdev01:~# cat /proc/cpuinfo | grep vmx flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt CPU is a Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz (fam: 06, model: 45, stepping: 01), Westmere. Then, where is the problem?? I don't understand what I am doing wrong. CentOS is 7.2 release fully patched using qemu package from virt repo: qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64 qemu-kvm-common-ev-2.3.0-31.el7.16.1.x86_64 qemu-img-ev-2.3.0-31.el7.16.1.x86_64 Thanks. -- Greetings, C. L. Martinez

1 0

xen 4.6.3-2 packages (with XSAs 185-188) making their way through CBS
by George Dunlap 10 Sep '16

10 Sep '16

Just a heads-up -- 4.6.3-2, for both CentOS 7 and CentOS 6, are making their way through the build system now and should be in the mirrors hopefully sometime later this afternoon. These contain patches for XSAs 185-188, one of which is a fairly critical update, so please update as soon as they're available. -George

3 2

No network using qemu-kvm-ev-2.3.0-31.el7.16.1
by C. L. Martinez 30 Aug '16

30 Aug '16

Hi all, To do some tests, I have installed a new CentOS7 host (fully patched) using qemu-kvm-ev-2.3.0-31.el7.16.1 instead of qemu-kvm's default package. And I have problems with network inside my guests. All guests can ping to CentOS host but nothing more: can't resolv dns names, can access via tcp to other hosts, etc ... Using same config on other CentOS7 host, but using default qemu-kvm package instead of qemu-kvm-ev-2.3.0-31.el7.16.1, all works ok. What am I doing wrong? Or is it a bug? Thanks -- Greetings, C. L. Martinez

3 4

Re: [CentOS-virt] No network using qemu-kvm-ev-2.3.0-31.el7.16.1
by C. L. Martinez 28 Aug '16

28 Aug '16

Ok, problem is not with qemu-kvm-ev-2.3.0-31.el7.16.1 package, it is with systemd-networkd. I have installed openvswitch and all works ok. Then, my question, is why is it not possible to use systemd-networkd for configure virtual switches to use them with KVM guests in CentOS 7 (using for other things, they seem work ok)?? In Ubuntu, Arch and Debian there is no problem with systemd-networkd configured bridges for KVM guests. Any idea why ?? Thanks. -- Greetings, C. L. Martinez

1 0

dracut-initqueue timeout with virt-install... but it works (kinda?)
by Matthew Crocker 25 Aug '16

25 Aug '16

Hello, I’m using virt-install to build a guest system with CentOS. The system boots up, times out with dracut-initqueue timeout and drops me into an emergency shell. If I exit the shell the install continues and I get a working machine. Any ideas? virt-install \ -n TEST \ -r 8192 \ --os-type=linux \ --disk=/vm-images/test.img,device=disk,bus=virtio,size=100,format=raw \ --ram=8192 \ --network bridge:br77 \ --location /home/CentOS-7-x86_64-Minimal-1511.iso \ --initrd-inject=/home/kickstart.cfg \ --extra-args="ks=file:/kickstart.cfg" \ --debug \ --accelerate kickstart.cfg: text install cdrom lang en_US.UTF-8 keyboard us network --onboot yes --device eth0 --bootproto dhcp --noipv6 rootpw testing123 firewall --service=ssh authconfig --enableshadow --passalgo=sha512 selinux --disable timezone --utc America/New_York bootloader --location=mbr zerombr clearpart --all --initlabel autopart reboot %packages --nobase @core %end — Matthew Crocker President - Crocker Communications, Inc. Managing Partner - Crocker Telecommunications, LLC E: matthew(a)corp.crocker.com E: matthew(a)crocker.com

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt