- Users - libvirt List Archives

[libvirt-users] add disk problems for domain
by zhijun liu 21 Nov '12

21 Nov '12

hi,all I use Java api `domain.attachDeviceFlags(xml, 0);` to add a disk for domain. the xml file like this: <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/dev/sp1353486595267/v1353488096262'/> <target dev='vdb' bus='virtio'/> </disk> then I use command `virsh detach-disk $domain vdb` to remove the disk. what I said above have no any errors.but the problem is when I restart this vm ,the disk still exist,because I see it from the command `virsh dumpxml $domain` ,how to remove the disk from this domain persistently. thanks in advance. >zhijun

2 1

[libvirt-users] Virtualbox support - documentation
by Brian Candler 21 Nov '12

21 Nov '12

At http://libvirt.org/drvvbox.html it says: "The libvirt VirtualBox driver can manage any VirtualBox version from version 2.2 onwards" However it looks like 4.2 is yet implemented. Perhaps the page could be updated? Thanks, Brian Candler. P.S. I see work is ongoing in this area: http://www.redhat.com/archives/libvir-list/2012-October/msg00038.html http://www.redhat.com/archives/libvir-list/2012-November/msg00575.html

1 0

[libvirt-users] Disk/volume hot-add question
by Harish Patil 21 Nov '12

21 Nov '12

Hello Why is the disk hot-add operation use PCI hotplug ? Below is the hot plugged device using info pci monitor cmd. > Bus 192, device 10, function 0: > SCSI controller: PCI device 1af4:1001 > IRQ 0. > BAR0: I/O at 0xc400 [0xc43f]. > BAR1: 32 bit memory at 0xf0101000 [0xf0101fff]. > id "mydisk" Could someone pls provide all the steps involved upto the point it appears in the guest kernel? Thx >harish

1 0

[libvirt-users] libvir: Domain Config error : internal error malformed uuid element
by huancong deng 19 Nov '12

19 Nov '12

what about this error ??? thanks a lot . -- personal blog : denghuancong.com facebook: facebook.com/denghuancong twitter : twitter.com/denghuancong

2 1

[libvirt-users] Fwd: unable to ping from guests in virbr0 to guests in virbr1 network
by Marwan Tanager 19 Nov '12

19 Nov '12

---------- Forwarded message ---------- From: mallapadi niranjan <niranjan.ashok(a)gmail.com> Date: Mon, Nov 19, 2012 at 7:30 PM Subject: Re: [libvirt-users] unable to ping from guests in virbr0 to guests in virbr1 network To: Marwan Tanager <marwan.tngr(a)gmail.com> On Mon, Nov 19, 2012 at 7:51 PM, Marwan Tanager <marwan.tngr(a)gmail.com>wrote: > On Mon, Nov 19, 2012 at 12:09:53PM +0530, mallapadi niranjan wrote: > > Hi all, > > > > I have 3 guests (2-RHEL4 and 1 RHEL6) and have some issues regarding > > networking between them. The 2 RHEL4 system's use default bridge virbr0 > and > > get ip's of range 192.168.122.0/24 (192.168.122.207, 192.168.122.167) > > > > I created another bridge (virbr1) with NAT forwarding (no dhcp). The > > network i choose was 192.168.100.0/24. And the third system (RHEL6) was > > assigned static ip-addres 192.168.100.101, > > > > >>From the RHEL6 system which uses virbr1 is able to ping systems in > > 192.168.122.0/24 series , but guest systems in 192.168.122.0/24 are not > > able to ping RHEL6 system (in virbr1) network. > > > > >>From the RHEL4 guests i am able to ping the gateway ip's > (192.168.122.1, > > 192.168.100.1) , but not the RHEL6 system > > > > > > Versions: > > Fedora release 16 (Verne) > > libvirt-0.9.6.3-1.fc16.x86_64 > > qemu-kvm-0.15.1-8.fc16.x86_64 > > > > Any hints on what could be the problem > > The problem is caused by the relative order of the iptables rules for > those two > networks. > > When libvirt created virbr1 for the network 192.168.100.0/24 it inserted a > couple of iptables rules on the FORWARDING chain for this interface, but it > added them before the rules of virbr0 on the same chain. Those rules > basically > are ordered as follows (at least on my system which I suspect is different > from > yours since I also had the same problem): > > 1. Forward packets destined for the interface that are part of an > established > connection. > 2. Forward packets coming from the interface. > 3. Forward packets coming from and destined to the same interface > (loopback). > 4. Reject forwarding anything else to the interface. > 5. Reject forwarding anything else from the interface. > okay that seems to be the behaviour: hain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- 0.0.0.0/0 192.168.100.0/24 state RELATED,ESTABLISHED ACCEPT all -- 192.168.100.0/24 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable ACCEPT all -- 0.0.0.0/0 192.168.200.0/24 state RELATED,ESTABLISHED ACCEPT all -- 192.168.200.0/24 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable ACCEPT all -- 0.0.0.0/0 192.168.122.0/24 state RELATED,ESTABLISHED ACCEPT all -- 192.168.122.0/24 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited I can ping from 192.168.100.0/24 -> 192.168.122.0/24 (but not the viceversa) > > Since those rules are inserted for every interface libvirt adds in this > order, > you can only ping from one interface to another if the set of rules for the > interface you are pinging from comes before that of the one you're pinging > to. > Otherwise, rule number 4 of the destination interface will get in the way > since > iptables matches the packets against the rules in a chain according to > their > order on it. > > A possible workaround: > > iptables-save >/path/to/iptables/dump/file > > then, edit the file to move all relevant rules that REJECT things on the > FORWARDING chain to the end of the chain. > > then put this command in your rc.local script: > > cat /path/to/iptables/dump/file | iptables-restore > > This solution is not reliable though because you will need to update the > file > containing the rules every time you add a new virtual network or update the > iptables rules for some other reason. > Right , > > Also, I hinted before at this problem on the list and someone pointed me > that > it's a bug, but nobody confirmed. Read my message on this topic with the > subject: Inconsistent iptables forwarding rules for virtual networks, to > get a > clearer picture. > > Okay, will look in to that mail > > Marwan >

