- Users - libvirt List Archives

[libvirt-users] Cannot connect to the existing LXC containers (console)
by Sebastien Douche 28 May '12

28 May '12

Hi, after 2 years of "pure" LXC usage, I'm trying now to administrate our LXC containers with libvirt No problem with a LXC container I create "from Scratch" (lxc-create), but with our existing containers, I've a strange behavior with the console: vsonde43 login: Debian GNU/Linux 5.0 vsonde43 console vsonde43 login: Debian GNU/Linux 5.0 vsonde43 tty1 vsonde43 login: Debian GNU/Linux 5.0 vsonde43 console vsonde43 login: Debian GNU/Linux 5.0 vsonde43 tty1 vsonde43 login: Debian GNU/Linux 5.0 vsonde43 console vsonde43 login: root Password: z Login incorrect vsonde43 login: Login incorrect vsonde43 login: root Password: Password: Login incorrect vsonde43 login: root INIT: Id "c2" respawning too fast: disabled for 5 minutes INIT: Id "c3" respawning too fast: disabled for 5 minutes INIT: Id "c4" respawning too fast: disabled for 5 minutes INIT: Id "c2" respawning too fast: disabled for 5 minutes INIT: Id "c3" respawning too fast: disabled for 5 minutes INIT: Id "c4" respawning too fast: disabled for 5 minutes Characters sometimes appears, and sometimes all keys are like the enter key. Any ideas? I tried many xml configurations w/o sucsess. Thanks. PS: libvirt 0.9.8 / lxc 0.7.5 -- Sebastien Douche <sdouche(a)gmail.com> Twitter: @sdouche / G+: +sdouche

2 4

[libvirt-users] Spawn new domains from a snapshot.
by NoxDaFox 27 May '12

27 May '12

