- Users - libvirt List Archives

[libvirt-users] Create qcow2 v3 volumes via libvirt
by Gionatan Danti 24 May '18

24 May '18

Hi all, on a fully patched CentOS 7.4 x86-64, I see the following behavior: - when creating a new volumes using vol-create-as, the resulting file is a qcow2 version 2 (compat=0.10) file. Example: [root@gdanti-lenovo vmimages]# virsh vol-create-as default zzz.qcow2 8589934592 --format=qcow2 --backing-vol /mnt/vmimages/centos6.img Vol zzz.qcow2 created [root@gdanti-lenovo vmimages]# file zzz.qcow2 zzz.qcow2: QEMU QCOW Image (v2), has backing file (path /mnt/vmimages/centos6.img), 8589934592 bytes [root@gdanti-lenovo vmimages]# qemu-img info zzz.qcow2 image: zzz.qcow2 file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 196K cluster_size: 65536 backing file: /mnt/vmimages/centos6.img backing file format: raw Format specific information: compat: 0.10 refcount bits: 16 - when creating a snapshot, the resulting file is a qcow2 version 3 (comapt=1.1) file. Example: [root@gdanti-lenovo vmimages]# virsh snapshot-create-as centos6left --disk-only --no-metadata snap.qcow2 Domain snapshot snap.qcow2 created [root@gdanti-lenovo vmimages]# file centos6left.snap.qcow2 centos6left.snap.qcow2: QEMU QCOW Image (v3), has backing file (path /mnt/vmimages/centos6left.qcow2), 8589934592 bytes [root@gdanti-lenovo vmimages]# qemu-img info centos6left.snap.qcow2 image: centos6left.snap.qcow2 file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 196K cluster_size: 65536 backing file: /mnt/vmimages/centos6left.qcow2 backing file format: qcow2 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false From what I know, this is a deliberate decision: compat=1.1 requires relatively recent qemu version, and creating a new volume play on the "safe side" of compatibility. It is possible to create a new volume using qcow2 version 3 (compat=1.1) format *using libvirt/virsh* (I know I can do that via qemu-img)? Any drawback on using version 3 format? Thanks. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti(a)assyoma.it - info(a)assyoma.it GPG public key ID: FF5F32A8

6 17

[libvirt-users] Unable to connect VMs to a bridge over bonded network on Debian 9 (works fine on Centos 7.4)
by Thing 23 May '18

23 May '18

Hi, Sorry of this is the wrong list, trying to find some help. I am trying to set up 2 KVM hosts using Debian 9 (connecting to a 3 node Centos 7.4 gluster cluster) To get the bandwidth I have bonded 2 NICS each end. However while the network works fine for the Debian VM host the VM guests cannot connect/get an IP using DHCP connecting to br0. (Same setup on the Centos end works fine however) On the Debian host if I connect to br1 which is a bridge to a NIC port it works fine. My problem then seems to be at the bonding layer for libvirt/kvm ? Here is my interfaces config, I cannot see the problem. The VM guest is on the gluster cluster and boots fine just no networking. any ideas what I am doing wrong pls? or a better group/list to go ask in? auto eno1 iface eno1 inet manual #iface eno1 inet static bond-master bond0 #address 192.168.1.62 #netmask 255.255.255.0 #gateway 192.168.1.1 #dns-nameservers 192.168.1.241 192.168.1.104 # mtu 9000 auto enp1s0f1 iface enp1s0f1 inet manual bond-master bond0 # mtu 9000 auto bond0 iface bond0 inet static bond-miimon 100 bond-mode 6 bond-updelay 200 bond-xmit_hash_policy layer3+4 bond-lacp-rate 1 # mtu 9000 # address 192.168.1.62 # netmask 255.255.255.0 # gateway 192.168.1.1 # dns-nameservers 192.168.1.241 192.168.1.104 slaves eno1 enp1s0f1 auto br0 iface br0 inet static address 192.168.1.62 netmask 255.255.255.0 gateway 192.168.1.1 dns-nameservers 192.168.1.241 192.168.1.104 bridge_ports bond0 #bridge_ports eno1 enp1s0f1 bridge_stp on bridge_fd 0.0 # mtu 9000 #post-up ifconfig bond0 mtu 9000 #post-up ip link set dev bond0 mtu 9000 #auto bond1 #iface bond1 inet static # address 10.100.200.62 # netmask 255.255.255.0 # bond_slaves enp3s0f1 # bond_primary enp3s0f1 # mtu 9000 auto br1 iface br1 inet static address 10.100.200.62 netmask 255.255.255.0 gateway 10.100.200.1 bridge_ports enp3s0f1 bridge_stp on bridge_fd 0.0 root@kvm02:/etc/network#

1 0

[libvirt-users] Attempting to use Secure Boot for Windows 10
by frizop f 22 May '18

22 May '18

