September 2014 - Users - libvirt List Archives

[libvirt-users] some problem with snapshot by libvirt
by xingxing gao 21 Nov '14

21 Nov '14

Hi,all,i am using libvirt to manage my vm,in these days i am testing the libvirt snapshot ,but meet some problem: the snapshot was created from this command: snapshot-create-as win7 --disk-only --diskspec vda,snapshot=external --diskspec hda,snapshot=no but when i tried to revert from the snapshot which created from the above command ,i got error below: virsh # snapshot-revert win7 1338041515 --force error: unsupported configuration: revert to external disk snapshot not supported yet version: virsh # version Compiled against library: libvir 0.9.4 Using library: libvir 0.9.4 Using API: QEMU 0.9.4 Running hypervisor: QEMU 1.0.93

4 8

[libvirt-users] win2k8 guest and (strange) number of cpus task manager sees
by lejeczek 08 Oct '14

08 Oct '14

hi everybody a qemu-kvm guest gets 16 cpus and Windows in "Device Manager" sees all sixteeen but "Task Manager" shows only 4, the same "System" properties say "(4 processors)" I'd like to learn a bit about this - is it some sort of "resources management" on the libvirt/qemu causing this? And what does it do to a guest performance-wise side? it's on Scientific L 7, qemu-kvm-1.5.3-60.el7_0.7.x86_64 libvirt-1.1.1-29.el7_0.1.x86_64 regards P.

2 2

[libvirt-users] what is the xml fomat about memory-backend-file
by Linhaifeng 08 Oct '14

08 Oct '14

Hi, I want to use virsh to create a VM with the qemu parameter '-object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on -numa node,memdev=mem'. How to write the XML file?

3 4

[libvirt-users] libvirt-sandbox on Fedora 21
by Gene Czarcinski 07 Oct '14

07 Oct '14

It sure would be nice if someone who knows what they are doing took a look at this problem: https://bugzilla.redhat.com/show_bug.cgi?id=1135762 The current situation on Fedora 21 is that virt-sandbox and virt-sandbox-service simply do not work if a network is defined (e.g., -N address-192.168.1.1/34). I would give dhcp as an example but to work, that needs to patch I submitted in another BZ report. Since both virt-sandbox -c lxc:/// -N <network>,source=default and doing systemctl start <sandbox> result in the same error and since I am running the fedora-virt-preview rpms and the failure *does not* occur on Fedora 20 but *does* occur on Fedora 21, I have to assume that the problem is not directly in libvirt. However, determining what/where the problem really is, is stretching my abilities a bit too far ... help!! Gene

2 3

[libvirt-users] time setting after suspend/resume
by Bill Kenworthy 03 Oct '14

03 Oct '14

Hi, I am using libvirt with qemu/kvm with qemu-guest-agent and suspend/save/resume linux and windows vm's. Time in Windows gets handled fine with ntp but I can get neither ntp or chrony to sync after resume without manually setting the time close to correct first. Searching has gotten me to the point where I can manually set the time using qemu-guest-agent but I cant figure out how to get libvirt to automaticly trigger this on resume. I am finding information saying it works but not how, or that its still work in progress and not implemented yet (but patches exist). Can someone either say "its not working yet" or explain what I am missing please? BillK

3 7

[libvirt-users] increase number of libvirt threads by starting tansient guest doamin - is it a bug?
by ustermann78＠web.de 02 Oct '14

02 Oct '14