Hello everybody, I would like to be able to spawn several domains from a given snapshot. Here's a possible scenario: - I start from disk image A.qcow2. - I made some changes to A and I take different snapshots: 1 - 2 - 3 - While A is still running I would like to run domains B and C from snapshot 2 I don't want to revert a domain, I want to create new ones. The original should be still running but it may be stopped if necessary. The idea I had was to create a qcow2 image through qemu-img (let's call it Z.qcow2), as I'm using copy on write for performances then I'd need to commit the changes contained in Z to A always using qemu-img. Is there any other better way? I would love to do it through libvirt, maybe specifying in the config file the backing store path of the whole disk and then giving as a source file the one containing deltas. This could be a good idea for realizing a cloud based system as a incredible amount of time would be saved though it. Imagine moving only qcow2 file containing deltas through the network and then give the base image to each node so that it can use it for start it's own domain. As well would be possible to store the heavy base image in a single node saving storage space. Lots of cpu cycles saved once new image versions must be deployed (typical case a windows update to propagate in the nodes network). NoxDaFox

2 3

[libvirt-users] How to specify the libvirtd in connect call
by Zhihua Che 25 May '12

25 May '12

Hi, Here is my situation, I install libvirt in a non-default directory and start libvird with sudo. While I can connect virsh to libvirtd using "virsh --connect qemu:///system", I fail to connect my app using "virConnectOpen("qemu:///system")", which complains "unable to locate libvirtd daemon in $PATH". Then, I take another try and add the path of libvirtd in env variable PATH. Unfortunately, it doesn't work. I read through the api reference and find no place to specify this path explicitly. Thanks for any tip. Harvey

1 1

[libvirt-users] monitor socket did not show up.: No such file or directory
by vipul borikar 23 May '12

23 May '12

I am using a Nimbus Cloud Middleware which in turn use Python libvirt binding to start VM's. Hypervisor is KVM. # virsh -c qemu:///system version Compiled against library: libvir 0.8.7 Using library: libvir 0.8.7 Using API: QEMU 0.8.7 Running hypervisor: QEMU 0.12.1 Some time i get the error in the Nimbus Logs it says : UnexpectedError: Problem creating the VM: monitor socket did not show up.: No such file or directory I googled but this particular not able to find. I checked the /var/log/libvirt/qemu/wrksp-427.log 2012-05-23 10:09:13.494: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin HOME=/root USER=root LOGNAME=root QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.1.0 -enable-kvm -m 2024 -smp 2,sockets=2,cores=1,threads=1 -name wrksp-427 -uuid e8c5c171-392c-02e4-b43c-b0b4279e55c5 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/wrksp-427.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -boot c -drive file=/VM/Nimbus/secureimages/wrksp-427/ param-vm.cdacb.in/cloud/5f4f0dcd//RHEL5.5_64bit_MPI,if=none,id=drive-ide0-0-0,format=raw-device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=24,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=a2:aa:bb:2e:d6:58,bus=pci.0,addr=0x3 -usb -vnc 127.0.0.1:22 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 10:09:13.512: 14116: info : libvirt version: 0.8.7, package: 18.el6 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2011-04-18-10:28:30, x86-008.build.bos.redhat.com) 10:09:13.512: 14116: debug : virCgroupNew:566 : New group /libvirt/qemu/wrksp-427 10:09:13.513: 14116: debug : virCgroupDetect:245 : Detected mount/mapping 0:cpu at /cgroup/cpu in 10:09:13.513: 14116: debug : virCgroupDetect:245 : Detected mount/mapping 1:cpuacct at /cgroup/cpuacct in 10:09:13.513: 14116: debug : virCgroupDetect:245 : Detected mount/mapping 2:cpuset at /cgroup/cpuset in 10:09:13.513: 14116: debug : virCgroupDetect:245 : Detected mount/mapping 3:memory at /cgroup/memory in 10:09:13.513: 14116: debug : virCgroupDetect:245 : Detected mount/mapping 4:devices at /cgroup/devices in 10:09:13.513: 14116: debug : virCgroupDetect:245 : Detected mount/mapping 5:freezer at /cgroup/freezer in 10:09:13.513: 14116: debug : virCgroupDetect:245 : Detected mount/mapping 6:blkio at /cgroup/blkio in 10:09:13.513: 14116: debug : virCgroupMakeGroup:497 : Make group /libvirt/qemu/wrksp-427 10:09:13.513: 14116: debug : virCgroupMakeGroup:509 : Make controller /cgroup/cpu/libvirt/qemu/wrksp-427/ 10:09:13.513: 14116: debug : virCgroupMakeGroup:509 : Make controller /cgroup/cpuacct/libvirt/qemu/wrksp-427/ 10:09:13.514: 14116: debug : virCgroupMakeGroup:509 : Make controller /cgroup/cpuset/libvirt/qemu/wrksp-427/ 10:09:13.514: 14116: debug : virCgroupMakeGroup:509 : Make controller /cgroup/memory/libvirt/qemu/wrksp-427/ 10:09:13.514: 14116: debug : virCgroupSetValueStr:290 : Set value '/cgroup/cpu/libvirt/qemu/wrksp-427/tasks' to '14116' 10:09:13.714: 14116: debug : virCgroupSetValueStr:290 : Set value '/cgroup/cpuacct/libvirt/qemu/wrksp-427/tasks' to '14116' 10:09:14.467: 14116: debug : virCgroupSetValueStr:290 : Set value '/cgroup/cpuset/libvirt/qemu/wrksp-427/tasks' to '14116' 10:09:15.467: 14116: debug : virCgroupSetValueStr:290 : Set value '/cgroup/memory/libvirt/qemu/wrksp-427/tasks' to '14116' 2012-05-23 10:09:16.537: shutting down There is no suspect in the log file. 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."

1 0

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] Renaming a LVM LV (where is vol-edit??)
by Dax Kelson 23 May '12

23 May '12

Hello, I'm using a LVM storage pool. I renamed a guest and I would like to change the LV name to match to avoid future confusion. How do i do this? There is no vol-edit command (fully updated RHEL6). Thanks, Dax Kelson

2 2

[libvirt-users] Failed to mount devpts
by Marco Yuen 23 May '12

23 May '12