1 0

[libvirt-users] unable to ping from guests in virbr0 to guests in virbr1 network
by mallapadi niranjan 19 Nov '12

19 Nov '12

Hi all, I have 3 guests (2-RHEL4 and 1 RHEL6) and have some issues regarding networking between them. The 2 RHEL4 system's use default bridge virbr0 and get ip's of range 192.168.122.0/24 (192.168.122.207, 192.168.122.167) I created another bridge (virbr1) with NAT forwarding (no dhcp). The network i choose was 192.168.100.0/24. And the third system (RHEL6) was assigned static ip-addres 192.168.100.101, >From the RHEL6 system which uses virbr1 is able to ping systems in 192.168.122.0/24 series , but guest systems in 192.168.122.0/24 are not able to ping RHEL6 system (in virbr1) network. >From the RHEL4 guests i am able to ping the gateway ip's (192.168.122.1, 192.168.100.1) , but not the RHEL6 system Versions: Fedora release 16 (Verne) libvirt-0.9.6.3-1.fc16.x86_64 qemu-kvm-0.15.1-8.fc16.x86_64 Any hints on what could be the problem Regards Niranjan

3 4

[libvirt-users] how to make the volume's format to qcow2 when creating volume
by zhijun liu 19 Nov '12

19 Nov '12

hi,all the following are files of pool and volume. storage pool is based on logical(LVM) and iscsi,now I create volume specified the format to "qcow2" *pool.xml* <pool type='logical'> <name>pool_190</name> <source> <device path='/dev/disk/by-path/ip-192.168.0.190:3260-iscsi-iqn.2012-11.com.cloudking:server.target1-lun-1'/> </source> <target> <path>/dev/pool_190</path> </target> </pool> *volume.xml* <?xml version="1.0" encoding="UTF-8" ?> <volume> <name>volume1</name> <capacity unit="GB">1</capacity> <target> <format type="qcow2" /> </target> </volume> *the problmes is :when the volume created successfully,However, the volume's format is 'raw'* like this image: /dev/pool_190/volume1 *file format: raw* virtual size: 1.0G (1073741824 bytes) disk size: 0 how to resolve this troublesome. libvirt :0.9.8 os:ubuntu12.04 many thanks for any reply....

2 1

Re: [libvirt-users] Failed to build libvirt-1.0.0-1.fc17.src.rpm on a CentOS 6.3 system
by Abbas 16 Nov '12

16 Nov '12

On 11/17/2012 02:47 AM, Frank Shi wrote: > Thanks much Abbas for your prompt response. Right, I have fixed all the > dependency issues. It compiled but failed during running test cases. I > prefer building from src-rpm is because I need to install the package onto > other machines. Building from src-rpm can generate rpm so it makes > future deploy easier. Then the start off point will be CentOS' srpms. You might still need to do some patchwork and testing before you get a working rpm (a reason why there's no third party repo for latest kvm and libvirt). Installing on multiple machines sounds like you tend towards stability and Fedora's packages won't do that job anyway! > Anyway, follow your recommendation, I downloaded the source tar and tried > to compile it from source. This time I am seeing following problems. What > could be the problem? > > Thanks, Frank > > =============== > $ tar xvf libvirt-1.0.0-rc1.tar.gz > $ libvirt-1.0.0 > $ ./configure Try using the supplied autogen script first. > libxl/libxl_conf.c:471: error: 'libxl_domain_build_info' It's a missing dep error. Quick time-savers for latest KVM and Libvirt (on latest CentOS 6.3): # qemu-kvm deps yum install gcc pkgconfig SDL-devel zlib-devel alsa-lib-devel pciutils-devel gnutls-devel glib glib2-devel ./configure --prefix=/usr --sysconfdir=/etc make && make install # libvirt deps yum install git python-devel libtool patch libxml2 libxml2-devel yajl-devel device-mapper-devel libnl-devel ./autogen-sh --system make && make install # packages to remove qemu-img qemu-kvm libvirt libvirt-client virt-top The kvm_intel manually loaded of course! ------ bassu

