April 2012 - Users - libvirt List Archives

[libvirt-users] virsh list not working with xen 4
by Rogério Vinhal Nunes 21 Sep '12

21 Sep '12

Hi, I'm having some trouble to get libvirt to show the correct power state of my virtual machines. I'm using Ubuntu 10.04 + Xen 4.1.1 + libvirt 0.8.8. virsh list --all only shows turned off machines registered in xend. If I turn them on, they just "disappear", and when I start machines directly from xml, they just doesn't appear at all. Libvirt is correctly connecting to xen as I can use the other commands fine, just the list option doesn't seem to work at all. What can I do to change that? # virsh version Compiled against library: libvir 0.8.8 Using library: libvir 0.8.8 Using API: Xen 3.0.1 Running hypervisor: Xen 4.1.0

2 1

[libvirt-users] qemu-kvm fails on RHEL6
by sumit sengupta 02 Jul '12

02 Jul '12

Hi, When I'm trying to run qemu-kvm command on RHEL6(linux kernel 2.6.32) then I get following errors which I think related to tap devices in my setup. Any idea why is that? bash$ LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.2.0 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name instance-00000027 -uuid a93aeed9-15f7-4ded-b6b3-34c8d2c101a8 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-00000027.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -kernel /home/sumitsen/openstack/nova/instances/instance-00000027/kernel -initrd /home/sumitsen/openstack/nova/instances/instance-00000027/ramdisk -append root=/dev/vda console=ttyS0 -drive file=/home/sumitsen/openstack/nova/instances/instance-00000027/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,fd=26,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=fa:16:3e:15:84:3e,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/home/sumitsen/openstack/nova/instances/instance-00000027/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 char device redirected to /dev/pts/1 qemu-kvm: -netdev tap,fd=26,id=hostnet0: TUNGETIFF ioctl() failed: Bad file descriptor TUNSETOFFLOAD ioctl() failed: Bad file descriptor qemu-kvm: -append root=/dev/vda: could not open disk image console=ttyS0: No such file or directory [sumitsen@sorrygate-dr ~]$ rpm -qa qemu-kvm qemu-kvm-0.12.1.2-2.209.el6.x86_64 Let me know if you need any other info. Thanks, Sumit

2 1

[libvirt-users] converting save/dump output into physical memory image
by Andrew Tappert 04 Jun '12

04 Jun '12

A lot of people in the security community, myself included, are interested in memory forensics these days. Virtualization is a natural fit with memory forensics because it allows one to get access to a guest's memory without having to introduce any extra software into the guest or otherwise interfere with it. Incident responders are particularly interested in getting memory dumps from systems they're investigating. Virsh has "save" and "dump" commands for storing the state of a guest to a file on disk, but memory of KVM guests doesn't get saved in the "standard" input format for memory forensics tools, which is a raw physical memory image. (This is what you'd get via the classical "dd /dev/mem" approach or the contemporary equivalent using the crash driver; and VMware Server and Workstation produce .vmem files, which are such raw physical memory images, when a guest is paused or snapshotted.) In order to analyze the memory of Libvirt/KVM guests with my Linux memory forensics software, Second Look, I've created a tool for converting Libvirt-QEMU-save files (output of virsh save command) or QEMU-savevm files (output of virsh dump command) to raw physical memory images. I've got a basic working capability, though I'm still tracking down some problems with a guest allocated 8GB RAM--not all the memory seems to be present in the save or dump file. And I haven't tested very extensively yet, version support is limited to what I myself am currently running, etc. I'd like to know if this is a capability that others are interested in. Is this something that would be of interest to the Libvirt project if I were to contribute the code, or to the KVM project, or do you think it best exists as a separate project? I've also got a proof-of-concept tool for converting hibernate images to raw physical memory images. Perhaps a collection of tools for converting various memory dump formats would be a good project. Anyone else interested in this kind of stuff? As an author of commercial memory forensics software I've got a vested interest in availability of good memory acquisition capabilities. But there are a number of people working on FOSS Linux memory analysis tools, too... Andrew

4 5

Re: [libvirt-users] Snapshot system: really confusing.
by NoxDaFox 23 May '12

23 May '12

