- Users - libvirt List Archives

[libvirt-users] VNC Server in libvirt
by Jaime Loureiro Acuña 09 Apr '13

09 Apr '13

My name is Jaime Loureiro and I work in the Network & Applications area in University of Vigo. I am writing to you hoping you can help me with some libvirt graphics issues. I was analysing the source code of the libvirt in order to find how to access the display of each virtual machine. We are trying to generate a video streaming from the graphics content, though it is not easy to find what function is the most appropriate to do that. We tried to use the screenshot feature, but the rate is to low to generate a smooth streaming. I suposse the vnc server is reading the graphics output of each virtual machine at a low level, however I cannot find the exact point where the server is. Currently I am trying to understand the function "virDomainOpenGraphics" in libvirt.c and, at a lower level, the function "qemuProcessHandleGraphics" in qemu_process.c, but I 'm not sure if it is possible to get what we need from them. I would appreciate any help or clue you could provide regarding this issue. Thank you very much in advance. Best regards,

2 1

[libvirt-users] reset = destroy start
by 邓焕聪 08 Apr '13

08 Apr '13

what is different between destroy -> start and reset in virsh? i meet this position , when i reset a domain, it cannot start , it stoped at initialize initd.but when i destory it ,and start it , it can run normally. i am very confuse about them. who can tell me the difference.... thanks a lots.

2 1

[libvirt-users] 2 Problems with attaching/detaching disks with virsh and KVM
by Daniele Testa 08 Apr '13

08 Apr '13

Hi, I am having 2 issues with disks and KVM. ISSUE 1: I am unable to detach a disk from a running KVM. (root@h2)-(/tmp)# virsh dumpxml vps_99 <domain type='kvm' id='224'> <name>vps_99</name> <uuid>5e24e17c-f0e4-1030-ac57-0050560018a2</uuid> <memory>524288</memory> <currentMemory>524288</currentMemory> <vcpu>1</vcpu> <os> <type arch='x86_64' machine='pc-0.12'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <on_poweroff>restart</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/kvm</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/nbd1'/> <target dev='vda' bus='virtio'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/nbd2'/> <target dev='vdb' bus='virtio'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/nbd3'/> <target dev='vde' bus='virtio'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/nbd4'/> <target dev='vdg' bus='virtio'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/nbd5'/> <target dev='vdi' bus='virtio'/> </disk> <interface type='bridge'> <mac address='00:50:56:00:1b:24'/> <source bridge='br0'/> <target dev='vnet3'/> <model type='virtio'/> </interface> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='5999' autoport='no' keymap='en-us'/> <video> <model type='cirrus' vram='9216' heads='1'/> </video> </devices> <seclabel type='dynamic' model='apparmor'> <label>libvirt-5e24e17c-f0e4-1030-ac57-0050560018a2</label> <imagelabel>libvirt-5e24e17c-f0e4-1030-ac57-0050560018a2</imagelabel> </seclabel> </domain> (root@h2)-(/tmp)# cat disk.xml <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/nbd5'/> <target dev='vdi' bus='virtio'/> </disk> (root@h2)-(/tmp)# virsh detach-device vps_99 disk.xml error: Failed to detach device from disk.xml error: operation failed: disk vdi cannot be detached - no PCI address for device (root@h2)-(/tmp)# virsh detach-disk vps_99 vdi error: operation failed: disk vdi cannot be detached - no PCI address for device I have tried specifing a <address> for each disk, ie: address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> However, I still get the same "no PCI" error. I am able to add and remove NEW disks to the virtual server after it has been started, but I can't detach the disks that were defined when the KVM was created (even though it looks exactly the same in the XML-file). ISSUE 2: When I add a disk to a KVM running linux (ubuntu in this case), it totally ignores my "target dev". I.e if I specify this: <target dev='vdi' bus='virtio'/> The disk is still being detected as "vdc". Removing the disk and adding it again, gives it "vdd" etc. So it seems it is pretty much just increamenting the letter and totally ignore my config. I read in the documentation that the target defined is just a "hint" for the system and is not always honered, but sorry, I simply cannot accept that :) There must be a way to specify the device the disk should be connected to. Amazon Web Services seems to be able to do this just fine. It will be a pain to write automated scripts when new disks are just attached to random devices. Regards, Daniele

1 0