Hi all, I've been trying to start a LXC container using libvirt, but I keep getting `Failed to mount devpts on /vservers/quantum/fs/dev/pts: Invalid argument'. I found a similar thread on the mailing list a couple months ago (https://www.redhat.com/archives/libvirt-users/2012-January/msg00052.html) but the solution posted didn't work for me. Anyone has any ideas? Extra Info: Libvirt version Compiled against library: libvir 0.9.12 Using library: libvir 0.9.12 Using API: LXC 0.9.12 Running hypervisor: LXC 3.3.5 Host is running F16, and the domain xml can found at http://pastebin.com/yWXQviVy Best regards, Marco

1 0

Re: [libvirt-users] Python Libvirt Bindings
by Hubert Zhang 22 May '12

22 May '12

https://www.redhat.com/archives/libvirt-users/2012-May/msg00005.html When I run the sample code with the case of Python code for using qemu+tcp with SASL, I always got this SASL error: Traceback (most recent call last): File "esxList.py", line 102, in ? conn = libvirt.openAuth(uri, auth, 0) File "/usr/lib/python2.4/site-packages/libvirt.py", line 102, in openAuth if ret is None:raise libvirtError('virConnectOpenAuth() failed') libvirt.libvirtError: authentication failed: Failed to start SASL negotiation: -4 (SASL(-4): no mechanism available: I have no problem to run the C&java code with qemu+tcp with SASL. Is it possible an error of Python binding? Thanks, -Hubert

2 2

[libvirt-users] Problem with pty
by Daniele Milani 22 May '12

22 May '12

Dear all I have the following problem: -I'm running libvirt 0.9.11 on ubuntu 12.04; -when I try to create a VM with the following configuration: ... <serial type='pty'> <source path='/dev/pts/2'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/2'> <source path='/dev/pts/2'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> ... I obtain this output: errore: Impossibile creare il dominio da domain_alpha_1.xml (error, impossible to create a domain from domain_alpha_1.xml) errore: errore interno Process exited while reading console log output: chardev: opening backend "pty" failed: Permission denied Does anyone know what's going wrong and ho to fix it? Thanks, Daniele Milani

2 2

[libvirt-users] F14->F16 Upgrade Results in Win2003 Server Client BSOD 0x7f
by Thomas J. Baker 21 May '12

21 May '12

Hello, I upgraded my kvm server from Fedora 14 to Fedora 16 and the only casualty was a Windows 2003 Server client that will no longer boot with and produces a BSOD. I admittedly know very little about Windows and this VM has been around - real hardware -> Parallels on a Mac -> linux kvm but it was working fine under Fedora 14. The client does boot fine under safe mode but anything higher than that (even safe mode with networking) results in the BSOD. I've tried explicitly setting the network driver to rtl8139 in virt-manager which appears to be what it was under F14 but it didn't help. Neither did just removing the NIC under Device Manager and letting it get recognized again. As you can guess given the description, this crusty old Win2003 server instance has some worth in that recreating it is very undesirable for all involved. I'd appreciate any tips on getting it working again. Thanks, tjb -- ======================================================================= | Thomas Baker email: tjb(a)unh.edu | | Systems Programmer | | Research Computing Center voice: (603) 862-4490 | | University of New Hampshire fax: (603) 862-1761 | | 332 Morse Hall | | Durham, NH 03824 USA http://wintermute.sr.unh.edu/~tjb | =======================================================================

2 2

[libvirt-users] Migration with rbd storage backend
by Andrey Korolyov 19 May '12

19 May '12

Hi, Seems that such migration is currently broken, at least for 0.9.11|0.9.12, with 0.9.8 all works fine: virsh migrate --live testvm qemu+tcp://towerbig/system ---snip--- 2012-05-17 21:22:30.250+0000: 16926: debug : qemuDriverCloseCallbackGet:605 : vm=testvm, uuid=feb7ccb6-1087-8661-9284-62e3a1e9f44a, conn=(nil) 2012-05-17 21:22:30.250+0000: 16926: debug : qemuDriverCloseCallbackGet:611 : cb=(nil) 2012-05-17 21:22:30.250+0000: 16926: error : virStorageFileIsSharedFSType:1007 : Invalid relative path 'rbd/testvm-Vwu': Invalid argument 2012-05-17 21:22:30.250+0000: 16926: debug : qemuDomainObjEndAsyncJob:955 : Stopping async job: migration out 2012-05-17 21:22:30.250+0000: 16926: debug : virDomainObjUnref:1645 : obj=0x1c00cd0 refs=3 2012-05-17 21:22:30.250+0000: 16926: debug : virDomainMigrateBegin3:6173 : xml (null) 2012-05-17 21:22:30.250+0000: 16926: debug : virDomainFree:2345 : dom=0x1d7ee30, (VM: name=testvm, uuid=feb7ccb6-1087-8661-9284-62e3a1e9f44a) 2012-05-17 21:22:30.250+0000: 16926: debug : virUnrefDomain:276 : unref domain 0x1d7ee30 testvm 1 ---snip--- Also there is a second point - libvirt doesn`t allow migration of VM until all snapshots has been deleted, which is not necessary for network filesystems, so it probably needs to be fixed. Thanks!

2 1

Re: [libvirt-users] How to use Python Binding with Lbivirt.
by Hubert Zhang 19 May '12

19 May '12

When I run the python test code I got the SASL error. But it's ok if I run the C sample code. Do you know the reason? Here is the message: libvir: RPC error : authentication failed: Failed to start SASL negotiation: -4 (SASL(-4): no mechanism available: No worthy mechs found) Traceback (most recent call last): File "esxList.py", line 101, in ? conn = libvirt.openAuth(uri, auth, 0) File "/usr/lib/python2.4/site-packages/libvirt.py", line 102, in openAuth if ret is None:raise libvirtError('virConnectOpenAuth() failed') libvirt.libvirtError: authentication failed: Failed to start SASL negotiation: -4 (SASL(-4): no mechanism available: No worthy mechs found) Thanks, -Hubert

1 0

[libvirt-users] USB passthrough of all USB-slots to guest
by eGerlach 18 May '12

18 May '12

Hi, how can I define passthrough of all USB-slots to a guest with libvirt? With qemu it's very easy: # kvm -usb -usbdevice host:0.* -usbdevice host:1.* -usbdevice host:2.* -usbdevice host:3.* ... This configuration of the VM gets *all* 4 USB-Slots. Every time somewhat USB-device is plugged in the VM gets it. virt-install manpage offers: --host-device 001.003 USB by bus, device (via lsusb). I installed a VM with option --host-device 001.001 according to output of lsusb. The XML-file generated: <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x1d6b'/> <product id='0x0002'/> </source> </hostdev> But no USB device is passed through automatically. I always need virsh attach-device virtualM myusb.xml with exact vendor and product ID. I want to plug in somewhat USB-Stick or other USB stuff without exploring vendor and product id before. Who can help? tia Ekkard

2 3

[libvirt-users] lxc: Add /dev/tty to lxcContainerPopulateDevices() ?
by Sukadev Bhattiprolu 18 May '12

18 May '12

Hi, src/lxc/lxc_container.c:lxcContainerPopulateDevices() has this table of devices that are automatically created when an lxc container is started. const struct { int maj; int min; mode_t mode; const char *path; } devs[] = { { LXC_DEV_MAJ_MEMORY, LXC_DEV_MIN_NULL, 0666, "/dev/null" }, { LXC_DEV_MAJ_MEMORY, LXC_DEV_MIN_ZERO, 0666, "/dev/zero" }, { LXC_DEV_MAJ_MEMORY, LXC_DEV_MIN_FULL, 0666, "/dev/full" }, { LXC_DEV_MAJ_MEMORY, LXC_DEV_MIN_RANDOM, 0666, "/dev/random" }, { LXC_DEV_MAJ_MEMORY, LXC_DEV_MIN_URANDOM, 0666, "/dev/urandom" }, }; Can we add '/dev/tty' to this list ? We were trying to run 'smbpasswd -a user' inside a container without /dev/tty and the fopen("/dev/tty", "w+") in smbpasswd made /dev/tty a regular file, breaking man(1), less(1), and ofcourse smbpasswd :-) Sure we can add /dev/tty to container's rc.local or something, but wouldn't it be in the same category as say, /dev/null or /dev/zero ? Sukadev