Hello, thank you for your fast reply! To help in comprehension I'll explain you a bit what am I trying to realize so the picture will be more clear. Basically it's a platform for debug, what I need is to access to the memory dump image and to the FS ones; I don't need any reverting support. The common lifecycle of a domain is: a) Given a backing store disk (qcow2) I create a new disk image: my_image.qcow2 b) I start this image and play around based on a persistent domain. c) I take several pictures (snapshots, dumps) of the VE state: I need at least readable pictures of the FileSystem and the RAM. d) I shutdown the guest. e) I extract valuable information from the pictures. This is the critical phase where all my doubts on libvirt platform come from. f) I store those information. g) I wipe out everything else. h) Ready for a new test, return to point a). libvirt is a great platform! And documentation is not bad at all. The only nebulous part is the snapshot part (I guessed was on hard development anyway). Now I'll answer to your points. > > Greetings, > > Hello, > > > > > I am developing a platform for test and debug use. > > > > The typical scenario I want to realize is the following: > > > > I run a .qcow2 image via QEMU-KVM, the running OS is not relevant. > > I want to take several snapshots of both Disk and RAM status; same file, > > separate files doesn't matter. > > I just need a way to have consistent information about them (better with > > XML description) and the data as well. > > I want to store these snapshots on my storage devices to use them whenever > > and wherever I want. > > Hopefully libvirt can supply what you are interested in; and be aware > that it is a work in progress (that is, unreleased qemu 1.1 and libvirt > 0.9.12 will be adding yet more features to the picture, in the form of > live block copy). I knew the situation, I saw a RFC of yours that is really interesting as it introduces snapshots of single storage volumes: virStorageVolSnapshotPtr. Really interesting under my point of view. > > > > > > Is it possible to store a single snapshot providing both the memory and > > disks state in a file (maybe a .qcow2 file)? > > Single file: no. Single snapshot: yes. The virDomainSnapshotCreateXML > API (exposed by virsh snapshot-create[-as]) is able to create a single > XML representation that libvirt uses to track the multiple files that > make up a snapshot including both memory and disk state. This would be enough, as long as I'm able to read those information. > > > Is there any way to get a unique interface which handles my snapshots? > > > > I was used to use the virDomainSnapshotCreateXML() defining the destination > > file in the XML with <disk> fields. > > Right now, you have a choice: > > 1. Don't use the DISK_ONLY flag. That means that you can't use <disk> > in the snapshot XML. The snapshot then requires qcow2 files, the VM > state is saved (it happens to be in the first qcow2 disk), and the disk > state is saved via qcow2 internal snapshots. That's good to know, I just got yesterday, reading your mails in the dev mailing list, where snapshots were stored; I always tried to look for a new file, unsuccessfully. > > 2. Use the DISK_ONLY flag. Then you can set up external snapshot file > names (basically, another layer of qcow2 files, where your original file > name is now the snapshot backing the new layer), and you get no VM state > directly. Here is where the <disk> element of the snapshot comes into > play. If you _also_ want to save VM state, you can use 'virsh save' > (virDomainSaveFlags) to save just VM state; but then you have to > coordinate things so that the disk snapshot and the VM state correspond > to the same point in guest time by pausing the guest before taking the > disk snapshot. > > > After updating libvirt it was not working anymore, I thought was a bug but > > then I realized it was intentional. > > The function complains about the fact that the <disk> parameter is not > > accepted anymore. > > What versions of libvirt are you playing with? <disk> was unrecognized > (and ignored) prior to 0.9.5; after that point, it can only be used with > the DISK_ONLY flag, but then you have to take the VM state separately. > I guessed that the <disk> tag was just ignored, I inherited the code from a previous project and I spent the first weeks struggling with what was not working. I was using libvirt 0.8.3-5 from debian squeeze, I migrated to wheezy to be able to access to libguestfs features, now I'm running libvirt 0.9.11. > Someday, I'd like to submit more patches to allow <disk> to be mixed > with live VM state, but I'm not there yet. > > > So I started guessing how to solve reading the API documentation and I fall > > in a completely nebulous world. > > > > For what I got: > > - virDomainSnapshotCreateXML(): > > According to flags can take system checkpoints (really useful) and disks > > snapshots. > > System checkpoints: What I need but I didn't find any way to retrieve the > > storage file; I'm only able to get the snapshot pointer, quite useless as > > from its pointer I can only print the XML description. > > The storage is in internal snapshots of your qcow2 file. Try 'qemu-img > info /path/to/file' to see those internal snapshots. You can also use > > qemu-img convert -s snapname /path/to/image /path/to/output Great! This is the information I needed: how to access to those damned snapshot in a readable way. I still believe anyway that an interface provided by libvirt would be really valuable. I am trying to stay as much as I can on libvirt to work on a higher level of abstraction, this is really important for my architecture. Using directly qemu is quite annoying but if at the moment is the only solution I'll move to that. > > as a way to extract that snapshot into a file that you can use > independently (but only while your guest is not running); alas, qemu > doesn't yet provide a way to extract this information from a running > domain, nor have I yet had time to map this functionality into libvirt > API. But I have requested qemu enhancements to allow it (perhaps by > qemu 1.2), as well as have a vision of where I plan to take the libvirt > API in the next year or so to make this more useful. ATM I don't need "on the fly" extraction, everything is done after turning off the guest, what I need is a way to get its state whenever I want, reading it is another business. But indeed this is something that in a future may be greatly valuable. > > > Disk snapshot: here through the XML description I can specify a target file > > where to write the information. But I still need the memory status. > > - virDomainSaveFlags(): > > No matter how I set the flags, it halts the guest; I need it still running > > afterward and I think that reverting the domain and restarting for my > > scenarios is unaffordable. > > Yeah, that's another thing on my list, to add a flag to > virDomainSaveFlags that will keep the domain running after the save is > complete, and/or enhance virDomainSnapshotCreateXML to incorporate a > domain save to an external file alongside disk snapshots at the same > point in guest time. I'd also like to play with background migration > (right now, virDomainSaveFlags does a foreground migrate-to-file, which > pauses the guest up front; but a minimal downtime solution would use the > live migration path which results in a larger output file but much less > downtime). > > > - virDomainCoreDump(): > > Does what I need for the memory, but doesn't give any XML description and > > doesn't supply any useful interface to handle it, I just get back an int > > that represent the exit status of the routine. > > virDomainCoreDump() and virDomainSaveFlags() both do a migration to > file, it's just that the core dump version isn't designed for reverting > like domain save. And there have been proposals on list for making core > dump management better (such as allowing you to get at a core dump file > from a remote machine; right now, the core dump can only be stored on > the same machine as the guest being dumped). > I think this is bad, why not merging these functions? Under an API point of view (I'm aware of architectural difficulties on the background) this is useless and confusing. Better a virDomainSaveFlags() with several configuration than two different functions. This is a complex system-management API, so anyone who'll use it will be conscious of that; I don't think that many flags and XML files will be confusing as long as they're clearly documented. But having multiple interfaces (alias functions/methods) that basically do the same in a different way with slightly different results is really confusing. Better have a single method configurable with XML files and flags than two without. (This is a point of view of mine as a developer). > > (other functions really similar) > > > > The question is: why all this confusion? > > Different qemu capabilities ('savevm', 'migrate', > 'blockdev-snapshot-sync'), different needs at the time each feature was > first added, etc. Ultimately, virDomainSnapshotCreateXML is the most > powerful interface, and I have plans to make it be a superset of > virDomainSaveFlags(), but I'm not there yet. Indeed is a powerful interface! But again: why those functions do something similar? Isn't better (always under an API point of view) having: - Two different interfaces that handle separately disk and state; if I want to revert/migrate I need to give both the results of those interfaces. - One interface that gives revert/migrate capability and one interface that, via flags or XML, gives the separate components. - Other combinations: may still be done as long as they're clear. Here we have: virDomainSnapshotCreateXML(): Takes complete snapshots, disk snapshots, no single-memory snapshots. It does it keeping the domain alive (paused). It stores information internally if flags=A, externally if flags=B. virDomainSaveFlags(): No complete snapshots, no disk snapshots, takes memory snapshots. It does it stopping the domain. It stores information externally. Under my point of view this can be done in a more clear way. Separation of duties: many small functions that do a single thing and a global one that wraps everything giving a complete package is a good example. > > > I absolutely understand the problematic that realizing a multiplatform > > snapshots management raises; but I think that for an API purpose what is > > implemented here is completely confusing the developer. > > Is there anything I can do to help improve the documentation? I know > that's an area where a picture can speak a thousand words; and as more > features get added into the snapshot picture, it probably becomes more > important to accurately display the various APIs and the advantages for > using each. What's basically missing is data flow and representation, you don't need to realize it by scratch (data format is strongly bound to qemu) but give an idea and provide references. What makes a documentation relevant is the way the reader has to access to information, must be easy! If snapshots reliy to qemu ones just link their documentation as well, so if I don't find enough clues I can go deeper as much as needed. If help is needed I can contribute, I just need to know where to look at when I need something. The platforms I'm working on are really time-consuming but this technology is really important under my point of view as it will reduce the time to maintain them. Thanks again for answering so fast! NoxDaFox PS: I forgot to CC the libvirt-users mailing list, sorry for the spam.

