- Users - libvirt List Archives

[libvirt-users] using LVM thin pool LVs as a storage for libvirt guest
by Jan Hutař 07 Nov '17

07 Nov '17

Hello, as usual, I'm few years behind trends so I have learned about LVM thin volumes recently and I especially like that your volumes can be "sparse" - that you can have 1TB thin volume on 250GB VG/thin pool. Is it somehow possible to use that with libvirt? I have found this post from 2014: https://www.redhat.com/archives/libvirt-users/2014-August/msg00010.html which says you should be able to create "sparse" volume with `virsh vol-create ...` or that libvirt should be able to see thin volumes you create yourself, but neither of that works for me (libvirt-3.2.1-6.fc26.x86_64). This way I try to create new: # vgs storage VG #PV #LV #SN Attr VSize VFree storage 1 1 0 wz--n- 267.93g 0 # lvs storage -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert [lvol0_pmspare] storage ewi------- 68.00m lvol1 storage twi-aotz-- 267.80g 0.00 0.44 [lvol1_tdata] storage Twi-ao---- 267.80g [lvol1_tmeta] storage ewi-ao---- 68.00m # virsh pool-dumpxml storage <pool type='logical'> <name>storage</name> <uuid>f523aed2-a7e4-4dc2-88db-0193a7337704</uuid> <capacity unit='bytes'>287687311360</capacity> <allocation unit='bytes'>287687311360</allocation> <available unit='bytes'>0</available> <source> <device path='/dev/nvme0n1p3'/> <name>storage</name> <format type='lvm2'/> </source> <target> <path>/dev/storage</path> </target> </pool> # cat /tmp/big.xml <volume> <name>big</name> <capacity>1073741824</capacity> <allocation>1048576</allocation> <target> <path>/dev/storage/big</path> </target> </volume> # virsh vol-create storage /tmp/big.xml error: Failed to create vol from /tmp/big.xml error: internal error: Child process (/usr/sbin/lvcreate --name big -L 1024K --type snapshot --virtualsize 1048576K storage) unexpected exit status 5: Volume group "storage" has insufficient free space (0 extents): 1 required. When I create thin volume manually, I do not see it: # lvcreate -n big -V 500G --thinpool storage/lvol1 Using default stripesize 64.00 KiB. WARNING: Sum of all thin volume sizes (500.00 GiB) exceeds the size of thin pool storage/lvol1 and the size of whole volume group (267.93 GiB)! For thin pool auto extension activation/thin_pool_autoextend_threshold should be below 100. Logical volume "big" created. # lvs storage -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert big storage Vwi-a-tz-- 500.00g lvol1 0.00 [lvol0_pmspare] storage ewi------- 68.00m lvol1 storage twi-aotz-- 267.80g 0.00 0.45 [lvol1_tdata] storage Twi-ao---- 267.80g [lvol1_tmeta] storage ewi-ao---- 68.00m # virsh vol-list storage Name Path ------------------------------------------------------------------------------ Do I understand the concept incorrectly, or is there something else to configure? At the end I want to get max IO performance with possibility to "overcommit disk space". I know I can use storage "dir", but thought there might be something faster? Thank you very much for a response, Jan -- Jan Hutar Systems Management QA jhutar(a)redhat.com Red Hat, Inc.

3 4

[libvirt-users] this function is not supported by the connection driver: virInterfaceDefineXML
by netsurfed 07 Nov '17

07 Nov '17

Hi all: I'm facing problems trying to define a bridge on Ubuntu 16.04, using libvirt 3.4.0. When I try to do: root@ubuntu-180:/tmp# virsh iface-define iface-testbr1.xml I get the following error: error: Failed to define interface from iface-testbr1.xml error: this function is not supported by the connection driver: virInterfaceDefineXML What can i do to make this function works normally? THX. The xml file as: <interface type='bridge' name='testbr1'> <mtu size='1500'/> <bridge stp='on' delay='1500'> <interface type='ethernet' name='enp9s0'> <link speed='1000' state='up'/> <mac address='0c:c4:7a:c1:63:17'/> </interface> </bridge> </interface> root@ubuntu-180:/tmp# uname -a Linux ubuntu-180 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

2 1

Re: [libvirt-users] Live Migration Issue
by Hans Knecht 07 Nov '17

07 Nov '17

Sorry, ctrl entered. I'm hoping someone here can help me figure out what's going on here. I've got two CentOS 7 hosts with shared storage that I'm trying to do live migrations between and I'm running into an error with VMs that were originally created on a CentOS 6 host and then moved the CentOS 7 hosts. The CentOS 6 VM runs fine on the host, and can do non-live migrations without any issues, however when attempting to live migrate the VM it fails. The VM itself is CentOS 7. Live migration does work when using VMs created using CentOS 7. Error message: "libvirtd virKeepAliveTimerInternal connection closed due to keep alive timeout. Cannot acquire state change lock (held by remoteDispatchDomainMigratePrepare3params)" Surrounding error messages here: Origin Host: https://pastebin.com/fLN6DRiq Recipient Host: https://pastebin.com/xR6mnaW2 The command being run is: Virsh --connect qemu:///system migrate --live vmname qemu+SSH://host2/system Firewall is turned off, SELinux is turned off, CentOS 7 CPUs are identical, both hosts fully updated. I've tried: Converting the VM from QCOW2 to Raw Converting the VM from QCOW2 to QCOW2 to try to get it to regenerate the XML/inject CentOS 7 Drivers Installed new drivers Updated all the packages in the VM. Removed all the Devices from the VM, except the HDDs. Hans Knecht - DevOps Network Administrator Kinsale Insurance Company I 2221 Edward Holland Drive I Suite 600 I Richmond, VA 23230 (804) 289-1300 x5102 office I (804) 673-5697 fax I <mailto:hans.knecht@kinsaleins.com> hans.knecht(a)kinsaleins.com I www.kinsaleins.com From: Hans Knecht [mailto:hans.knecht@kinsaleins.com] Sent: Monday, November 06, 2017 8:38 AM To: 'libvirt-users(a)redhat.com' <libvirt-users(a)redhat.com> Subject: Live Migration Issue I'm hoping someone here can help me figure out what's going on here. I've got two CentOS 7 hosts with shared storage that I'm trying to do live migrations between and I'm running into an error with VMs that were originally created on a CentOS 6 host and then moved the CentOS 7 hosts. The CentOS 6 VM runs fine on the host, and can do non-live migrations without any issues, however when attempting to live migrate the VM it fails with the following error message: Hans Knecht - DevOps Network Administrator Kinsale Insurance Company I 2221 Edward Holland Drive I Suite 600 I Richmond, VA 23230 (804) 289-1300 x5102 office I (804) 673-5697 fax I <mailto:hans.knecht@kinsaleins.com> hans.knecht(a)kinsaleins.com I www.kinsaleins.com <http://www.kinsaleins.com/> This communication constitutes an electronic communication within the meaning of the Electronic Communications Privacy Act, 19 USC 2510, and its disclosure is strictly limited to the recipient intended by the sender of this message. This communication may contain confidential and privileged material for the sole use of the intended recipient and the disclosure to anyone other than the intended recipient does not constitute a loss of the confidential or privileged nature of the communication. If you are not the intended recipient, please contact the sender by return electronic mail and delete all copies of this communication. Please check for any defects or viruses before opening or using any attachments. There is no warranty that this e-mail is virus free or without error. No Kinsale Company is liable if an attachment is altered without its written consent. Thank you.

