March 2013 - Users - libvirt List Archives

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

22 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] managedsave results in unexpected shutdown from inside Windows
by Nicolas Sebrecht 28 Jun '13

28 Jun '13

Hi, I'm facing a strange behaviour of windows 2008 guests. After a virsh managedsave and start, the windows guest open a "unexpected shutdown" window. The window looks like this one (randomly taken from the web): http://toastytech.com/guis/srv2k3login2.jpg This happens in all virtualized windows in a hypervisor. Has anyone else experienced such issue? Thanks, -- Nicolas Sebrecht

3 15

[libvirt-users] How to use xl (in place of xm) with libvirt 1.0.2 and Xen 4.2.1 in Ubuntu 13.04?
by Gizmo Chicken 21 May '13

21 May '13

QUESTION: What, if anything, can I do so that I can use xl (in place of xm) with libvirt 1.0.2 and Xen 4.2.1 in Ubuntu 13.04? BACKGROUND: I am testing a fully updated (as of March 27) installation of Ubuntu 13.04 that includes the following packages: libvirt - version 1.0.2-0ubuntu9 xen-hypervisor-4.2-amd64 - version 4.2.1-0ubuntu1 Upon setting TOOLSTACK=xm in /etc/default/xen (as well as making a few needed tweaks to /etc/xen/xend-config.sxp), libvirt and virt-manager worked great. Yippee! I guess that I should be happy that the xm toolstack still works with Xen 4.2.1 and quit while I'm ahead, but... According to libvirt's documentation: "libxl: Starting with Xen 4.2, the legacy XenD/xm toolstack is deprecated in favor of libxl, also commonly called libxenlight. libvirt supports this new Xen toolstack via the libxl driver. If XenD is enabled, the legacy xen driver consisting of the above mentioned channels will be used. If XenD is disabled, the libxl driver will be used." See http://libvirt.org/drvxen.html. In view of the above, I attempted to use xl in place xm by setting TOOLSTACK=xl in /etc/default/xen. And after doing so (both with and without, the above mentioned tweaks to /etc/xen/xend-config.sxp), I recieved the following error when attempting to start virt-manager: Unable to connect to libvirt. unable to connect to 'localhost:8000': Connection refused Verify that: - A Xen host kernel was booted - The Xen service has been started Libvirt URI is: xen:/// Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 1027, in _open_thread self.vmm = self._try_open() File "/usr/share/virt-manager/virtManager/connection.py", line 1009, in _try_open flags) File "/usr/lib/python2.7/dist-packages/libvirt.py", line 102, in openAuth if ret is None:raise libvirtError('virConnectOpenAuth() failed') libvirtError: unable to connect to 'localhost:8000': Connection refused

2 4

[libvirt-users] remote connection issue 'virsh -c qemu+ssh:///root@localhost/system list'
by Yin Olivia-R63875 09 Apr '13

09 Apr '13

Hi, I'm trying remote connection with qemu hypervisor on FSL PPC board. The libvirt server is the PPC board. root@ppc:~# ifconfig eth0 10.193.20.109 root@ppc:~# libvirtd -d root@ppc:~# virsh -c qemu:///system define test.xml root@ppc:~# virsh -c qemu:///system start test root@ppc:~# virsh -c qemu:///system list --all Id Name State ---------------------------------------------------- 2 test running Connect from an X86 PC (Ubuntu 10.04) to the PPC board. user@x86:~$ virsh -c qemu+ssh://root@10.193.20.109/system list --all The authenticity of host '10.193.20.109 (10.193.20.109)' can't be established. RSA key fingerprint is 2f:56:07:08:da:7d:ac:41:45:57:d2:12:15:19:67:e0. Are you sure you want to continue connecting (yes/no)? yes root(a)10.193.20.109's password: error: failed to connect to the hypervisor error: End of file while reading data: Warning: Permanently added '10.193.20.109' (RSA) to the list of known hosts. nc: invalid option -- 'U' BusyBox v1.19.4 (2013-03-08 13:08:18 CST) multi-call binary. Usage: nc [-iN] [-wN] [-l] [-p PORT] [-f FILE|IPADDR PORT] [-e PROG]: Input/output error I tried to verify the remote connection on localhost. But it also failed as below: root@mpc8572ds:~# virsh -c qemu+ssh:///root@localhost/system list --all root@localhost's password: error: failed to connect to the hypervisor error: End of file while reading data: nc: invalid option -- 'U' BusyBox v1.19.4 (2013-03-08 13:08:18 CST) multi-call binary. Usage: nc [-iN] [-wN] [-l] [-p PORT] [-f FILE|IPADDR PORT] [-e PROG]: Input/output error Could anyone give suggestion on this issue? Best Regards, Olivia

2 3

[libvirt-users] Host modifications
by Benoit Friry 04 Apr '13

04 Apr '13

Hello, I test libvirt 0.9.12 on Debian. I am disappointed by changes made on my host without any notice. Examples: - editing interfaces with virsh or virt-manager modifies my /etc/network/interfaces. It's not clear at first glance that I can even cut myself from the host when editing remotely. The initial file is not even saved. - starting default network (nat) adds rules in netfilter. I have not seen how to create another network nat conf without calling clean-traffic nwfilter (it is not explicit in network XML file). Is it hardcoded ? I think it would be nice: - to be alerted before any host modification, - to be able to change the templates, for instance: - not including any nwfilter when creating a network, - script called when adding a file in a dir pool, - and so on. Did I miss something? Am I alone to disappointed by such behavior? Thanks, Benoit

3 4

[libvirt-users] migrate qemu domains
by Yin Olivia-R63875 03 Apr '13

03 Apr '13

Hi, I tried to migrate qemu domains between same two Freescale PPC platforms. 1) Migrate test domain from Host1(10.193.20.109) to Host2(10.193.20.181). root@ppc-host1:~# virsh migrate test qemu+tls://10.193.20.181/system or root@ppc-host2:~# virsh -c qemu+tls://10.193.20.109/system migrate test qemu:///system I waited for a while and finally got error message as below: error: Unable to read from monitor: Connection reset by peer Exactly, when waiting (I guess during migration), the migrated domain is pasued on both source and destination nodes. root@ppc-host1:~# virsh -c qemu:///system list --all Id Name State ---------------------------------------------------- 5 test paused And meanwhile, the destination domain is also paused when waiting root@ppc-host2:~# virsh -c qemu:///system list --all Id Name State ---------------------------------------------------- 2 test paused Finally, the migrated domain on source node is shut off. root@ppc-host1:~# virsh -c qemu:///system list --all Id Name State ---------------------------------------------------- - test shut off But can't find any domain on destination node any longer. root@ppc-host2:~# virsh -c qemu:///system list --all Id Name State ---------------------------------------------------- As I know qemu-system-ppc doesn't support live migration on Freescale PPC platform yet. My question is whether it depends on qemu implementation to migrate qemu hypervisor with libvirt? >From the above experiment, it seemed that migration happened but not succeeded finally. Best Regards, Olivia

3 4

[libvirt-users] virt-manager connect remote KVM host and graphic control guest problem
by cochen 03 Apr '13

03 Apr '13

Hi developer, i got a problem and need your help!(my english not very good) My KVM host in IDC, and there are some restrict in there lead to me connect to KVM host by port 22 or 16509 impossible. In generally If i want login my KVM host i must login in to a "stepping stones" first, then login to that KVM host.( Now assume that the KVM host ip is 1.1.1.1 and the "stepping stones" ip is 2.2.2.2). So i use the "portforwarding" (i used the manner of "qemu+tcp" to connect KVM host, the default port is 16509), I visit the port 16509 in "stepping stones" machine 1.1.1.1 and then 1.1.1.1 port forwarding to 2.2.2.2:16509. And then my virt-manager connect KVM host successful！ But my trouble is comming too. I can't use virt-manager to control my guest by graphic. I "portforwarding" the port 5911(i had already defined my guest vnc port), but is unuseful. I used command "netstat -antl" in KVM host found that : tcp 0 0 127.0.0.1:5911 0.0.0.0:* LISTEN tcp 0 0 1.1.1.1:16509 2.2.2.2:63325 ESTABLISHED tcp 0 0 0.0.0.0:16509 0.0.0.0:* LISTEN As you see, 5911 listen into localhost(127.0.0.1), but 16509 listen into the 1.1.1.1 and 0.0.0.0. So I think if 5911 listen 0.0.0.0 or 1.1.1.1 everything is ok. Here is my virt-manager.log: [Thu, 28 Mar 2013 00:57:16 virt-manager 3242] DEBUG (engine:471) window counter incremented to 2 [Thu, 28 Mar 2013 00:57:16 virt-manager 3242] DEBUG (console:1078) Starting connect process for proto=vnc trans=tcp connhost=2.2.2.2 connuser=root connport=None gaddr=127.0.0.1 gport=5911 gsocket=None [Thu, 28 Mar 2013 00:57:16 virt-manager 3242] DEBUG (console:374) VNC connecting to 2.2.2.2:5911 [Thu, 28 Mar 2013 00:57:18 virt-manager 3242] DEBUG (console:961) Viewer disconnected How can i use virt-manager to control my guest by graphic? thank you very much!!!