hello, if i start a transient guest doamin via "virsh create abcd.xml" i see an additional libvirt thread and also some open files: pstree -h `pgrep libvirtd` libvirtd───11*[{libvirtd}] libvirtd 3016 root 21w REG 253,0 6044 1052094 /var/log/libvirt/libxl/abcd.log libvirtd 3016 root 22r FIFO 0,8 0t0 126124 pipe libvirtd 3016 root 23w FIFO 0,8 0t0 126124 pipe libvirtd 3016 root 24u REG 0,37 0 4 /proc/xen/privcmd libvirtd 3016 root 25u unix 0xffff8807d2c3ad80 0t0 126125 socket libvirtd 3016 root 26r FIFO 0,8 0t0 126127 pipe libvirtd 3016 root 27w FIFO 0,8 0t0 126127 pipe libvirtd 3016 root 28r FIFO 0,8 0t0 124783 pipe libvirtd 3016 root 29w FIFO 0,8 0t0 124783 pipe libvirtd 3016 root 30r FIFO 0,8 0t0 127140 pipe libvirtd 3016 root 31w FIFO 0,8 0t0 127140 pipe if i destroy these vm via "virsh destroy abcd", i see that the additional thread still exists and also the list of openfiles is the same. if i start the transient guest domain again, i observe an increase in the number of libvirt threads ans also in the list of openfiles: [root@localhost libxl]# pstree -h `pgrep libvirtd` libvirtd───12*[{libvirtd}] libvirtd 3016 root 21w REG 253,0 13783 1052094 /var/log/libvirt/libxl/abcd.log libvirtd 3016 root 22r FIFO 0,8 0t0 126124 pipe libvirtd 3016 root 23w FIFO 0,8 0t0 126124 pipe libvirtd 3016 root 24u REG 0,37 0 4 /proc/xen/privcmd libvirtd 3016 root 25u unix 0xffff8807d2c3ad80 0t0 126125 socket libvirtd 3016 root 26r FIFO 0,8 0t0 126127 pipe libvirtd 3016 root 27w FIFO 0,8 0t0 126127 pipe libvirtd 3016 root 28r FIFO 0,8 0t0 124783 pipe libvirtd 3016 root 29w FIFO 0,8 0t0 124783 pipe libvirtd 3016 root 30r FIFO 0,8 0t0 127140 pipe libvirtd 3016 root 31w FIFO 0,8 0t0 127140 pipe libvirtd 3016 root 32w REG 253,0 13783 1052094 /var/log/libvirt/libxl/abcd.log libvirtd 3016 root 33r FIFO 0,8 0t0 129039 pipe libvirtd 3016 root 34w FIFO 0,8 0t0 129039 pipe libvirtd 3016 root 35u REG 0,37 0 4 /proc/xen/privcmd libvirtd 3016 root 36u unix 0xffff8807d398bb80 0t0 129040 socket libvirtd 3016 root 37r FIFO 0,8 0t0 129042 pipe libvirtd 3016 root 38w FIFO 0,8 0t0 129042 pipe libvirtd 3016 root 39r FIFO 0,8 0t0 129043 pipe libvirtd 3016 root 40w FIFO 0,8 0t0 129043 pipe libvirtd 3016 root 41r FIFO 0,8 0t0 129044 pipe libvirtd 3016 root 42w FIFO 0,8 0t0 129044 pipe if i destroy the doamin again and define them via "virsh define abcd.xml" and start them then via "virsh start abcd", the number of libvirtd threads don´t increase again and also the number of open files is the same. My question: is it normal that for transient guest domains the created libvirtd thread sill exists and also the open files after i destroy the doamin? or is it bug? thanks max

5 12

[libvirt-users] KVM resource analysis
by Adam King 30 Sep '14

30 Sep '14

Morning all, What is the recommended tool for resource analysis on hypervisors? Many thanks, Adam King IT Systems Administrator

2 2

[libvirt-users] PXE booting from specific vNIC using libvirt
by Pasquale Porreca 29 Sep '14

29 Sep '14

Hello I managed yet to create a KVM Virtual Machine with several network interfaces (vNICs) and to make it boot from network using PXE. Anyway I noticed that, if there is no answer from a pxe server on the first vNIC, the dhcp request is sent on every vNIC until it gets a response (or the vNIC list ends). I would like to know if there is a way to specify that the dhcp request should be triggered on a specific interface and if it fails stop or try again on same interface (if rebootTimeout is set). Best Regards -- Pasquale Porreca DEK Technologies Via dei Castelli Romani, 22 00040 Pomezia (Roma) Mobile +39 3394823805 Skype paskporr

1 0