2 1

[libvirt-users] Has libvirt guest pagecache level ?
by mxs kolo 06 Nov '17

06 Nov '17

Greetings Has libvirt dedicated page cache area for guest ? If not - what is the difference between cache='none' and cache='directsync' ? >The optional cache attribute controls the cache mechanism, possible >values are "default", "none", "writethrough", "writeback", "directsync" >(like "writethrough", but it bypasses the host page cache) and >"unsafe" (host may cache all disk io, and sync requests from guest >are ignored). As I understand 'unsafe' - always remove flags O_SYNC|O_DIRECT fron guest level. What about other cache options - how it work ? Would be glad see any schema or description, if You have. b.r. Maxim Kozin

1 0

[libvirt-users] Live Migration Issue
by Hans Knecht 06 Nov '17

06 Nov '17

I'm hoping someone here can help me figure out what's going on here. I've got two CentOS 7 hosts with shared storage that I'm trying to do live migrations between and I'm running into an error with VMs that were originally created on a CentOS 6 host and then moved the CentOS 7 hosts. The CentOS 6 VM runs fine on the host, and can do non-live migrations without any issues, however when attempting to live migrate the VM it fails with the following error message: Hans Knecht - DevOps Network Administrator Kinsale Insurance Company I 2221 Edward Holland Drive I Suite 600 I Richmond, VA 23230 (804) 289-1300 x5102 office I (804) 673-5697 fax I <mailto:hans.knecht@kinsaleins.com> hans.knecht(a)kinsaleins.com I www.kinsaleins.com <http://www.kinsaleins.com/> This communication constitutes an electronic communication within the meaning of the Electronic Communications Privacy Act, 19 USC 2510, and its disclosure is strictly limited to the recipient intended by the sender of this message. This communication may contain confidential and privileged material for the sole use of the intended recipient and the disclosure to anyone other than the intended recipient does not constitute a loss of the confidential or privileged nature of the communication. If you are not the intended recipient, please contact the sender by return electronic mail and delete all copies of this communication. Please check for any defects or viruses before opening or using any attachments. There is no warranty that this e-mail is virus free or without error. No Kinsale Company is liable if an attachment is altered without its written consent. Thank you.

1 0

[libvirt-users] What global_quota option mean? What's its logic?
by Volo M. 03 Nov '17

03 Nov '17

Hi techs, Could you please explain or refer me to documentation where I could find a description of global_quota schedinfo option. Someone told me that it could mean a cpu limitation in percents like: global_quota : 25000 (does it mean cpu limit % set to 25 ?) Is it true? What other parameters mean in below output? I didn't find any related documentation at libvirt.org. Could you help me to describe me or refer to some description what below schedinfo options mean? Thanks. [root@cpkvm ~]# virsh list Id Name State ---------------------------------------------------- 3 kvmtestvm running [root@cpkvm ~]# virsh schedinfo 3 Scheduler : posix cpu_shares : 154 vcpu_period : 100000 vcpu_quota : -1 emulator_period: 100000 emulator_quota : -1 global_period : 100000 global_quota : -1 iothread_period: 100000 iothread_quota : -1 [root@cpkvm ~]# virsh schedinfo 3 --set global_quota=25 Scheduler : posix error: invalid argument: value of 'global_quota' is out of range [1000, 18446744073709551] [1000, 18446744073709551] - what this range mean? [root@cpkvm ~]# [root@cpkvm ~]# virsh schedinfo 3 --set global_quota=25000 Scheduler : posix cpu_shares : 154 vcpu_period : 100000 vcpu_quota : 12500 emulator_period: 100000 emulator_quota : -1 global_period : 100000 global_quota : 25000 iothread_period: 100000 iothread_quota : 25000 [root@cpkvm ~]#

3 2

[libvirt-users] net interface direct - no IP communication between guest & host
by lejeczek 01 Nov '17

01 Nov '17

hi everyone I wonder why, when I attach an interface like this: virsh # attach-interface --domain win10Ent --type direct --source nm-team --config --persistent --model virtio host cannot ip ping the guest and vice versa, yet guest can ping other nodes(outside of its host, connected via phys net via a switch) Would you know? I thought maybe routing on the host, so I did: $ route add -host 192.168.2.222 dev nm-team but to no avail. I wonder if it's lower layer, arp kernel bits? thanks, L.

2 2

[libvirt-users] libvirt/dnsmasq is not adhering to static DHCP assignments
by Dagmawi Biru 31 Oct '17

31 Oct '17

Given the following network configuration: =========== <network> <name>osc_mgmt</name> <uuid>d93fe709-14ae-4a0e-8989-aeaa8c76c513</uuid> <forward mode='route'/> <bridge name='osc_mgmt' stp='on' delay='0'/> <mac address='52:54:00:3f:fe:10'/> <ip address='192.168.80.254' netmask='255.255.255.0'> <dhcp> <range start='192.168.80.1' end='192.168.80.200'/> <host mac='52:54:00:2c:85:92' name='openstack-controller-00' ip='192.168.80.1'/> <host mac='52:54:00:e2:4b:25' name='openstack-database-00' ip='192.168.80.2'/> <host mac='52:54:00:50:91:04' name='openstack-keystone-00' ip='192.168.80.3'/> <host mac='52:54:00:fe:5b:36' name='openstack-rabbitmq-00' ip='192.168.80.7'/> <host mac='52:54:00:95:ca:bd' name='openstack-glance-00' ip='192.168.80.5'/> </dhcp> </ip> </network> When attempting to bring up the relevant interface in the virtual machine, I get an incorrect IP address assigned, different from the one I statically set up per the XML above. As you can see, the device with MAC '52:54:00:e2:4b:25' should really be getting 192.168.80.2, but what happens when we bring this interface up is this: =========== root@openstack-database-00:/home/osc# ifup ens11 Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/ens11/... Sending on LPF/ens11/... Sending on Socket/fallback DHCPDISCOVER on ens11 to 255.255.255.255 port 67 interval 3 (xid=0x6769e42a) DHCPREQUEST of 192.168.80.27 on ens11 to 255.255.255.255 port 67 (xid=0x2ae46967) DHCPOFFER of 192.168.80.27 from 192.168.80.254 DHCPACK of 192.168.80.27 from 192.168.80.254 bound to 192.168.80.27 -- renewal in 1407 seconds. Some additional info about the VM and network it's attached to =========== [root@dragon dnsmasq]# virsh domiflist openstack-database-00 Interface Type Source Model MAC ------------------------------------------------------- vnet12 bridge br20 virtio 52:54:00:6c:ce:b9 vnet13 network VM_MGMT rtl8139 52:54:00:7d:ca:87 vnet14 network osc_mgmt rtl8139 52:54:00:e2:4b:25 [root@dragon dnsmasq]# virsh net-info osc_mgmt Name: osc_mgmt UUID: d93fe709-14ae-4a0e-8989-aeaa8c76c513 Active: yes Persistent: yes Autostart: yes Bridge: osc_mgmt =========== What's strange is that the first VM seems to work correctly and gets an assigned address of 192.168.80.1, but for some reason the others don't. Any ideas?