2 1

[libvirt-users] How to give access to /dev/tty
by Guillaume Thouvenin 02 Apr '13

02 Apr '13

Hello, First I apologize because I sent this email on the lxc-users mailing by error. So sorry for the double message. I'm trying to run an X server inside a container. I was able to achieve this with lxc-tools (and that is why I mixed myself between the 2 lists) by setting the option lxc.tty = 4 that allows access to 4 tty. Now I want to use libvirt because my final goal is to create a container with GPU capabilities from Openstack (that uses libvirt). When I start an X server with "startx -- :1" in a container I have the error: Fatal server error: xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory) I also tried with :2 and :3 but I still have the same error (except that the name of the log file changed between Xorg.{1,2,3}.log. I copied the xml file of my container at the end of the email. Thus my question is how can I give an access to /dev/tty0 to the container? Or maybe it is not the right way to start an X server in the container. Best regards, Guillaume <domain type='lxc' id='28247'> <name>lxcvm1</name> <uuid>d4014dfc-f4db-5791-c0d2-817547921ce1</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='x86_64'>exe</type> <init>/sbin/init</init> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/lib/libvirt/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/home/thouveng/virtualization/lxc/lxcvm1/rootfs'/> <target dir='/'/> </filesystem> <interface type='network'> <mac address='00:16:3e:3e:06:4d'/> <source network='default'/> <target dev='veth0'/> </interface> <console type='pty' tty='/dev/pts/2'> <source path='/dev/pts/2'/> <target type='lxc' port='0'/> <alias name='console0'/> </console> <console type='pty'> <source path='/dev/pts/6'/> <target type='lxc' port='1'/> <alias name='console1'/> </console> <console type='pty'> <source path='/dev/pts/7'/> <target type='lxc' port='2'/> <alias name='console2'/> </console> </devices> <seclabel type='none'/> </domain>

4 7

[libvirt-users] question about vm management in libvirt
by Wangkai (Kevin,C) 30 Mar '13

30 Mar '13

Dear, I am a beginner of using libvirt to manage the vm, and I checked the libvirt manual. And I found the libvirt can creat, destroy, start and stop the vm, and it can manage The resource of the vm, such as storage, cpus, memory, networking and so on. And I have one doubt, Can It know the vm internal running state? Such as vm reboot, Exception, hang up, or signals received by the vm processes. I am using qemu driver. Thanks and Regards, Kevin

1 0

[libvirt-users] Support for Microsoft HyperV Server 2012
by Tejas Sumant 30 Mar '13

30 Mar '13

Hi there, Does LibVirt support Microsoft HyperV Server 2012? If not, what is plan to support the same? Thanks. -- Tejas Sumant

2 2

[libvirt-users] Snapshot without volumes temporarily
by Hubert Chiang 29 Mar '13

29 Mar '13

Hello, I want to do a snapshot which the VM has volumes. But I want to skip the volume check when I do the snapshot. (Which means I want to do a snapshot without detaching the volume) So I try to write a snapshot XML refer by http://libvirt.org/formatsnapshot.html as following: vda is my VM basic disk (qcow2) vdb is a volume (raw) ================ t1.xml =============== <domainsnapshot> <disks> <disk name='vda' snapshot='internal'> <source file='/var/lib/libvirt/VM1/disk' /> </disk> <disk name='vdb' snapshot='no' /> </disks> </domainsnapshot> ===================================== with this command: # virsh snapshot-create VM1 --xmlfile t1.xml and get the message: # error: argument unsupported: unable to handle disk requests in snapshot My environment is Libvirt 0.9.8, Qemu 1.0.0 on Ubuntu12.04.02 I try to do this action before at libvirt 0.9.2 QEMU 0.14.1 on Ubuntu 11.10 before with following commands, It's success. Step1. I copy the XML from /etc/libvirt/qemu/VM1.xml to VM1.xml.backup Step2. I edit the VM1.xml to remove the disk tag which is create by volume Step3. do virsh command: virsh snapshot-create VM1 Step4. Move VM1.xml.backup to VM1.xml It's success on libvirt 0.9.2. But on 0.9.8 It doesn't work. Because libvirt will check the setups from memory not the XML file in /etc/libvirt/qemu/ What could I do with libvirt 0.9.8? Thanks in advance.

2 2

[libvirt-users] virsh migrate ---no route to host
by Hari Pyla 29 Mar '13

29 Mar '13

Hi, I am trying to migrate a guest domain from one node to another. I've tried several options of the virsh migrate command, but in vain. It seems to be a networking issue. I wanted to make sure that my setup is correct and that I am not missing anything. I've issued the below command on the source node (n0): [user@n0 ~]$ virsh --connect qemu:///system migrate --verbose Fedora-17-x86_64-1 qemu+ssh://n1/system error: unable to connect to server at 'n1:49156': No route to host I was wondering if you have any ideas on how to fix this issue. My current setup/configuration: 1. virsh version : 0.10.2 2. The user has all the necessary access control setup. I've referenced http://libvirt.org/auth.html I am able to locally and remotely connect to both the nodes. I am also able to start, stop and perform other actions on guest domains on local and remote nodes, e.g., /* access destination node */ [user@n0 ~]$ virsh --connect qemu+ssh://n1/system list --all Id Name State ---------------------------------------------------- /* access local node */ [user@n0 ~]$ virsh --connect qemu:///system list --all Id Name State ---------------------------------------------------- 2 Fedora-17-x86_64-1 running - Fedora-18-x86_64-DVD shut off 3. ssh keys are configured for password less access to both the nodes 4. I've opened ports 49152-49215 on the destination node i.e., n1. please see below. [user@n1 images]$ sudo iptables -L [sudo] password for user: Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- anywhere anywhere udp dpt:domain ACCEPT tcp -- anywhere anywhere tcp dpt:domain ACCEPT udp -- anywhere anywhere udp dpt:bootps ACCEPT tcp -- anywhere anywhere tcp dpt:bootps ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT icmp -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh REJECT all -- anywhere anywhere reject-with icmp-host-prohibited ACCEPT tcp -- anywhere anywhere tcp dpts:49152:49215 ACCEPT tcp -- anywhere anywhere tcp spts:49152:49215 Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere 192.168.122.0/24 state RELATED,ESTABLISHED ACCEPT all -- 192.168.122.0/24 anywhere ACCEPT all -- anywhere anywhere REJECT all -- anywhere anywhere reject-with icmp-port-unreachable REJECT all -- anywhere anywhere reject-with icmp-port-unreachable REJECT all -- anywhere anywhere reject-with icmp-host-prohibited Chain OUTPUT (policy ACCEPT) target prot opt source destination 5. I've restarted the libvirtd after updating the iptables. I don't think that is necessary, but did it anyway. I was wondering if I am missing something. Any help is greatly appreciated. Thanks, --Hari

1 0

[libvirt-users] virsh migrate --no route to host
by Hari Pyla 29 Mar '13

29 Mar '13

Hi, I am trying to migrate a guest domain from one node to another. I've tried several options of the virsh migrate command, but in vain. It seems to be a networking issue. I wanted to make sure that my setup is correct and that I am not missing anything. I've issued the below command on the source node (n0): [user@n0 ~]$ virsh --connect qemu:///system migrate --verbose Fedora-17-x86_64-1 qemu+ssh://n1/system error: unable to connect to server at 'n1:49156': No route to host I was wondering if you have any ideas on how to fix this issue. My current setup/configuration: 1. virsh version : 0.10.2 2. The user has all the necessary access control setup. I've referenced http://libvirt.org/auth.html I am able to locally and remotely connect to both the nodes. I am also able to start, stop and perform other actions on guest domains on local and remote nodes, e.g., /* access destination node */ [user@n0 ~]$ virsh --connect qemu+ssh://n1/system list --all Id Name State ---------------------------------------------------- /* access local node */ [user@n0 ~]$ virsh --connect qemu:///system list --all Id Name State ---------------------------------------------------- 2 Fedora-17-x86_64-1 running - Fedora-18-x86_64-DVD shut off 3. ssh keys are configured for password less access on both the nodes 4. I've opened ports 49152-49215 on the destination node i.e., n1. please see below. [user@n1 images]$ sudo iptables -L [sudo] password for user: Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- anywhere anywhere udp dpt:domain ACCEPT tcp -- anywhere anywhere tcp dpt:domain ACCEPT udp -- anywhere anywhere udp dpt:bootps ACCEPT tcp -- anywhere anywhere tcp dpt:bootps ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT icmp -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh REJECT all -- anywhere anywhere reject-with icmp-host-prohibited ACCEPT tcp -- anywhere anywhere tcp dpts:49152:49215 ACCEPT tcp -- anywhere anywhere tcp spts:49152:49215 Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere 192.168.122.0/24 state RELATED,ESTABLISHED ACCEPT all -- 192.168.122.0/24 anywhere ACCEPT all -- anywhere anywhere REJECT all -- anywhere anywhere reject-with icmp-port-unreachable REJECT all -- anywhere anywhere reject-with icmp-port-unreachable REJECT all -- anywhere anywhere reject-with icmp-host-prohibited Chain OUTPUT (policy ACCEPT) target prot opt source destination 5. I've restarted the libvirtd after updating the iptables. I dont think that is necessary, but did it anyway. I was wondering if I am missing something. Any help is greatly appreciated. Thanks, --Hari