2 3

[libvirt-users] Regarding persistence of VM's after live migration (virDomainMigrateToURI() problem)
by Coding Geek 02 May '12

02 May '12

Hello I am working with 3 host machines each running xen with shared NFS storage. I am working on automatic load balancing if one host is over utilized and another is under utilized by measuring the utilization from xentop. I am facing a problem after migration of VM. I am setting the flags ( 1| 8| 16) in order to do live migration, persist VM on destination, undefine host from source. After migration if I shut off the migrated VM on destination host it does not persist. I am using the migrateToURI() API for migration. Please help how to make VM persist on destination. Thank you, Tasvinder Singh -- -- "To Iterate is Human, To Recurse is Divine"

3 6

[libvirt-users] Console to RHEL6.1 container
by Sukadev Bhattiprolu 01 May '12

01 May '12

We are trying to create RHEL6.1 container and having trouble getting a proper console to the container. I have used lxc containers in the past and lxc has a script (lxc-fedora) to setup a basic Fedora container. Is there something similar or docs with virtmgr ? We started out making a copy of the root fs and using that copy as the root for the container. I made a couple of tweaks to the container rootfs: 1. ensured that /dev/ptmx is a symlink to pts/ptmx 2. Added 'newinstance' option to the devpts mount in fstab The container xml file is attached. If devpts entry in container's fstab has the 'newinstance' option, I get a brief "domain test01 started" message on the stdout. When I run 'virsh consle test01', I only see a few messages --- Setting hostname node03: [ OK ] Setting up Logical Volume Management: No volume groups found [ OK ] Checking filesystems [ OK ] mount: can't find / in /etc/fstab or /etc/mtab Mounting local filesystems: [ OK ] Enabling local filesystem quotas: [ OK ] Enabling /etc/fstab swaps: [ OK ] --- and then a hang wihtout a shell. At ths point sshd or any of the other services don't appear to be running. If I remove the 'newinstance' entry in fstab and run 'virsh start test01' the container starts up ok. I get all "console" messages on whichever is my current /dev/pts/0 ! At this point sshd and many other services are running and I can ssh in. Even in this case, though 'virsh console test01' shows the same _few_ messages as above and no login shell. Back to the newinstance case, by putting some debug messages in the container's /etc/rc.sysinit, I see that devpts is already mounted with newinstance. With lxc, in setup_pts(), we unmount devpts in the container and then mount with newinstance. I wonder what that sequence is with virtmgr. I double checked that /dev/ptmx in container is a symlink to pts/ptmx and that CONFIG_DEVPTS_MULTIPLE_INSTANCES=y. Appreciate any tips on how I can get access to the console of the RHEL6.1 container. Suka Suka

1 1

[libvirt-users] question of iSCSI pool on the same iSCSI target
by david_zhu 28 Apr '12

28 Apr '12

3 2

[libvirt-users] Is there a way for telling libvirt to auto define an xml under /etc/libvirt/qemu?
by Raoul Scarazzini 26 Apr '12

26 Apr '12

Hi everybody, like in the subject: is there a way for telling libvirt to auto define an xml under /etc/libvirt/qemu? I mean, sometimes it happens to have the /etc/libvirt/qemu shared between nodes, say with a NFS share, since I can set a new xml on a node and I want o see the virtual machine on all the others, is there a way to automate this or am I obligated to launch virsh define <xml> on EACH node? Thank you so much, -- Raoul Scarazzini Solution Architect MMUL: Niente è impossibile da realizzare, se lo pensi bene! +39 3281776712 rasca(a)mmul.it http://www.mmul.it

4 3

[libvirt-users] Installing the python libvirt bindings in a virtualenv
by Daniel Gonzalez 26 Apr '12

26 Apr '12