3 3

[libvirt-users] guest state "in shutdown"
by Lying 30 Oct '17

30 Oct '17

Hello,I just encountered a problem my virtual machine is not a normal shutdown and I get state is "in shutdown" when i check it using "virsh list --all" why i get the error state,and how i should solve it?

1 0

[libvirt-users] guest cost long time to boot
by 柘龙义 26 Oct '17

26 Oct '17

hello, my virtual guest always cost long times to boot, all device load finish ,but still cost 15s to make display light

1 0

Re: [libvirt-users] Need to increase the rx and tx buffer size of my interface
by Ashish Kurian 26 Oct '17

26 Oct '17

Hi Yalan, In the previous email you mentioned "tx_queue_size='512' will not work in the guest with direct type interface, in fact, no matter what you set, it will not work and guest will get the default '256'. " So if I am using macvtap for my interfaces, then the device type will always be direct type. Does it mean that there is no way I can increase the buffer size with the macvtap interfaces? Best Regards, Ashish Kurian On Thu, Oct 26, 2017 at 9:04 AM, Ashish Kurian <ashishbnv(a)gmail.com> wrote: > Hi Yalan, > > Thank you for your comment on qemu-kvm-rhev > > I am waiting for a response about my previous email with the logs > attached. I do not understand what is the problem. > > > On Oct 26, 2017 8:58 AM, "Yalan Zhang" <yalzhang(a)redhat.com> wrote: > > Hi Ashish, > > Please never mind for qemu-kvm-rhev. > qemu with the code base 2.10.0 will support the tx_queue_size and > rx_queue_size. > > Thank you~ > > > > > > ------- > Best Regards, > Yalan Zhang > IRC: yalzhang > Internal phone: 8389413 > > On Thu, Oct 26, 2017 at 2:22 PM, Yalan Zhang <yalzhang(a)redhat.com> wrote: > >> Hi Ashish, >> >> Are these packages available for free? How can I install them? >> => You did have vhost backend driver. Do not set <driver name='qemu'...>, >> by default it will use vhost as backend driver. >> >> Is it possible to have my interfaces with an IP address inside the VM to >> be bridged to the physical interfaces on the host? >> => Yes, you can create a linux bridge with physical interface connected, >> and use bridge type interface. Refer to https://libvirt.org/formatd >> omain.html#elementsNICSBridge >> direct type is also ok (but your host and guest have no access to each >> other). >> >> Is it also a possibility that I change the rx and tx buffer on the >> physical interface on the host and it is reflected automatically inside the >> VM as you said it will always receive the default value of the host? >> => No, it do not receive the default value of the host. It's the default >> value related with the virtual device driver on the guest. >> hostdev type interface will passthrough the physical interface or VF of >> the host to guest, it will get the device's parameters for rx and tx buffer. >> >> >> >> ------- >> Best Regards, >> Yalan Zhang >> IRC: yalzhang >> Internal phone: 8389413 >> >> On Thu, Oct 26, 2017 at 1:30 PM, Ashish Kurian <ashishbnv(a)gmail.com> >> wrote: >> >>> Hi Yalan, >>> >>> Thank you for your response. I do not have the following packages >>> installed >>> >>> vhost backend driver >>> qemu-kvm-rhev package >>> >>> Are these packages available for free? How can I install them? >>> >>> In my KVM VM, I must have an IP address to the interfaces that I am >>> trying to increasing the buffers. That is the reason I was using macvtap >>> (direct type interface). Is it possible to have my interfaces with an IP >>> address inside the VM to be bridged to the physical interfaces on the host? >>> >>> Is it also a possibility that I change the rx and tx buffer on the >>> physical interface on the host and it is reflected automatically inside the >>> VM as you said it will always receive the default value of the host? >>> >>> >>> Best Regards, >>> Ashish Kurian >>> >>> On Thu, Oct 26, 2017 at 6:45 AM, Yalan Zhang <yalzhang(a)redhat.com> >>> wrote: >>> >>>> Hi Ashish, >>>> >>>> I have tested with your xml in the first mail, and it works for rx_queue_size(see >>>> below). >>>> multiqueue need to work with vhost backend driver. And when you set >>>> "queues=1" it will ignored. >>>> >>>> Please check your qemu-kvm-rhev package, should be newer than >>>> qemu-kvm-rhev-2.9.0-16.el7_4.2 >>>> And the logs? >>>> >>>> tx_queue_size='512' will not work in the guest with direct type >>>> interface, in fact, no matter what you set, it will not work and guest will >>>> get the default '256'. >>>> We only support vhost-user backend to have more than 256. refer to >>>> https://libvirt.org/formatdomain.html#elementsNICSEthernet >>>> >>>> tx_queue_size >>>> The optional tx_queue_size attribute controls the size of virtio ring >>>> for each queue as described above. The default value is hypervisor >>>> dependent and may change across its releases. Moreover, some hypervisors >>>> may pose some restrictions on actual value. For instance, QEMU v2.9 >>>> requires value to be a power of two from [256, 1024] range. In addition to >>>> that, this may work only for a subset of interface types, e.g. >>>> aforementioned QEMU enables this option only for vhostuser type. Since >>>> 3.7.0 (QEMU and KVM only) >>>> multiqueue only supports vhost as backend driver. >>>> >>>> # rpm -q libvirt qemu-kvm-rhev >>>> libvirt-3.2.0-14.el7_4.3.x86_64 >>>> qemu-kvm-rhev-2.9.0-16.el7_4.9.x86_64 >>>> >>>> 1. the xml as below >>>> <interface type='direct'> >>>> <mac address='52:54:00:00:b5:99'/> >>>> <source dev='eno1' mode='vepa'/> >>>> <model type='virtio'/> >>>> <driver name='vhost' queues='5' rx_queue_size='512' >>>> tx_queue_size='512'> >>>> <host csum='off' gso='off' tso4='off' tso6='off' ecn='off' >>>> ufo='off' mrg_rxbuf='off'/> >>>> <guest csum='off' tso4='off' tso6='off' ecn='off' ufo='off'/> >>>> </driver> >>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' >>>> function='0x0'/> >>>> </interface> >>>> >>>> 2. after start the vm, check the qemu command line: >>>> *-netdev >>>> tap,fds=26:28:29:30:31,id=hostnet0,vhost=on,vhostfds=32:33:34:35:36* >>>> -device virtio-net-pci,csum=off,gso=off,host_tso4=off,host_tso6=off, >>>> host_ecn=off,host_ufo=off,mrg_rxbuf=off,guest_csum=off,guest >>>> _tso4=off,guest_tso6=off,guest_ecn=off,guest_ufo=off, >>>> *mq=on,vectors=12,rx_queue_size=512,tx_queue_size=512*,netdev=hostnet >>>> 0,id=net0,mac=52:54:00:00:b5:99,bus=pci.0,addr=0x3 >>>> >>>> 3. check on guest >>>> # ethtool -g eth0 >>>> Ring parameters for eth0: >>>> Pre-set maximums: >>>> RX: *512 ==> rx_queue_size works* >>>> RX Mini: 0 >>>> RX Jumbo: 0 >>>> TX: *256 ===> no change* >>>> Current hardware settings: >>>> RX: *512 **==> rx_queue_size works* >>>> RX Mini: 0 >>>> RX Jumbo: 0 >>>> TX: *256 ===> no change* >>>> >>>> # ethtool -l eth0 >>>> Channel parameters for eth0: >>>> Pre-set maximums: >>>> RX: 0 >>>> TX: 0 >>>> Other: 0 >>>> Combined: *5 ==> queues what we set* >>>> Current hardware settings: >>>> RX: 0 >>>> TX: 0 >>>> Other: 0 >>>> Combined: 1 >>>> >>>> >>>> If change to qemu as driver, >>>> # virsh edit rhel7 >>>> .. >>>> <interface type='direct'> >>>> <mac address='52:54:00:00:b5:99'/> >>>> <source dev='eno1' mode='vepa'/> >>>> <model type='virtio'/> >>>> <driver name='qemu' queues='5' rx_queue_size='512' >>>> tx_queue_size='512'> >>>> <host csum='off' gso='off' tso4='off' tso6='off' ecn='off' >>>> ufo='off' mrg_rxbuf='off'/> >>>> <guest csum='off' tso4='off' tso6='off' ecn='off' ufo='off'/> >>>> </driver> >>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' >>>> function='0x0'/> >>>> </interface> >>>> .. >>>> Domain rhel7 XML configuration edited. ==> the xml can validate and save >>>> >>>> # virsh start rhel7 >>>> Domain rhel7 started >>>> >>>> >>>> # virsh dumpxml rhel7 | grep /interface -B9 >>>> <source dev='eno1' mode='vepa'/> >>>> <target dev='macvtap0'/> >>>> <model type='virtio'/> >>>> *<driver name='qemu' queues='5' rx_queue_size='512' >>>> tx_queue_size='512'>* >>>> <host csum='off' gso='off' tso4='off' tso6='off' ecn='off' >>>> ufo='off' mrg_rxbuf='off'/> >>>> <guest csum='off' tso4='off' tso6='off' ecn='off' ufo='off'/> >>>> </driver> >>>> <alias name='net0'/> >>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' >>>> function='0x0'/> >>>> </interface> >>>> >>>> >>>> * -netdev tap,fds=26:28:29:30:31*,id=hostnet0 -device >>>> virtio-net-pci,csum=off,gso=off,host_tso4=off,host_tso6=off, >>>> host_ecn=off,host_ufo=off,mrg_rxbuf=off,guest_csum=off,guest >>>> _tso4=off,guest_tso6=off,guest_ecn=off,guest_ufo=off, >>>> *rx_queue_size=512,tx_queue_size=512*,netdev=hostnet0,id=net0,mac=52: >>>> 54:00:00:b5:99,bus=pci.0,addr=0x3 >>>> >>>> *"mq=on,vectors=12" is missing*, indicates there is no multiqueue >>>> >>>> and check on guest >>>> >>>> # ethtool -l eth0 >>>> Channel parameters for eth0: >>>> Pre-set maximums: >>>> RX: 0 >>>> TX: 0 >>>> Other: 0 >>>> Combined: 1 ==> no multiqueue >>>> Current hardware settings: >>>> RX: 0 >>>> TX: 0 >>>> Other: 0 >>>> Combined: 1 >>>> >>>> # ethtool -g eth0 >>>> Ring parameters for eth0: >>>> Pre-set maximums: >>>> RX: *512* >>>> RX Mini: 0 >>>> RX Jumbo: 0 >>>> TX: 256 >>>> Current hardware settings: >>>> RX: *512* >>>> RX Mini: 0 >>>> RX Jumbo: 0 >>>> TX: 256 >>>> >>>> >>>> >>>> >>>> ------- >>>> Best Regards, >>>> Yalan Zhang >>>> IRC: yalzhang >>>> Internal phone: 8389413 >>>> >>>> On Thu, Oct 26, 2017 at 2:33 AM, Ashish Kurian <ashishbnv(a)gmail.com> >>>> wrote: >>>> >>>>> Hi Michal, >>>>> >>>>> An update to what I have already said : when I try adding <driver >>>>> name='qemu' txmode='iothread' ioeventfd='on' event_idx='off' queues='1' >>>>> rx_queue_size='512' tx_queue_size='512'> although it showed me the error as >>>>> mentioned, when I checked the xml again I saw that <driver >>>>> name='qemu' txmode='iothread' ioeventfd='on' event_idx='off' > is added to >>>>> the interface. >>>>> >>>>> The missing parameters are : queues='1' rx_queue_size='512' >>>>> tx_queue_size='512' >>>>> >>>>> Best Regards, >>>>> Ashish Kurian >>>>> >>>>> On Wed, Oct 25, 2017 at 5:07 PM, Ashish Kurian <ashishbnv(a)gmail.com> >>>>> wrote: >>>>> >>>>>> Hi Michal, >>>>>> >>>>>> What I found was that when I restarted the machine and did a virsh >>>>>> edit command to see the xml config, I see that it is was not actually >>>>>> changed. This suggests why I saw 256 again after restarting. >>>>>> >>>>>> So now I tried again to edit the xml via virsh edit command and used >>>>>> the following to set the parameters. >>>>>> >>>>>> <driver name='qemu' txmode='iothread' ioeventfd='on' event_idx='off' >>>>>> queues='1' rx_queue_size='512' tx_queue_size='512'> >>>>>> </driver> >>>>>> >>>>>> It was not accepted and I got the error saying : >>>>>> >>>>>> >>>>>> error: XML document failed to validate against schema: Unable to >>>>>> validate doc against /usr/share/libvirt/schemas/domain.rng >>>>>> Extra element devices in interleave >>>>>> Element domain failed to validate content >>>>>> >>>>>> What does this imply? I have two more other interfaces and do I have >>>>>> to the same to them also? >>>>>> >>>>>> Btw, there are now logs generated now in the domain log or libvirtd >>>>>> log >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Best Regards, >>>>>> Ashish Kurian >>>>>> >>>>>> On Wed, Oct 25, 2017 at 2:50 PM, Michal Privoznik < >>>>>> mprivozn(a)redhat.com> wrote: >>>>>> >>>>>>> On 10/25/2017 01:53 PM, Ashish Kurian wrote: >>>>>>> > Dear Users/Developers, >>>>>>> > >>>>>>> > I am using a KVM Ubuntu VM as a degrader to apply specific delays >>>>>>> to >>>>>>> > incoming packets. As the delay for my packets can be higher than >>>>>>> 7.5 >>>>>>> > seconds, there is not enough buffer on my interface to buffer all >>>>>>> the >>>>>>> > packets. Therefore those overflowing packets are dropped in the >>>>>>> machine and >>>>>>> > not forwarded. >>>>>>> > >>>>>>> > When I tried to use the command ethtool -G ens8 rx 512 to >>>>>>> increase the >>>>>>> > buffer size, I get the following error. >>>>>>> > >>>>>>> > Cannot set device ring parameters: Operation not permitted >>>>>>> > >>>>>>> > I have kept the VM xml files as specified in the link : >>>>>>> > https://libvirt.org/formatdomain.html. The value that I kept in >>>>>>> my xml file >>>>>>> > is as follows. >>>>>>> > >>>>>>> > <interface type='direct'> >>>>>>> > <mac address='52:54:00:72:f9:eb'/> >>>>>>> > <source dev='enp7s0f0' mode='vepa'/> >>>>>>> > <model type='virtio'/> >>>>>>> > <driver name='vhost' queues='5' rx_queue_size='512' >>>>>>> > tx_queue_size='512'> >>>>>>> > <host csum='off' gso='off' tso4='off' tso6='off' ecn='off' >>>>>>> ufo='off' >>>>>>> > mrg_rxbuf='off'/> >>>>>>> > <guest csum='off' tso4='off' tso6='off' ecn='off' ufo='off'/> >>>>>>> > </driver> >>>>>>> > <address type='pci' domain='0x0000' bus='0x00' slot='0x08' >>>>>>> > function='0x0'/> >>>>>>> > </interface> >>>>>>> > <interface type='direct'> >>>>>>> > <mac address='52:54:00:00:b5:99'/> >>>>>>> > <source dev='enp7s0f1' mode='vepa'/> >>>>>>> > <model type='virtio'/> >>>>>>> > <driver name='vhost' queues='5' rx_queue_size='512' >>>>>>> > tx_queue_size='512'> >>>>>>> > <host csum='off' gso='off' tso4='off' tso6='off' ecn='off' >>>>>>> ufo='off' >>>>>>> > mrg_rxbuf='off'/> >>>>>>> > <guest csum='off' tso4='off' tso6='off' ecn='off' ufo='off'/> >>>>>>> > </driver> >>>>>>> > <address type='pci' domain='0x0000' bus='0x00' slot='0x09' >>>>>>> > function='0x0'/> >>>>>>> >>>>>>> So what does the qemu command line look like? You can find it in >>>>>>> either >>>>>>> libvirtd log or domain log. >>>>>>> >>>>>>> http://wiki.libvirt.org/page/DebugLogs >>>>>>> >>>>>>> Michal >>>>>>> >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> libvirt-users mailing list >>>>> libvirt-users(a)redhat.com >>>>> https://www.redhat.com/mailman/listinfo/libvirt-users >>>>> >>>> >>>> >>> >> > >

