- Users - libvirt List Archives

[libvirt-users] [qemu-kvm] Network bandwidth limits via libvirt
by 卓浩凡 16 Jun '17

16 Jun '17

Hi all, I try to understand why the network bandwidth limits are not applied to my ubuntu 16.04.2 VM (qemu-kvm driver) and I would need some insights. I create my VM network with virsh and when I issue a dumpxml on my network, I can see that bandwidth limits are set: virsh # net-dumpxml nat_limit <network> <name>nat_limit</name> <uuid>4b5e128d-9ad0-4ccc-9424-dee60b71861a</uuid> <forward mode='nat'> <nat> <port start='1024' end='65535'/> </nat> </forward> <bridge name='virbr1' stp='on' delay='0'/> <mac address='52:54:00:af:99:73'/> <bandwidth> <inbound average='10' peak='50' burst='10'/> <outbound average='128' peak='256' burst='256'/> </bandwidth> <ip address='192.168.123.1' netmask='255.255.255.0'> <dhcp> <range start='192.168.123.2' end='192.168.123.254'/> </dhcp> </ip> </network> And the net info is: virsh # net-info nat_limit Name: nat_limit UUID: 4b5e128d-9ad0-4ccc-9424-dee60b71861a Active: yes Persistent: yes Autostart: yes Bridge: virbr1 Then, I create my VM, and the source of interface is the network, like this: virsh # dumpxml virt20 ... <interface type='network'> <mac address='52:54:00:a2:5b:10'/> <source network='nat_limit' bridge='virbr1'/> <target dev='vnet2'/> <model type='rtl8139'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> ... However when I send a big file with netper I don't see any limits applied to the transfer rate. I've checked the domain log and I didn't see any qemu command line argument related to bandwidth limits. Could you tell me why the network bandwidth limits can not work? Do network limits are managed in another way? Thanks. Below some information about my hypervisor: root@ubuntu-04:~# virsh -V Virsh command line tool of libvirt 1.3.1 See web site at http://libvirt.org/ Compiled with support for: Hypervisors: QEMU/KVM LXC UML Xen LibXL OpenVZ VMWare VirtualBox ESX Test Networking: Remote Network Bridging Interface netcf Nwfilter VirtualPort Storage: Dir Disk Filesystem SCSI Multipath iSCSI LVM RBD Sheepdog ZFS Miscellaneous: Daemon Nodedev AppArmor Secrets Debug Readline Modular qemu version: 2.5.0 Thanks, Netsurfed

2 1

[libvirt-users] Isolate VMs' network
by Chris 07 Jun '17

07 Jun '17

All, I'm trying to setup a network with some virtual machines, that can connect to each other and to the internet, but neither to the host nor to other VMs. Is there any preconfigured network filter or best-practice for this setup? Of course, I could setup iptables rules on the host, but I'd prefer libvirt to handle them. - Chris

5 12

Re: [libvirt-users] libvirtd not accepting connections
by Martin Kletzander 06 Jun '17

06 Jun '17