[libvirt-users] URL to install Ubuntu Server guest
by Javi Legido 05 Apr '13

05 Apr '13

Hi there. Can somebody please confirm if the url to install an Ubuntu Server is http://archive.ubuntu.com/ubuntu/dists/quantal/main/installer-amd64/ ? If not kindly provide the right one. I want to perform a net installation, rather than point to an .iso image. Regards. Javier

1 1

[libvirt-users] virt-manager slow to connect, hangs on new host dialog
by martin f krafft 04 Apr '13

04 Apr '13

Hello, I am using virt-manager 0.9.4 on a Debian unstable system (libvirt 0.9.12) to connect to a libvirtd via SSH running on a Debian testing system (also version 0.9.12), and I have a problem using virt-manager, which first takes ages to connect, then freezes. The SSH connection is top-quality, the hosts are next to each other and connected by Gigabit Ethernet. virsh connections work fine. Unfortunately, when I run virt-manager and connect to the host, the host's capabilities are fetched very quickly (according to virt-manager's debug output), but it then takes 20–30 seconds until the connection is established. Logging libvirtd with log_level=2 produces nothing useful. Hence I tried with log_level=1, which is mayhem. Attached is the log output from the moment I told virt-manager to connect until shortly after the connection has been established. Maybe someone can figure out what's going on? I cannot… The next problem is that when I then try to create a host, I am shown the dialog and can enter one or two characters into the name field, then the GUI completely freezes, and so does libvirtd on the other system (ctrl-c does not work anymore). I have also captured this part of the session in a second log file, which provides no clues for me. Does anyone else know what might be going on? Thanks, -- martin | http://madduck.net/ | http://two.sentenc.es/ "es ist immer etwas wahnsinn in der liebe. es ist aber auch immer etwas vernunft im wahnsinn." - friedrich nietzsche spamtraps: madduck.bogus(a)madduck.net

2 8