Anybody have a guide on using secure boot? I managed to set */usr/share/edk2/ovmf/OVMF_CODE.secboot.fd* as the* <loader readonly='yes' type='pflash'>*, but when I change this windows only shows me a black screen. I've also tried to fiddle with the following two settings: *<type arch='x86_64' machine='pc-q35-2.10'>* I'm running fedora 27. Any advice on how to implement secure boot for a VM under KVM/Virt-Manager/qemu/etc etc. I found this https://en.opensuse.org/openSUSE:UEFI_Secure_boot_using_qemu-kvm but it doesn't seem to match up with what I'm seeing on a few different aspects, (obviously of which, is I'm not using SuSE) Anyway, any help at all on this would be greatly appreciated. Thanks! -frizop

1 0

[libvirt-users] Performance of guest
by Allence 22 May '18

22 May '18

I recently used Linux in VMware, but I discovered that kvm can replace it, so I created the kvm environment and then started a window on the host system. But when I use it, I have a problem. My guest's performance is not very good. For example, when I use Windows without kvm, the “lol” fps is 160, but my guest is only 135. why? I only have one guest what is the reason? What can we do to promote my performance? There are my some settings for me. timer: hypervclock cpu: 8 socket(intel@ core i7 7700k) memory: 16G GPU: 1060 network: virtio my environment: libvirt: 4.2 qemu: 2.12 windows: windows 7 host: ubuntu server 1604 If you need my detailed settings, please let me know.

2 2

[libvirt-users] the version between 2.5.0 and 3.0.0
by lizhuoyao 21 May '18

21 May '18

hi everyone: I found that the next version of libvirt-2.5.0 is 3.0.0 in https://gitlab.com/libvirt/libvirt/ or ftp://libvirt.org/libvirt/. Why? Is that the change between 2.5.0 and 3.0.0 is much?Then what is the change? -- Have a good day

2 1

[libvirt-users] Guest's CPU frequency cannot be similar to host system
by Allence 18 May '18

18 May '18

My resource: kernel: 4.16.8 host system: Ubuntu 16.04 Llbvirt : 4.2 Qemu : 2.12 Cpu : intel@core i7 6700 guest system: windows7 professional My problem: In my host, Cpu frequency is 3800~3900 MHz(4 socket and 2 thread) because i turn on “Intel Turbo Boost”. And silent frequency is 3.40 GHz. Then i boot my guest, But in Guest my cpu frequency is 3408 MHz. why it's not 3800 MHz? And here is my guest xml: <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='8' threads='1'/> </cpu>

2 2

[libvirt-users] changing pci addr of SCSI storage controller: Red Hat, Inc Virtio block device (rev 01)
by daggs 12 May '18

12 May '18

Greetings, when execute lspci inside my vm linux guest, I see this: :/# lspci | grep -i scsi 03:00.0 SCSI storage controller: Red Hat, Inc Virtio block device (rev 01) I don't see any such address in my xml file, is it possible to move that controller to another pci addr? Thanks, Dagg.

2 3

[libvirt-users] e1000 network interface takes a long time to set the link ready
by Ihar Hrachyshka 11 May '18

11 May '18

Hi, In kubevirt, we discovered [1] that whenever e1000 is used for vNIC, link on the interface becomes ready several seconds after 'ifup' is executed, which for some buggy images like cirros may slow down boot process for up to 1 minute [2]. If we switch from e1000 to virtio, the link is brought up and ready almost immediately. For the record, I am using the following versions: - L0 kernel: 4.16.5-200.fc27.x86_64 #1 SMP - libvirt: 3.7.0-4.fc27 - guest kernel: 4.4.0-28-generic #47-Ubuntu Is there something specific about e1000 that makes it initialize the link too slowly on libvirt or guest side? [1] https://github.com/kubevirt/kubevirt/issues/936 [2] https://bugs.launchpad.net/cirros/+bug/1768955 Ihar

4 6

Re: [libvirt-users] about python-libvirt
by Andrea Bolognani 10 May '18

10 May '18

[re-adding libvirt-users; please don't take replies off-list] On Thu, 2018-05-10 at 17:32 +0800, lizhuoyao wrote: > Thanks! > > But I'm not clear that what the language binding means? > What the relationship between they? Is that the code from > https://libvirt.org/sources/ can be replaced completely by > the code from https://libvirt.org/sources/python? Language bindings are the means through which libvirt, which is implemented in C, can be used from non-C languages such as Python. It's basically a bunch of glue code that allows Python code to call into C code. In order to use libvirt from Python, you need to have *both* libvirt itself *and* the Python bindings installed on the system: libvirt-python doesn't replace libvirt, and in fact can't work at all unless the C library is available as well. -- Andrea Bolognani / Red Hat / Virtualization

1 0

[libvirt-users] about python-libvirt
by lizhuoyao 10 May '18

10 May '18

hi boys： the libvirt code in ftp://libvirt.org does get the function of python-libvirt? Or the python-libvirt is another code ? -- Have a good day

3 2