3 7

[libvirt-users] question about how to set rng device on vm
by Yalan Zhang 26 Oct '17

26 Oct '17

Hi Amos, I'm a libvirt QE, and I can not understand the setting on libvirt.org for rng device. Could you please help to explain a little? (The xml in https://libvirt.org/formatdomain.html#elementsRng) <devices> <rng model='virtio'> <rate period="2000" bytes="1234"/> <backend model='random'>/dev/random</backend>  <backend model='egd' type='udp'> *<source mode='bind' service='1234'/>* * <source mode='connect' host='1.2.3.4' service='1234'/>* </backend> </rng> </devices> How did it work with source mode='bind' and source mode='connect' together? which process on guest or host will act as server part, which for client part? One detail example: start a vm with below device, and no egd running on host: <rng model='virtio'> <backend model='egd' type='udp'> <source mode='bind' service='1234'/> <source mode='connect' host='127.0.0.1' service='1234'/> </backend> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </rng> qemu command line: -chardev udp,id=charrng0,host=127.0.0.1,port=1234,localaddr=,localport=1234 -object rng-egd,id=objrng0,chardev=charrng0 -device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x9 In my understanding the purpose of the rng device on guest is to provide guest a hardware RNG device /dev/hwrng which obtain seeds from the host. The source can be /dev/random on host, then the xml will be: <rng model='virtio'> <backend model='random'>/dev/random</backend> </rng> can be hardware on host: <rng model='virtio'> <backend model='random'>/dev/hwrng</backend> </rng> can be edg daemon running on host: <rng model='virtio'> <backend model='egd' type='tcp'> <source mode='connect' host='127.0.0.1' service='1234'/> </backend> </rng> (on host, there should be a egd daemon running on tcp 127.0.0.1:1234 # egd.pl --debug-client --nofork localhost:1234) Thank you very much and look forward for your response! ------- Best Regards, Yalan Zhang IRC: yalzhang Internal phone: 8389413

