- Users - libvirt List Archives

[libvirt-users] Is there a good way to "slot" libvirtd versions?
by Whit Blauvelt 02 Aug '11

02 Aug '11

Hi, Is there a reasonable way to alternately use several versions of libvirtd on the same system? I ask because there are features of 0.9.X I want to experiment with, yet also need to use the systems where I'm doing that to connect via virt-manager and virsh to non-experimental systems running 0.8.8 and 0.8.3 on Ubuntu - which the compiled-from-tar 0.9.x has an incompatibility with. As far as I can see with library dependencies there's no simple way to run different editions of the libvirtd stack alternately on the same system. But I could easily be missing a trick. Anyone have this working? Thanks, Whit

1 0

[libvirt-users] centos6.0 unable to install guests w/ kickstart via virt-install
by Charles 01 Aug '11

01 Aug '11

How does one use virt-install and kickstart ? I've seen others have success but I've had no joy thus far. BTW, my interactive virt-installs for centos6 guests work just fine AND I can do unattended kickstarts for vms by booting from centos6 install dvd and typing the kickstart commands from the boot: prompt. However, kickstart commands in --extra-args when used w/ virt-install just don't seem to work for me. It looks like the kickstart file is just getting ignored .. virt-install -n d2 \ -r 1024 \ --vcpus=2 \ -l http://mirror.cogentco.com/pub/linux/centos/6/os/x86_64/ \ --accelerate -v \ --disk path=/data/vm/d2.img,size=10 \ --os-type=linux \ --os-variant=rhel6 --network=bridge:br0 -x "ks=http://10.1.10.2/id400ks.cfg ip=10.1.10.2 netmask=255.255.255.0 gateway=10.1.10.1 dns=8.8.8.8" The above will boot from the mirror and then launch into the interactive graphical installer as though the kickstart file isn't even there. kickstart file is here http://pastebin.com/ZChtv2C5 I also tried 'virsh edit domain' and set cmdline to <cmdline>ks=http://10.1.10.2/id400ks.cfg</cmdline> and that didn't work. vm would'nt start. details ... uname -a Linux myhost 2.6.32-71.29.1.el6.x86_64 #1 SMP Mon Jun 27 19:49:27 BST 2011 x86_64 x86_64 x86_64 GNU/Linux [root vm]# rpm -qa | grep libvir libvirt-0.8.1-27.el6_0.6.x86_64 libvirt-client-0.8.1-27.el6_0.6.x86_64 libvirt-python-0.8.1-27.el6_0.6.x86_64 [root vm]# rpm -qa | grep kvm qemu-kvm-tools-0.12.1.2-2.113.el6_0.8.x86_64 qemu-kvm-0.12.1.2-2.113.el6_0.8.x86_64 any hlp apprec. C.

1 0

[libvirt-users] UID/GID for qemu & kvm
by Jeff 30 Jul '11

30 Jul '11

We use AD infrastructure for user/group management, and GID 107 is already in use. Can I create an AD entry for the kvm and qemu groups with different GIDs, as well as the qemu user/UID? From looking at the libvirt package, it appears it does a getent to see if these exist and, if not, creates them locally, so I assume adding them to AD is ok - and that the GID/UID specified in the package isn't explicitly necessary. Just looking for verification. - Jeff

1 0

[libvirt-users] ANNOUNCE: ruby-libvirt 0.4.0
by Chris Lalancette 29 Jul '11

29 Jul '11