Hi, I have a virtualenv which I am using for production (I need python 2.7 and certain libraries which can not be easily installed on the host environment). Now I am trying to install also libvirt, but I have not succeeded yet. The problem that I have now looks quite difficult to solve. This is the script I am using to install libvirt (bash script): install_libvirt_ ( ) { local myvirtualenv="$1" local libvirt_tag=v0.9.9 cd $TMP_DIR git clone git://libvirt.org/libvirt.git cd libvirt git checkout $libvirt_tag mkdir -p $VIRTUALENVS_DIR/$myvirtualenv/usr sudo apt-get install autopoint # configure: error: You must install the GnuTLS library in order to compile and run libvirt sudo apt-get install -y gnutls-bin gnutls-dev # configure: error: You must install device-mapper-devel/libdevmapper >= 1.0.0 to compile libvirt sudo apt-get install -y libdevmapper-dev libdevmapper # configure: error: You must install python-devel to build Python bindings sudo apt-get install -y python-all-dev ./autogen.sh --prefix=$VIRTUALENVS_DIR/$myvirtualenv/usr --enable-compile-warnings=error make make install } But this is failing with error message: checking for python script directory... ${prefix}/lib/python2.7/site-packages checking for python extension module directory... ${exec_prefix}/lib/python2.7/site-packages configure: error: You must install python-devel to build Python bindings python-devel does not exist. I have used python-all-dev, but it has not solved the problem. Has somebody succeeded in installing libvirt-python inside a virtualenv? Thanks, Daniel Gonzalez

2 2

[libvirt-users] Snapshot system: really confusing.
by NoxDaFox 25 Apr '12

25 Apr '12

Greetings, I am developing a platform for test and debug use. The typical scenario I want to realize is the following: I run a .qcow2 image via QEMU-KVM, the running OS is not relevant. I want to take several snapshots of both Disk and RAM status; same file, separate files doesn't matter. I just need a way to have consistent information about them (better with XML description) and the data as well. I want to store these snapshots on my storage devices to use them whenever and wherever I want. Is it possible to store a single snapshot providing both the memory and disks state in a file (maybe a .qcow2 file)? Is there any way to get a unique interface which handles my snapshots? I was used to use the virDomainSnapshotCreateXML() defining the destination file in the XML with <disk> fields. After updating libvirt it was not working anymore, I thought was a bug but then I realized it was intentional. The function complains about the fact that the <disk> parameter is not accepted anymore. So I started guessing how to solve reading the API documentation and I fall in a completely nebulous world. For what I got: - virDomainSnapshotCreateXML(): According to flags can take system checkpoints (really useful) and disks snapshots. System checkpoints: What I need but I didn't find any way to retrieve the storage file; I'm only able to get the snapshot pointer, quite useless as from its pointer I can only print the XML description. Disk snapshot: here through the XML description I can specify a target file where to write the information. But I still need the memory status. - virDomainSaveFlags(): No matter how I set the flags, it halts the guest; I need it still running afterward and I think that reverting the domain and restarting for my scenarios is unaffordable. - virDomainCoreDump(): Does what I need for the memory, but doesn't give any XML description and doesn't supply any useful interface to handle it, I just get back an int that represent the exit status of the routine. (other functions really similar) The question is: why all this confusion? I absolutely understand the problematic that realizing a multiplatform snapshots management raises; but I think that for an API purpose what is implemented here is completely confusing the developer. Regards, NoxDaFox.

2 1

[libvirt-users] Non-Root not able to use openReadOnly()
by vipul borikar 24 Apr '12

24 Apr '12

Hi, I have a code : import libvirt con = libvirt.openReadOnly(None) print con.listDomainsID() When i run the above code using root i get the proper output... but when i use non-root user it givers be a empty list [ ] If i change the 2nd line to con = libvirt.open(qemu:///system) It works. I am using RHEL 6.1 with default kvm and libvirt. unix_sock_group = "virt" in libvirtd.conf where virt is a group of non-root user group = "virt" in qemu.conf is set. Any Ideas???? -- Thanks Vipul Borikar "Our task must be to free ourselves...by widening our circle of compassion to embrace all living creatures and the whole of nature and its beauty."

2 1

[libvirt-users] Creating Domain and moving a kvm disk under libvirt control
by James Allsopp 20 Apr '12

20 Apr '12

Hi, I'm trying to start using libvirt on my debian machine, but am having some issues. Regardless of using command-line or gui interface with virt-manager, building the virtual machine stalls on 0 with no indication of why it has stopped working. How do I go about fixing this or diagnosing this problem. Also I've a .img file that work s with KVM, would there be anyway to import it for use with libvirt? Thanks James

2 2

[libvirt-users] Using Sys::Virt with Libvirt
by John Wayne 20 Apr '12

20 Apr '12

Anyone using Sys::Virt CPAN Perl Module with Libvirt? I am unable to install Sys::Virt using cpan, Sys::Virt cannot find Libvirt, even though I have it installed. I tried setting LD_LIBRARY_PATH and also PKG_CONFIG_PATH to point to Libvirt, and in both case Sys::Virt was not able to find Libvirt. During installation Sys::Virt times out with : Sys-Virt-0.9.4/INSTALL CPAN: File::Temp loaded ok (v0.22) CPAN.pm: Going to build D/DA/DANBERR/Sys-Virt-0.9.4.tar.gz libvirt >= 0.9.4 is required Warning: No success on command[/usr/bin/perl Makefile.PL INSTALLDIRS=site] Warning (usually harmless): 'YAML' not installed, will not store persistent state DANBERR/Sys-Virt-0.9.4.tar.gz /usr/bin/perl Makefile.PL INSTALLDIRS=site -- NOT OK Running make test Make had some problems, won't test Running make install Make had some problems, won't install Could not read '/root/.cpan/build/Sys-Virt-0.9.4-DiRtOZ/META.yml'. Falling back to other methods to determine prerequisites Failed during this command: DANBERR/Sys-Virt-0.9.4.tar.gz : writemakefile NO '/usr/bin/perl Makefile.PL INSTALLDIRS=site' returned status 256 I have tried with both Libvirt 0.9.11 and Sys::Virt 0.9.11 in addition to Libvirt 0.9.4 with Sys::Virt 0.9.4. Thanks

1 0

[libvirt-users] Error on running libvirt (dnsmasq)
by John Wayne 20 Apr '12

20 Apr '12

Hi, I am running libvirt on RHEL 6.2 and getting this below error when I start the daemon: /usr/sbin/libvirtd --verbose 2012-04-20 06:00:13.366+0000: 26900: info : libvirt version: 0.9.11 2012-04-20 06:00:13.366+0000: 26900: error : virExecWithHook:424 : Cannot find 'dnsmasq' in path: No such file or directory 2012-04-20 06:00:13.405+0000: 26900: warning : ebiptablesDriverInit:4066 : Could not find 'ebtables' executable 2012-04-20 06:00:13.419+0000: 26900: error : virCommandWait:2306 : internal error Child process (/bin/sh -c IPT=/sbin/ip6tables cmd='$IPT -n -L FORWARD' eval res=\$$"${cmd} 2>&1"$ if [ $? -ne 0 ]; then echo "Failure to execute command '${cmd}' : '${res}'."; exit 1;fi ) status unexpected: exit status 1 2012-04-20 06:00:13.419+0000: 26900: error : ebiptablesDriverInit:4101 : Testing of ip6tables command failed: Failure to execute command '$IPT -n -L FORWARD' : 'WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. ip6tables v1.4.7: can't initialize ip6tables table `filter': Address family not supported by protocol Perhaps ip6tables or your kernel needs to be upgraded.'. I compiled libvirt from the source, do I really need dnsmasq? Thanks

3 2

[libvirt-users] Building an RPM
by John Wayne 20 Apr '12

20 Apr '12

Hi, I have downloaded libvirt-0.9.11 and compiled it on my RHEL 6.2 system. I am trying to build a binary RPM for distribution, I am not sure what the best way to go about doing this is. http://libvirt.org/FAQ.html suggests that I try 'make rpm', however that ends in the below error: missing XHTML1 DTD cp: cannot stat `./api.html': No such file or directory make[2]: *** [distdir] Error 1 rm news.html.tmp goals.html.tmp archnetwork.html.tmp formatsecret.html.tmp drvopenvz.html.tmp windows.html.tmp testtck.html.tmp drvlxc.html.tmp apps.html.tmp docs.html.tmp formatstorageencryption.html.tmp drvvbox.html.tmp formatdomain.html.tmp php.html.tmp drvhyperv.html.tmp errors.html.tmp hacking.html.tmp format.html.tmp hooks.html.tmp api.html.tmp storage.html.tmp formatcaps.html.tmp relatedlinks.html.tmp compiling.html.tmp index.html.tmp archdomain.html.tmp downloads.html.tmp auth.html.tmp archnode.html.tmp hvsupport.html.tmp bugs.html.tmp java.html.tmp locking.html.tmp logging.html.tmp testapi.html.tmp formatnetwork.html.tmp bindings.html.tmp uri.html.tmp drvtest.html.tmp sitemap.html.tmp drvqemu.html.tmp contact.html.tmp formatnwfilter.html.tmp intro.html.tmp drvxen.html.tmp drvesx.html.tmp drvvmware.html.tmp testsuites.html.tmp devguide.html.tmp firewall.html.tmp architecture.html.tmp migration.html.tmp todo.html.tmp formatsnapshot.html.tmp formatstorage.html.tmp internals.html.tmp deployment.html.tmp api_extension.html.tmp drvuml.html.tmp virshcmdref.html.tmp csharp.html.tmp python.html.tmp drvremote.html.tmp archstorage.html.tmp remote.html.tmp drivers.html.tmp formatnode.html.tmp make[2]: Leaving directory `/home/user/libvirt-0.9.11/docs' make[1]: *** [distdir] Error 1 make[1]: Leaving directory `/home/user/libvirt-0.9.11' make: *** [rpm] Error 2 Any clue on how to proceed? I am not sure why api.html is missing, since this is a clean untar of the 0.9.11 tar file, and './configure;make;make install' all worked without any issues. Thanks!

3 3

[libvirt-users] Thread-safety issues with vbox driver ?
by Jean-Baptiste Rouault 19 Apr '12

19 Apr '12

Hi, I'm experiencing weird things with the vbox driver when using multiple threads. Following is the snippet of code I experience problems with /*****************************************************/ #include <stdlib.h> #include <stdio.h> #include <pthread.h> #include <libvirt/libvirt.h> void *create_and_destroy(void *arg) { virDomainPtr dom = (virDomainPtr)arg; char buf[VIR_UUID_STRING_BUFLEN]; virDomainGetUUIDString(dom, buf); if (virDomainCreate(dom) != 0) { printf("failed to start %s\n", buf); goto end; } printf("%s started\n", buf); if (virDomainDestroy(dom) != 0) { printf("failed to destroy %s\n", buf); } printf("%s destroyed\n", buf); end: virDomainFree(dom); pthread_exit(NULL); } int main(int argc, char **argv) { virConnectPtr conn = virConnectOpen("vbox:///session"); int i; int count = virConnectNumOfDefinedDomains(conn); char **names = malloc(count * sizeof(char *)); virConnectListDefinedDomains(conn, names, count); virDomainPtr *doms = malloc(count * sizeof(virDomainPtr)); for (i = 0 ; i < count ; ++i) { doms[i] = virDomainLookupByName(conn, names[i]); } pthread_t *threads = malloc(count * sizeof(pthread_t)); pthread_attr_t attr; pthread_attr_init(&attr); pthread_attr_setdetachstate(&attr, PTHREAD_CREATE_JOINABLE); for (i = 0 ; i < count ; ++i) { pthread_create(&threads[i], &attr, create_and_destroy, (void *)doms[i]); } pthread_attr_destroy(&attr); for (i = 0 ; i < count ; ++i) { pthread_join(threads[i], NULL); } virConnectClose(conn); pthread_exit(NULL); } /************************************************/ Here is the output of the program with 2 defined domains: > libvir: VBOX error : operation failed: OpenRemoteSession/LaunchVMProcess failed, domain can't be started > failed to start c538c89a-70da-42ab-a88a-5aeb15698c12 > 034cf837-abe7-4c48-8373-0ddcf480d416 started > 034cf837-abe7-4c48-8373-0ddcf480d416 destroyed Sometimes the first domain really fails to start, but sometimes it starts correctly but libvirt reports an error. Sometimes domains aren't destroyed but libvirt reports no error at all. If there is only one domain, no problem occurs at all. I also tried the same code (ie with multiple domains) but with only one thread and it works well. I managed to reproduce these issues with libvirt 0.9.4, 0.9.7, using VirtualBox 4.0 and 4.1. -- Jean-Baptiste ROUAULT Ingénieur R&D - diateam : Architectes de l'information Phone : +33 (0)9 53 16 02 70 Fax : +33 (0)2 98 050 051

3 6

[libvirt-users] USB Passthrough of two identical devices
by Hendrik Friedel 19 Apr '12

19 Apr '12

Hello, I re-post my question from some days ago, as I got no reply.. Please let me know, if my question is unclear, or if I can do anything to make answering it easier. I appreciate your help. Greetings, Hendrik Hello, I'd like to pass throug two identical devices to my VM. (using libvirt, guest is debian). For one device, it works like this: <hostdev mode='subsystem' type='usb'> <source> <vendor id='0x4fa'/> <product id='0x2490'/> </source> <boot order='2'/> </hostdev> But now, I have another device just like this one: Bus 001 Device 007: ID 04fa:2490 Dallas Semiconductor DS1490F 2-in-1 Fob, 1-Wire adapter Bus 001 Device 005: ID 04fa:2490 Dallas Semiconductor DS1490F 2-in-1 Fob, 1-Wire adapter Unfortunately, only one of these two devices appears for the Guest, even if I duplicate the above entry. Now, there's this option to pass devices: <address bus='0x06' device='0x02''/> But the Bus/Device can/might change... Maybe this can be overcome by udev (and maybe this is the default in ubuntu? can someone confirm?) I have tried the latter syntax aswell. Here the log-file: Code: LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc -cpu qemu32 -enable-kvm -m 256 -smp 1 -name WG -uuid fd90f0d6-122c-992f-a399-4105ee30d6e3 -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/WG.monitor,server,nowait -monitor chardev:monitor -boot c -drive file=/var/lib/zentyal/machines/WG/WG-Test.qcow2,if=scsi,index=0,boot=on,format=qcow2 -net nic,macaddr=00:16:3e:5d:c7:9e,vlan=0,name=nic.0 -net tap,fd=29,vlan=0,name=tap.0 -serial none -parallel none -usb -usbdevice mouse -vnc 0.0.0.0:0,password -k de -vga cirrus -usbdevice host:04fa:2490 -usbdevice host:04fa:2490 usb_create: no bus specified, using "usb.0" for "usb-host" husb: open device 1.5 husb: config #1 need -1 husb: 1 interfaces claimed for configuration 1 husb: grabbed usb device 1.5 usb_create: no bus specified, using "usb.0" for "usb-host" What's odd in this: -usbdevice host:04fa:2490 -usbdevice host:04fa:2490 And this, although I had used the bus/device syntax... So, what would you recommend? Regards, Hendrik

1 0

[libvirt-users] CfP 7th Workshop on Virtualization in High-Performance Cloud Computing (VHPC'12)
by VHPC 12 19 Apr '12

19 Apr '12

we apologize if you receive multiple copies of this CFP. =================================================================== CALL FOR PAPERS 7th Workshop on Virtualization in High-Performance Cloud Computing VHPC '12 as part of Euro-Par 2012, Rhodes Island, Greece =================================================================== Date: August 28, 2012 Workshop URL: http://vhpc.org SUBMISSION DEADLINE: Rolling abstract submission June 4, 2012 - Full paper submission SCOPE: Virtualization has become a common abstraction layer in modern data centers, enabling resource owners to manage complex infrastructure independently of their applications. Conjointly, virtualization is becoming a driving technology for a manifold of industry grade IT services. The cloud concept includes the notion of a separation between resource owners and users, adding services such as hosted application frameworks and queueing. Utilizing the same infrastructure, clouds carry significant potential for use in high-performance scientific computing. The ability of clouds to provide for requests and releases of vast computing resources dynamically and close to the marginal cost of providing the services is unprecedented in the history of scientific and commercial computing. Distributed computing concepts that leverage federated resource access are popular within the grid community, but have not seen previously desired deployed levels so far. Also, many of the scientific data centers have not adopted virtualization or cloud concepts yet. This workshop aims to bring together industrial providers with the scientific community in order to foster discussion, collaboration and mutual exchange of knowledge and experience. The workshop will be one day in length, composed of 20 min paper presentations, each followed by 10 min discussion sections. Presentations may be accompanied by interactive demonstrations. TOPICS Topics of interest include, but are not limited to: Higher-level cloud architectures, focusing on issues such as: - Languages for describing highly-distributed compute jobs - Workload characterization for VM-based environments - Optimized communication libraries/protocols in the cloud - Cross-layer optimization of numeric algorithms on VM infrastructure - System and process/bytecode VM convergence - Cloud frameworks and API sets - Checkpointing/migration of large compute jobs - Instrumentation interfaces and languages - VMM performance (auto-)tuning on various load types - Cloud reliability, fault-tolerance, and security - Software as a Service (SaaS) architectures - Research and education use cases - Virtualization in cloud, cluster and grid environments - Cross-layer VM optimizations - Cloud use cases including optimizations - VM-based cloud performance modelling - Performance and cost modelling Lower-level design challenges for Hypervisors, VM-aware I/O devices, hardware accelerators or filesystems in VM environments, especially: - Cloud, grid and distributed filesystems - Hardware for I/O virtualization (storage/network/accelerators) - Storage and network I/O subsystems in virtualized environments - Novel software approaches to I/O virtualization - Paravirtualized I/O subsystems for modified/unmodified guests - Virtualization-aware cluster interconnects - Direct device assignment - NUMA-aware subsystems in virtualized environments - Hardware Accelerators in virtualization (GPUs/FPGAs) - Hardware extensions for virtualization - VMMs/Hypervisors for embedded systems Data Center management methods, including: - QoS and and service levels - VM cloud and cluster distribution algorithms - VM load-balancing in Clouds - Hypervisor extensions and tools for cluster and grid computing - Fault tolerant VM environments - Virtual machine monitor platforms - Management, deployment and monitoring of VM-based environments - Cluster provisioning in the Cloud PAPER SUBMISSION Papers submitted to the workshop will be reviewed by at least two members of the program committee and external reviewers. Submissions should include abstract, key words, the e-mail address of the corresponding author, and must not exceed 10 pages, including tables and figures at a main font size no smaller than 11 point. Submission of a paper should be regarded as a commitment that, should the paper be accepted, at least one of the authors will register and attend the conference to present the work. Accepted papers will be published in the Springer LNCS series - the format must be according to the Springer LNCS Style. Initial submissions are in PDF; authors of accepted papers will be requested to provide source files. Format Guidelines: http://www.springer.de/comp/lncs/authors.html Style template: ftp://ftp.springer.de/pub/tex/latex/llncs/latex2e/llncs2e.zip Abstract Submission Link: http://edas.info/newPaper.php?c=11943 IMPORTANT DATES Rolling abstract submission June 4, 2012 - Full paper submission June 29, 2012 - Acceptance notification July 20, 2012 - Camera-ready version due August 28, 2012 - Workshop Date CHAIR Michael Alexander (chair), TU Wien, Austria Gianluigi Zanetti (co-chair), CRS4, Italy Anastassios Nanos (co-chair), NTUA, Greece PROGRAM COMMITTEE Paolo Anedda, CRS4, Italy Giovanni Busonera, CRS4, Italy Brad Calder, Microsoft, USA Roberto Canonico, University of Napoli Federico II, Italy Tommaso Cucinotta, Alcatel-Lucent Bell Labs, Ireland Werner Fischer, Thomas-Krenn AG, Germany William Gardner, University of Guelph, USA Marcus Hardt, Forschungszentrum Karlsruhe, Germany Sverre Jarp, CERN, Switzerland Shantenu Jha, Louisiana State University, USA Xuxian Jiang, NC State, USA Nectarios Koziris, National Technical University of Athens, Greece Simone Leo, CRS4, Italy Ignacio Llorente, Universidad Complutense de Madrid, Spain Naoya Maruyama, Tokyo Institute of Technology, Japan Jean-Marc Menaud, Ecole des Mines de Nantes, France Dimitrios Nikolopoulos, Foundation for Research&Technology Hellas, Greece Jose Renato Santos, HP Labs, USA Walter Schwaiger, TU Wien, Austria Yoshio Turner, HP Labs, USA Kurt Tutschku, University of Vienna, Austria Lizhe Wang, Indiana University, USA Chao-Tung Yang, Tunghai University, Taiwan DURATION: Workshop Duration is one day. GENERAL INFORMATION The workshop will be held as part of Euro-Par 2012. Euro-Par 2012: http://europar2012.cti.gr/

1 0

[libvirt-users] Problems using latest qemu-kvm and latest libvirt ( hvm missing )
by Bhasker C V 18 Apr '12

18 Apr '12

Hi all I have faced this issue already and the solution was to go back to a old version of qemu-kvm and/or libvirt and things start falling into place but this time I would want to solve this. I have used these versions as per the o/p of the commands below. To jumpstart a new machine which is libvirt capable, it always is a hastle to find out which of the version combination of libvirt,qemu-kvm will work. Just by picking the latest of the two versions does not help and ends up not supporting hvm at all $ sudo virsh capabilities <capabilities> <host> <uuid>34373030-3635-435a-4a32-313230485156</uuid> <cpu> <arch>x86_64</arch> <model>Westmere</model> <vendor>Intel</vendor> <topology sockets='2' cores='4' threads='2'/> <feature name='rdtscp'/> <feature name='pdpe1gb'/> <feature name='dca'/> <feature name='pdcm'/> <feature name='xtpr'/> <feature name='tm2'/> <feature name='est'/> <feature name='smx'/> <feature name='vmx'/> <feature name='ds_cpl'/> <feature name='monitor'/> <feature name='dtes64'/> <feature name='pclmuldq'/> <feature name='pbe'/> <feature name='tm'/> <feature name='ht'/> <feature name='ss'/> <feature name='acpi'/> <feature name='ds'/> <feature name='vme'/> </cpu> <power_management/> <migration_features> <live/> <uri_transports> <uri_transport>tcp</uri_transport> </uri_transports> </migration_features> </host> </capabilities> $ virsh --version 0.9.11 $ qemu-system-x86_64 --version QEMU emulator version 1.0,1 (qemu-kvm-1.0.1), Copyright (c) 2003-2008 Fabrice Bellard $ sudo virsh uri qemu:///system $ sudo virsh version Compiled against library: libvir 0.9.11 Using library: libvir 0.9.11 Using API: QEMU 0.9.11 error: failed to get the hypervisor version error: internal error Cannot find suitable emulator for x86_64 $ which kvm /usr/local/bin/kvm Can someone tell me, please, what is the version of qemu-kvm which will work well with the latest libvirt 0.9.11 ? since clearly the latest versions of qemu-kvm and libvirt are not compatible fully (atleast not hvm). Even better if this is documented somewhere visible so that a lot of time can be saved in iterating through the versions of qemu-kvm to find out which one will work. -- Bhasker C V Secure Mails: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x4D05FEEC54E47413

1 1

[libvirt-users] [API reference] Are there XML-handling API to retrieve info directly from xml configure file
by Zhihua Che 18 Apr '12

18 Apr '12

Hi, everyone I'm writing a application using libvirt and need to query guest os's virtual network interface usage, like bytes read or written through a given interface. I know int virDomainInterfaceStats(virDomainPtr dom, const char * path, virDomainInterfaceStatsPtr stats, size_t size) is designed for my purpose but I 'm not sure how I determine the second parameter path. I'm now think of determining the virtual interface by parsing the domain's xml configure file. But I don't find that libvirt supply such functions, that means, I have to resort to other library lik libxml? thanks

4 15

[libvirt-users] Guests can't connect to each other
by Anthony Bourguignon 18 Apr '12

18 Apr '12

Hi, I'm using libvirt and qemu on Debian Wheezy. I'm having a strange behavior. Guests can't connect to each other when they're on the same host. On the host I'm using bonding (in active / backup mode) and vlan. It looks like this : eth0 \ / macvtap0 bond0 --- vlan222 eth1 / \ macvtap1 So I've got two guests, let's say A and B. When I try to ping B from A, it works : # ping -s 3000 -c 5 78.109.95.11 PING 78.109.95.11 (78.109.95.11) 3000(3028) bytes of data. 3008 bytes from 78.109.95.11: icmp_req=1 ttl=64 time=0.065 ms 3008 bytes from 78.109.95.11: icmp_req=2 ttl=64 time=2.19 ms 3008 bytes from 78.109.95.11: icmp_req=3 ttl=64 time=1.43 ms --- 78.109.95.11 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4001ms rtt min/avg/max/mdev = 0.065/0.960/2.197/0.760 ms But nothing happens when I try to ssh it (not even a timeout). You'll find enclosed the tcpdump captures on the source and the destination. It's the same when I use netcat in udp. At the same time, connection from the host to one guest is working perfectly. There is no iptables rule on the host, and nothing too on the guests. Here are the virsh dumpxml of the different components : # virsh dumpxml vm1 <domain type='kvm' id='11'> <name>vm1</name> <uuid>4eaaed00-c610-b468-ad55-600a0b4e244c</uuid> <memory>2048000</memory> <currentMemory>2048000</currentMemory> <memoryBacking> <hugepages/> </memoryBacking> <vcpu cpuset='0,2,4,8,10,12,14'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0,8'/> <vcpupin vcpu='1' cpuset='2,10'/> <vcpupin vcpu='2' cpuset='4,12'/> <vcpupin vcpu='3' cpuset='6,14'/> <vcpupin vcpu='4' cpuset='0,8'/> <vcpupin vcpu='5' cpuset='2,10'/> <vcpupin vcpu='6' cpuset='4,12'/> <vcpupin vcpu='7' cpuset='6,14'/> </cputune> <os> <type arch='x86_64' machine='pc-1.0'>hvm</type> <boot dev='hd'/> <boot dev='network'/> </os> <features> <acpi/> <apic/> </features> <cpu match='exact'> <model>Westmere</model> <vendor>Intel</vendor> <topology sockets='1' cores='8' threads='1'/> <feature policy='require' name='tm2'/> <feature policy='require' name='est'/> <feature policy='require' name='vmx'/> <feature policy='require' name='ds'/> <feature policy='require' name='smx'/> <feature policy='require' name='ss'/> <feature policy='require' name='vme'/> <feature policy='require' name='dtes64'/> <feature policy='require' name='rdtscp'/> <feature policy='require' name='ht'/> <feature policy='require' name='dca'/> <feature policy='require' name='pbe'/> <feature policy='require' name='tm'/> <feature policy='require' name='pdcm'/> <feature policy='require' name='pdpe1gb'/> <feature policy='require' name='ds_cpl'/> <feature policy='require' name='pclmuldq'/> <feature policy='require' name='xtpr'/> <feature policy='require' name='acpi'/> <feature policy='require' name='monitor'/> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/kvm</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source dev='/dev/vps/vm1'/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <interface type='network'> <mac address='52:54:00:0e:58:ae'/> <source network='vlan222'/> <target dev='macvtap0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='5900' autoport='yes' listen='0.0.0.0' keymap='fr'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vga' vram='9216' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> </domain> # virsh dumpxml vm2 <domain type='kvm' id='13'> <name>vm2</name> <uuid>4f760831-22b1-ff3b-26e7-6b3fec49e918</uuid> <memory>2048000</memory> <currentMemory>2048000</currentMemory> <memoryBacking> <hugepages/> </memoryBacking> <vcpu cpuset='1,3,5,7,9,11,13,15'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1,3,5,7,9,11,13,15'/> <vcpupin vcpu='1' cpuset='1,3,5,7,9,11,13,15'/> <vcpupin vcpu='2' cpuset='1,3,5,7,9,11,13,15'/> <vcpupin vcpu='3' cpuset='1,3,5,7,9,11,13,15'/> <vcpupin vcpu='4' cpuset='1,3,5,7,9,11,13,15'/> <vcpupin vcpu='5' cpuset='1,3,5,7,9,11,13,15'/> <vcpupin vcpu='6' cpuset='1,3,5,7,9,11,13,15'/> <vcpupin vcpu='7' cpuset='1,3,5,7,9,11,13,15'/> </cputune> <os> <type arch='x86_64' machine='pc-1.0'>hvm</type> <boot dev='hd'/> <boot dev='network'/> </os> <features> <acpi/> <apic/> </features> <cpu match='exact'> <model>Westmere</model> <vendor>Intel</vendor> <topology sockets='1' cores='4' threads='2'/> <feature policy='require' name='tm2'/> <feature policy='require' name='est'/> <feature policy='require' name='vmx'/> <feature policy='require' name='ds'/> <feature policy='require' name='smx'/> <feature policy='require' name='ss'/> <feature policy='require' name='vme'/> <feature policy='require' name='dtes64'/> <feature policy='require' name='rdtscp'/> <feature policy='require' name='ht'/> <feature policy='require' name='dca'/> <feature policy='require' name='pbe'/> <feature policy='require' name='tm'/> <feature policy='require' name='pdcm'/> <feature policy='require' name='pdpe1gb'/> <feature policy='require' name='ds_cpl'/> <feature policy='require' name='pclmuldq'/> <feature policy='require' name='xtpr'/> <feature policy='require' name='acpi'/> <feature policy='require' name='monitor'/> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/kvm</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source dev='/dev/vps/vm2'/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <interface type='network'> <mac address='52:54:00:cb:ce:41'/> <source network='vlan222'/> <target dev='macvtap1'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='5901' autoport='yes' listen='0.0.0.0' keymap='fr'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vga' vram='9216' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> </domain> # virsh net-dumpxml vlan222 <network> <name>vlan222</name> <uuid>2b763b5c-4ec1-9b5f-b29d-b7a7ea0f743d</uuid> <forward dev='vlan222' mode='bridge'> <interface dev='vlan222'/> </forward> </network> Thanks in advance to help me understand this issue.

3 7

[libvirt-users] help:any docs for open vswitch supporting?
by yue wang 18 Apr '12

18 Apr '12

hi everybody, i saw the new feature: network: support Open vSwitch. how to use this feature? are there any documents about that? i didn't find it on the website. Thanks, Heuye

5 6

[libvirt-users] USB Passthrough with two identical devices
by Hendrik Friedel 17 Apr '12

17 Apr '12

Hello, I'd like to pass throug two identical devices to my VM. (using libvirt, guest is debian). For one device, it works like this: <hostdev mode='subsystem' type='usb'> <source> <vendor id='0x4fa'/> <product id='0x2490'/> </source> <boot order='2'/> </hostdev> But now, I have another device just like this one: Bus 001 Device 007: ID 04fa:2490 Dallas Semiconductor DS1490F 2-in-1 Fob, 1-Wire adapter Bus 001 Device 005: ID 04fa:2490 Dallas Semiconductor DS1490F 2-in-1 Fob, 1-Wire adapter Unfortunately, only one of these two devices appears for the Guest, even if I duplicate the above entry. Now, there's this option to pass devices: <address bus='0x06' device='0x02''/> But the Bus/Device can/might change... Maybe this can be overcome by udev (and maybe this is the default in ubuntu? can someone confirm?) I have tried the latter syntax aswell. Here the log-file: Code: LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc -cpu qemu32 -enable-kvm -m 256 -smp 1 -name WG -uuid fd90f0d6-122c-992f-a399-4105ee30d6e3 -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/WG.monitor,server,nowait -monitor chardev:monitor -boot c -drive file=/var/lib/zentyal/machines/WG/WG-Test.qcow2,if=scsi,index=0,boot=on,format=qcow2 -net nic,macaddr=00:16:3e:5d:c7:9e,vlan=0,name=nic.0 -net tap,fd=29,vlan=0,name=tap.0 -serial none -parallel none -usb -usbdevice mouse -vnc 0.0.0.0:0,password -k de -vga cirrus -usbdevice host:04fa:2490 -usbdevice host:04fa:2490 usb_create: no bus specified, using "usb.0" for "usb-host" husb: open device 1.5 husb: config #1 need -1 husb: 1 interfaces claimed for configuration 1 husb: grabbed usb device 1.5 usb_create: no bus specified, using "usb.0" for "usb-host" What's odd in this: -usbdevice host:04fa:2490 -usbdevice host:04fa:2490 And this, although I had used the bus/device syntax... So, what would you recommend? Regards, Hendrik

1 0

[libvirt-users] What does cpu_time returned by virDomainGetCPUStats mean?
by Zhihua Che 17 Apr '12

17 Apr '12

hi, everyone. I find an 'interesting' thing involving virDomainGetCPUStats(). I call it for cpu usage consumed by a domain and get a array of virTypedParameter. My system is 2-core and hyperviser return 1 parameter per cpu. So the contents of the array is like this. virTypedParameter[0] { .fiedl = "cpu_time" .type = 4 .value.ul = 51640610899 } virTypedParameter[1] { .field = "cpu_time" .type = 4 .value.ul = 55302820304 } I thought this value store the run time of the cpu since last boot. But I find I was wrong because this value would increase until it wraps down and doesn't reset even the domain is restarted. So, what does this value mean? How can I get the CPU usage of the domain? I found nothing on the API reference doc page:-(. No word is related with the meaning of the returned array of virTypedParameter by virDomainGetCPUStats().

3 7

[libvirt-users] Ansis Atteka has invited you to use Google Talk
by Ansis Atteka 16 Apr '12

16 Apr '12

------------------------------------------------------------------------ Ansis Atteka has invited you to sign up for Google Talk so you can talk to each other for free over your computers. To sign-up, go to: http://www.google.com/accounts/NewAccount?service=talk&sendvemail=true&skip… Google Talk is a downloadable Windows* application that offers: - Free calls over your computer anytime, from anywhere, and for as long as you want - A simple and intuitive user interface for sending instant messages or making calls--no clutter, pop-ups or ads - Superior voice quality through just a microphone and computer speaker - Fast file transfers with no restrictions on file type After signing-up, download Google Talk and sign in with your new Google Account username and password. You can then begin inviting anyone you want to talk to for free. Google Talk works with any computer speaker and microphone, such as the ones built-in to many PC laptops today, as well as with wired and wireless headsets and USB phones. Google Talk also works across all firewalls. Google Talk is still in beta. Just like with Gmail, we're working hard to add features and make improvements, so we might also ask for your comments and suggestions periodically. We appreciate your help in making it even better! Thanks, The Google Talk Team To learn more about Google Talk before signing up, visit: http://www.google.com/talk/about.html (If clicking the URLs in this message does not work, copy and paste them into the address bar of your browser). * Not a Windows user? No problem. You can also connect to the Google Talk service from any platform using third-party clients (http://www.google.com/talk/otherclients.html)

1 0