2 2

[libvirt-users] Using virsh to connect to ESX
by Mauro Monteiro 17 May '12

17 May '12

Hello All, I have just started studying the libvirt and I am trying to connect to ESX Server (version 4) using virsh (version 0.7.5) using the following command: virsh -c esx+ssh://root@<fully qualified hostname)> It inquires the root password and as soon as I inform the password it throws the error: error: cannot recv data: Connection reset by peer error: failed to connect to the hypervisor I can access my server using ssh. I am running it from Ubuntu 10.04 and the libvirt version 0.7.5. Can someone help me? -- []'s Mauro

2 1

[libvirt-users] Python 3.2 support for libvirt API?
by Patrick Wilbur 17 May '12

17 May '12

Hey all, I apologize if this has been asked many times already (new to the list). I'm trying to write a Python script that makes use of the libvirt API, and I'm trying my best to make the script both Python 2.x and 3.x compatible. Is the libvirt module available for Python 3.x yet, and, if so, what is the module name that I need to import? What is the package name to install on my OS (Ubuntu 11.10)? Thanks in advance, Pat Wilbur -- Patrick F. Wilbur Researcher, Consultant, Educator, Computer Science Graduate at Clarkson University patrick.wilbur(a)gmail.com wilburpf(a)clarkson.edu Check out our book: http://runningxen.com Consulting: http://pfwilbur.com My website: http://pdub.net