3 2

Re: [libvirt-users] terminating on signal 15 from pid 2146 (/usr/sbin/libvirtd)
by Matwey V. Kornilov 26 Oct '17

26 Oct '17

2017-10-20 17:14 GMT+03:00 Matwey V. Kornilov <matwey.kornilov(a)gmail.com>: > 2017-10-20 15:16 GMT+03:00 Martin Kletzander <mkletzan(a)redhat.com>: >> On Fri, Oct 20, 2017 at 03:07:19PM +0300, Matwey V. Kornilov wrote: >>> >>> 2017-10-20 14:59 GMT+03:00 Martin Kletzander <mkletzan(a)redhat.com>: >>>> >>>> On Thu, Oct 19, 2017 at 09:11:00PM +0300, Matwey V. Kornilov wrote: >>>>> >>>>> >>>>> Hello, >>>>> >>>>> I use libvirt 3.3.0 and qemu 2.9.0 >>>>> >>>>> My domain XML spec is the following: >>>>> >>>>> <domain type='qemu'> >>>>> <name>s390_generic</name> >>>>> <uuid>82b4d16e-b636-447e-9fda-41d44616bce8</uuid> >>>>> <memory unit='KiB'>1048576</memory> >>>>> <currentMemory unit='KiB'>1048576</currentMemory> >>>>> <vcpu placement='static'>1</vcpu> >>>>> <os> >>>>> <type arch='s390x' machine='s390-ccw-virtio-2.9'>hvm</type> >>>>> <boot dev='hd'/> >>>>> </os> >>>>> <clock offset='utc'/> >>>>> <on_poweroff>destroy</on_poweroff> >>>>> <on_reboot>restart</on_reboot> >>>>> <on_crash>destroy</on_crash> >>>>> <devices> >>>>> <emulator>/usr/bin/qemu-system-s390x</emulator> >>>>> <disk type='block' device='disk'> >>>>> <driver name='qemu' type='raw' cache='none' io='native'/> >>>>> <source dev='/dev/lvm_pda/libvirt_s390'/> >>>>> <target dev='vda' bus='virtio'/> >>>>> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0000'/> >>>>> </disk> >>>>> <disk type='file' device='cdrom'> >>>>> <driver name='qemu' type='raw'/> >>>>> <target dev='sda' bus='scsi'/> >>>>> <readonly/> >>>>> <address type='drive' controller='0' bus='0' target='0' unit='0'/> >>>>> </disk> >>>>> <controller type='scsi' index='0' model='virtio-scsi'> >>>>> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0002'/> >>>>> </controller> >>>>> <interface type='bridge'> >>>>> <mac address='52:54:00:e8:61:7e'/> >>>>> <source bridge='br0'/> >>>>> <model type='virtio'/> >>>>> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0001'/> >>>>> </interface> >>>>> <console type='pty'> >>>>> <target type='sclp' port='0'/> >>>>> </console> >>>>> <memballoon model='virtio'> >>>>> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0003'/> >>>>> </memballoon> >>>>> <panic model='s390'/> >>>>> </devices> >>>>> </domain> >>>>> >>>>> The issue is that when I try to start it, it starts and shutdowns >>>>> immediately: >>>>> >>>>> virsh # start s390_generic >>>>> Domain s390_generic started >>>>> >>>>> virsh # >>>>> >>>>> In the domain log file I see the following: >>>>> >>>>> 2017-10-19 18:10:21.633+0000: starting up libvirt version: 3.3.0, qemu >>>>> version: 2.9.0(openSUSE Leap 42.3), hostname: oak.local >>>>> LC_ALL=C >>>>> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin >>>>> QEMU_AUDIO_DRV=none /usr/bin/qemu-system-s390x -name >>>>> guest=s390_generic,debug-threads=on -S -object >>>>> >>>>> >>>>> secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-7-s390_generic/master-key.aes >>>>> -machine s390-ccw-virtio-2.9,accel=tcg,usb=off,dump-guest-core=off -m >>>>> 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid >>>>> 82b4d16e-b636-447e-9fda-41d44616bce8 -display none -no-user-config >>>>> -nodefaults -chardev >>>>> >>>>> >>>>> socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-7-s390_generic/monitor.sock,server,nowait >>>>> -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc >>>>> -no-shutdown -boot strict=on -device >>>>> virtio-scsi-ccw,id=scsi0,devno=fe.0.0002 -drive >>>>> >>>>> >>>>> file=/dev/lvm_pda/libvirt_s390,format=raw,if=none,id=drive-virtio-disk0,cache=none,aio=native >>>>> -device >>>>> >>>>> >>>>> virtio-blk-ccw,scsi=off,devno=fe.0.0000,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 >>>>> -drive if=none,id=drive-scsi0-0-0-0,readonly=on -device >>>>> >>>>> >>>>> scsi-cd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0 >>>>> -netdev tap,fd=26,id=hostnet0 -device >>>>> >>>>> >>>>> virtio-net-ccw,netdev=hostnet0,id=net0,mac=52:54:00:e8:61:7e,devno=fe.0.0001 >>>>> -chardev pty,id=charconsole0 -device >>>>> sclpconsole,chardev=charconsole0,id=console0 -device >>>>> virtio-balloon-ccw,id=balloon0,devno=fe.0.0003 -msg timestamp=on >>>>> 2017-10-19T18:10:21.701184Z qemu-system-s390x: -chardev >>>>> pty,id=charconsole0: char device redirected to /dev/pts/5 (label >>>>> charconsole0) >>>>> 2017-10-19T18:10:21.721299Z qemu-system-s390x: terminating on signal 15 >>>>> from pid 2146 (/usr/sbin/libvirtd) >>>>> 2017-10-19 18:10:21.985+0000: shutting down, reason=shutdown >>>>> >>>> >>>> You don't have much logging enabled, so there's not that much info. >>>> What's >>>> in >>>> the libvirtd.log? what is the status reason for the domain? I.e. output >>>> of >>>> `virsh domstate --reason` ? >>> >>> >>> How could I increase log level? There is nothing in libvirtd.log. >>> >> >> https://wiki.libvirt.org/page/DebugLogs > > Too much info for me... > > -- > With best regards, > Matwey V. Kornilov -- With best regards, Matwey V. Kornilov