1 0

[libvirt-users] Failed to build libvirt-1.0.0-1.fc17.src.rpm on a CentOS 6.3 system
by Frank Shi 16 Nov '12

16 Nov '12

Hi, List, I am seeing following problems when building libvirt-1.0.0-1.fc17.src.rpm. The first failed test case is xml2sexprtest as you can see below. $ sudo rpmbuild -ba SPECS/libvirt.spec + make check TEST: virshtest ........................................ 40 ........... 51 OK TEST: sockettest ...................................... 38 OK TEST: virbuftest .... 4 OK TEST: commandtest ..................... 21 OK TEST: virhashtest .............. 14 OK TEST: virnetmessagetest ..... 5 OK TEST: virnetsockettest ............... 15 OK TEST: viratomictest .. 2 OK TEST: utiltest ... 3 OK TEST: virnettlscontexttest ........................................ 40 ........ 48 OK TEST: shunloadtest . 1 OK TEST: virtimetest ............... 15 OK TEST: viruritest .................. 18 OK TEST: virkeyfiletest . 1 OK TEST: virauthconfigtest ...... 6 OK TEST: virbitmaptest ...... 6 OK TEST: virlockspacetest ....... 7 OK TEST: securityselinuxtest TEST: virdrivermoduletest ....... 7 OK TEST: xml2sexprtest .!.!!.....................!..!!!!.!!!!!! 40 !!!!!!!!!!... 53 FAIL TEST: sexpr2xmltest ........................................ 40 ........... 51 OK TEST: xmconfigtest ..............!.!.!.!.!.!.!.!.!.!.!.!.!. 40 !.!.!.!.!.!.!.!.!...!.!.!. 66 FAIL TEST: xencapstest .......... 10 OK TEST: statstest TEST: reconnect TEST: qemuxml2argvtest ........................................ 40 ........................................ 80 ........................................ 120 ........................................ 160 ........................................ 200 ........................................ 240 ...... 246 OK TEST: qemuxml2xmltest ........................................ 40 ........................................ 80 ................................... 115 OK TEST: qemuxmlnstest ....... 7 OK TEST: qemuargv2xmltest ........................................ 40 ................................... 75 OK TEST: qemuhelptest ................ 16 OK TEST: domainsnapshotxml2xmltest ....... 7 OK TEST: qemumonitortest .. 2 OK TEST: qemumonitorjsontest !!!!! 5 FAIL TEST: esxutilstest .... 4 OK TEST: vmx2xmltest ........................................ 40 .......... 50 OK TEST: xml2vmxtest ........................................ 40 ..... 45 OK TEST: networkxml2xmltest ................ 16 OK TEST: networkxml2argvtest ......... 9 OK TEST: nwfilterxml2xmltest ........................................ 40 . 41 OK TEST: storagevolxml2xmltest ....... 7 OK TEST: storagepoolxml2xmltest ............. 13 OK TEST: nodedevxml2xmltest ............. 13 OK TEST: interfacexml2xmltest ................... 19 OK TEST: cputest ........................................ 40 .......................... 66 OK TEST: eventtest ............... 15 OK TEST: libvirtdconftest ....................................... 39 OK make[1]: *** [check-TESTS] Error 1 make: *** [check-am] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.E2o2Vs (%check) Bad exit status from /var/tmp/rpm-tmp.E2o2Vs (%check) Not sure whether the failures are related to xml. Anyway, following is a list of xml packages installed, python-lxml-2.2.3-1.1.el6.x86_64 xmldb-api-sdk-0.1-0.4.20011111cvs.1.5.el6.noarch xmlto-0.0.23-3.el6.x86_64 xmlrpc-c-1.16.24-1209.1840.el6.x86_64 xml-commons-resolver-1.1-4.18.el6.x86_64 xmlrpc-c-client-1.16.24-1209.1840.el6.x86_64 xmldb-api-0.1-0.4.20011111cvs.1.5.el6.noarch xmlrpc3-client-3.0-4.15.el6.noarch xmlgraphics-commons-1.3.1-1.1.el6.noarch libxml2-devel-2.7.6-4.el6_2.4.x86_64 libxml2-2.7.6-4.el6_2.4.x86_64 xml-common-0.6.3-32.el6.noarch perl-libxml-perl-0.08-10.el6.noarch libxml2-python-2.7.6-4.el6_2.4.x86_64 xml-commons-apis-1.3.04-3.6.el6.x86_64 # cat /proc/version Linux version 2.6.32-279.el6.x86_64 (mockbuild(a)c6b9.bsys.dev.centos.org) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Fri Jun 22 12:19:21 UTC 2012 Thanks, Frank

