October 2018 - Users - libvirt List Archives

Re: [libvirt-users] [virt-tools-list] Virt-manager: Restricted networks
by Cole Robinson 02 Oct '18

02 Oct '18

On 10/02/2018 08:50 AM, Olivier Léobal wrote: > Hello, > > 'Isolated' networks created in VMM (I’m running 1.4.3) still connect to > the host (as gateway). Is it possible to avoid this? It is my > understanding that QEMU provides a 'restrict' option for that, but I > don't understand it well, and can’t find it in VMM. > ccing libvirt-users That's expected of isolated mode, according to this: https://wiki.libvirt.org/page/VirtualNetworking#Isolated_mode I'm not sure if/how to go about creating a network that only VMs can communicate on - Cole

2 1

[libvirt-users] This QEMU doesn't support the LSI 53C895A SCSI controller
by Gionatan Danti 02 Oct '18

02 Oct '18

Hi all, trying to edit a domain xml to enable an LSI SCSI controller I get the following error: error: unsupported configuration: This QEMU doesn't support the LSI 53C895A SCSI controller It is my understanding that the error is raised due to RedHat disabling this controller in its own qemu-kvm builds. This seems an unfortunate decision, as it makes harder to migrate from VMWare (which uses LSI SCSI and SAS adapters) to RH+KVM. Can anyone elaborate on this decision? It is possible to enable LSI controller support in RedHat 7.x? Should I open a BZ against it? Thanks. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti(a)assyoma.it - info(a)assyoma.it GPG public key ID: FF5F32A8

2 3

[libvirt-users] libvirt reported capabilities doesn't match /proc/cpuinfo while the model does match
by Braiam Peguero 01 Oct '18

01 Oct '18

Hi, According to virsh capabilities I only have the following cpu features: <cpu> <arch>x86_64</arch> <model>IvyBridge-IBRS</model> <vendor>Intel</vendor> <microcode version='32'/> <topology sockets='1' cores='4' threads='1'/> <feature name='ds'/> <feature name='acpi'/> <feature name='ss'/> <feature name='ht'/> <feature name='tm'/> <feature name='pbe'/> <feature name='dtes64'/> <feature name='monitor'/> <feature name='ds_cpl'/> <feature name='vmx'/> <feature name='smx'/> <feature name='est'/> <feature name='tm2'/> <feature name='xtpr'/> <feature name='pdcm'/> <feature name='pcid'/> <feature name='osxsave'/> <feature name='arat'/> <feature name='ssbd'/> <feature name='xsaveopt'/> <feature name='invtsc'/> <pages unit='KiB' size='4'/> <pages unit='KiB' size='2048'/> </cpu> Meanwhile, cpuinfo reports the following: 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 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts flush_l1d bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf This results on my cpu being detected, if I allow host copy, as AMD chip and the guest becomes unbearably slow. The model of the host cpu is correct. I'm using Debian testing/unstable. Compiled against library: libvirt 4.7.0 Using library: libvirt 4.7.0 Using API: QEMU 4.7.0 Running hypervisor: QEMU 2.12.0 -- Braiam

2 1

[libvirt-users] Libvirt TLS with Short Lived Certificates
by Charles Urquiola 01 Oct '18

01 Oct '18

I want to use short lived certificates with libvirtd to provided TLS access to the daemon. New certificates are generated on a daily basis and delivered to the host. Does libvirtd re-read TLS certificates with a reload of the service, systemctl reload libvirtd, or with a SIGHUP or is a full restart of the daemon required? --charlie

2 1