2 5

[libvirt-users] How to assign to PCI slot 0
by Fortman, Andrew 26 Oct '17

26 Oct '17

Hi, I'm new to this group so bear with me. So I need to passthrough a pci device on a particular bus and slot to get Linux to recognize it correctly. I need pci bus 6, slot 0. However whenever I try to use this slot inside of virsh edit it complains: error: XML error: Invalid PCI address 0000:06:00.0. slot must be >= 1 Failed. Try again? [y,n,i,f,?]: Is there a way to work around this ? Like can I disable the strict XML checking or even run the qemu commands manually? Thanks, Andy

2 1

[libvirt-users] virsh does no longer respond to commands
by Dominik Psenner 26 Oct '17

26 Oct '17

Hi, after a recent live backup done with a snapshot, blockcommit failed and a subsequent (manual) blockjob abort got stuck. Now we are unable to do basic operations on the virtual machine like if it was frozen and when issuing another command we see the following: $ virsh shutdown $domain error: Failed to shutdown domain $domain error: Timed out during operation: cannot acquire state change lock (held by remoteDispatchDomainBlockJobAbort) $ virsh blockcommit $domain --active --pivot error: Timed out during operation: cannot acquire state change lock (held by remoteDispatchDomainBlockJobAbort) $ virsh blockjob $domain --abort error: Timed out during operation: cannot acquire state change lock (held by remoteDispatchDomainBlockJobAbort) Houston, we've got a problem. We have roughly 16 hours to fix this. Any help is appreciated! -- Dominik Psenner