1 0

[libvirt-users] netfilter+libvirt=(smth got broken?)
by Nikolai Zhubr 28 Mar '13

28 Mar '13

Hello, I'm having problem setting up filtering traffic for a virtual machine managed by libvirt. Strange thing is, such a setup has been working fine for me on an older version of distro (namely, opensuse 11.3 w/updates, kernel 2.6.34, libvirt 0.8.8) but refused to work on shiny new opensuse 12.4 (kernel 3.7.10, libvirt 1.0.2). The definition of filter in question is pretty simple: <filter name='some-filt' chain='ipv4'> <rule action='accept' direction='in'> <tcp dstportstart='110'/> </rule> <rule action='drop' direction='inout'> <all/> </rule> </filter> So basically it should allow incoming connections to the specified port number and nothing else. After activating this filter on a box in question, connections to 110 started to fail (timeout). Examining iptables rules manually and comparing them to the rules from my old box did not reveal anything suspicious to me. However, through just pure guesswork, I managed to ocasionally "fix" the problem by manually editing 3 relevant rules as follows: --A FI-vnet0 -p tcp -m tcp --sport 110 -m conntrack --ctstate ESTABLISHED -m conntrack --ctdir ORIGINAL -j RETURN +-A FI-vnet0 -p tcp -m tcp --sport 110 -m conntrack --ctstate ESTABLISHED -m conntrack --ctdir REPLY -j RETURN --A FO-vnet0 -p tcp -m tcp --dport 110 -m conntrack --ctstate NEW,ESTABLISHED -m conntrack --ctdir REPLY -j ACCEPT +-A FO-vnet0 -p tcp -m tcp --dport 110 -m conntrack --ctstate NEW,ESTABLISHED -m conntrack --ctdir ORIGINAL -j ACCEPT --A HI-vnet0 -p tcp -m tcp --sport 110 -m conntrack --ctstate ESTABLISHED -m conntrack --ctdir ORIGINAL -j RETURN +-A HI-vnet0 -p tcp -m tcp --sport 110 -m conntrack --ctstate ESTABLISHED -m conntrack --ctdir REPLY -j RETURN So essentially, just manually swtiching "--ctdir" values to their opposites makes the filter allow connections to port 110. I've also verified that the filter still blocks unwanted connections originating from port 110 from VM exactly as it should: (in VM): netcat -v -v -n -p 110 192.168.122.1 22 (UNKNOWN) [192.168.122.1] 22 (?) : Connection timed out set 0, rcvd 0 I've then compared /proc/net/nf_conntrack on both (old and new) boxes. They look roughly the same, nothing suspicious. This all looks to me as if "--ctdir" argument somehow magically changed its meaning to the opposite, but this just cannot be! I'm out of ideas and looking for insights. Any hints appreciated quite a lot. Thank you. Nikolai

4 12

[libvirt-users] Bug in DOMINFO command when balloon driver is used on a vm with more then 8 GB of MaxMemory ?
by fc lists 26 Mar '13

26 Mar '13

