[libvirt-users] [virtual interface] detach interface during boot succeed with no changes
by Yalan Zhang
Hi guys,
when I detach an interface from vm during boot (vm boot not finished), it
always fail. I'm not sure if there is an existing bug. I have
confirmed with someone that for disk, there is similar behavior, if
this is also acceptable?
# virsh destroy rhel7.2; virsh start rhel7.2 ;sleep 2; virsh
detach-interface rhel7.2 network 52:54:00:98:c4:a0; sleep 2; virsh
dumpxml rhel7.2 |grep /interface -B9
Domain rhel7.2 destroyed
Domain rhel7.2 started
Interface detached successfully
<address type='pci' domain='0x0000' bus='0x00' slot='0x06'
function='0x0'/>
</controller>
<interface type='network'>
<mac address='52:54:00:98:c4:a0'/>
<source network='default' bridge='virbr0'/>
<target dev='vnet0'/>
<model type='rtl8139'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03'
function='0x0'/>
</interface>
When I detach after the vm boot, expand the sleep time to 10, it will succeed.
# virsh destroy rhel7.2; virsh start rhel7.2 ;sleep 10; virsh
detach-interface rhel7.2 network 52:54:00:98:c4:a0; sleep 2; virsh
dumpxml rhel7.2 |grep /interface -B9
Domain rhel7.2 destroyed
Domain rhel7.2 started
Interface detached successfully
-------
Best Regards,
Yalan Zhang
IRC: yalzhang
Internal phone: 8389413
1 year, 10 months
[libvirt-users] Question about disabling UFO on guest
by Bao Nguyen
Hello everyone,
I would like to ask a question regarding to disable UFO of virtio vNIC in
my guest. I have read the document at https://libvirt.org/formatdomain.html
*host*
The csum, gso, tso4, tso6, ecn and ufo attributes with possible
values on and off can be used to turn off host offloading options. By
default, the supported offloads are enabled by QEMU. *Since 1.2.9 (QEMU
only)* The mrg_rxbuf attribute can be used to control mergeable rx buffers
on the host side. Possible values are on (default) and off. *Since 1.2.13
(QEMU only)*
*guest*
The csum, tso4, tso6, ecn and ufo attributes with possible
values on and off can be used to turn off guest offloading options. By
default, the supported offloads are enabl
ed by QEMU.
*Since 1.2.9 (QEMU only)*
Then I disabled UFO on my vNIC on guest as the following configuration
<devices>
<interface type='network'>
<source network='default'/>
<target dev='vnet1'/>
<model type='virtio'/>
<driver name='vhost' txmode='iothread' ioeventfd='on' event_idx='off'
queues='5' rx_queue_size='256' tx_queue_size='256'>
*<host gso='off' ufo='off' />*
*<guest ufo='off'/>*
</driver>
</interface>
</devices>
Then I reboot my node to get the change effect and it works. However, can I
disable the UFO without touching the host OS? or it always has to disable
on both host and guest like that?
Thanks,
Brs,
Natsu
3 years, 11 months
[libvirt-users] Using qemu active blockcommit results in 'Permission denied' error
by Marcus Hoffmann
Hello all,
I tried following this guide:
https://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit
Unfortunately when I try to do the final virsh blockcommit step I always
get the following error:
error: internal error: unable to execute QEMU command 'block-commit':
Could not reopen file: Permission denied
I checked directory und image file permissions, app-armor profiles (set
to complain mode for now.) and libvirt logs but nothing there gives me
any hints what might be going wrong.
This is on a debian buster system, using
libvirtd (libvirt) 5.0.0
qemu 3.1+dfsg-7
I would appreciate any hints on how to proceed/get more debug info on this.
Thanks!
Marcus
5 years, 1 month
[libvirt-users] Easy solution for custom firewall rules- is it possible?
by Joshua Kramer
Hello All-
I've looked in several places and haven't found an answer to this
question: is it possible to have libvirt add custom rules to iptables
for virtual network interfaces? I took a look at the "Firewall and
Network Filtering in Libvirt" page and it seems overly complicated for
what I want to do.
Given an interface virbr2 and its network 192.168.4.0/24, libvirt
installs the following rules in iptables. Essentially, these rules
will drop any packets for the interface virbr2 where the source or
destination is not on the 192.168.4.0/24 network.
-P FORWARD ACCEPT
-A FORWARD -d 192.168.4.0/24 -o virbr2 -j ACCEPT
-A FORWARD -s 192.168.4.0/24 -i virbr2 -j ACCEPT
-A FORWARD -i virbr2 -o virbr2 -j ACCEPT
-A FORWARD -o virbr2 -j REJECT --reject-with icmp-port-unreachable
-A FORWARD -i virbr2 -j REJECT --reject-with icmp-port-unreachable
I have a VPN server on the 4/24 network- and it hands out addresses in
the 8/24 network. So I would like libvirt to also create the
following rules in iptables:
-A FORWARD -d 192.168.8.0/24 -o virbr2 -j ACCEPT
-A FORWARD -s 192.168.8.0/24 -i virbr2 -j ACCEPT
I've tried creating direct rules in firewalld for the FORWARD_direct
chain. Firewalld happily creates those rules, but they are never
reached, because they fall AFTER the libvirt rules. I've also tried
creating an IP address on the virbr2 interface in the 8/24 network,
but that doesn't work either. How can I get this done?
Thanks!!
-JK
5 years, 1 month
[libvirt-users] logging of domains
by Lentes, Bernd
Hi,
recently i had some domains stopped without any obvious reason for me. Unfortunately i didn't find the cause.
I'd like to log information about the domains that i have more information the next time this will happen.
In /etc/libvirt/libvirtd.conf i have:
log_level = 3
log_outputs="3:file:/var/log/libvirt/libvirtd.log"
which creates enormous log files, but with logrotate and xz i can manage that. But i think this is just
related to libvirtd.
The logs for the domains under /var/log/libvirt/qemu are poor and very small, nearly no information.
Is there a way to be more verbose with the domains so that i may find helpful information in these logs when the domains stop for the next time ?
Thanks.
Bernd
--
Bernd Lentes
Systemadministration
Institut für Entwicklungsgenetik
Gebäude 35.34 - Raum 208
HelmholtzZentrum münchen
bernd.lentes(a)helmholtz-muenchen.de
phone: +49 89 3187 1241
phone: +49 89 3187 3827
fax: +49 89 3187 2294
http://www.helmholtz-muenchen.de/idg
wer Fehler macht kann etwas lernen
wer nichts macht kann auch nichts lernen
Helmholtz Zentrum Muenchen
Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH)
Ingolstaedter Landstr. 1
85764 Neuherberg
www.helmholtz-muenchen.de
Stellv. Aufsichtsratsvorsitzender: MinDirig. Dr. Manfred Wolter
Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Heinrich Bassler, Kerstin Guenther
Registergericht: Amtsgericht Muenchen HRB 6466
USt-IdNr: DE 129521671
5 years, 1 month
[libvirt-users] libvirt blkiotune mechanism
by Maksym Isaiev
Hello!
We are using oVirt in our infrastructure, which uses libvirt as backend. Last time we needed to activate storage QoS aka libvirt blkiotune parameters. So some questions appeared about how libvirt limitation mechanism works:
1. What happened to overlimit storage traffic in small time period after we apply blkiotune parameters on high loaded virtual machine on fly:
a) All over-limit traffic pulled into some queue, where all disk transactions can be successfully finished with QoS throughput?
b) All over-limitation data dropped and opened transactions state became failed?
c) All active transactions finishes on speed beyond blkiotune parameters limit, but all new transactions immediately are limited based on configured limits?
Thanks in advance!
5 years, 1 month
[libvirt-users] Snapshot of single block device
by jarek
Hello!
I have a guest with one qcow2 disk image (vda) and one physical
partition (sda) from host. When I'm trying to get snapshot with:
virsh snapshot-create-as .....
It fails with message: error: unsupported configuration: source for
disk 'sda' is not a regular file; refusing to generate external
snapshot name
I understand, that it is not possible to make a snapshot of physical
device, but it is enough for me to take snapshot of vda. How to force
virsh to ignore sda ?
best regards
Jarek
5 years, 2 months
[libvirt-users] [Libvirt failed to claim Virtual Functions on hostdev network after VM reboot]
by Fuzail Ahmad
Problem Statement:
Libvirt failed to claim Virtual Functions on hostdev network after VM
reboot.
Version-Release number of selected component (if applicable):
libvirtd (libvirt) 2.0.0
kernel-4.1.12-112.16.4.el7uek.x86_64
Reproducible: Not always
Description:
I am doing a reboot of Virtual machines and sometimes one of the VM
does not start and fail with the following error
In total I have spun 3 VMs out of which 2 gets started and 1 of them
fail with the below error.
[root@sriov2 ~]# virsh start VM3
error: Failed to attach interface
error: internal error: network 'hostnet' requires exclusive access to
interfaces, but none are available
[root@sriov2 ~]# virsh net-dumpxml hostnet
<network connections='2'>
<name>hostnet</name>
<uuid>c1fb4ead-21b8-4d69-8ad9-669c55b3dfc7</uuid>
<forward mode='hostdev' managed='yes'>
<address type='pci' domain='0x0000' bus='0x0f' slot='0x10' function='0x0'/>
<address type='pci' domain='0x0000' bus='0x0f' slot='0x10' function='0x2'/>
</forward>
</network>
However, "ip link show" command shows 8 VFs in total.
# ip link show ens2
ens2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP
mode DEFAULT qlen 1000
link/ether 00:0a:f7:d5:a7:50 brd ff:ff:ff:ff:ff:ff
vf 0 MAC 52:54:00:6d:7c:a0, spoof checking off, link-state auto
vf 1 MAC 52:54:00:44:c9:b6, spoof checking off, link-state auto
vf 2 MAC 52:54:00:30:7a:86, spoof checking off, link-state auto
vf 3 MAC c6:9a:1b:82:90:ea, spoof checking off, link-state auto
vf 4 MAC 46:db:e2:33:c7:a4, spoof checking off, link-state auto
vf 5 MAC 76:65:e1:f7:82:78, spoof checking off, link-state auto
vf 6 MAC 8e:a0:8b:e5:1a:66, spoof checking off, link-state auto
vf 7 MAC ba:f4:83:19:80:bf, spoof checking off, link-state auto
#
Please, letme know if I need to attach any additional information.
Regards
Fuzail
5 years, 2 months
[libvirt-users] libvirtd not starting
by Lothar Schilling
Hi everybody,
I've set up an new CentOS 7.6.1810 server. Then, via yum I installed
qemu-kvm libvirt libvirt-python libguestfs-tools virt-install. There
were no problems. But when I try to
systemctl start libvirtd
I get the following message:
"libvirtd: process 472: arguments to dbus_message_iter_append_basic()
were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed
in file ../../dbus/dbus-message.c line 2754."
Starting libvirtd manually just by issuing the command "libvirtd"
without any further arguments is working, though.
I do not have the slightest idea what is going on, especially as I
didn't change anything about the config files.
Any help would be appreciated, thank you
Lothar Schilling
5 years, 2 months