[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

Re: [libvirt-users] [libvirt] how to use svirt
by Alex Jia 03 Apr '13

03 Apr '13

On 04/03/2013 10:25 AM, yue wrote: > > hi,all > > i know svirt is merged into libvirt upstream, but how to use them? > You had better to ask this kind of question to libvirt-users(a)redhat.com in the future, it's a user mail listing, you may ask all kind of libvirt usage questions if you want, the following is some reference: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/h… http://libvirt.org/drvqemu.html#securitysvirt http://danwalsh.livejournal.com/30565.html > > thanks > > > > > -- > libvir-list mailing list > libvir-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/libvir-list

2 1

[libvirt-users] Cannot recv data: Connection reset by peer
by Guillaume Thouvenin 03 Apr '13

03 Apr '13

Hello, I'm trying to install and use libvirt 1.0.4 on an Ubuntu 12.04.2. I compiled libvirt by doing: $ ./configure --with-selinux=no --with-gnutls $ make $ sudo make install Everything works fine and are installed under /usr/local Then I started the libvirtd manually and try to start a linux container that has the following configuration: $ virsh -c lxc:/// dumpxml lxcvm1 <domain type='lxc'> <name>lxcvm1</name> <uuid>168edaae-e3b5-2d06-7c65-9aa444a6f234</uuid> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='x86_64'>exe</type> <init>/bin/sh</init> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/local/libexec/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/home/thouveng/lxc_dir/lxcvm1/rootfs'/> <target dir='/'/> </filesystem> <console type='pty'> <target type='lxc' port='0'/> </console> </devices> </domain> When I start the container I have the following error: $ virsh -c lxc:/// start lxcvm1 error: Failed to start domain lxcvm1 error: internal error guest failed to start: PATH=/bin:/sbin TERM=linux container=lxc-libvirt container_uuid=168edaae-e3b5-2d06-7c65-9aa444a6f234 LIBVIRT_LXC_UUID=168edaae-e3b5-2d06-7c65-9aa444a6f234 LIBVIRT_LXC_NAME=lxcvm1 /bin/sh error receiving signal from container: Input/output error The libvirtd is started with info option so I can see: 2013-04-03 08:49:20.167+0000: 17046: error : virNetSocketReadWire:1362 : Cannot recv data: Connection reset by peer 2013-04-03 08:49:20.267+0000: 17051: error : virLXCProcessStart:1248 : internal error guest failed to start: PATH=/bin:/sbin TERM=linux container=lxc-libvirt container_uuid=168edaae-e3b5-2d06-7c65-9aa444a6f234 LIBVIRT_LXC_UUID=168edaae-e3b5-2d06-7c65-9aa444a6f234 LIBVIRT_LXC_NAME=lxcvm1 /bin/sh error receiving signal from container: Input/output error In libvirtd.conf I have: auth_unix_ro = "none" auth_unix_rw = "none" auth_tcp = "none" auth_tls = "none" And in libvirt.conf everything is commented. I have this error as normal user (in libvirtd group) and also as root. Any hints to go further in the debugging are welcome. Regards, Guillaume

2 2

[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] problem in view vm created by virsh create
by 高松 02 Apr '13

02 Apr '13

<domain type='kvm'> <name>eucalyptus-windows</name> <os> <type>hvm</type> <boot dev='cdrom'/> </os> <features> <acpi/> </features> <memory>524288</memory> <vcpu>1</vcpu> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='file'> <source file='/root/windows.server_2003_sp2.img'/> <target dev='hda'/> </disk> <disk type='file' device='disk'> <source file='/root/secondary.img'/> <target dev='vda' bus='virtio'/> </disk> <disk type='file' device='floppy'> <source file='/root/floppy.img'/> <target dev='fda'/> </disk> <disk type='file' device='cdrom'> <source file='/root/windows_server_2003_sp2.iso'/> <target dev='hdc'/> <readonly/> </disk> <interface type='bridge'> <source bridge='eucabr899'/> <model type='rtl8139'/> </interface>  <graphics type='vnc' port='-1' listen='0.0.0.0' passwd='123456'/> </devices> </domain> ========================================================= I issue the command of "virsh create libvirt-kvm-windows.xml" to create a vm, and it is successful.Above is the content,but when I try to connect to the VM both try vinagre and virt-manager,what I got is only black screen,I can't understand and please help!

2 1

[libvirt-users] nparams in virNodeGetCPUStats and CPU utilization
by Hari Pyla 02 Apr '13

02 Apr '13

Hi, I am trying to get the CPU utilization of a node and I am using virNodeGetCPUStats(...) Here is my code snippet. The error checking is omitted for brevity. /* get the number of params */ retval = virNodeGetCPUStats (conn, VIR_NODE_CPU_STATS_ALL_CPUS,\ NULL, &nparams, 0); printf ("nparams: %d\n", nparams); /* allocate space for the params */ params = (virNodeCPUStatsPtr *) malloc (sizeof (virNodeCPUStats) * nparams ); /* get the values */ retval = virNodeGetCPUStats (conn, VIR_NODE_CPU_STATS_ALL_CPUS,\ params, &nparams, 0); for ( i = 0 ; i < nparams ; i++) { printf ("params[%d].field: %s \tparams[%d].value: %llu\n", i, params[i].field, i, params[i].value); } output: nparams: 4 params[0].field: kernel params[0].value: 77930000000 params[1].field: user params[1].value: 568270000000 params[2].field: idle params[2].value: 471429230000000 params[3].field: iowait params[3].value: 67100000000 The documentation at http://libvirt.org/html/libvirt-libvirt.html on the virNodeGetCPUStats(...) API says that nparams is dynamic. Does that mean that not all params are available for a node? I was hoping that nparams would be 5 and that params[4] would contain the utilization (VIR_NODE_CPU_STATS_UTILIZATION). If the answer to the above is 'yes'. Then, I was wondering as to what would be the correct way to calculate the CPU utilization of a node?. Thanks, --Hari

1 0

[libvirt-users] XML error: missing security model on virsh migrate
by Hari Pyla 02 Apr '13

02 Apr '13

Hi, I am trying to migrate a VM from one node to another and I get the following error message. [user@n0 ~]$ virsh --c qemu:///system migrate --verbose Fedora-17-x86_64-1 qemu+ssh://n1/system error: XML error: missing security model when using multiple labels On both the src and dest nodes, I've disabled SELinux and I have the following libvirt version installed $virsh --connect qemu:///system version --daemon Compiled against library: libvirt 0.10.2 Using library: libvirt 0.10.2 Using API: QEMU 0.10.2 Running hypervisor: QEMU 0.12.1 Running against daemon: 0.10.2 Any help is greatly appreciated. Thanks, --Hari

3 4

[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