Hi , I Sent this to the wrong list (libvirt-devel) on friday ... so i am trying to send it to the correct one this time. Apologize for double posting. I also created a ticket on bugzilla.redhat.com for this https://bugzilla.redhat.com/show_bug.cgi?id=927336 still i am posting it here because is absolutely possible i am doing something wrong and someone here will see it . Description of the problem: When the virsh setmem command is used to inflate (or deflate) the balloon on a VM to which 8GB of MaxMemory or more are allocated then the information reported with virsh dominfo , virsh dumpxml after the balloon change has been performed are wrong. The actual balloon is inflated correctly though and that is verifiable both in the vm itself and through the "virsh dommemstat" commands. Platform is Centos 6.4 (problem was present in 6.3 as well starting with libvirt-0.9.10-21.el6.3.7 ) The patch that actually is causing the problem is patch number 398 in the src rpm for libvirt-0.9.10-21.el6.3.7 : libvirt-Wire-up-handling-for-QMP-s-BALLOON_EVENT.patch ( https://bugzilla.redhat.com/show_bug.cgi?id=884713) And i verified it by removing the patch and recompiling the rpm , that indeed worked perfectly after that. The problem exists in every version up to the latest (that is what i am running now) but now the patch is part of the libvirt source code in itself and not a patch in the rpm anymore. Software used: # yum list installed | egrep -i "qemu|libvirt" gpxe-roms-qemu.noarch 0.9.7-6.9.el6 @base libvirt.x86_64 0.10.2-18.el6_4.2 @updates libvirt-client.x86_64 0.10.2-18.el6_4.2 @updates libvirt-python.x86_64 0.10.2-18.el6_4.2 @updates qemu-img.x86_64 2:0.12.1.2-2.355.0.1.el6.centos.2 @updates qemu-kvm.x86_64 2:0.12.1.2-2.355.0.1.el6.centos.2 @updates qemu-kvm-tools.x86_64 2:0.12.1.2-2.355.0.1.el6.centos.2 @updates Full example ( long and include debug logs ) : 1) Start VM with 12GB of MAX and CURRENT (12582912) (tail -f libvirtd.log | grep -i balloon) 2013-03-22 21:06:34.438+0000: 23180: debug : qemuMonitorSetBalloon:1690 : mon=0x7f3d6c1789e0 newmem=12582912 2013-03-22 21:06:34.438+0000: 23180: debug : virJSONValueToString:1133 : result={"execute":"balloon","arguments":{"value":12884901888},"id":"libvirt-6"} 2013-03-22 21:06:34.438+0000: 23180: debug : qemuMonitorJSONCommandWithFd:265 : Send command '{"execute":"balloon","arguments":{"value":12884901888},"id":"libvirt-6"}' for write with FD -1 2013-03-22 21:06:34.438+0000: 23180: debug : qemuMonitorSend:903 : QEMU_MONITOR_SEND_MSG: mon=0x7f3d6c1789e0 msg={"execute":"balloon","arguments":{"value":12884901888},"id":"libvirt-6"} 2013-03-22 21:06:34.439+0000: 23179: debug : qemuMonitorIOWrite:461 : QEMU_MONITOR_IO_WRITE: mon=0x7f3d6c1789e0 buf={"execute":"balloon","arguments":{"value":12884901888},"id":"libvirt-6"} # dominfo 2 Id: 2 Name: centos_jt UUID: bc25a6c4-ba34-a593-47c7-6372999946d6 OS Type: hvm State: running CPU(s): 1 CPU time: 26.6s Max memory: 12582912 KiB Used memory: 12582912 KiB Persistent: yes Autostart: disable Managed save: no Security model: none Security DOI: 0 2) set mem to 8GB (Fail as described) # setmem 2 --live --config --size 8388608 2013-03-22 21:13:45.522+0000: 23183: debug : qemuMonitorSetBalloon:1690 : mon=0x7f3d6c1789e0 newmem=8388608 2013-03-22 21:13:45.522+0000: 23183: debug : virJSONValueToString:1133 : result={"execute":"balloon","arguments":{"value":8589934592 },"id":"libvirt-9"} 2013-03-22 21:13:45.522+0000: 23183: debug : qemuMonitorJSONCommandWithFd:265 : Send command '{"execute":"balloon","arguments":{"value":8589934592},"id":"libvirt-9"}' for write with FD -1 2013-03-22 21:13:45.522+0000: 23183: debug : qemuMonitorSend:903 : QEMU_MONITOR_SEND_MSG: mon=0x7f3d6c1789e0 msg={"execute":"balloon","arguments":{"value":8589934592},"id":"libvirt-9"} 2013-03-22 21:13:45.523+0000: 23179: debug : qemuMonitorIOWrite:461 : QEMU_MONITOR_IO_WRITE: mon=0x7f3d6c1789e0 buf={"execute":"balloon","arguments":{"value":8589934592},"id":"libvirt-9"} 2013-03-22 21:13:45.528+0000: 23179: debug : qemuMonitorIOProcess:353 : QEMU_MONITOR_IO_PROCESS: mon=0x7f3d6c1789e0 buf={"timestamp": {"seconds": 1363986825, "microseconds": 528314}, "event": "BALLOON_CHANGE", "data": {"actual": 12883853312}} 2013-03-22 21:13:45.528+0000: 23179: debug : qemuMonitorJSONIOProcessLine:152 : Line [{"timestamp": {"seconds": 1363986825, "microseconds": 528314}, "event": "BALLOON_CHANGE", "data": {"actual": 12883853312}}] 2013-03-22 21:13:45.528+0000: 23179: debug : virJSONValueFromString:975 : string={"timestamp": {"seconds": 1363986825, "microseconds": 528314}, "event": "BALLOON_CHANGE", "data": {"actual": 12883853312}} 2013-03-22 21:13:45.528+0000: 23179: debug : qemuMonitorJSONIOProcessLine:167 : QEMU_MONITOR_RECV_EVENT: mon=0x7f3d6c1789e0 event={"timestamp": {"seconds": 1363986825, "microseconds": 528314}, "event": "BALLOON_CHANGE", "data": {"actual": 12883853312}} 2013-03-22 21:13:45.528+0000: 23179: debug : qemuMonitorJSONIOProcessEvent:138 : handle BALLOON_CHANGE handler=0x4b4de0 data=0x1685ce0 2013-03-22 21:13:45.528+0000: 23179: debug : qemuMonitorEmitBalloonChange:1151 : mon=0x7f3d6c1789e0 2013-03-22 21:13:45.528+0000: 23179: debug : qemuProcessHandleBalloonChange:1248 : Updating balloon from 12582912 to 12581888 kb 2013-03-22 21:13:46.528+0000: 23179: debug : qemuMonitorIOProcess:353 : QEMU_MONITOR_IO_PROCESS: mon=0x7f3d6c1789e0 buf={"timestamp": {"seconds": 1363986826, "microseconds": 352941}, "event": "BALLOON_CHANGE", "data": {"actual": 12884901888}} 2013-03-22 21:13:46.528+0000: 23179: debug : qemuMonitorJSONIOProcessLine:152 : Line [{"timestamp": {"seconds": 1363986826, "microseconds": 352941}, "event": "BALLOON_CHANGE", "data": {"actual": 12884901888}}] 2013-03-22 21:13:46.528+0000: 23179: debug : virJSONValueFromString:975 : string={"timestamp": {"seconds": 1363986826, "microseconds": 352941}, "event": "BALLOON_CHANGE", "data": {"actual": 12884901888}} 2013-03-22 21:13:46.528+0000: 23179: debug : qemuMonitorJSONIOProcessLine:167 : QEMU_MONITOR_RECV_EVENT: mon=0x7f3d6c1789e0 event={"timestamp": {"seconds": 1363986826, "microseconds": 352941}, "event": "BALLOON_CHANGE", "data": {"actual": 12884901888}} 2013-03-22 21:13:46.528+0000: 23179: debug : qemuMonitorJSONIOProcessEvent:138 : handle BALLOON_CHANGE handler=0x4b4de0 data=0x1686770 2013-03-22 21:13:46.528+0000: 23179: debug : qemuMonitorEmitBalloonChange:1151 : mon=0x7f3d6c1789e0 2013-03-22 21:13:46.528+0000: 23179: debug : qemuProcessHandleBalloonChange:1248 : Updating balloon from 12581888 to 12582912 kb virsh # dominfo 2 Id: 2 Name: centos_jt UUID: bc25a6c4-ba34-a593-47c7-6372999946d6 OS Type: hvm State: running CPU(s): 1 CPU time: 41.6s Max memory: 12582912 KiB Used memory: 12582912 KiB Persistent: yes Autostart: disable Managed save: no Security model: none Security DOI: 0 virsh # dommemstat 2 actual 8388608 rss 599916 The Balloon was actually inflated , and in the VM i can see 8GB of Ram available with free 3) setmem to to 3000000 (Fail as described) 2013-03-22 21:18:19.182+0000: 23181: debug : qemuMonitorSetBalloon:1690 : mon=0x7f3d6c1789e0 newmem=3000000 2013-03-22 21:18:19.182+0000: 23181: debug : virJSONValueToString:1133 : result={"execute":"balloon","arguments":{"value":3072000000 },"id":"libvirt-63"} 2013-03-22 21:18:19.182+0000: 23181: debug : qemuMonitorJSONCommandWithFd:265 : Send command '{"execute":"balloon","arguments":{"value":3072000000},"id":"libvirt-63"}' for write with FD -1 2013-03-22 21:18:19.182+0000: 23181: debug : qemuMonitorSend:903 : QEMU_MONITOR_SEND_MSG: mon=0x7f3d6c1789e0 msg={"execute":"balloon","arguments":{"value":3072000000},"id":"libvirt-63"} 2013-03-22 21:18:19.183+0000: 23179: debug : qemuMonitorIOWrite:461 : QEMU_MONITOR_IO_WRITE: mon=0x7f3d6c1789e0 buf={"execute":"balloon","arguments":{"value":3072000000},"id":"libvirt-63"} 2013-03-22 21:18:19.184+0000: 23179: debug : qemuMonitorIOProcess:353 : QEMU_MONITOR_IO_PROCESS: mon=0x7f3d6c1789e0 buf={"timestamp": {"seconds": 1363987099, "microseconds": 184245}, "event": "BALLOON_CHANGE", "data": {"actual": 12883853312}} 2013-03-22 21:18:19.184+0000: 23179: debug : qemuMonitorJSONIOProcessLine:152 : Line [{"timestamp": {"seconds": 1363987099, "microseconds": 184245}, "event": "BALLOON_CHANGE", "data": {"actual": 12883853312}}] 2013-03-22 21:18:19.184+0000: 23179: debug : virJSONValueFromString:975 : string={"timestamp": {"seconds": 1363987099, "microseconds": 184245}, "event": "BALLOON_CHANGE", "data": {"actual": 12883853312}} 2013-03-22 21:18:19.184+0000: 23179: debug : qemuMonitorJSONIOProcessLine:167 : QEMU_MONITOR_RECV_EVENT: mon=0x7f3d6c1789e0 event={"timestamp": {"seconds": 1363987099, "microseconds": 184245}, "event": "BALLOON_CHANGE", "data": {"actual": 12883853312}} 2013-03-22 21:18:19.184+0000: 23179: debug : qemuMonitorJSONIOProcessEvent:138 : handle BALLOON_CHANGE handler=0x4b4de0 data=0x1688320 2013-03-22 21:18:19.184+0000: 23179: debug : qemuMonitorEmitBalloonChange:1151 : mon=0x7f3d6c1789e0 2013-03-22 21:18:19.191+0000: 23179: debug : qemuProcessHandleBalloonChange:1248 : Updating balloon from 12582912 to 12581888 kb 2013-03-22 21:18:20.184+0000: 23179: debug : qemuMonitorIOProcess:353 : QEMU_MONITOR_IO_PROCESS: mon=0x7f3d6c1789e0 buf={"timestamp": {"seconds": 1363987100, "microseconds": 184128}, "event": "BALLOON_CHANGE", "data": {"actual": 11874074624}} 2013-03-22 21:18:20.184+0000: 23179: debug : qemuMonitorJSONIOProcessLine:152 : Line [{"timestamp": {"seconds": 1363987100, "microseconds": 184128}, "event": "BALLOON_CHANGE", "data": {"actual": 11874074624}}] 2013-03-22 21:18:20.184+0000: 23179: debug : virJSONValueFromString:975 : string={"timestamp": {"seconds": 1363987100, "microseconds": 184128}, "event": "BALLOON_CHANGE", "data": {"actual": 11874074624}} 2013-03-22 21:18:20.184+0000: 23179: debug : qemuMonitorJSONIOProcessLine:167 : QEMU_MONITOR_RECV_EVENT: mon=0x7f3d6c1789e0 event={"timestamp": {"seconds": 1363987100, "microseconds": 184128}, "event": "BALLOON_CHANGE", "data": {"actual": 11874074624}} 2013-03-22 21:18:20.184+0000: 23179: debug : qemuMonitorJSONIOProcessEvent:138 : handle BALLOON_CHANGE handler=0x4b4de0 data=0x1685ce0 2013-03-22 21:18:20.184+0000: 23179: debug : qemuMonitorEmitBalloonChange:1151 : mon=0x7f3d6c1789e0 2013-03-22 21:18:20.184+0000: 23179: debug : qemuProcessHandleBalloonChange:1248 : Updating balloon from 12581888 to 11595776 kb 2013-03-22 21:18:21.184+0000: 23179: debug : qemuMonitorIOProcess:353 : QEMU_MONITOR_IO_PROCESS: mon=0x7f3d6c1789e0 buf={"timestamp": {"seconds": 1363987100, "microseconds": 224930}, "event": "BALLOON_CHANGE", "data": {"actual": 11661934592}} 2013-03-22 21:18:21.184+0000: 23179: debug : qemuMonitorJSONIOProcessLine:152 : Line [{"timestamp": {"seconds": 1363987100, "microseconds": 224930}, "event": "BALLOON_CHANGE", "data": {"actual": 11661934592}}] 2013-03-22 21:18:21.184+0000: 23179: debug : virJSONValueFromString:975 : string={"timestamp": {"seconds": 1363987100, "microseconds": 224930}, "event": "BALLOON_CHANGE", "data": {"actual": 11661934592}} 2013-03-22 21:18:21.184+0000: 23179: debug : qemuMonitorJSONIOProcessLine:167 : QEMU_MONITOR_RECV_EVENT: mon=0x7f3d6c1789e0 event={"timestamp": {"seconds": 1363987100, "microseconds": 224930}, "event": "BALLOON_CHANGE", "data": {"actual": 11661934592}} 2013-03-22 21:18:21.184+0000: 23179: debug : qemuMonitorJSONIOProcessEvent:138 : handle BALLOON_CHANGE handler=0x4b4de0 data=0x1686770 2013-03-22 21:18:21.184+0000: 23179: debug : qemuMonitorEmitBalloonChange:1151 : mon=0x7f3d6c1789e0 2013-03-22 21:18:21.184+0000: 23179: debug : qemuProcessHandleBalloonChange:1248 : Updating balloon from 11595776 to 11388608 virsh # dominfo 2 Id: 2 Name: centos_jt UUID: bc25a6c4-ba34-a593-47c7-6372999946d6 OS Type: hvm State: running CPU(s): 1 CPU time: 53.0s Max memory: 12582912 KiB Used memory: 11388608 KiB Persistent: yes Autostart: disable Managed save: no Security model: none Security DOI: 0 virsh # dommemstat 2 actual 3000000 rss 599036 4) Restart the SAME vm with 4GB of Current and Max (4194304) 2013-03-22 21:20:58.894+0000: 23182: debug : qemuMonitorSetBalloon:1690 : mon=0x7f3d643eb5a0 newmem=4194304 2013-03-22 21:20:58.894+0000: 23182: debug : virJSONValueToString:1133 : result={"execute":"balloon","arguments":{"value":4294967296},"id":"libvirt-6"} 2013-03-22 21:20:58.894+0000: 23182: debug : qemuMonitorJSONCommandWithFd:265 : Send command '{"execute":"balloon","arguments":{"value":4294967296},"id":"libvirt-6"}' for write with FD -1 2013-03-22 21:20:58.894+0000: 23182: debug : qemuMonitorSend:903 : QEMU_MONITOR_SEND_MSG: mon=0x7f3d643eb5a0 msg={"execute":"balloon","arguments":{"value":4294967296},"id":"libvirt-6"} 2013-03-22 21:20:58.894+0000: 23179: debug : qemuMonitorIOWrite:461 : QEMU_MONITOR_IO_WRITE: mon=0x7f3d643eb5a0 buf={"execute":"balloon","arguments":{"value":4294967296},"id":"libvirt-6"} virsh # dominfo 3 Id: 3 Name: centos_jt UUID: bc25a6c4-ba34-a593-47c7-6372999946d6 OS Type: hvm State: running CPU(s): 1 CPU time: 15.4s Max memory: 4194304 KiB Used memory: 4194304 KiB Persistent: yes Autostart: disable Managed save: no Security model: none Security DOI: 0 virsh # dommemstat 3 actual 4194304 rss 431384 5) reduce ram to 1GB (Works) virsh # setmem 3 --live --config --size 1048576 2013-03-22 21:26:08.783+0000: 23183: debug : qemuMonitorSetBalloon:1690 : mon=0x7f3d643eb5a0 newmem=1048576 2013-03-22 21:26:08.783+0000: 23183: debug : virJSONValueToString:1133 : result={"execute":"balloon","arguments":{"value":1073741824},"id":"libvirt-11"} 2013-03-22 21:26:08.783+0000: 23183: debug : qemuMonitorJSONCommandWithFd:265 : Send command '{"execute":"balloon","arguments":{"value":1073741824},"id":"libvirt-11"}' for write with FD -1 2013-03-22 21:26:08.783+0000: 23183: debug : qemuMonitorSend:903 : QEMU_MONITOR_SEND_MSG: mon=0x7f3d643eb5a0 msg={"execute":"balloon","arguments":{"value":1073741824},"id":"libvirt-11"} 2013-03-22 21:26:08.784+0000: 23179: debug : qemuMonitorIOWrite:461 : QEMU_MONITOR_IO_WRITE: mon=0x7f3d643eb5a0 buf={"execute":"balloon","arguments":{"value":1073741824},"id":"libvirt-11"} 2013-03-22 21:26:08.789+0000: 23179: debug : qemuMonitorIOProcess:353 : QEMU_MONITOR_IO_PROCESS: mon=0x7f3d643eb5a0 buf={"timestamp": {"seconds": 1363987568, "microseconds": 789570}, "event": "BALLOON_CHANGE", "data": {"actual": 4293918720}} 2013-03-22 21:26:08.789+0000: 23179: debug : qemuMonitorJSONIOProcessLine:152 : Line [{"timestamp": {"seconds": 1363987568, "microseconds": 789570}, "event": "BALLOON_CHANGE", "data": {"actual": 4293918720}}] 2013-03-22 21:26:08.789+0000: 23179: debug : virJSONValueFromString:975 : string={"timestamp": {"seconds": 1363987568, "microseconds": 789570}, "event": "BALLOON_CHANGE", "data": {"actual": 4293918720}} 2013-03-22 21:26:08.789+0000: 23179: debug : qemuMonitorJSONIOProcessLine:167 : QEMU_MONITOR_RECV_EVENT: mon=0x7f3d643eb5a0 event={"timestamp": {"seconds": 1363987568, "microseconds": 789570}, "event": "BALLOON_CHANGE", "data": {"actual": 4293918720}} 2013-03-22 21:26:08.789+0000: 23179: debug : qemuMonitorJSONIOProcessEvent:138 : handle BALLOON_CHANGE handler=0x4b4de0 data=0x1686360 2013-03-22 21:26:08.789+0000: 23179: debug : qemuMonitorEmitBalloonChange:1151 : mon=0x7f3d643eb5a0 2013-03-22 21:26:08.789+0000: 23179: debug : qemuProcessHandleBalloonChange:1248 : Updating balloon from 4194304 to 4193280 kb 2013-03-22 21:26:09.789+0000: 23179: debug : qemuMonitorIOProcess:353 : QEMU_MONITOR_IO_PROCESS: mon=0x7f3d643eb5a0 buf={"timestamp": {"seconds": 1363987569, "microseconds": 408889}, "event": "BALLOON_CHANGE", "data": {"actual": 1073741824}} 2013-03-22 21:26:09.789+0000: 23179: debug : qemuMonitorJSONIOProcessLine:152 : Line [{"timestamp": {"seconds": 1363987569, "microseconds": 408889}, "event": "BALLOON_CHANGE", "data": {"actual": 1073741824}}] 2013-03-22 21:26:09.789+0000: 23179: debug : virJSONValueFromString:975 : string={"timestamp": {"seconds": 1363987569, "microseconds": 408889}, "event": "BALLOON_CHANGE", "data": {"actual": 1073741824}} 2013-03-22 21:26:09.789+0000: 23179: debug : qemuMonitorJSONIOProcessLine:167 : QEMU_MONITOR_RECV_EVENT: mon=0x7f3d643eb5a0 event={"timestamp": {"seconds": 1363987569, "microseconds": 408889}, "event": "BALLOON_CHANGE", "data": {"actual": 1073741824}} 2013-03-22 21:26:09.789+0000: 23179: debug : qemuMonitorJSONIOProcessEvent:138 : handle BALLOON_CHANGE handler=0x4b4de0 data=0x16826e0 2013-03-22 21:26:09.789+0000: 23179: debug : qemuMonitorEmitBalloonChange:1151 : mon=0x7f3d643eb5a0 2013-03-22 21:26:09.789+0000: 23179: debug : qemuProcessHandleBalloonChange:1248 : Updating balloon from 4193280 to 1048576 kb virsh # dominfo 3 Id: 3 Name: centos_jt UUID: bc25a6c4-ba34-a593-47c7-6372999946d6 OS Type: hvm State: running CPU(s): 1 CPU time: 28.6s Max memory: 4194304 KiB Used memory: 1048576 KiB Persistent: yes Autostart: disable Managed save: no Security model: none Security DOI: 0 virsh # dommemstat 3 actual 1048576 rss 411740