2 1

[libvirt-users] authentication failed, but why?
by huancong deng 16 Nov '12

16 Nov '12

I set the me into the group libvirt and write the config for libvirtd: ================================================== listen_tls = 0 listen_tcp = 0 auth_tcp = "none" mdns_adv = 0 unix_sock_group = "libvirt" unix_sock_ro_perms = "0770" unix_sock_rw_perms = "0770" unix_sock_dir = "/var/run/libvirt" log_filters = "1:libvirt 1:util 1:qemu" log_output = "1:file:/var/log/libvirt/libvirtd.log" max_clients = 500 min_workers = 10 max_workers = 50 max_requests = 50 max_client_requests = 8 =========================================== but I can't login the libvirt: [xxxxxx@u70 ~]$ virsh error : authentication failed: Authorization requires authentication but no agent is available. who can tell me why? thanks a lot. :)

1 0

[libvirt-users] Handling connection closes in (older) Sys::Virt
by Henrik Ahlgren 14 Nov '12

14 Nov '12

I hope this is the correct mailing list for discussing the Sys::Virt Perl module. It appears that the most recent version has a new method called register_close_callback that, I believe, can be used to catch errors when the connection to libvirt is closed, e.g. due to libvirt restart or a network related issue. (I've been testing this simply by killing the the SSH process in the libvirt server.) However, Debian still ships libvirt 0.9.12 in stable backports and testing, as probably do many other mainstream distributions. The latest Perl bindings that can be installed from CPAN is thus 0.9.12 and it does not have support for close callbacks. Not only that, when a Perl program loses the (ssh) connection to libvirt, Perl just crashes: Program received signal SIGPIPE, Broken pipe. 0x00007ffff73de0d0 in __write_nocancel () from /lib/libpthread.so.0 Setting a $SIG{PIPE} handler does not seem to help. Is there any possibility of a Perl program surviving and gracefully handling a closed libvirt connection with libvirt version 0.9.12 or older? Henrik

2 4

[libvirt-users] Virt-io Kernels for older RHEL/CentOS versions
by Chandana De Silva 14 Nov '12

14 Nov '12

All, I need to run a number of guests which user older distributions of RHEL and CentOS on an RHEL 6.3 host. The versions are; 4.8 - i386 5.1 - i386 5.2 - x86_64 5.3 - i386 Currently I am running these with the E1000 network driver and the IDE driver. Where can I find kernels (or modules) for virtio for these OS's ? Thanks in advance Chandana

2 2

[libvirt-users] virt-install kickstart local file
by Joe Linoff 13 Nov '12

13 Nov '12

Hi Everybody: I am trying to get virt-install to work with a kickstart file that is on the local file system. I tried using the --initrd-inject="/tmp" --extra-args="ks=file:/myks.cfg" but I got this error message: ERROR --extra-args only work if specified with --location. Here is the basic command: virt-install \ --accelerate \ --cdrom /tools/iso/CentOS-6.3-x86_64-bin-DVD1.iso \ --disk device=disk,path="/var/lib/libvirt/images/myguest.img" \ --graphics vnc \ --name myguest \ --os-type linux \ --os-variant rhel6 \ --ram 2048 \ --vpcus 1,maxvcpus=4 \ --initrd-inject "/tmp" \ --extra-args "ks=file:/myks.cfg" Why do I need the location? I thought that was only used when installatiing from a distribution tree. I am using a DVD ISO image. If I have to use it, how would I specify it? If this approach won't work, I could move the ks.cfg file to an NFS mounted file system but I am not sure what the syntax is for that. I am running this on a CentOS 6.3 system. libvirt: 0.9.10 qemu: 0.12.1 Thank you, Joe

2 1

[libvirt-users] virt-viewer X forwarding through ssh broken since FC17 upgrade?
by Ken Coar 13 Nov '12

13 Nov '12

Ever since I upgraded my laptop from FC15 to FC17, I've been getting this message when I ssh to some RHEL6 hosts inside Red Hat. In particular, I'm trying to do this: virt-viewer --connect \ qemu+ssh://kvm11.devlab.phx1.redhat.com/system \ bork-s01.candlepin.dev.devlab.phx1.redhat.com This is the message I get: X11 forwarding request failed on channel 0 A viewer window pops up for a fraction of a second and then goes away. Using -vvvv on the local ssh command gives a few possibly related messages: debug2: x11_get_proto: /usr/bin/xauth list :0.0 2>/dev/null debug1: Requesting X11 forwarding with authentication spoofing. debug2: channel 0: request x11-req confirm 1 debug1: Requesting authentication agent forwarding. debug2: channel 0: request auth-agent-req(a)openssh.com confirm 0 : debug1: Remote: No xauth program; cannot forward with spoofing. This is new, and, not being an X maven, largely opaque to me. xauth is provided by package xorg-x11-xauth, which is typically *not* installed. Installing it on the system to which I'm trying to ssh gets rid of the message, but doesn't change the up-down behaviour of the viewer window. Temporarily moving my local /usr/bin/xauth leads to this message in addition: Warning: No xauth data; using fake authentication data for X11 forwarding. X11 forwarding request failed on channel 0 Since there's a window popping up at all, I doubt this is directly related to the problem getting the viewer to run. However, on systems *with* xauth installed 'echo $DISPLAY' shows a value, but on those *without* xauth, $DISPLAY is null. (So why am I getting any sort of X popup at all in that case?) Has anyone else seen this, and hopefully have a solution? The problem is actually two-fold: 1. Why 'X11 forwarding failed' and how to get rid of it/revert to behaviour in previous versions; and 2. Why is virt-viewer dying and how to keep it alive. (Again, how to revert to 'it *used* to work' conditions. ;-) ) Thanks! -- #ken B-)} Ken Coar, RHCE, RHCSA, Sanagendamgagwedweinini IT Engineering Tower, Red Hat/RDU "Millennium hand and shrimp!"

2 2

[libvirt-users] difference between ` virsh save ` and `virsh snapshot
by zhijun liu 13 Nov '12

13 Nov '12

what the difference between ` virsh save ` and `virsh snapshot`? are they all used for backup for vm?have any details articles to introduce vm bakcup or image bakcup with libvirt? thanks in advance. liuzhijun

2 1

[libvirt-users] Threads per vCPU and vCPU clock
by Vinicius Gonçalves Braga 13 Nov '12

13 Nov '12

Hi, is there a way to get the number of threads per vCPU and the vCPU clock? Thanks!

2 1

[libvirt-users] the acl mode of files created by libvirtd
by Hao.Zhang 12 Nov '12

12 Nov '12

Hi, all I use virsh save command to dump a domain, the mode is 0600, and belongs to "root", how can i change the mode? Thanks. William -- That night, I thanked God for seeing me thought the day of days and prayed I would make it through tomorrow. I also promised that if some day I could get home again, I would find a nice peaceful town and spend rest of my life in peace.

2 1

[libvirt-users] where is libvirt-python document??
by 宣铭艺 12 Nov '12

12 Nov '12

Hi libvirt users: Who can tell me where is the fucking doc? I want to use libvirt-python in my project.But I can't found the doc. I only found "TBD" in http://libvirt.org/guide/html/Application_Development_Guide-Language_Bindin… Did I miss something? Thanks. -- 樱宝宝: http://www.xuanmingyi.com

3 4

[libvirt-users] the acl mode of files created by libvirtd
by Hao.Zhang 11 Nov '12

11 Nov '12

Hi, all I use virsh save command to dump a domain, the mode is 0600, and belongs to "root", how can i change the mode? William -- That night, I thanked God for seeing me thought the day of days and prayed I would make it through tomorrow. I also promised that if some day I could get home again, I would find a nice peaceful town and spend rest of my life in peace.

1 0

[libvirt-users] [LXC][Openstack] Clarifications needed on usage of libvirt-lxc for openstack
by Sujay M 11 Nov '12

11 Nov '12

Hi everyone, I've some doubts regarding the usage/working of libvirt-lxc with openstack. I'm doing a project titled "Low density virtualization for Storage cloud" 1. Can i use libvirt for lxc with Openstack swift alone (excluding nova, glance and keystone)? If no what other openstack components should i use for virtualization? (Is it necessary to install openstack nova to do virtualization with libvirt-lxc?) 2. How virtualization for storage services work ? Any good articles. 3. I want to set up a cloud storage environment with low density virtualization ie lxc. I'm using Openstack swift (Object storage) for storage services. I want to virtualize this. Few resources on how i can do this using libvirt-lxc? -- Best Regards, Sujay M Final year B.Tech Computer Engineering NITK Surathkal contact: +918971897571

2 1

[libvirt-users] move VM disk images between storage pools on the same host
by Paul Raines 09 Nov '12

09 Nov '12

I created a new LVM type storage pool on my server and would like to move my VM disk volumes in a directory-based pool into this new pool. But I cannot figure out how that is done. I find plenty of information on how to migrate live VM images from one host to another, but not on how to just move one live from one storage pool to another on the same host. If it cannot be done live, how an I do it non-live? I guess non-live I could clone, but that would change the MAC address. Just seems that if libvirt can migrate live it should be able to move a VM between storage pools on the same host even easier. --------------------------------------------------------------- Paul Raines http://help.nmr.mgh.harvard.edu MGH/MIT/HMS Athinoula A. Martinos Center for Biomedical Imaging 149 (2301) 13th Street Charlestown, MA 02129 USA The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.

3 3

[libvirt-users] Updating an "interface" device has no effect on network filters
by Guido Winkelmann 09 Nov '12

09 Nov '12

Hi, I am trying to update the network filters on running guest machines (qemu backend) without having to restart the domain. Say I have a running domain "test" with this interface: <interface type='bridge'> <mac address='52:54:00:84:6d:6d'/> <source bridge='virbr1'/> <model type='virtio'/> <filterref filter='clean-traffic-with-v6'> <parameter name='IP' value='172.18.1.9'/> <parameter name='IPV6' value='fe80::5054:ff:fe84:6d6d'/> <parameter name='MAC' value='52:54:00:84:6d:6d'/> </filterref> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> Now I want that domain to be able to use an additional IP address for some reason, so I write a file uppdevice.xml with this content: <interface type='bridge'> <mac address='52:54:00:84:6d:6d'/> <source bridge='virbr1'/> <model type='virtio'/> <filterref filter='clean-traffic-with-v6'> <parameter name='IP' value='172.18.1.9'/> <parameter name='IP' value='172.18.1.10'/> <parameter name='IPV6' value='fe80::5054:ff:fe84:6d6d'/> <parameter name='MAC' value='52:54:00:84:6d:6d'/> </filterref> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> and run update-device test-cpu-restrict2 upddevice.xml in virsh. This appears to work without problems and produces no error messages (it prints "Device updated successfully"), except the ebtables script on the host machine does not get updated after that and consequently, the new IP address is not usable. Regards, Guido

1 0

[libvirt-users] Failed to access console after launching LXC through libvirt
by unicell 09 Nov '12

09 Nov '12

Hi, I'm trying to manage LXC instances through OpenStack, which use libvirt as a virtualization driver layer. After launching LXC instance, I simply could not attach to the console. virsh # list Id Name State ---------------------------------- 14366 instance-00000078 running virsh # console 14366 Connected to domain instance-00000078 Escape character is ^] And it keeps stuck here. Initially I thought it could be a cgroup device config issue, and tried to "echo ‘c 5:1 rwm' >/cgroup/devices/libvirt/lxc/instance-00000078/devices.allow“, to add /dev/console access right to the container. But it does not work, console stilll not working. Before the cgroup tweaking, devices.list are as follows [root@localhost libvirt]# cat /cgroup/devices/libvirt/lxc/instance-0000007a/devices.list c 1:3 rwm c 1:5 rwm c 1:7 rwm c 1:8 rwm c 1:9 rwm c 5:0 rwm c 5:2 rwm c 136:* rwm I'm not quite sure what kind of issue could possibly cause this console access issue. Cause I'm now using two different guest OS templates on two different host OSes. Following are some symptoms I observed. * (g) for container guest OS * (h) for host OS * NOTE: Ubuntu guest os are generated by lxc-create -t ubuntu, which is an Ubuntu 12.04 based lxc template. CentOS guest os are handcrafted by myself, taking reference of http://wiki.1tux.org/wiki/Lxc/Installation/Guest/Centos/6 1. Ubuntu (g) launched by lxc-start on Ubuntu 12.04 host, console works 2. Ubuntu (g) launched by OpenStack / libvirt on Ubuntu 12.04 host, console works 3. Ubuntu (g) launched by OpenStack / libvirt on CentOS 6.3 host, console NOT works 4. CentOS (g) launched by lxc-start on Ubuntu 12.04 host, console works 5. CentOS (g) launched by OpenStack / libvirt on Ubuntu12.04 host, console NOT works 6. CentOS (g) launched by OpenStack / libvirt on CentOS 6.3 host, console NOT works So somehow I feel it could be something related to LXC template rootfs, but Host OS do make a difference (2 vs. 3). lxc-start / libvirt also makes a difference (4 vs. 5), but that might be caused by cgroup setting. Could someone shed me some clues to further digging this issue? Thanks! -- Qiu Yu

3 8

[libvirt-users] A warning about "async message processing ."
by xuanmao_001 09 Nov '12

09 Nov '12

Hi, all: when I used virsh connect host like "virsh connect qemu+tcp://root@ip_address/system", I had a warning message about "warning: virNetClientIncomingEvent: 1660 : Something went wrong during async message processing" But I can even operated. Is there a reason can cause the warning? thanks. xuanmao_001

1 1

[libvirt-users] OpenStack+libvirt+lxc: lxcContainerGetSubtree:1199 : Failed to read /proc/mounts
by unicell 08 Nov '12

08 Nov '12

Hi, I'm running OpenStack on CentOS 6.3 to manage lxc instances. And running into series of problem relating libvirt and lxc interaction. For example, libvirt_lxc segfault ( https://bugzilla.redhat.com/show_bug.cgi?id=874549) which has an upstream fix. And another bugs such as fail to start when SELinux disabled. Finally, I decides to adopt libvirt 0.10.2, self compiled from libvirt-0.10.2-1.fc17.src.rpm. And now coming across following message when starting lxc container. lxcContainerGetSubtree:1199 : Failed to read /proc/mounts: No such file or directory Could it be something related to my container template setting? Or host setting? Or simply just another bug? I'm not a libvirt guy, so please, do shed me some lights on how to fix it. Thanks very much. libvirtd log with LIBVIRT_DEBUG=1 -- 2012-11-08 12:41:10.106+0000: 28362: info : libvirt version: 0.10.2, package: 1.el6 (Unknown, 2012-11-08-20:20:52, localhost) 2012-11-08 12:41:10.106+0000: 28362: error : virLXCControllerRun:1418 : error receiving signal from container: Input/output error 2012-11-08 12:41:10.222+0000: 24641: error : virNetDevSetOnline:536 : Cannot get interface flags on 'veth0': No such device 2012-11-08 12:41:10.227+0000: 24641: error : virNWFilterDHCPSnoopEnd:2131 : internal error ifname "veth0" not in key map 2012-11-08 12:41:10.229+0000: 24641: error : virNetDevGetIndex:653 : Unable to get index for interface veth0: No such device 2012-11-08 12:41:10.370+0000: 24640: error : virLXCProcessStop:701 : internal error Invalid PID -1 for container 2012-11-08 12:41:10.370+0000: 24640: error : virLXCProcessStop:701 : internal error Invalid PID -1 for container 2012-11-08 12:48:26.136+0000: 30706: info : libvirt version: 0.10.2, package: 1.el6 (Unknown, 2012-11-08-20:20:52, localhost) 2012-11-08 12:48:26.136+0000: 30706: error : virDomainObjParseNode:10094 : XML error: unexpected root element <domain>, expecting <domstatus> 2012-11-08 12:48:50.878+0000: 30695: error : virNetSocketReadWire:1176 : Cannot recv data: Connection reset by peer 2012-11-08 12:48:50.977+0000: 30698: error : virLXCProcessStart:1145 : internal error guest failed to start: PATH=/bin:/sbin TERM=linux container=lxc-libvirt container_uuid=ecc871cb-58be-4ae4-b216-a8a62b894a7f LIBVIRT_LXC_UUID=ecc871cb-58be-4ae4-b216-a8a62b894a7f LIBVIRT_LXC_NAME=instance-00000077 LIBVIRT_LXC_CMDLINE=console=ttyS0 /sbin/init 2012-11-08 12:48:50.863+0000: 1: info : libvirt version: 0.10.2, package: 1.el6 (Unknown, 2012-11-08-20:20:52, localhost) 2012-11-08 12:48:50.863+0000: 1: error : lxcContainerGetSubtree:1199 : Failed to read /proc/mounts: No such file or directory 2012-11-08 12:48:50.863+0000: 31202: info : libvirt version: 0.10.2, package: 1.el6 (Unknown, 2012-11-08-20:20:52, localhost) 2012-11-08 12:48:50.863+0000: 31202: error : virLXCControllerRun:1418 : error receiving signal from container: Input/output error 2012-11-08 12:48:50.979+0000: 30698: error : virNetDevSetOnline:536 : Cannot get interface flags on 'veth0': No such device 2012-11-08 12:48:50.984+0000: 30698: error : virNWFilterDHCPSnoopEnd:2131 : internal error ifname "veth0" not in key map 2012-11-08 12:48:50.986+0000: 30698: error : virNetDevGetIndex:653 : Unable to get index for interface veth0: No such device 2012-11-08 12:48:51.127+0000: 30695: error : virLXCProcessStop:701 : internal error Invalid PID -1 for container 2012-11-08 12:48:51.128+0000: 30695: error : virLXCProcessStop:701 : internal error Invalid PID -1 for container 2012-11-08 12:48:54.709+0000: 30695: error : virNetSocketReadWire:1184 : End of file while reading data: Input/output error 2012-11-08 12:48:54.710+0000: 30695: error : virNetSocketReadWire:1184 : End of file while reading data: Input/output error lxc log -- tail -f lxc/instance-00000077.log 2012-11-08 12:48:50.723+0000: starting up PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin LIBVIRT_DEBUG=3 LIBVIRT_LOG_OUTPUTS=3:stderr /usr/libexec/libvirt_lxc --name instance-00000077 --console 21 --security=none --handshake 24 --background --veth veth1 PATH=/bin:/sbin TERM=linux container=lxc-libvirt container_uuid=ecc871cb-58be-4ae4-b216-a8a62b894a7f LIBVIRT_LXC_UUID=ecc871cb-58be-4ae4-b216-a8a62b894a7f LIBVIRT_LXC_NAME=instance-00000077 LIBVIRT_LXC_CMDLINE=console=ttyS0 /sbin/init 2012-11-08 12:48:50.863+0000: 1: info : libvirt version: 0.10.2, package: 1.el6 (Unknown, 2012-11-08-20:20:52, localhost) 2012-11-08 12:48:50.863+0000: 1: error : lxcContainerGetSubtree:1199 : Failed to read /proc/mounts: No such file or directory 2012-11-08 12:48:50.863+0000: 31202: info : libvirt version: 0.10.2, package: 1.el6 (Unknown, 2012-11-08-20:20:52, localhost) 2012-11-08 12:48:50.863+0000: 31202: error : virLXCControllerRun:1418 : error receiving signal from container: Input/output error libvirt xml -- <domain type='lxc'> <name>instance-00000077</name> <uuid>ecc871cb-58be-4ae4-b216-a8a62b894a7f</uuid> <memory unit='KiB'>524288</memory> <currentMemory unit='KiB'>524288</currentMemory> <vcpu placement='static'>2</vcpu> <os> <type arch='x86_64'>exe</type> <init>/sbin/init</init> <cmdline>console=ttyS0</cmdline> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/libexec/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/home/stack/nova_state/instances/instance-00000077/rootfs'/> <target dir='/'/> </filesystem> <interface type='bridge'> <mac address='fa:16:3e:40:ec:11'/> <source bridge='br100'/> <filterref filter='nova-instance-instance-00000077-fa163e40ec11'> <parameter name='DHCPSERVER' value='10.48.253.1'/> <parameter name='IP' value='10.48.253.2'/> <parameter name='PROJMASK' value='255.255.255.0'/> <parameter name='PROJNET' value='10.48.253.0'/> </filterref> </interface> <console type='pty'> <target type='lxc' port='0'/> </console> </devices> </domain> cat /proc/mounts -- [root@localhost libvirt]# cat /proc/mounts rootfs / rootfs rw 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 devtmpfs /dev devtmpfs rw,nosuid,relatime,size=32967000k,nr_inodes=8241750,mode=755 0 0 devpts /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0 /dev/sda2 / ext4 rw,relatime,barrier=1,data=ordered 0 0 /proc/bus/usb /proc/bus/usb usbfs rw,relatime 0 0 /dev/mapper/xenvg-home /home ext4 rw,relatime,barrier=1,data=ordered 0 0 none /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0 sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0 none /noah/tmp tmpfs rw,relatime,mode=755 0 0 cgroup /cgroup/cpuset cgroup rw,relatime,cpuset 0 0 cgroup /cgroup/cpu cgroup rw,relatime,cpu 0 0 cgroup /cgroup/cpuacct cgroup rw,relatime,cpuacct 0 0 cgroup /cgroup/memory cgroup rw,relatime,memory 0 0 cgroup /cgroup/devices cgroup rw,relatime,devices 0 0 cgroup /cgroup/freezer cgroup rw,relatime,freezer 0 0 cgroup /cgroup/net_cls cgroup rw,relatime,net_cls 0 0 cgroup /cgroup/blk_io cgroup rw,relatime,blkio 0 0 cgroup /cgroup/ns cgroup rw,relatime,ns 0 0 /dev/nbd15 /home/stack/nova_state/instances/instance-00000070/rootfs ext3 rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered 0 0 /dev/nbd14 /home/stack/nova_state/instances/instance-00000071/rootfs ext3 rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered 0 0 /dev/nbd13 /home/stack/nova_state/instances/instance-00000073/rootfs ext3 rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered 0 0 /dev/nbd12 /home/stack/nova_state/instances/instance-00000075/rootfs ext3 rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered 0 0 /dev/nbd11 /home/stack/nova_state/instances/instance-00000076/rootfs ext3 rw,relatime,errors=continue,barrier=1,data=ordered 0 0 /dev/nbd10 /home/stack/nova_state/instances/instance-00000077/rootfs ext3 rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered 0 0 -- Qiu Yu

2 2