[libvirt-users] Running the test fails virnetmessagetest with libvirt 1.2.8
by Stefano Ricci 29 Sep '14

29 Sep '14

Hello I apologize in advance for my English. I compiled the new version of libvirt 1.2.8 on an environment Development Linux from Scratch with the following configure: configure: Configuration summary configure: ===================== configure: configure: Drivers configure: configure: Xen: no configure: QEMU: yes configure: UML: yes configure: OpenVZ: no configure: VMware: no configure: VBox: yes configure: XenAPI: no configure: xenlight: no configure: LXC: no configure: PHYP: yes configure: ESX: no configure: Hyper-V: no configure: Parallels: no configure: Bhyve: no configure: Test: yes configure: Remote: yes configure: Network: yes configure: Libvirtd: yes configure: Interface: yes configure: macvtap: yes configure: virtport: yes configure: configure: Storage Drivers configure: configure: Dir: yes configure: FS: no configure: NetFS: no configure: LVM: yes configure: iSCSI: yes configure: SCSI: yes configure: mpath: yes configure: Disk: no configure: RBD: no configure: Sheepdog: no configure: Gluster: no configure: ZFS: no configure: configure: Security Drivers configure: configure: SELinux: yes (/sys/fs/selinux) configure: AppArmor: no (install profiles: no) configure: configure: Driver Loadable Modules configure: configure: dlopen: -ldl configure: configure: Libraries configure: configure: apparmor: no configure: attr: yes (CFLAGS='' LIBS='-lattr') configure: audit: no configure: avahi: no configure: blkid: yes (CFLAGS='-I/install/include/blkid -I/install/include/uuid ' LIBS='-L/install/lib -lblkid ') configure: capng: no configure: curl: no configure: dbus: yes (CFLAGS='-I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include ' LIBS='-ldbus-1 ') configure: fuse: yes (CFLAGS='-D_FILE_OFFSET_BITS=64 -I/usr/include/fuse ' LIBS='-lfuse -pthread ') configure: glusterfs: no configure: hal: no configure: netcf: no configure: numactl: no configure: openwsman: no configure: pciaccess: yes (CFLAGS='' LIBS='-lpciaccess ') configure: readline: yes (CFLAGS='' LIBS='-lreadline') configure: sanlock: no configure: sasl: yes (CFLAGS='' LIBS='-lsasl2') configure: selinux: yes (CFLAGS='' LIBS='-lselinux') configure: ssh2: yes (CFLAGS='' LIBS='-lssh2 ') configure: systemd_daemon: no configure: udev: yes (CFLAGS='' LIBS='-ludev ') configure: yajl: yes (CFLAGS='' LIBS='-lyajl') configure: libxml: -I/usr/include/libxml2 -lxml2 configure: dlopen: -ldl configure: openwsman: no configure: gnutls: -lgnutls configure: firewalld: no configure: polkit: no configure: xen: no configure: xenapi: no configure: xenlight: no configure: pcap: -I/usr/include -L/usr/lib -lpcap configure: nl: -I/usr/include/libnl3 -I/usr/include/libnl3 -lnl-3 -lnl-route-3 -lnl-3 configure: mscom: no configure: xdr: configure: rbd: no configure: pm-utils: yes configure: configure: Test suite configure: configure: Coverage: no configure: Alloc OOM: no configure: configure: Miscellaneous configure: configure: Debug: yes configure: Use -Werror: no configure: Warning Flags: -W -Waddress -Waggressive-loop-optimizations -Wall -Warray-bounds -Wattributes -Wbad-function-cast -Wbuiltin-macro-redefined -Wcast-align -Wchar-subscripts -Wclobbered -Wcomment -Wcomments -Wcoverage-mismatch -Wcpp -Wdeprecated-declarations -Wdisabled-optimization -Wdiv-by-zero -Wdouble-promotion -Wempty-body -Wendif-labels -Wextra -Wformat-contains-nul -Wformat-extra-args -Wformat-security -Wformat-y2k -Wformat-zero-length -Wfree-nonheap-object -Wignored-qualifiers -Wimplicit -Wimplicit-function-declaration -Wimplicit-int -Winit-self -Winline -Wint-to-pointer-cast -Winvalid-memory-model -Winvalid-pch -Wjump-misses-init -Wlogical-op -Wmain -Wmaybe-uninitialized -Wmissing-braces -Wmissing-declarations -Wmissing-field-initializers -Wmissing-include-dirs -Wmissing-parameter-type -Wmissing-prototypes -Wmultichar -Wnarrowing -Wnested-externs -Wnonnull -Wnormalized=nfc -Wold-style-declaration -Wold-style-definition -Woverflow -Woverride-init -Wpacked-bitfield-compat -Wparentheses -Wpointer-arith -Wpointer-sign -Wpointer-to-int-cast -Wpragmas -Wreturn-local-addr -Wreturn-type -Wsequence-point -Wshadow -Wsizeof-pointer-memaccess -Wstrict-aliasing -Wstrict-prototypes -Wsuggest-attribute=const -Wsuggest-attribute=format -Wsuggest-attribute=noreturn -Wsuggest-attribute=pure -Wswitch -Wsync-nand -Wtrampolines -Wtrigraphs -Wtype-limits -Wuninitialized -Wunknown-pragmas -Wunused -Wunused-but-set-parameter -Wunused-but-set-variable -Wunused-function -Wunused-label -Wunused-local-typedefs -Wunused-parameter -Wunused-result -Wunused-value -Wunused-variable -Wvarargs -Wvariadic-macros -Wvector-operation-performance -Wvolatile-register-var -Wwrite-strings -fdiagnostics-show-option -funit-at-a-time -Wno-sign-compare -Wjump-misses-init -Wno-format-nonliteral -Wframe-larger-than=4096 -fstack-protector-strong -fexceptions -fasynchronous-unwind-tables -fipa-pure-const -Wno-suggest-attribute=pure -Wno-suggest-attribute=const configure: DTrace: no configure: numad: no configure: XML Catalog: /etc/xml/catalog configure: Init script: check configure: Char device locks: /var/lock configure: configure: Developer Tools configure: configure: Wireshark dissector: no configure: configure: Privileges configure: configure: QEMU: root:root The compilation finishes without any problems but in the execution of the tests fails virnetmessagetest. When i tried using the libvirtd running without any problems but I can not run the Connection with the virsh command virsh -c qemu:///system that returns the following error: "Unable to encode message header" and the log shows the error: "virNetSocketReadWire: 1523: End of file while reading dates: Error of input / output". There 's someone who can give me a hand to solve the problem? thanks Stefano