1 0

[libvirt-users] Failed to boot lxc with libvirt 1.0.3:2013-03-25 06:54:17.620+0000: 1: error : lxcContainerMountBasicFS:563 : Failed to mount /selinux on /selinux type selinuxfs flags=e opts=(null): No such device
by 张章 25 Mar '13

25 Mar '13

hi all, I am using lxc with libvirt. But I can't boot lxc container by libvirt 1.0.3(libvirt 0.9.8 works) . Below is my environment. Do I miss something? lxc1.xml:<domain type='lxc'> <name>lxc1</name> <memory>1024000</memory> <cputune> <shares>100</shares> </cputune> <os> <type>exe</type> <init>/bin/sh</init> </os> <devices> <console type = 'pty'/> </devices></domain> I used virsh -c lxc:/// create lxc1.xml and got the following error:2013-03-25 06:54:17.620+0000: 1: info : libvirt version: 1.0.32013-03-25 06:54:17.620+0000: 1: error : lxcContainerMountBasicFS:563 : Failed to mount /selinux on /selinux type selinuxfs flags=e opts=(null): No such device2013-03-25 06:54:17.620+0000: 10668: info : libvirt version: 1.0.32013-03-25 06:54:17.620+0000: 10668: error : virLXCControllerRun:1468 : error receiving signal from container: Input/output error My OS: Ubuntu 11.10 Can anyone help me? Thanks a lot! regardszhangzhang