2 1

[libvirt-users] libvirt, lxc, "/dev/log" ENOENT
by dennis jenkins 15 May '12

15 May '12

Hello. I am experimenting with LXC via libvirt on my Gentoo development system. I can start the LXC domain and connect to its console. However, I am unable to login as root. I've used "chroot" and "passwd" from the host system to explicitly set the root password. Still no luck. So I began debugging.... I ran "strace" on the container's "login" process (after agetty exec'd login). I noticed that it was unable to open "/dev/log". Sure enough the unix domain socket did not exist inside the container (as seen from outside the container). So I tweaked my host's syslog-ng.conf file to create this socket. My hope was to monitor the log events generated by the login process. So the log device certainly exists (and it tests ok with the 'logger' command): The LXC file-system was created with the "lxc-gentoo" script ( http://lxc-gentoo.sourceforge.net/) The only changes that I've made to the container's file system is to change roots' password ($rootfs/etc/shadow) and configure syslog-ng to create a logging socket at $rootfs/dev/log. I've even edit "$rootfs/etc/shadow" and completely removed root's password hash. I still can't log into the account from "virsh console". I thought that maybe I was unable to authenticate because the "login" process cannot log success/failure to /dev/log. However, I know from experience that on other Gentoo systems I can login as root even when syslog-ng is kaput, and /dev/log does not exist. "/etc/pam.d" inside the container is byte-for-byte the same as my host system, and I can authenticate as root from the physical console. I have a few main questions: 1) Is my domain configured correctly? 2) Why is the container unable to write to the "/dev/log" provided from outside the container? 3) Why am I unable to authenticate as the "root" user? Thank you for your time. ostara ~ # virsh -c lxc:/// start dwj-lnx-dev Domain dwj-lnx-dev started ostara ~ # virsh -c lxc:/// console dwj-lnx-dev Connected to domain dwj-lnx-dev Escape character is ^] INIT: version 2.88 booting Gentoo Linux; http://www.gentoo.org/ Copyright 1999-2009 Gentoo Foundation; Distributed under the GPLv2 Press I to enter interactive boot mode * Skipping mount of /proc as it's already mounted * Skipping mount of /sys as it's already mounted * Using existing device nodes in /dev ... [ ok ] * Skipping mount of /dev/pts as it's already mounted * Remounting root filesystem read-only ... mount: / is busy [ !! ] * Skipping root filesystem check (fstab's passno == 0) ... [ ok ] * Checking all filesystems ... [ ok ] * Mounting local filesystems ... mount: mount point /dev/shm does not exist * Some local filesystem failed to mount [ !! ] * Mounting USB device filesystem (usbfs) ... [ ok ] * Activating (possible) swap ... [ ok ] * Setting system clock using the hardware clock [UTC] ... [ ok ] * Configuring kernel parameters ... error: "Read-only file system" setting key "net.ipv4.conf.default.rp_filter" error: "Read-only file system" setting key "net.ipv4.conf.all.rp_filter" [ ok ] * Cleaning /var/lock, /var/run ... [ ok ] * Wiping /tmp directory ... [ ok ] * Starting lo * Bringing up lo * 127.0.0.1/8 [ ok ] * Adding routes * 127.0.0.0/8 ... [ ok ] INIT: Entering runlevel: 3 * Starting eth0 * Bringing up eth0 * 192.168.2.199 [ ok ] * Adding routes * default via 192.168.2.1 ... [ ok ] * Mounting network filesystems ... [ ok ] /lib64/rcscripts/sh/rc-services.sh: line 412: /etc/init.d/udev-postmount: Permission denied * Starting local ... [ ok ] This is ostara.unknown_domain (Linux x86_64 3.2.12-gentoo) 23:06:09 ostara login: ostara ~ # virsh -c lxc:/// version Compiled against library: libvir 0.9.11 Using library: libvir 0.9.11 Using API: LXC 0.9.11 Running hypervisor: LXC 3.2.12 ostara ~ # ls -l /vm/lxc/dwj-lnx-dev/dev/log srw-rw-rw- 1 root root 0 May 14 17:31 /vm/lxc/dwj-lnx-dev/dev/log ostara ~ # logger -s /vm/lxc/dwj-lnx-dev/dev/log "CAPYBARA" djenkins: /vm/lxc/dwj-lnx-dev/dev/log CAPYBARA ostara ~ # tail -n 100 /var/log/messages | grep CAPYBARA May 14 17:58:57 localhost djenkins: /vm/lxc/dwj-lnx-dev/dev/log CAPYBARA (lots of strace setup omitted): Buried about 60% down in the strace output is the attempt by "login" inside the container to access "/dev/log", which failed (ENOENT). open("/etc/passwd", O_RDONLY|O_CLOEXEC) = 3 lseek(3, 0, SEEK_CUR) = 0 fstat(3, {st_mode=S_IFREG|0644, st_size=720, ...}) = 0 mmap(NULL, 720, PROT_READ, MAP_SHARED, 3, 0) = 0x7fc6ccb66000 lseek(3, 720, SEEK_SET) = 720 munmap(0x7fc6ccb66000, 720) = 0 close(3) = 0 time([1337035715]) = 1337035715 socket(PF_FILE, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 3 connect(3, {sa_family=AF_FILE, path="/dev/log"}, 110) = -1 ENOENT (No such file or directory) close(3) = 0 fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 0), ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fc6ccb66000 write(1, "\n", 1) = 1 write(1, "Login incorrect\n", 16) = 16 time(NULL) = 1337035715 This is my domain config: ostara ~ # virsh -c lxc:/// dumpxml dwj-lnx-dev <domain type='lxc'> <name>dwj-lnx-dev</name> <uuid>fbcd8c3a-9939-12b4-727d-5d3526bc448f</uuid> <memory unit='KiB'>500000</memory> <currentMemory unit='KiB'>500000</currentMemory> <vcpu>2</vcpu> <os> <type arch='x86_64'>exe</type> <init>/sbin/init</init> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/libexec/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/vm/lxc/dwj-lnx-dev'/> <target dir='/'/> </filesystem> <interface type='bridge'> <mac address='52:54:00:3e:d9:7c'/> <source bridge='br0'/> </interface> <console type='pty'> <target type='lxc' port='0'/> </console> </devices> </domain>

1 0

[libvirt-users] Script execution at Boot
by vipul borikar 14 May '12

14 May '12

I am using KVM on RHEL 6.1. When i try to run a RHEL 5.5 Guest using virt-manager the a shell script put under rc.local runs properly. But when i try to run Guest using cmd line the script doesn't run. I mean it gives error code as 1 . The commands like echo works but executing another shell script under rc.local file doesn't run and gives return code as 1. I know its weird question .. but just was curious is there any parameter in xml file which affects the environment of the boot sequence ??? I can give the both the xml file if needed. -- 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."

1 0

[libvirt-users] Permission issue with cgroups
by Antonio Carlos Salzvedel Furtado Junior 12 May '12

12 May '12

Hello libvirt users, I'm using the cgroup with QEMU guests. At /etc/libvirt/qemu.conf, I have the following parameter: cgroup_controllers = [ "cpu" ] This controller is successfully mounted and libvirt is able to create subgroups for each VM, it's really great the cgroups support in libvirt. The problem is that I can only set the parameters of a given cgroup under the cpu controller if I'm logged in as root. I want another user to have that permission as well. I tried to modify the file /etc/cgconfig.conf to change the permissions. The file is exactly this: group libvirt { perm { admin { uid = opennebula; gid = opennebula; } task { uid = root; gid = root; } } cpu { cpu.shares=512; } } This configuration above does not seem to modify any of the administration permissions. Only the root can edit the parameters under libvirt. The cpu entry was added just to check whether this configuration was read by cgroups at all. The 'cpu.shares' does change in group libvirt. I was careful to start libvirt only after the service cgconfig was restarted. Thanks in advance, Antonio Carlos Furtado

2 4

[libvirt-users] libvirtd fails to start on f16 64bit
by Chad Roberts 12 May '12

12 May '12

Hello, For quite some time, my libvirtd was working great. I came back today to fire-up a VM, but noticed that libvirtd was not running. When I try to start it, I get the following error... libvirtd: symbol lookup error: libvirtd: undefined symbol: avahi_client_new Can anyone shed some light on what my problem may be? Thanks, Chad

1 0

[libvirt-users] segfault with libvirt-0.9.11.3-1
by ovirt＠qip.ru 11 May '12

11 May '12

Hi, ALL On fedora16 hosts with vdsm-4.9.6 after libvirtd daemon started in messages there are too many errors even if no one VM's running, and vdsmd not started May 11 14:44:59 kvm02 kernel: [ 6670.207465] virsh[11015]: segfault at 38 ip 00007f047a52c535 sp 00007fffe3cb0e50 error 4 in libvirt.so.0.9.11[7f047a4bb000+2fd000] May 11 14:44:59 kvm02 kernel: [ 6670.227244] virsh[11018]: segfault at 38 ip 00007f7afe3e6535 sp 00007fff41983d00 error 4 in libvirt.so.0.9.11[7f7afe375000+2fd000] May 11 14:45:09 kvm02 kernel: [ 6680.662175] virsh[11201]: segfault at 38 ip 00007ffe6c129535 sp 00007fffa82c5720 error 4 in libvirt.so.0.9.11[7ffe6c0b8000+2fd000] May 11 14:45:09 kvm02 kernel: [ 6680.679462] virsh[11204]: segfault at 38 ip 00007f9f3c596535 sp 00007fff7cc6c580 error 4 in libvirt.so.0.9.11[7f9f3c525000+2fd000] May 11 14:45:09 kvm02 kernel: [ 6680.696003] virsh[11207]: segfault at 38 ip 00007fa06fb01535 sp 00007fff23cb2260 error 4 in libvirt.so.0.9.11[7fa06fa90000+2fd000] May 11 14:45:09 kvm02 kernel: [ 6680.720678] virsh[11213]: segfault at 38 ip 00007fe557d0b535 sp 00007fff15262720 error 4 in libvirt.so.0.9.11[7fe557c9a000+2fd000] May 11 14:45:09 kvm02 kernel: [ 6680.740552] virsh[11216]: segfault at 38 ip 00007f9dc1507535 sp 00007fff71795540 error 4 in libvirt.so.0.9.11[7f9dc1496000+2fd000] May 11 14:45:20 kvm02 kernel: [ 6691.200793] virsh[11431]: segfault at 38 ip 00007f595f11e535 sp 00007fffc620f660 error 4 in libvirt.so.0.9.11[7f595f0ad000+2fd000] May 11 14:45:20 kvm02 kernel: [ 6691.220691] virsh[11434]: segfault at 38 ip 00007fa843d8c535 sp 00007fff611a4d60 error 4 in libvirt.so.0.9.11[7fa843d1b000+2fd000] May 11 14:45:20 kvm02 kernel: [ 6691.237276] virsh[11437]: segfault at 38 ip 00007f7ece215535 sp 00007fffe0d9ff60 error 4 in libvirt.so.0.9.11[7f7ece1a4000+2fd000] May 11 14:45:20 kvm02 kernel: [ 6691.258537] virsh[11443]: segfault at 38 ip 00007f6bc89f2535 sp 00007fff95244620 error 4 in libvirt.so.0.9.11[7f6bc8981000+2fd000] May 11 14:45:20 kvm02 kernel: [ 6691.278057] virsh[11446]: segfault at 38 ip 00007f4c16f36535 sp 00007fff35394480 error 4 in libvirt.so.0.9.11[7f4c16ec5000+2fd000] May 11 14:45:31 kvm02 kernel: [ 6701.766999] virsh[11660]: segfault at 38 ip 00007f8b64ce7535 sp 00007fffac3014c0 error 4 in libvirt.so.0.9.11[7f8b64c76000+2fd000] May 11 14:45:31 kvm02 kernel: [ 6701.786796] virsh[11663]: segfault at 38 ip 00007f6184ead535 sp 00007fff790ccd50 error 4 in libvirt.so.0.9.11[7f6184e3c000+2fd000] May 11 14:45:31 kvm02 kernel: [ 6701.806817] virsh[11666]: segfault at 38 ip 00007f5aa114f535 sp 00007fffb3d06d60 error 4 in libvirt.so.0.9.11[7f5aa10de000+2fd000] May 11 14:45:31 kvm02 kernel: [ 6701.831577] virsh[11672]: segfault at 38 ip 00007f2d6d123535 sp 00007fff3f45e820 error 4 in libvirt.so.0.9.11[7f2d6d0b2000+2fd000] May 11 14:45:31 kvm02 kernel: [ 6701.851596] virsh[11675]: segfault at 38 ip 00007f8160f16535 sp 00007ffff211d210 error 4 in libvirt.so.0.9.11[7f8160ea5000+2fd000] During compilation I saw this error PASS: start PASS: undefine PASS: vcpupin TEST: virsh-all ........................................ 40 ........................................ 80 .../virsh-all: line 34: 14498 Segmentation fault $abs_top_builddir/tools/virsh -c $test_url $i < /dev/null > /dev/null 2>&1 ...................................... 120 ........................................ 160 ............................ 188 OK PASS: virsh-all PASS: virsh-optparse PASS: virsh-schedinfo but compilation finished and all rpms were created environment: [root@kvm02 ~]# uname -a Linux kvm02 3.3.4-3.fc16.x86_64 #1 SMP Thu May 3 14:46:44 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux [root@kvm02 ~]# rpm -q qemu-kvm qemu-kvm-0.15.1-4.fc16.x86_64 [root@kvm02 ~]# rpm -q libvirt libvirt-0.9.11.3-1.fc16.x86_64 [root@kvm02 ~]# rpm -q vdsm vdsm-4.9.6-0.163.git0633cd2.fc16.x86_64 How is it possible to correct this? --

1 0

[libvirt-users] listing active and defined vs inactive and defined domains
by John Wayne 11 May '12

11 May '12

i am trying to list active + defined and inactive + defined domains using libvirt 0.9.4 i can get active domains using: def s_activedomains(conn): #get active domain ids numofdomains=libvirt.virConnect.numOfDomains(conn) activedomains=libvirt.virConnect.listDomainsID(conn) return activedomains i am stuck on how to get inactive domains the example listed here http://libvirt.org/guide/html/Application_Development_Guide-Guest_Domains-L… under example 4.4 and example 4.5 seems to be outdated looking at /usr/lib64/python2.6/site-packages/libvirt.py, line 2337 says that "Note that this won't work for inactive domains which have an ID of -1" i think example 4.5 is wrong because if inactive domains have an id of -1, then i can't call virDomainLookupBy{Name,ID}

2 1

[libvirt-users] Forward port 4444 to a static-IP VM
by Sean Abbott 11 May '12

11 May '12

I'm attempting to set up a selenium grid on virtual machines. The default NAT is good enough for almost everything, but I need to be able to send my hub VM requests on port 4444. I've attempted to get this going by adding the following to my iptables firewall: -t nat -A PREROUTING -p tcp --dport 4444 -j DNAT --to-destination 192.168.122.107:4444 -t filter -A FORWARD -m state -d 192.168.122.107 --state NEW,RELATED,ESTABLISHED -j ACCEPT And...it's not working. I can hit the port and make requests from the host. Help, please? Thanks! sean

1 0

[libvirt-users] serial console
by John Wayne 11 May '12

11 May '12

hi, when creating a domain using libvirt python api, how would i tell libvirt to use a unique serial port number for domains? in the libvirt.virConnect.defineXML(conn,domainxml) call when i create the domainxml object, i need to ensure that the part below has a unique # for target port <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> currently the domains running on hypervisors have target port numbers such as 1,2,3 and so on. thanks

3 2

[libvirt-users] virsh console logging and pty usage
by Doug Goldstein 11 May '12

11 May '12

Is it possible to both log the serial console and to actually use it? A few of the VMs I've got are configured as follows: <serial type='file'> <source path='/var/log/libvirt/qemu/serial/bb-2.6.18-128.el5-x86_64.log'/> <target port='0'/> </serial> <console type='file'> <source path='/var/log/libvirt/qemu/serial/bb-2.6.18-128.el5-x86_64.log'/> <target type='serial' port='0'/> </console> Because people are hoping to capture the logs after the fact to see if there was any console output which could help them debug an issue. However, if you need to connect to the console of the VM its impossible (e.g. it needs the root password for a fsck). Any suggestions to allow logging but allow it to be usable via "virsh console" as well? Thanks. -- Doug Goldstein

3 3