2 4

[libvirt-users] Need to increase the rx and tx buffer size of my interface
by Ashish Kurian 26 Oct '17

26 Oct '17

Dear Users/Developers, I am using a KVM Ubuntu VM as a degrader to apply specific delays to incoming packets. As the delay for my packets can be higher than 7.5 seconds, there is not enough buffer on my interface to buffer all the packets. Therefore those overflowing packets are dropped in the machine and not forwarded. When I tried to use the command ethtool -G ens8 rx 512 to increase the buffer size, I get the following error. Cannot set device ring parameters: Operation not permitted I have kept the VM xml files as specified in the link : https://libvirt.org/formatdomain.html. The value that I kept in my xml file is as follows. <interface type='direct'> <mac address='52:54:00:72:f9:eb'/> <source dev='enp7s0f0' mode='vepa'/> <model type='virtio'/> <driver name='vhost' queues='5' rx_queue_size='512' tx_queue_size='512'> <host csum='off' gso='off' tso4='off' tso6='off' ecn='off' ufo='off' mrg_rxbuf='off'/> <guest csum='off' tso4='off' tso6='off' ecn='off' ufo='off'/> </driver> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </interface> <interface type='direct'> <mac address='52:54:00:00:b5:99'/> <source dev='enp7s0f1' mode='vepa'/> <model type='virtio'/> <driver name='vhost' queues='5' rx_queue_size='512' tx_queue_size='512'> <host csum='off' gso='off' tso4='off' tso6='off' ecn='off' ufo='off' mrg_rxbuf='off'/> <guest csum='off' tso4='off' tso6='off' ecn='off' ufo='off'/> </driver> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> After I saved the xml and redefined the machine and started it up, I checked to see if the buffers are increased. I still see that the buffers are as follows. Ring parameters for ens9: Pre-set maximums: RX: 4096 RX Mini: 0 RX Jumbo: 0 TX: 4096 Current hardware settings: RX: *256* RX Mini: 0 RX Jumbo: 0 TX: *256* How can I increase the buffer on my KVM VM? Best Regards, Ashish Kurian

3 6

[libvirt-users] virsh + remote VirtualBox
by Konstantin Suvorov 25 Oct '17

25 Oct '17

Hello, I have the following setup: 1. MacOS host with VirtualBox installed 2. Ubuntu 16.04 host with libvirt installed What I try to do: Manage VMs executed inside VirtualBox on host 1 with libvirt tools from host 2. I have vboxwebsrv up and running on my MacOS host. I can successfully manage VMs remotely (e.g. with phpvirtualbox). But libvirt (virsh in particular) doesn't work. Reading debug logs, manuals and numerous internet threads leads me to a conclusion, that libvirt does not support remote connection to VirtualBox directly and only via libvirtd daemon installed on the same remote host as VirtualBox. Is this correct? If my assumption is correct, why is that so? Why libvirt can't manage remote VirtualBox directly? Regards, Konstantin.

2 1

[libvirt-users] domain CPU topology
by llilulu 24 Oct '17

24 Oct '17

Hi When I create a domain from xml file, the vcpu number point in <vcpu/>, I not point <cpu><topology> in xml file, when allocate more than 2 vpcus, some(windows) system can't use all vcpu. But I point <cpu><topology sockets='1' cores='num' threads='1'/></cpu>. num is <vcpu>'num'</vcpu>. then whindows can use all vcpus. I want to know when no ponit <cpu><topology> ,what default cpu topology. if point cpu topology, what rule guide cpu topology, I find VMware Workstation can point cpu num,and core of per cpu. all cores is cpu*core.

1 0

[libvirt-users] libvirtd audit log
by llilulu 23 Oct '17

23 Oct '17

Hi I according to libvirt.org Audit log guide ,I install auditd in my system(ubuntu 16.04.2), but when I operate guest running in host, I can't not find guest audit log in /var/log/audit/audit.log, audit_level=1. when I change audit_level=2, I restart libvirtd, libvirtd start failed. Thanks

1 0

[libvirt-users] terminating on signal 15 from pid 2146 (/usr/sbin/libvirtd)
by Matwey V. Kornilov 20 Oct '17

20 Oct '17

Hello, I use libvirt 3.3.0 and qemu 2.9.0 My domain XML spec is the following: <domain type='qemu'> <name>s390_generic</name> <uuid>82b4d16e-b636-447e-9fda-41d44616bce8</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='s390x' machine='s390-ccw-virtio-2.9'>hvm</type> <boot dev='hd'/> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-s390x</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source dev='/dev/lvm_pda/libvirt_s390'/> <target dev='vda' bus='virtio'/> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0000'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='sda' bus='scsi'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='scsi' index='0' model='virtio-scsi'> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0002'/> </controller> <interface type='bridge'> <mac address='52:54:00:e8:61:7e'/> <source bridge='br0'/> <model type='virtio'/> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0001'/> </interface> <console type='pty'> <target type='sclp' port='0'/> </console> <memballoon model='virtio'> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0003'/> </memballoon> <panic model='s390'/> </devices> </domain> The issue is that when I try to start it, it starts and shutdowns immediately: virsh # start s390_generic Domain s390_generic started virsh # In the domain log file I see the following: 2017-10-19 18:10:21.633+0000: starting up libvirt version: 3.3.0, qemu version: 2.9.0(openSUSE Leap 42.3), hostname: oak.local LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-system-s390x -name guest=s390_generic,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-7-s390_generic/master-key.aes -machine s390-ccw-virtio-2.9,accel=tcg,usb=off,dump-guest-core=off -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 82b4d16e-b636-447e-9fda-41d44616bce8 -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-7-s390_generic/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device virtio-scsi-ccw,id=scsi0,devno=fe.0.0002 -drive file=/dev/lvm_pda/libvirt_s390,format=raw,if=none,id=drive-virtio-disk0,cache=none,aio=native -device virtio-blk-ccw,scsi=off,devno=fe.0.0000,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-scsi0-0-0-0,readonly=on -device scsi-cd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0 -netdev tap,fd=26,id=hostnet0 -device virtio-net-ccw,netdev=hostnet0,id=net0,mac=52:54:00:e8:61:7e,devno=fe.0.0001 -chardev pty,id=charconsole0 -device sclpconsole,chardev=charconsole0,id=console0 -device virtio-balloon-ccw,id=balloon0,devno=fe.0.0003 -msg timestamp=on 2017-10-19T18:10:21.701184Z qemu-system-s390x: -chardev pty,id=charconsole0: char device redirected to /dev/pts/5 (label charconsole0) 2017-10-19T18:10:21.721299Z qemu-system-s390x: terminating on signal 15 from pid 2146 (/usr/sbin/libvirtd) 2017-10-19 18:10:21.985+0000: shutting down, reason=shutdown What is the issue?