2 1

[libvirt-users] virsh list running VMs as idle, libvirt-1.0.3 xen-4.2
by Heiko L. 24 Mar '13

24 Mar '13

1 0

[libvirt-users] virsh list show shutdown VMs only
by Heiko L. 24 Mar '13

24 Mar '13

Hallo, I am using virsh with squeeze and xen-4.2+linux-3.8 (compiled) Problem: "virsh list -all" shows VMs only in shutdown state. (see: test3 virsh list shutdown) virsh start/shutdown works correctly. I suspect that version of libvirt is to old. Is their some workaround without updating system? regards Heiko details: - test1 start vm root@e2:/tmp# virsh start vm1_test1 Domain vm1_test1 started root@e2:/tmp# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 64487 8 r----- 6834.7 vm1_test1 6 96 1 -b---- 2.3 root@e2:/tmp# virsh list Id Name State ---------------------------------- root@e2:/tmp# virsh list --all Id Name State ---------------------------------- root@e2:/tmp# -> vm running, but "virsh list" show nothing - test2 debug virsh list root@e2:/tmp# LIBVIRT_DEBUG=1 virsh list | egrep -v "do_open|virRegister" 14:36:38.540: debug : virInitialize:340 : register drivers 14:36:38.541: debug : xenHypervisorInit:2010 : Using new hypervisor call: 40002 14:36:38.542: debug : xenHypervisorInit:2123 : Failed to find any Xen hypervisor method 14:36:38.542: debug : vboxRegister:122 : VBoxCGlueInit failed, using dummy driver 14:36:38.543: debug : virConnectOpenAuth:1499 : name=(null), auth=0x7f46145b2700, flags=0 14:36:38.543: debug : xenUnifiedOpen:326 : Trying hypervisor sub-driver 14:36:38.543: debug : xenUnifiedOpen:329 : Activated hypervisor sub-driver 14:36:38.543: debug : xenUnifiedOpen:337 : Trying XenD sub-driver 14:36:38.546: debug : xenUnifiedOpen:340 : Activated XenD sub-driver 14:36:38.546: debug : xenUnifiedOpen:353 : Trying XS sub-driver 14:36:38.547: debug : xenStoreOpen:345 : Failed to add event handle, disabling events 14:36:38.547: debug : xenUnifiedOpen:356 : Activated XS sub-driver 14:36:38.551: debug : xenUnifiedOpen:392 : Trying Xen inotify sub-driver 14:36:38.551: debug : xenInotifyXendDomainsDirLookup:139 : Looking for dom with uuid: d868acf8-56b7-b260-4c85-c2e1e2a67e9b 14:36:38.576: debug : virGetDomain:382 : New hash entry 0x65b0a0 14:36:38.576: debug : virDomainFree:2243 : domain=0x65b0a0 14:36:38.576: debug : virUnrefDomain:463 : unref domain 0x65b0a0 vm1_test1 1 14:36:38.576: debug : virReleaseDomain:416 : release domain 0x65b0a0 vm1_test1 d868acf8-56b7-b260-4c85-c2e1e2a67e9b 14:36:38.576: debug : virReleaseDomain:433 : unref connection 0x634ad0 2 14:36:38.576: debug : xenInotifyOpen:441 : Adding a watch on /var/lib/xend/domains 14:36:38.576: debug : xenInotifyOpen:453 : Building initial config cache 14:36:38.576: debug : xenInotifyOpen:460 : Registering with event loop 14:36:38.576: debug : xenInotifyOpen:464 : Failed to add inotify handle, disabling events 14:36:38.576: debug : xenUnifiedOpen:395 : Activated Xen inotify sub-driver 14:36:38.576: debug : doRemoteOpen:565 : proceeding with name = xen:/// 14:36:38.576: debug : remoteIO:9888 : Do proc=66 serial=0 length=28 wait=(nil) 14:36:38.576: debug : remoteIO:9963 : We have the buck 66 0x7f461474d010 0x7f461474d010 14:36:38.577: debug : remoteIODecodeMessageLength:9316 : Got length, now need 64 total (60 more) 14:36:38.577: debug : remoteIOEventLoop:9814 : Giving up the buck 66 0x7f461474d010 (nil) 14:36:38.577: debug : remoteIO:9992 : All done with our call 66 (nil) 0x7f461474d010 14:36:38.577: debug : remoteIO:9888 : Do proc=1 serial=1 length=48 wait=(nil) 14:36:38.577: debug : remoteIO:9963 : We have the buck 1 0x65e2d0 0x65e2d0 14:36:38.608: debug : remoteIODecodeMessageLength:9316 : Got length, now need 56 total (52 more) 14:36:38.608: debug : remoteIOEventLoop:9814 : Giving up the buck 1 0x65e2d0 (nil) 14:36:38.608: debug : remoteIO:9992 : All done with our call 1 (nil) 0x65e2d0 14:36:38.608: debug : doRemoteOpen:942 : Adding Handler for remote events 14:36:38.608: debug : doRemoteOpen:949 : virEventAddHandle failed: No addHandleImpl defined. continuing without events. 14:36:38.609: debug : doRemoteOpen:565 : proceeding with name = xen:/// 14:36:38.609: debug : remoteIO:9888 : Do proc=66 serial=0 length=28 wait=(nil) 14:36:38.609: debug : remoteIO:9963 : We have the buck 66 0x69e3b0 0x69e3b0 14:36:38.609: debug : remoteIODecodeMessageLength:9316 : Got length, now need 64 total (60 more) 14:36:38.609: debug : remoteIOEventLoop:9814 : Giving up the buck 66 0x69e3b0 (nil) 14:36:38.609: debug : remoteIO:9992 : All done with our call 66 (nil) 0x69e3b0 14:36:38.610: debug : remoteIO:9888 : Do proc=1 serial=1 length=48 wait=(nil) 14:36:38.610: debug : remoteIO:9963 : We have the buck 1 0x69e3b0 0x69e3b0 14:36:38.643: debug : remoteIODecodeMessageLength:9316 : Got length, now need 56 total (52 more) 14:36:38.643: debug : remoteIOEventLoop:9814 : Giving up the buck 1 0x69e3b0 (nil) 14:36:38.643: debug : remoteIO:9992 : All done with our call 1 (nil) 0x69e3b0 14:36:38.643: debug : doRemoteOpen:942 : Adding Handler for remote events 14:36:38.643: debug : doRemoteOpen:949 : virEventAddHandle failed: No addHandleImpl defined. continuing without events. 14:36:38.643: debug : doRemoteOpen:565 : proceeding with name = xen:/// 14:36:38.643: debug : remoteIO:9888 : Do proc=66 serial=0 length=28 wait=(nil) 14:36:38.643: debug : remoteIO:9963 : We have the buck 66 0x6de490 0x6de490 14:36:38.645: debug : remoteIO:9888 : Do proc=1 serial=1 length=48 wait=(nil) 14:36:38.645: debug : remoteIO:9963 : We have the buck 1 0x6de490 0x6de490 14:36:38.677: debug : remoteIODecodeMessageLength:9316 : Got length, now need 56 total (52 more) 14:36:38.677: debug : remoteIOEventLoop:9814 : Giving up the buck 1 0x6de490 (nil) 14:36:38.677: debug : remoteIO:9992 : All done with our call 1 (nil) 0x6de490 14:36:38.677: debug : doRemoteOpen:942 : Adding Handler for remote events 14:36:38.677: debug : doRemoteOpen:949 : virEventAddHandle failed: No addHandleImpl defined. continuing without events. 14:36:38.677: debug : virConnectNumOfDomains:1894 : conn=0x634ad0 Id Name State ---------------------------------- 14:36:38.678: debug : virConnectClose:1525 : conn=0x634ad0 14:36:38.678: debug : virUnrefConnect:294 : unref connection 0x634ad0 1 14:36:38.678: debug : remoteIO:9888 : Do proc=2 serial=2 length=28 wait=(nil) 14:36:38.678: debug : remoteIO:9963 : We have the buck 2 0x6de490 0x6de490 14:36:38.678: debug : remoteIODecodeMessageLength:9316 : Got length, now need 56 total (52 more) 14:36:38.678: debug : remoteIOEventLoop:9814 : Giving up the buck 2 0x6de490 (nil) 14:36:38.678: debug : remoteIO:9992 : All done with our call 2 (nil) 0x6de490 14:36:38.678: debug : remoteIO:9888 : Do proc=2 serial=2 length=28 wait=(nil) 14:36:38.678: debug : remoteIO:9963 : We have the buck 2 0x65e2d0 0x65e2d0 14:36:38.679: debug : remoteIODecodeMessageLength:9316 : Got length, now need 56 total (52 more) 14:36:38.679: debug : remoteIOEventLoop:9814 : Giving up the buck 2 0x65e2d0 (nil) 14:36:38.679: debug : remoteIO:9992 : All done with our call 2 (nil) 0x65e2d0 14:36:38.679: debug : remoteIO:9888 : Do proc=2 serial=2 length=28 wait=(nil) 14:36:38.679: debug : remoteIO:9963 : We have the buck 2 0x65e2d0 0x65e2d0 14:36:38.680: debug : remoteIODecodeMessageLength:9316 : Got length, now need 56 total (52 more) 14:36:38.680: debug : remoteIOEventLoop:9814 : Giving up the buck 2 0x65e2d0 (nil) 14:36:38.680: debug : remoteIO:9992 : All done with our call 2 (nil) 0x65e2d0 14:36:38.682: debug : virReleaseConnect:249 : release connection 0x634ad0 -> entry "unref domain 0x65b0a0 vm1_test1 1" found but not displayed - test3 virsh list shutdown # virsh shutdown vm1_test1 Domain vm1_test1 is being shutdown root@e2:/tmp# virsh list Id Name State ---------------------------------- root@e2:/tmp# virsh list --all Id Name State ---------------------------------- - vm1_test1 shut off -> "virsh list" show vm if shutdown only - version # apt-cache policy libvirt0 libvirt0: Installed: 0.8.3-5+squeeze2 Candidate: 0.8.3-5+squeeze2 Version table: *** 0.8.3-5+squeeze2 0 # uname -a Linux e2 3.8.0-xen0 #1 SMP Fri Mar 1 14:01:33 CET 2013 x86_64 GNU/Linux # xm info | grep ^xen_m xen_major : 4 xen_minor : 2