All, I'm pleased to announce the release of ruby-libvirt 0.4.0. ruby-libvirt is a ruby wrapper around the libvirt API. Version 0.4.0 brings new APIs, more documentation, and bugfixes: * Updated Domain class, implementing dom.memory_parameters=, dom.memory_parameters, dom.updated?, dom.migrate2, dom.migrate_to_uri2, dom.migrate_set_max_speed, dom.qemu_monitor_command, dom.blkio_parameters, dom.blkio_parameters=, dom.state, dom.open_console, dom.screenshot, and dom.inject_nmi * Implementation of the Stream class, which covers the libvirt virStream APIs * Add the ability to build against non-system libvirt libraries * Updated Error object, which now includes the libvirt code, component and level of the error, as well as all of the error constants from libvirt.h * Updated Connect class, implementing conn.sys_info, conn.stream, conn.interface_change_begin, conn.interface_change_commit, and conn.interface_change_rollback * Updated StorageVol class, implementing vol.download and vol.upload * Various bugfixes Version 0.4.0 is available from http://libvirt.org/ruby: Tarball: http://libvirt.org/ruby/download/ruby-libvirt-0.4.0.tgz Gem: http://libvirt.org/ruby/download/ruby-libvirt-0.4.0.gem It is also available from rubygems.org; to get the latest version, run: $ gem install ruby-libvirt As usual, if you run into questions, problems, or bugs, please feel free to mail me (clalance(a)redhat.com) and/or the libvirt mailing list. -- Chris Lalancette

1 0

[libvirt-users] management tools for kvm
by David M. Barlieb 29 Jul '11

29 Jul '11

I have been installing kvm guests on a number of hosts and have been managing them through a single virt manager on one of the hosts. I am looking for a tool that will allow me to manage them from a windows workstation, possibly using a web interface. Everything I've looked at and read about seems to require a linux workstation to install on, like oVirt or ConVirt. I am looking for a product that can run on a windows workstation using either firefox or ie. dave

7 9

[libvirt-users] Seg fault in 0.9.4-rc1
by Whit Blauvelt 29 Jul '11

29 Jul '11

Hi, Using virt-manager, asking to migrate a kvm domain from the same box virt-manager is running on to another consistently results in libvirtd faulting on the local box. Migration in the other direction, from the second box to the box virt-manager is on, works fine. A libvirtd log made with debug=1 is at http://transpect.com/debug/libvirtd_segfault.log It was doing the same thing with a recent 0.9.3 git version too. This is with virt-manager 0.9.0. Whit

2 2

[libvirt-users] qemu:///session vs qemu:///system
by Peter Thomassen 28 Jul '11

28 Jul '11

Hi, I am running several QEMU VMs on a host machine. There's different persons being responsible for different VMs. I would like to find a way to allow everybody to manage just the VMs they are assigned to (i.e. insert some ISO file, stop the machine and so on) without allowing them to disturb the other VMs. Also, I would like to allow these persons to set up new VMs (there's plenty of unallocated storage) without having to ask me (root) to do it for them, but without allowing them to delete other VMs. (Just setting user rights on the filesystem is not enough, as I use LVM volumes which are not assigned to a user in the typical sense, are they?) I know that most of this could probably be achieved by using qemu:///session instead of qemu:///system. However, I read that there's networking issue in this case (which issues precisely?), and I am also not sure if there's other disadvantages like less efficient handling in some situations by the kernel, or whatever. Is anybody there who could clarify this for me? Thank you, Peter

1 0

[libvirt-users] small webGUI?
by Stefan G. Weichinger 28 Jul '11

28 Jul '11

Greetings, at a customer we run a single VM for a specific application. Unfortunately this VM does not start automatically with the host although I checked the relevant box within virtual machine manager. I assume upgrading libvirt might help (we run 0.8.7-r1 right now, gentoo linux). Aside from that it would be good to have a simple WebGUI for the users to let them press START just in case. They run Windows on their machines so I can't give them VMM ... Could you point me at the most simple GUI to do that? I'd prefer something very lightweight without too much requirements (for example I'd like to avoid installing mysql for that ;-) ). Thank you, Stefan

1 2

[libvirt-users] with current libvirt git virsh expects vbox, refuses kvm define
by Whit Blauvelt 28 Jul '11

28 Jul '11

Okay, just installed libvirt from today's git on two Ubuntu systems. The first one went fine (except for continuation of the problem that virsh and virt-manager cannot connect to 0.8.3 systems that's been there in the 0.9.x libvirts) ... but on the second, after install, "virsh list --all" presents nothing. And: # virsh define tu1004.xml error: Failed to define domain from tu1004.xml error: internal error unexpected domain type kvm, expecting vbox These are _exactly_ the same xml files as are still working on the first system. And in both cases the new libvirt was built with defaults. Long ago the second system did have VirtualBox on it, so that may have been found while it was setting up config, but that's no good reason for KVM to fail here, right? Must be a thing with the git. Ran the 0.9.3 release built on this system previously without this problem. Whit