2 3

[libvirt-users] virsh configure bridge network
by Charlotte 20 Oct '17

20 Oct '17

i creat a docker-machine-kvm,now,virsh edit mymachine,there show : i don't know how configure, let my machine can accessed by public network. please help me

1 0

[libvirt-users] Fwd: terminating on signal 15 from pid 2146 (/usr/sbin/libvirtd)
by Matwey V. Kornilov 19 Oct '17

19 Oct '17

Hello, I use libvirt 3.3.0 and qemu 2.9.0 My domain XML spec is the following: <domain type='qemu'> <name>s390_generic</name> <uuid>82b4d16e-b636-447e-9fda-41d44616bce8</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='s390x' machine='s390-ccw-virtio-2.9'>hvm</type> <boot dev='hd'/> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-s390x</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source dev='/dev/lvm_pda/libvirt_s390'/> <target dev='vda' bus='virtio'/> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0000'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='sda' bus='scsi'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='scsi' index='0' model='virtio-scsi'> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0002'/> </controller> <interface type='bridge'> <mac address='52:54:00:e8:61:7e'/> <source bridge='br0'/> <model type='virtio'/> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0001'/> </interface> <console type='pty'> <target type='sclp' port='0'/> </console> <memballoon model='virtio'> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0003'/> </memballoon> <panic model='s390'/> </devices> </domain> The issue is that when I try to start it, it starts and shutdowns immediately: virsh # start s390_generic Domain s390_generic started virsh # In the domain log file I see the following: 2017-10-19 18:10:21.633+0000: starting up libvirt version: 3.3.0, qemu version: 2.9.0(openSUSE Leap 42.3), hostname: oak.local LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-system-s390x -name guest=s390_generic,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-7-s390_generic/master-key.aes -machine s390-ccw-virtio-2.9,accel=tcg,usb=off,dump-guest-core=off -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 82b4d16e-b636-447e-9fda-41d44616bce8 -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-7-s390_generic/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device virtio-scsi-ccw,id=scsi0,devno=fe.0.0002 -drive file=/dev/lvm_pda/libvirt_s390,format=raw,if=none,id=drive-virtio-disk0,cache=none,aio=native -device virtio-blk-ccw,scsi=off,devno=fe.0.0000,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-scsi0-0-0-0,readonly=on -device scsi-cd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0 -netdev tap,fd=26,id=hostnet0 -device virtio-net-ccw,netdev=hostnet0,id=net0,mac=52:54:00:e8:61:7e,devno=fe.0.0001 -chardev pty,id=charconsole0 -device sclpconsole,chardev=charconsole0,id=console0 -device virtio-balloon-ccw,id=balloon0,devno=fe.0.0003 -msg timestamp=on 2017-10-19T18:10:21.701184Z qemu-system-s390x: -chardev pty,id=charconsole0: char device redirected to /dev/pts/5 (label charconsole0) 2017-10-19T18:10:21.721299Z qemu-system-s390x: terminating on signal 15 from pid 2146 (/usr/sbin/libvirtd) 2017-10-19 18:10:21.985+0000: shutting down, reason=shutdown What is the issue? -- With best regards, Matwey V. Kornilov

1 0

[libvirt-users] "virsh define" modify xml configuration file
by d tbsky 19 Oct '17

19 Oct '17

hi: I upgrade my system from rhel 7.3 to 7.4. so libvirt upgrade to 3.2. I found command "virsh define vm.xml" sometimes modify "vm.xml". I thought the command will read vm.xml, not write to it. is this kind of behavior by design? for example vm.xml with the line <cpu mode='custom' match='exact'> will be replaced with <cpu mode='custom' match='exact' check='partial'> Regards, tbskyd

2 2

[libvirt-users] Can we disable write to /sys/fs/cgroup tree inside container ?
by mxs kolo 18 Oct '17

18 Oct '17

Hi all Each lxc container on node have mounted tmpfs for cgroups tree: [root-inside-lxc@tst1 ~]# mount | grep cgroups cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_prio,net_cls) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) It's by default, at least in my case. Problem is, that it's full cgroups tree - from hardware node and from all another containers on node. [root-inside-lxc@tst1 ~]# for i in `ls /sys/fs/cgroup/devices/machine.slice/machine-lxc*/devices.list`; do echo $i; cat $i; done /sys/fs/cgroup/devices/machine.slice/machine-lxc\x2d10297\x2dtst2.scope/devices.list c 1:3 rwm c 1:5 rwm c 1:7 rwm c 1:8 rwm c 1:9 rwm c 5:0 rwm c 5:2 rwm c 10:229 rwm b 253:6 rw c 136:* rwm /sys/fs/cgroup/devices/machine.slice/machine-lxc\x2d9951\x2dtst1.scope/devices.list c 1:3 rwm c 1:5 rwm c 1:7 rwm c 1:8 rwm c 1:9 rwm c 5:0 rwm c 5:2 rwm c 10:229 rwm b 253:7 rw c 136:* rwm Hardware node file, view inside tst1 container: [root-inside-lxc@tst1 ~]# cat /sys/fs/cgroup/devices/devices.list a *:* rwm What is best way to prevent viewing and editing of all cgroups structures except belonging to current lxc container (selinux, apparmor ) ? Why libvirt mount /sys/fs/cgroup/* inside container as rw ? We use kernel 3.10.0-693.2.2.el7.x86_64 and XFS and therefore our containers are privileged. Yes, we know that in such containers root can use SysRq at least for reboot hardware node. But problem with cgroups can be more hidden and cryptic. p.s. As show short test, root user can disable device zero on node [root-lxc@tst1 ~]# echo "c 1:5 rwm" > /sys/fs/cgroup/devices/devices.deny or all devices in another container [root-lxc@tst1 ~]# echo "a *:* rwm" > /sys/fs/cgroup/devices/machine.slice/machine-lxc\x2d10297\x2dtst2.scope/devices.deny b.r. Maxim Kozin

2 2

[libvirt-users] File option for smbios.
by Julio Faracco 18 Oct '17

18 Oct '17

Hi guys, Does anybody knows if there is an option to set a binary file for smbios? Currently, I'm doing this approach: <qemu:commandline> <qemu:arg value='-smbios'/> <qemu:arg value='file=/var/run/libvirt/qemu/smbios_type_1.bin'/> </qemu:commandline> Has libvirt a method as <smbios mode='host'/> ? -- Julio Cesar Faracco

1 0