[adding back the ML, you probably hit reply instead of reply-all, this way other people might help if they know more] On Fri, Jun 02, 2017 at 08:10:01AM -0400, Michael C. Cambria wrote: > >Hi, > >libvirtd never seems to get notified that there is work to do. journalct >-f indicated that nothing was logged when connections were attempted via >virsh. > >I also tried 'LIBVIRT_DEBUG=1 libvirtd --verbose' and once startup >finished, there were no more log entries even though virsh attempts were >made. > That's because it gets overridden by the configuration files. This might be a bug, but it's not related to what's happening. >"ps ax" shows about a dozen "qemu-system-alpha" processes. I don't know >if it matters but I didn't expect to see this. I didn't intentionally >configure alpha emulations (assuming that's what it is) and certainly >don't want to waste resources having it running. > Libvirt caches the capabilities of the emulators it can find in your system in order not to waste resources. These processes are expected to go away after they reply with all libvirt asks them for. However, it seems like the initialization cannot be completed precisely due to the fact that these processes don't communicate. There might be some details about qemu-system-alpha that are different when compared to, e.g. qemu-system-x86 and libvirt is not (yet) adapted to them, but I installed that emulator and libvirt daemon runs as usual. It looks like a problem in QEMU. Could you, as a workaround, try uninstalling that qemu binary from your system and restarting the service? Also, what versions of libvirt and qemu do you have installed? >Here is gdb output: > >$ sudo gdb -batch -p $(pidof libvirtd) -ex "t a a bt full" > batch.out >[mcc@eastie-fid4-com triage]$ cat batch.out >[New LWP 17587] >[New LWP 17588] >[New LWP 17589] >[New LWP 17590] >[New LWP 17591] >[New LWP 17592] >[New LWP 17593] >[New LWP 17594] >[New LWP 17595] >[New LWP 17596] >[New LWP 17597] >[New LWP 17598] >[New LWP 17599] >[New LWP 17600] >[New LWP 17601] >[New LWP 17602] >[Thread debugging using libthread_db enabled] >Using host libthread_db library "/lib64/libthread_db.so.1". >0x00007fcd6b4a501d in poll () at ../sysdeps/unix/syscall-template.S:84 >84 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) > >Thread 17 (Thread 0x7fcd3bf18700 (LWP 17602)): >#0 0x00007fcd6b4a501d in poll () at ../sysdeps/unix/syscall-template.S:84 >No locals. >#1 0x00007fcd6b4c310e in __poll_chk (fds=<optimized out>, >nfds=<optimized out>, timeout=<optimized out>, fdslen=<optimized out>) >at poll_chk.c:27 >No locals. >#2 0x00007fcd6f07bf41 in poll (__timeout=-1, __nfds=<optimized out>, >__fds=0x7fcd3bf16ec0) at /usr/include/bits/poll2.h:41 >No locals. >#3 virCommandProcessIO (cmd=cmd@entry=0x7fcd344228f0) at >util/vircommand.c:2049 > i = <optimized out> > fds = {{fd = 22, events = 1, revents = 0}, {fd = 24, events = >1, revents = 0}, {fd = 1802946632, events = 32717, revents = 0}} > nfds = <optimized out> > outfd = <optimized out> > errfd = 24 > inlen = 0 > outlen = 0 > errlen = 0 > inoff = 0 > ret = 0 > __func__ = "virCommandProcessIO" > __FUNCTION__ = "virCommandProcessIO" >#4 0x00007fcd6f08025a in virCommandRun (cmd=cmd@entry=0x7fcd344228f0, >exitstatus=exitstatus@entry=0x7fcd3bf1749c) at util/vircommand.c:2274 > ret = 0 > outbuf = 0x7fcd341c1850 "`\030\034\064\315\177" > errbuf = 0x0 > st = {st_dev = 140519450702688, st_ino = 5007254661694877440, >st_nlink = 140519321774352, st_mode = 1862726288, st_uid = 32717, st_gid >= 1865325018, __pad0 = 32717, st_rdev = 140732281970554, st_size = 0, >st_blksize = 11, st_blocks = 8, st_atim = {tv_sec = 140519321774368, >tv_nsec = 140519450703056}, st_mtim = {tv_sec = 140519321774352, tv_nsec >= 140519450703024}, st_ctim = {tv_sec = 140520244259750, tv_nsec = >140520310044608}, __glibc_reserved = {140520244259750, 140520310041179, >140519321774320}} > string_io = <optimized out> > async_io = <optimized out> > str = 0x7fcd3bf17420 "\260t\361;\315\177" > tmpfd = <optimized out> > __FUNCTION__ = "virCommandRun" > __func__ = "virCommandRun" >#5 0x00007fcd404a27cf in virQEMUCapsInitQMP (qmperr=0x7fcd3bf174a0, >runGid=107, runUid=107, libDir=<optimized out>, qemuCaps=0x7fcd340fd3e0) >at qemu/qemu_capabilities.c:3700 > cmd = 0x7fcd344228f0 > pid = 0 > ret = -1 > mon = 0x0 > status = 0 > monarg = 0x7fcd343a2570 >"unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait" > vm = 0x0 > config = {type = 9, data = {file = {path = 0x7fcd34151d90 >"/var/lib/libvirt/qemu/capabilities.monitor.sock", append = 0}, nmdm = >{master = 0x7fcd34151d90 >"/var/lib/libvirt/qemu/capabilities.monitor.sock", slave = 0x0}, tcp = >{host = 0x7fcd34151d90 >"/var/lib/libvirt/qemu/capabilities.monitor.sock", service = 0x0, listen >= false, protocol = 0}, udp = {bindHost = 0x7fcd34151d90 >"/var/lib/libvirt/qemu/capabilities.monitor.sock", bindService = 0x0, >connectHost = 0x0, connectService = 0x0}, nix = {path = 0x7fcd34151d90 >"/var/lib/libvirt/qemu/capabilities.monitor.sock", listen = false}, >spicevmc = 873799056, spiceport = {channel = 0x7fcd34151d90 >"/var/lib/libvirt/qemu/capabilities.monitor.sock"}}, logfile = 0x0, >logappend = 0} > monpath = 0x7fcd34151d90 >"/var/lib/libvirt/qemu/capabilities.monitor.sock" > pidfile = 0x7fcd341ad8b0 >"/var/lib/libvirt/qemu/capabilities.pidfile" > xmlopt = 0x0 >#6 virQEMUCapsNewForBinaryInternal (binary=binary@entry=0x7fcd34016cb0 >"/usr/bin/qemu-system-alpha", libDir=<optimized out>, >cacheDir=0x7fcd343be860 "/var/cache/libvirt/qemu", runUid=107, >runGid=107, qmpOnly=qmpOnly@entry=false) at qemu/qemu_capabilities.c:3830 > qemuCaps = 0x7fcd340fd3e0 > sb = {st_dev = 64768, st_ino = 1838294, st_nlink = 1, st_mode = >33261, st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = >8829680, st_blksize = 4096, st_blocks = 17248, st_atim = {tv_sec = >1496358589, tv_nsec = 77994286}, st_mtim = {tv_sec = 1492132244, tv_nsec >= 0}, st_ctim = {tv_sec = 1494196699, tv_nsec = 451929606}, >__glibc_reserved = {0, 0, 0}} > rv = <optimized out> > qmperr = 0x7fcd341c1870 "" > __FUNCTION__ = "virQEMUCapsNewForBinaryInternal" >#7 0x00007fcd404a3a73 in virQEMUCapsNewForBinary (runGid=<optimized >out>, runUid=<optimized out>, cacheDir=<optimized out>, >libDir=<optimized out>, binary=0x7fcd34016cb0 >"/usr/bin/qemu-system-alpha") at qemu/qemu_capabilities.c:3871 >No locals. >#8 virQEMUCapsCacheLookup (cache=cache@entry=0x7fcd341c9000, >binary=0x7fcd34016cb0 "/usr/bin/qemu-system-alpha") at >qemu/qemu_capabilities.c:3986 > ret = 0x0 > __func__ = "virQEMUCapsCacheLookup" >#9 0x00007fcd404a3d22 in virQEMUCapsInitGuest >(guestarch=VIR_ARCH_ALPHA, hostarch=VIR_ARCH_X86_64, >cache=0x7fcd341c9000, caps=0x7fcd341a9980) at qemu/qemu_capabilities.c:824 > qemubinCaps = 0x0 > x86_32on64_kvm = <optimized out> > ppc64_kvm = <optimized out> > kvmbin = 0x0 > ret = -1 > i = <optimized out> > binary = 0x7fcd34016cb0 "/usr/bin/qemu-system-alpha" > kvmbinCaps = 0x0 > native_kvm = <optimized out> > arm_32on64_kvm = <optimized out> >#10 virQEMUCapsInit (cache=0x7fcd341c9000) at qemu/qemu_capabilities.c:1109 > caps = 0x7fcd341a9980 > i = 1 > hostarch = VIR_ARCH_X86_64 > __func__ = "virQEMUCapsInit" >#11 0x00007fcd404def20 in virQEMUDriverCreateCapabilities >(driver=driver@entry=0x7fcd34342370) at qemu/qemu_conf.c:766 > i = <optimized out> > j = <optimized out> > caps = <optimized out> > sec_managers = 0x0 > doi = <optimized out> > model = <optimized out> > lbl = <optimized out> > type = <optimized out> > cfg = 0x7fcd3448cbb0 > virtTypes = {3, 1} > __FUNCTION__ = "virQEMUDriverCreateCapabilities" > __func__ = "virQEMUDriverCreateCapabilities" >#12 0x00007fcd4051fef3 in qemuStateInitialize (privileged=true, >callback=<optimized out>, opaque=<optimized out>) at qemu/qemu_driver.c:844 > driverConf = 0x0 > conn = 0x0 > cfg = 0x7fcd3448cbb0 > run_uid = <optimized out> > run_gid = <optimized out> > hugepagePath = 0x0 > i = <optimized out> > __FUNCTION__ = "qemuStateInitialize" >#13 0x00007fcd6f1789af in virStateInitialize (privileged=<optimized >out>, callback=0x55f56a9b3180 <daemonInhibitCallback>, >opaque=0x55f56be1cf00) at libvirt.c:770 > i = 9 > __func__ = "virStateInitialize" >#14 0x000055f56a9b31db in daemonRunStateInit (opaque=0x55f56be1cf00) at >libvirtd.c:959 > dmn = 0x55f56be1cf00 > sysident = 0x7fcd34000910 > __func__ = "daemonRunStateInit" >#15 0x00007fcd6f0d98f2 in virThreadHelper (data=<optimized out>) at >util/virthread.c:206 > args = 0x0 > local = {func = 0x55f56a9b31a0 <daemonRunStateInit>, funcName = >0x55f56a9f28d3 "daemonRunStateInit", worker = false, opaque = >0x55f56be1cf00} >#16 0x00007fcd6b7766ca in start_thread (arg=0x7fcd3bf18700) at >pthread_create.c:333 > __res = <optimized out> > pd = 0x7fcd3bf18700 > now = <optimized out> > unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140519450707712, >-3574063505887647860, 0, 140732281962543, 140519450708416, >140519450707712, 3601779982174594956, 3601954753778231180}, >mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = >0x0, cleanup = 0x0, canceltype = 0}}} > not_first_call = <optimized out> > pagesize_m1 = <optimized out> > sp = <optimized out> > freesize = <optimized out> > __PRETTY_FUNCTION__ = "start_thread" >#17 0x00007fcd6b4b0f7f in clone () at >.../sysdeps/unix/sysv/linux/x86_64/clone.S:105 >No locals. > [...]

3 15

[libvirt-users] why increasing vCPUs increasing the CPU sockets for QEMU+KVM
by girish kumar 06 Jun '17

06 Jun '17

Hi All, I am new here, please warn me If I am not following proper etiquette of this mailing list. I am breaking my head, regarding why libvirt is defining multiple CPU sockets when I increase the vCPU count. As and when I increase the vCPU count in libvirt guest XML, it is increasing the CPU sockets in qemu instance. " -smp 4,sockets=4,cores=1,threads=1 " instead " -smp 4,sockets=1,cores=4,threads=1" Does not this lower the performance of the guest as the host and guest architectures gets different in that case. Also please suggest a guest configuration which will take advantage of the host CPU architecture. Your help will be highly appreciated. -- Regards, Girish

2 3

[libvirt-users] vm live migration memory copy
by Hui Jing 04 Jun '17

04 Jun '17

Hi All, I am wondering when we do live migration, how much memory is transferred? I guess it must be one of the three below, but not sure which one: 1. The amount of memory allocated to VM 2. The memory currently used by VM (actual Mem usage in guest) 3. The memory used by the qemu process (RSS). Best Regards, Hui

2 1

[libvirt-users] Debugging Windows 10 Guest Flakiness
by David Morrison 02 Jun '17

02 Jun '17

Hello, I'm not sure if I'm asking this question in the right place, so please redirect me if there's a better list. I recently set up a Windows 10 guest on an Arch Linux host with libvirt and KVM/Qemu, using IOMMU to enable GPU passthrough. I followed this guide to set up the VM: https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF The problem that I'm having is that the guest is very flaky: sometimes the guest will just hang indefinitely, and sometimes the guest loses network connectivity. Usually when either of these behaviors happens, restarting the libvirtd daemon on the host resolves the issue, but that's not always true, and sometimes when I restart libvirtd it causes my entire (host) machine to lock up! I have enabled log_output level 1 in /etc/libvirt/libvirtd.conf and have monitored the log file during one of these hangs, but I don't see any obvious errors or problems in the log file itself (and there's a lot of information to sort through, so I may have missed something). Some specifics about my setup: Motherboard: ASUS Sabertooth X79 CPU: Intel i7 4930K Host GPU: GeForce GT 730 Guest GPU: GeForce GTX 780 Virtual network interface: NAT with the virtio driver I'm *reasonably* confident that the problem is not with the GPU passthrough setup, as I'm able to run FurMark (a GPU burn-in tool) on the guest with no problems. However, I haven't yet been able to reliably reproduce the error at all, so I'm pretty much at a loss as to where to go from here. Can anyone on this list point me in a good direction to look, or have you seen anything like this before? I'm happy to provide debug logs or any other information that is helpful, as well. Thanks for your time, David

1 0

[libvirt-users] No way to stop virStream error after guest stop
by JosÉ Luis Valencia Gutierrez 02 Jun '17

02 Jun '17

Hello everyone, I am opening a virChannel(unix) to a domain and receiving data with a non-blocking virStream using events, when the connected domain gets stopped(which deletes the channel unix socket) by calling destroy, shutdown, pause or migrate on that domain, with the stream open the read event is triggered repeatedly, and virStreamRecv returns 0 bytes indicating EOF but neither virStreamFinish nor virStreamFinish is working to stop the stream to trigger the event . Each time the event is called I got this errors. libvirt: I/O Stream Utils error : this function is not supported by the connection driver: virStreamRecv libvirt: I/O Stream Utils error : this function is not supported by the connection driver: virStreamFinish libvirt: I/O Stream Utils error : this function is not supported by the connection driver: virStreamEventRemoveCallback Is there other way to stop getting this errors? or perhaps this is a bug. Thanks in advance. Jose Valencia

2 8

[libvirt-users] libvirtd not accepting connections
by Michael C. Cambria 01 Jun '17

01 Jun '17

Hi, Ever since I recently upgraded to Fedora 25, I can't get kvm working. It's worked on this system since initial fedora 20 install. All upgrades were done via yum, then once available, dnf. I do have libvirt-sock in LISTENING state: STREAM LISTENING /var/run/libvirt/libvirt-sock I noticed I also have multiple connections in CONNECTING state: STREAM CONNECTING 0 /var/run/libvirt/libvirt-sock STREAM CONNECTING 0 /var/run/libvirt/libvirt-sock STREAM CONNECTING 0 /var/run/libvirt/libvirt-sock I rebooted and tried again. Each e.g. 'virsh -c" or virt-manager command I issue, I end up with another socket in CONNECTING state. restarting libvirtd.service close them leaving just one LISTENING strace for virsh -c shows: 4301 socket(AF_UNIX, SOCK_STREAM, 0) = 5 4301 connect(5, {sa_family=AF_UNIX, sun_path="/var/run/libvirt/libvirt-sock"}, 110) = 0 4301 getsockname(5, {sa_family=AF_UNIX}, [128->2]) = 0 4301 futex(0x7f3c0a2e4fc8, FUTEX_WAKE_PRIVATE, 2147483647) = 0 4301 fcntl(5, F_GETFD) = 0 4301 fcntl(5, F_SETFD, FD_CLOEXEC) = 0 4301 fcntl(5, F_GETFL) = 0x2 (flags O_RDWR) 4301 fcntl(5, F_SETFL, O_RDWR|O_NONBLOCK) = 0 systemctl status libvirtd.service and journalctl -f -u libvirtd.service do not show any log entries for libvird after it has been started. e.g. it doesn't log anything about the connection attempts. Anyone have an idea where to look next? Thanks, MikeC

2 1

[libvirt-users] VM memory monitor
by zhunxun＠gmail.com 01 Jun '17

01 Jun '17

Hello，I want to know what the "virsh dommemstat " really stand for?the rss in result really indicatre the physical memory that the VM has used? thanks! zhunxun(a)gmail.com

1 0

[libvirt-users] Hopefully simple question
by Leroy Tennison 31 May '17

31 May '17

Is there a way to determine what the hypervisor default NIC is? I'm using kvm/libvirt/qemu. If this is the wrong forum please please reply with that.

3 2

[libvirt-users] Another hopefully simple question
by Leroy Tennison 31 May '17

31 May '17

Actually the last for now. Is there a way to determine from the hypervisor (kvm/libvirt/qemu) if a VM has unmounted a partition?

2 1

[libvirt-users] can't establish more than 1000 connections with virsh
by dw 26 May '17

26 May '17

Hi: I'm trying to connect with libvirtd with virsh from a remote PC,but only can establish 1000 connections. If try more connections,prompt: "error: failed to connect to the hypervisor error: Failed to open file '/etc/libvirt/libvirt.conf': Too many open files" I tried in another PC,also get the same prompt. Anybody know why? Thanks! environment: libvirt:libvirt-2.0.0-10.el7 OS:centos7.3

2 6

[libvirt-users] nwfilter - how to protect VM's
by Thiago Oliveira 25 May '17

25 May '17

Hello guys! I have just one physical NIC (eth0) and some libvirt networks. Each network created represents one customer and it is working fine. My question is how can I protect between the customer's networks? For example: The host 192.168.2.2 from the network 192.168.2.0/30 can not access any VM in others networks but the 192.168.2.2 can access 192.168.0.1 because it is the gateway to the internet and this host can receive incoming connections from the internet. I would like to tag with VLAN for example but I don't have sure if this is the best way. See below my route table [image: Imagem inline 1] Thank you guys. Thiago

1 0

[libvirt-users] How to show underlying QEMU command line using virsh
by Roman Storozhenko 24 May '17

24 May '17

Hello, everybody I use virt to run my VM's and QEMU as a hypervisor. There is a file describing my virtual machine: /etc/libvirt/qemu/centos7.0.xml As you know it contains xml representation of my VM. Is there any way to show underlying qemu command that virsh runs using that file? For example: qemu-system-x86-64 -m 1024 -smp 2 -... If no, is there any way to figure it out during VM run ? --- Thanks in advance, Roman Storozhenko

4 3

[libvirt-users] How to set guest console size in libvirt configuration options?
by Roman Storozhenko 24 May '17

24 May '17

Hello, everybody I use virsh to run my VM and QEMU as a hypervisor. When I connect to it, it shows me a console with a some predefined size. I know that I am able to update grub configuration to pass the correct size as a kernel command line option or use stty something like: stty rows 62 cols 213 and it's resizes correctly. But is there any way to define the console's size outside the guest, in the VM's configuration? --- Thanks in advance, Roman Storozhenko

2 1

[libvirt-users] How to fit with Apparmor when upgrade to new libvirt version?
by Eddie Yen 24 May '17

24 May '17

Hi everyone, this is my first post at this mailing list. I have a question about upgrading libvirt, but also can fit to Apparmor. For example, I already installed KVM + libvirt from apt-get on Ubuntu 14.04. But the libvirt version is 1.2.9, so I want upgrade to 1.3.4 manually. Search the Internet, only few posts show how to edit so that can launch VM with Apparmor enabled. Most of posts says disable Apparmor is good idea, but I don't want to do that. I already done these things: 1. Replace apparmor profiles from examples/apparmor into /etc/apparmor.d 2. Use --with-apparmor and --with-apparmor-profiles to compile. But I still get virt-aa-helper DENIED message when I try to launch VM. Any ideas? Many thanks, Eddie.

1 0

[libvirt-users] Odd Virsh Capabilities response
by W Kern 23 May '17

23 May '17

Tried to migrate a few VMs from existing system to an older host that we threw in the rack to facilitate some server reshuffling. Migration complained about lack of capabilities (which I expected its an older server) but when I looked at what I should throw into the xml file I got a core2duo when it should have been at least Penryn or something (Xeon E5345) Of course the VMs work fine with that cpu def so its not a bit deal at the moment, but I am still curious Is it some sort of lookup table bug or is the server BIOS wonky? ----------------------------------------------------------- OS: Up to date U16 Xenial on an HP DL380 server. Stock libraries for that distro libvirt0/xenial-updates,now 1.3.1-1ubuntu10.8 amd64 [installed,automatic] qemu-kvm/xenial-updates,xenial-security,now 1:2.5+dfsg-5ubuntu10.14 amd64 [installed,automatic] QEMU Full virtualization cat /proc/cpu shows processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU E5345 @ 2.33GHz stepping : 11 microcode : 0xb4 cpu MHz : 2333.361 # virsh capabilities <capabilities> <host> <uuid>33393138-3335-5553-4538-31324e39414b</uuid> <cpu> <arch>x86_64</arch> <model>core2duo</model> <vendor>Intel</vendor> <topology sockets='2' cores='4' threads='1'/> <feature name='lahf_lm'/> <feature name='dca'/> <feature name='pdcm'/> <feature name='xtpr'/> <feature name='cx16'/> <feature name='tm2'/> <feature name='est'/> <feature name='vmx'/> <feature name='ds_cpl'/> <feature name='dtes64'/> <feature name='pbe'/> <feature name='tm'/> <feature name='ht'/> <feature name='ss'/> <feature name='acpi'/> <feature name='ds'/> <pages unit='KiB' size='4'/> <pages unit='KiB' size='2048'/> </cpu> <power_management> <suspend_mem/> <suspend_disk/> <suspend_hybrid/> </power_management> <migration_features> <live/> <uri_transports> <uri_transport>tcp</uri_transport> <uri_transport>rdma</uri_transport> </uri_transports> </migration_features> <topology> <cells num='1'> <cell id='0'> <memory unit='KiB'>32945368</memory> <pages unit='KiB' size='4'>8236342</pages> <pages unit='KiB' size='2048'>0</pages> <distances> <sibling id='0' value='10'/> </distances> <cpus num='8'> <cpu id='0' socket_id='0' core_id='0' siblings='0'/> <cpu id='1' socket_id='1' core_id='0' siblings='1'/> <cpu id='2' socket_id='0' core_id='2' siblings='2'/> <cpu id='3' socket_id='1' core_id='2' siblings='3'/> <cpu id='4' socket_id='0' core_id='1' siblings='4'/> <cpu id='5' socket_id='1' core_id='1' siblings='5'/> <cpu id='6' socket_id='0' core_id='3' siblings='6'/> <cpu id='7' socket_id='1' core_id='3' siblings='7'/> </cpus> </cell> </cells> </topology>

2 2

[libvirt-users] error message
by Eric Blake 23 May '17

23 May '17

[moderator note: re-posting to list with screenshot deleted, in order to meet list policy size constraints] hello, i am trying to install libvirt but getting some error . even though i am folowing your instructions and steps please help me out this

1 0

[libvirt-users] live migration
by Hossein Azizabadi 23 May '17

23 May '17

I’m interested with the modifications of live migration with all storage on KVM . I intend to ask, modification performed on which part of KVM? Do storage blocks migrate sequentialy? I need information about it

1 0

[libvirt-users] disabling dnsmasq
by Michael Ströder 22 May '17

22 May '17

HI! I have some virtual networks (not only bridged) in my libvirt 3.3.0 installation and therefore libvirt always starts dnsmasq. But I want to use my own DHCP and DNS servers which are correctly working for this VM infrastructure. How to completely disable dnsmasq in libvirt? Ciao, Michael.

2 1

[libvirt-users] Access to the wiki
by Jlozada2426 22 May '17

22 May '17

Hello, I was wondering if I could get access to the wiki. I want to contribute and help out. Jonathan Lozada De La Matta Linux System Administrator ask.sysadminonlinux.org Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

[libvirt-users] <source mode='private'> for PPPoE?
by Michael Ströder 19 May '17

19 May '17

HI! I'm currently reviewing my (functional) setup with one physical ethernet interface eth1 of the host system being connected to a VDSL modem (not router!). A fully virtualized guest acts as router with this source mode: <source dev='eth1' mode='bridge'/> Reading the docs [1] I'm thinking whether mode='private' would be a better choice because the network packets are supposed to be sent exclusively to the VDSL modem and received from there. Any thoughts? Ciao, Michael. [1] https://libvirt.org/formatdomain.html#elementsNICSDirect

1 0

[libvirt-users] Duplicate reboot events
by Innus, Martins 17 May '17

17 May '17

Hi, Running on: $ cat /etc/redhat-release CentOS Linux release 7.3.1611 (Core) And: $ rpm -qa |grep libvirt libvirt-daemon-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-qemu-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-secret-2.0.0-10.el7_3.5.x86_64 libvirt-client-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-network-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-storage-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-config-nwfilter-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-config-network-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-nodedev-2.0.0-10.el7_3.5.x86_64 libvirt-2.0.0-10.el7_3.5.x86_64 libvirt-python-2.0.0-2.el7.x86_64 libvirt-daemon-driver-nwfilter-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-lxc-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-interface-2.0.0-10.el7_3.5.x86_64 I’m seeing duplicated reboot events when using the python event api. Use is simplified down to the simple test case attached. Running with that results in: $ sudo ./libvirt_events_single.py Reboot: Domain i-06945b37(21) 1494958504.72 Reboot: Domain i-06945b37(21) 1494958504.74 This is reproducible 100% of the time by doing /sbin/reboot from within a VM started with qemu-kvm. Any ideas on whats going on? Let me know if any other information would be useful. Thanks Martins

2 6

[libvirt-users] Callback re-registration after libvirtd restart
by Daniel Kučera 17 May '17

17 May '17

Hi all, I'm using libvirt-go and I following code to listen for lifecycle events: func event_listen() { log.Printf("event_listen %s", conf.Libvirt.LocalUrl) hv, err := libvirt.NewConnect(conf.Libvirt.LocalUrl) lifecycleCallback := func(c *libvirt.Connect, d *libvirt.Domain, event *libvirt.DomainEventLifecycle) { event_message(c, d, "lifecycle", event) } _, err = hv.DomainEventLifecycleRegister(nil, lifecycleCallback) if err != nil { log.Printf("unable to register event callback") return } log.Printf("Libvirt event listener started") go func() { for err == nil { err = libvirt.EventRunDefaultImpl() log.Printf("EventRunDefaultImpl err: %+v", err) } time.Sleep(time.Second) event_listen() }() } It works ok until I restart libvirtd (service libvirtd restart). After that, the inner go func waits some time and continues without error. But the callback is not working anymore. My question is, how can I detect hv reconnect (I guess it's happening in background) so I know when to reinitialize callbacks? Thanks. BR Daniel Kucera.

3 7

[libvirt-users] Poor network performance
by Sławomir Kapłoński 16 May '17

16 May '17

Hello, I have some problem with poor network performance on libvirt with qemu and openvswitch. I’m using libvirt 1.3.1, qemu 2.5 and openvswitch 2.6.0 on Ubuntu 16.04 currently. My connection diagram looks like below: +---------------------------+ +---------------------------+ | Net namespace | +------------------+ | OVS bridge | | | | | | | | | | VM | | | | | | | +----+---+ +----+-----+ +----+---+ | | +------+tap dev | | veth A +---------+ veth B | | | | +--------+ +----------+ +--------+ | | iperf -s<---------------------------------------------------------------------------+iperf -c | | | | | | | +------------------+ | | | | | | | | +---------------------------+ +---------------------------+ I haven’t got any QoS in tc configured on any interface. When I do this iperf test I have something about 150Mbps only. IMHO it should be something about 20-30 Gbps there. Other strange thing is that if I made more such VMS (each connected in same way, with own OVS bridge and own namespace) bandwidth is lower for each of them and it looks for me that summarize bandwidth is then something about 1Gbps (30 VMs - each got something about 30Mbps in such test). When I removed VM and added „tap dev” as internal port in OVS and made same test, then I had result about 30 Gbps. I have no idea what can be wrong there. Maybe someone of You had such problems earlier? One more thing, on different host with Ubuntu 14.04, OVS 2.0.2, Libvirt 1.3.1 and qemu 2.3 I don’t have this problem. Kernel on both hosts is 4.4.0 (from Ubuntu repo). Pozdrawiam / Best regards Sławek Kapłoński slawek(a)kaplonski.pl

2 3