1 1

Re: [libvirt-users] How to configure the container's NIC automatically with an assigned IP address
by WANG Cheng D 28 Sep '14

28 Sep '14

Dear Gene, Thank you for your response. I want to assign a static IP address to my container, I wonder if I can achieve this by editing the container's /etc/sysconfig/network-scripts/ifcfg-eth0. I tried this, but failed, and eth0 is always not assigned an IP address automatically (my host and guest are fedora19). Am I missing something? I don't know much about the booting procedure of a container, and how the network NIC is configured during the booting. The content of container's /etc/sysconfig/network-scripts/ifcfg-eth0 is as follows: BOOTPROTO="static" DEVICE="eth0" TYPE="Ethernet" ONBOOT="yes" IPADDR=192.168.128.15 PREFIX=24 GATEWAY=192.168.128.254 With my warmest regards, Cheng > Dear all, > > I want to run a TCP/IP application automatically after I start the > container using "virsh -c lxc:/// start mycontainer". Does anybody > know how to configure the NIC automatically with an assigned IP > address? I couldn't find useful information from domain XML format > spec and it only talks how to set the mac address > (http://libvirt.org/formatdomain.html) . > > Your response will be highly appreciated. > > Cheng > > Take a look at: http://sandbox.libvirt.org/networking/ Note: Specifying dhcp does not currently work. I have created a patch to fix that. See: https://bugzilla.redhat.com/show_bug.cgi?id=1133686

1 0