1 1

[libvirt-users] howto make libvirtd xen-4.2
by Heiko L. 24 Mar '13

24 Mar '13

Hallo I wanted to compile libvirtd on xen-4.2 but on [3] wrote: ...current version of libvirt is not compatible with xen 4.2... Which version that I can test? regards heiko -------------------------------------------------- - details 130305.xen.make.libvirtd #### var tmp=/tmp libvirtver="0.10.2" pkgs="libxml2-dev libdevmapper-dev" #### dl cd $tmp ## dl [2] wget ftp://libvirt.org/libvirt/libvirt-$libvirtver.tar.gz apt-get install $pkgs #### make tar -xzf libvirt-$libvirtver.tar.gz cd libvirt-$libvirtver ./configure make && make install ----------------------------------------------------- #### details # make ... CC libvirt_driver_xen_impl_la-xen_inotify.lo CCLD libvirt_driver_xen_impl.la CCLD libvirt_driver_xen.la CC libvirt_driver_libxl_impl_la-libxl_conf.lo In file included from libxl/libxl_conf.c:43: libxl/libxl_conf.h:61: error: field 'ctx' has incomplete type libxl/libxl_conf.h:80: error: field 'ctx' has incomplete type libxl/libxl_conf.h:81: error: expected specifier-qualifier-list before 'libxl_waiter' libxl/libxl_conf.c: In function 'libxlMakeDomCreateInfo': libxl/libxl_conf.c:365: warning: implicit declaration of function 'libxl_init_create_info' [-Wimplicit-function-declaration] libxl/libxl_conf.c:365: warning: nested extern declaration of 'libxl_init_create_info' [-Wnested-externs] - on [3] wrote: ...current version of libvirt is not compatible with xen 4.2... ========================================================================= [1] https://www.redhat.com/archives/libvirt-users/2012-September/msg00113.html Re: [libvirt-users] virsh list not working with xen 4 virsh list --all only shows turned off machines registered in xend. [2] ftp://libvirt.org/libvirt/ Index of ftp://libvirt.org/libvirt/ [3] http://superuser.com/questions/481662/xen-4-2-on-centos-6-3-cant-compile-a-… Xen 4.2 on CentOs 6.3 : can't compile a libvirt 0.9.10 xen-activated? ...current version of libvirt is not compatible with xen 4.2...

1 1

[libvirt-users] Errors while using blkiotune command
by Saurabh Deochake 23 Mar '13

23 Mar '13

Hi all, I want to limit the I/O bandwidth inside the container, so I used virsh command blkiotune. But when I enter a command: virsh # blkiotune lxcguest --weight 250 I get following errors: error: Unable to change blkio parameters error: Requested operation is not valid: blkio cgroup isn't mounted I also have blkio cgroup mounted. What can be the problem? Thanks in advance. Regards, Saurabh Deochake

4 6

[libvirt-users] [bump] Storage pool created on the "wrong" vg
by Alaric Haag 23 Mar '13

23 Mar '13

________________________________ From: Alaric Haag Sent: Tuesday, March 19, 2013 2:39 PM To: libvirt-users(a)redhat.com Subject: Storage pool created on the "wrong" vg Hello all, (Hopefully, I am posing this question to the correct list!) I seem to have mis-clicked through the creation of an LVM-based storage pool in virt-manager and it is using a volume group containing LVs dedicated to the root/swap filesystems. As these are active LVs, there seems no way to remove this pool. Is that true? My reading thus far suggests that, with LVM storage units, you can't delete them from the pool without REALLY deleting them from the VG. I'm "new enough" to KVM to be missing something obvious, but I'd be pretty shocked if a "structure" like a storage pool can't be deconstructed. Kind regards, Alaric ------------------------ Here's a bit more detail in the hope someone might help: I clicked through the creation of a storage pool, and accidentally used the wrong volume group, so I have: virsh # vol-list vm_pool Name Path ----------------------------------------- lv_root /dev/vg_01/lv_root lv_swap /dev/vg_01/lv_swap These two LVs, in group vg_01, are the / and swap partition of the host system. I meant for the pool to reside on vg_vm, a different volume group. Can I safely run: virsh # vol-delete lv_root --pool=vm_pool virsh # vol-delete lv_swap --pool=vm_pool virsh # pool-delete vm_pool or do the first two steps actually destroy the LVs in vg_01 thus bringing my system crashing down? The link below strongly suggests I cannot delete these logical volumes from the pool, but is a "draft" for OpenSUSE. (I'm running libvirt 0.10.2-18 on RHEL6) http://doc.opensuse.org/products/draft/SLES/SLES-kvm_sd_draft/cha.libvirt.s… If that's the case, is there ANY way to undo my mistake and remove this pool? I am most grateful for any guidance! Alaric

1 0

Re: [libvirt-users] remote connection issue 'virsh -c qemu+ssh:///root@localhost/system list'
by Javi Legido 22 Mar '13

22 Mar '13