5 11

Re: [libvirt-users] VirtualBox headless
by Guilherme Santos 27 Jul '11

27 Jul '11

My objective is also to run headless virtual machines through libvirt library. I am using an Ubuntu 10.04 distro and libvirt 0.9.2. Before asking you guys about it, I searched on the web and found this: Hi, > > thanks for your hint. > > I read the lines in the documentation, but unfortunately editing the xml > > within virsh lead to the errors. > > The Solution to a headless domain was to edit the XML file from bash and > then > > #virsh: define <domainname.xml> > > to reload the new values for the graphics type of the machine. > > Obvioulsy something went wrong when editing "live".... > > Regards, > Christian > > Am 24.06.2010 18:27, schrieb Jean-Baptiste Rouault: > > Hi, > > > > Something like this should work, as can be seen in the > > > documentation here : http://libvirt.org/formatdomain.html#elementsGraphics > > > > <drivers> > > <graphics type='rdp' autoport='yes' /> > > > </drivers> > > > > Regards, > > > > Jean-Baptiste > > > > > >> Hello, > >> > >> I'm trying to use the VirtualBox/vbox driver together with libvirt 0.8.1 > >> on a Ubuntu Lucid Machine, VirtualBox Release 3.1. > > >> > >> The goal is to run the virtual machines headless and to connect using RDP. > >> > >> When starting a virtual domain using 'virsh start <domainname>' the GUI > >> of VirtualBox will pop up and I see no option to prevent this. If X is > > >> not running, the virsh command will terminate with 'unknown failure'. > >> > >> I've found some hints on inclusion of the headless statement in the > >> 'graphics' part of the XML definition file, but when I tree to adopt > > >> this, the editing of the file will crash. > >> > >> Has anyone achieved to manage VBox machines with libvirt on a headless > >> server ? > >> > >> Thanks in advance for some hints or experiences with this issue, > > >> Christian > >> > > Unfortunately this isn't working for me. Following is my XML configuration: <domain type='vbox'> <name>THEDOMAIN</name> <uuid>33f6e188-1479-46f4-9d90-4d5a2d3a30f2</uuid> <memory>393216</memory> <currentMemory>393216</currentMemory> <vcpu>1</vcpu> <os> <type arch='i686'>hvm</type> <boot dev='hd'/> <boot dev='cdrom'/> </os> <features> <acpi/> </features> <clock offset='localtime'/> <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> <devices> <disk type='file' device='disk'> <source file='/local/vbox-shared.vdi' /> <target dev='hda' bus='ide'/> </disk> <disk type='file' device='cdrom'> <source file='/local/ubuntu-11.04-desktop-i386.iso' /> <target dev='hdc' bus='ide'/> </disk> <interface type='user'> <mac address='08:00:27:9a:d0:63'/> <model type='Am79C973'/> </interface> <input type='mouse' bus='ps2'/> <graphics type='rdp' autoport='yes' /> <video> <model type='vbox' vram='12' heads='1'> <acceleration accel3d='no' accel2d='no'/> </model> </video> </devices> </domain> When I run command *virsh start THEDOMAIN* it is popping up the following error message: *OpenRemoteSession/LaunchVMProcess failed, domain can't be started* As it wasn't working I also tried other options, but unfortunately, using all other graphic type options (except for 'spice', which I didn't try) the GUI is launched. I don't think I'll be needing a RDP connection, neither anything similar to that, except if these are necessary to basic management of the vm through virsh (start, stop, reboot, create and revert snapshots). Isn't there one simple way to run a virtual machine domain headless without vnc, spice or rdp servers? If not, which could be going wrong in my xml configuration? To help understanding of my desired behavior, what I need is to do through virsh what can be done using *VBoxManage startvm THEDOMAIN --headless* or *VBoxHeadless startvm THEDOMAIN*, because will use other hypervisors in the future, so it is a critical thing to me. Thanks in advance for the help, Guilherme Santos

2 1