Hi Olivia. Another think that you should check is socat package. In my documented example the hypervisor running KVM is a Debian squeeze, and I had to proceed this way: sudo aptitude update; sudo aptitude install netcat socat -R sudo vim /bin/netcatsocket #!/bin/bash socat - unix-client:$2 sudo chmod +x /bin/netcatsocket You can try it and see if it helps or not. PD: looping in again the list, I replied just to Olivia before Cheers El 21/03/2013 12:47, "Yin Olivia-R63875" <r63875(a)freescale.com> escribió: > Hi Javier, > > Thanks for your help. > From the pages you provided, I guess you suggest is as below: > * Cannot recv data: Host key verification failed. : Connection reset by > peer > > Sucede al lanzar: > > virt-manager -c qemu+ssh://usuario@hipervisor/system > > Solucion: iniciar una sesion SSH para almacenar las claves del hipervisor > en el cliente: > > ssh usuario@hipervisor > > Exactly, I've login with ssh and then connect with virsh. > > user@x86:~$ ssh root(a)10.193.20.109 > root(a)10.193.20.109's password: > root@ppc:~# exit > logout > Connection to 10.193.20.109 closed. > > user@x86:~$ virsh -c qemu+ssh://root@10.193.20.109/system list --all > root(a)10.193.20.109's password: > error: failed to connect to the hypervisor > error: End of file while reading data: nc: invalid option -- 'U' > BusyBox v1.19.4 (2013-03-08 13:08:18 CST) multi-call binary. > > Usage: nc [-iN] [-wN] [-l] [-p PORT] [-f FILE|IPADDR PORT] [-e PROG]: > Input/output error > > It still failed to connect the hypervisor, instead of ssh issue. > > Best Regards, > Olivia > > > -----Original Message----- > > From: javilegido(a)gmail.com [mailto:javilegido@gmail.com] On Behalf Of > Javi > > Legido > > Sent: Thursday, March 21, 2013 7:35 PM > > To: Yin Olivia-R63875 > > Subject: Re: [libvirt-users] remote connection issue 'virsh -c > > qemu+ssh:///root@localhost/system list' > > > > Hi Olivia. > > > > It's in spanish, but pretty easy to follow, maybe it helps you: > > > > > http://wiki.legido.com/doku.php?id=informatica:linux:virtualizacion:kvm#adm > > inistrar_kvm_y_vm_desde_una_gui_en_el_cliente > > > > With this guide you should be able to connect from a client machine (for > > instance your laptop) to the hypervisor (KVM) if both have SSH > connectivity. > > > > Cheers. > > > > Javier > > > > 2013/3/21 Yin Olivia-R63875 <r63875(a)freescale.com>: > > > Hi, > > > > > > I'm trying remote connection with qemu hypervisor on FSL PPC board. > > > > > > The libvirt server is the PPC board. > > > > > > root@ppc:~# ifconfig eth0 10.193.20.109 root@ppc:~# libvirtd -d > > > root@ppc:~# virsh -c qemu:///system define test.xml root@ppc:~# virsh > > > -c qemu:///system start test root@ppc:~# virsh -c qemu:///system list > > > --all > > > Id Name State > > > ---------------------------------------------------- > > > 2 test running > > > > > > Connect from an X86 PC (Ubuntu 10.04) to the PPC board. > > > > > > user@x86:~$ virsh -c qemu+ssh://root@10.193.20.109/system list --all > > > The authenticity of host '10.193.20.109 (10.193.20.109)' can't be > > established. > > > RSA key fingerprint is 2f:56:07:08:da:7d:ac:41:45:57:d2:12:15:19:67:e0. > > > Are you sure you want to continue connecting (yes/no)? yes > > > root(a)10.193.20.109's password: > > > error: failed to connect to the hypervisor > > > error: End of file while reading data: Warning: Permanently added > > '10.193.20.109' (RSA) to the list of known hosts. > > > nc: invalid option -- 'U' > > > BusyBox v1.19.4 (2013-03-08 13:08:18 CST) multi-call binary. > > > > > > Usage: nc [-iN] [-wN] [-l] [-p PORT] [-f FILE|IPADDR PORT] [-e PROG]: > > > Input/output error > > > > > > > > > > > > I tried to verify the remote connection on localhost. But it also > failed > > as below: > > > > > > root@mpc8572ds:~# virsh -c qemu+ssh:///root@localhost/system list > > > --all root@localhost's password: > > > error: failed to connect to the hypervisor > > > error: End of file while reading data: nc: invalid option -- 'U' > > > BusyBox v1.19.4 (2013-03-08 13:08:18 CST) multi-call binary. > > > > > > Usage: nc [-iN] [-wN] [-l] [-p PORT] [-f FILE|IPADDR PORT] [-e PROG]: > > > Input/output error > > > > > > > > > Could anyone give suggestion on this issue? > > > > > > > > > Best Regards, > > > Olivia > > > > > > > > > _______________________________________________ > > > libvirt-users mailing list > > > libvirt-users(a)redhat.com > > > https://www.redhat.com/mailman/listinfo/libvirt-users > > >

1 0

[libvirt-users] Libvirt dead, pid still exists
by SHREE DUTH AWASTHI 21 Mar '13

21 Mar '13

Hi All, Refering to the link below, I got to know that previous versions of Libvirtd had this issue. https://www.redhat.com/archives/libvirt-users/2012-August/msg00104.html We are using libvirt-0.10.0 but we are facing the same issue. Procedure to reproduce : 1. Login to some domain name say CLA-0 using virsh. (i) # virsh list --all Id Name State ---------------------------------------------------- 4 CLA-0 running (ii) # virsh console 4 Connected to domain CLA-0 Escape character is ^] 2. Whenever we exit from the above CLA-0 domain by pressing ctrl-] We are getting the Segmentation fault, however core is not generated but we have debugged it through gdb Program received signal SIGSEGV, Segmentation fault. 0x00007ffff5a96c71 in pthread_mutex_lock () from /lib64/libpthread.so.0 (gdb) bt #0 0x00007ffff5a96c71 in pthread_mutex_lock () from /lib64/libpthread.so.0 #1 0x00007ffff78c8b97 in ?? () from /usr/lib64/libvirt.so.0 #2 0x00007ffff78b6297 in ?? () from /usr/lib64/libvirt.so.0 #3 0x00007ffff7865b65 in virHashRemoveEntry () from /usr/lib64/libvirt.so.0 #4 0x00007ffff78b60d0 in ?? () from /usr/lib64/libvirt.so.0 #5 0x00007ffff78c95f9 in ?? () from /usr/lib64/libvirt.so.0 #6 0x00007ffff78ce711 in virStreamAbort () from /usr/lib64/libvirt.so.0 #7 0x000000000042b546 in ?? () #8 0x000000000042b8f3 in ?? () #9 0x00007ffff78c983a in ?? () from /usr/lib64/libvirt.so.0 #10 0x00007ffff7843cc5 in virEventPollRunOnce () from /usr/lib64/libvirt.so.0 #11 0x00007ffff78428f5 in virEventRunDefaultImpl () from /usr/lib64/libvirt.so.0 #12 0x00007ffff793407d in virNetServerRun () from /usr/lib64/libvirt.so.0 #13 0x000000000040c483 in ?? () #14 0x00007ffff534cbbe in __libc_start_main () from /lib64/libc.so.6 ---Type <return> to continue, or q <return> to quit--- #15 0x000000000040b139 in ?? () #16 0x00007fffffffe7d8 in ?? () #17 0x000000000000001c in ?? () #18 0x0000000000000001 in ?? () #19 0x00007fffffffea73 in ?? () #20 0x0000000000000000 in ?? () After this point libvirtd is dead. # service libvirtd status libvirtd dead but pid file exists >From the mail conversation between you and Andrey we came to know that patch has been provided for this problem. Could you please share us the fix. Thanking you in anticipation. Thanks and Regards, Shree Duth Awasthi.

1 0

[libvirt-users] About live migration with snapshots
by Chiang Hubert 21 Mar '13

21 Mar '13

Hello, I'd like to live migration with snapshots. But it doesn't work. It comes out a message "cannot migrate domain with 1 snapshots" Then I try to trace the code(Libvirt 0.9.8 to 1.0.3), I find out the code in src/qemu/qemu_migration.c @ Line 1395 - 1440 (Libvirt 1.0.3) It will check the VM which has snapshots or not. I just curious about this limitation, why the VM can't live migration with snapshots? What happen if I skip this check? Does it has any suggestion way or virsh command with options to do live migration with snapshots? Thanks a lot. Hubert

3 2

[libvirt-users] SSD Trim needed? Physical Block Device Keep Track Of Guest FS Blocks?
by d hee 21 Mar '13

21 Mar '13

I am trying to figure out if a SSD drive needs to receive trim commands from the KVM guest filesystem(strictly Linux ext4 in this case).... When a file is deleted inside a KVM guest(ext4 and raw image)....If a SSD is the underlying block device that the KVM raw disk image resides on, does the SDD drive need to know which block(s) are marked for reuse within the raw image? Or is it since the Guest raw image is a container that the physical hard drive has no concern about the filesystem blocks within the Guest? Meaning the physical disk would only be concerned with the image itself as a whole...such as if the whole image was deleted? Thanks, -Darin

2 1