- Devel - libvirt List Archives

[Libvir] PATCH 0/2: Capabilities and features
by David Lutterkort 30 Jul '07

30 Jul '07

Hi, these two patches extend the features libvirt reports in the capabilities XML; in particular, features are now reported for the QEMU driver, and features for both Xen and QEMU include information on ACPI/APIC support. Tools that rely on feature reporting, in general, need to know whether a certain feature is on or off by default, and whether that can be toggled, because users will be asking for one of three things for their VM: * Feature X (e.g., ACPI) must be on/present in the VM * Feature X must not be on/present in the VM * It doesn't matter whether feature X is there or not For example, in QEMU, ACPI is on by default, but can be turned off. The APIC on the other hand, is always there and can't be turned off. That is now reported as <features> <acpi default="on" toggle="yes"/> <apic default="on" toggle="no"/> </features> It's unfortunate that the format for PAE (<pae/> vs. <nonpae/>) reporting doesn't fit into this scheme. I didn't want to start with having tags <X/> and <nonX/> for each feature; that means that parsers need to special case PAE. It's probably too late, but it would be nice if PAE was reported in a similar format, with <pae> correponding to <pae default="on" toggle="no"/>, <nonpae/> corresponding to <pae default="yes" toggle="no"/>, and having both together corresponding to <pae default="yes" toggle="yes"/>, but that's a separate discussion from these patches. David

4 12

[Libvir] [PATCH] virsh Range check in Credit Scheduler
by Atsushi SAKAI 30 Jul '07

30 Jul '07

Hi, Add Range check in Credit Scheduler. Signed-off-by: Atsushi SAKAI <sakaia(a)jp.fujitsu.com> Thanks Atsushi SAKAI

6 20

[Libvir] [PATCH] add a ttyconsole command
by Daniel Veillard 26 Jul '07

26 Jul '07

It was pointed out that we have a vncdisplay command but none for extracting the TTY console device: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=239687 the trivial associated patch adds it as well as the doc in the man page Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard(a)redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

3 4

[Libvir] PATCH: Separate QEMU impl of nodeinfo API
by Daniel P. Berrange 25 Jul '07

25 Jul '07

While fixing the QEMU nodeinfo API to correctly deal with case where CPU sockets have sparse numbering (eg sockets 0 & 3 are populated), I realized that OpenVZ doesn't have a nodeinfo API, and its requirements are basically identical to the QEMU driver's. So this patch moves the impl of the nodeinfo API into a nodeinfo.c file, and makes both the QEMU and OpenVZ driver call out to this shared impl. I also put #ifdef __linux__ around the impl since code reading /proc/cpuinfo is never going to work on any non-Linux platform. For non linux I just return -1 which'll get treated as not-implemented. If QEMU driver is ported to work on Solaris, the nodeinfo.c file can be easily extended for their custom impl. Finally I'm adding a testcase with a bunch of example /proc/cpuinfo files to validate correctness Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|

3 4

[Libvir] [PATCH] Python bindings: Use virDomain/NetworkGetConnect instead of storing connection in domain/network object
by Richard W.M. Jones 24 Jul '07

24 Jul '07

Previously[1] I patched libvirt to add the virDomainGetConnect and virNetworkGetConnect functions. The rationale for these is explained here[2]. The attached patch makes the Python bindings use these functions instead of storing the connection object explicitly. Rich. [1]https://www.redhat.com/archives/libvir-list/2007-June/msg00365.html [2]https://www.redhat.com/archives/libvir-list/2007-June/msg00352.html

3 8

[Libvir] Release of libvirt-0.3.1
by Daniel Veillard 24 Jul '07

24 Jul '07

Quite a few things were fixed since 0.3.0, and it was looking like a new release at this point would be a good idea. Availbale at ftp://libvirt.org/libvirt/ * Documentation: - index to remote page - script to test certificates - IPv6 remote support docs (Daniel Berrange) - document VIRSH_DEFAULT_CONNECT_URI in virsh man page (David Lutterkort) - Relax-NG early grammar for the network XML (David Lutterkort) * Bug fixes: - leaks in disk XML parsing (Masayuki Sunou) - hypervisor alignment call problems on PPC64 (Christian Ehrhardt) - dead client registration in daemon event loop (Daniel Berrange) - double free in error handling (Daniel Berrange) - close on exec for log file descriptors in the daemon (Daniel Berrange) - avoid caching problem in remote daemon (Daniel Berrange) - avoid crash after QEmu domain failure (Daniel Berrange) * Improvements: - checks of x509 certificates and keys (Daniel Berrange) - error reports in the daemon (Daniel Berrange) - checking of Ethernet MAC addresses in XML configs (Masayuki Sunou) - support for a new clock switch between UTC and localtime (Daniel Berrange) - early version of OpenVZ support (Shuveb Hussain) - support for input devices on PS/2 and USB buses (Daniel Berrange) - more tests especially the QEmu support (Daniel Berrange) - range check in credit scheduler (with Saori Fukuta and Atsushi Sakai) - add support for listen VNC parameter un QEmu and fix command line arg (Daniel Berrange) * Cleanups: - debug tracing (Richard Jones) - removal of --with-qemud-pid-file (Richard Jones) - remove unused virDeviceMode - new util module for code shared between drivers (Shuveb Hussain) - xen header location detection (Richard Jones) thanks to everybody who helped for this release, with bug reports or patches ! Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard(a)redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

1 0

[Libvir] PATCH: Make QEMU driver honour 'listen' flag for VNC
by Daniel P. Berrange 24 Jul '07

24 Jul '07

In QEMU 0.9.0 or later it is possible to tell QEMU to only listen on a particular IP address. THis patch adapts the code so that it honours the 'listen' attribute on the <graphics> tag if using QEMU >= 0.9.0. It also re-enables the tests for this capability that I temporarily disabled. src/qemu_conf.c | 37 +++++++++++++----- src/qemu_conf.h | 1 tests/qemuxml2argvdata/qemuxml2argv-graphics-sdl.args | 2 tests/qemuxml2argvtest.c | 4 - tests/qemuxml2xmltest.c | 2 5 files changed, 32 insertions(+), 14 deletions(-) Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|

3 5

[Libvir] PATCH: Fix crash in cleanup when VM creation fails
by Daniel P. Berrange 24 Jul '07

24 Jul '07

If using the 'virDomainCreateLinux' call to create a VM, a so called 'transient' domain will be created - ie one without any config file. There is special code in the qemudShutdownVMDaemon method to cleanup the resources associated with such domains, in particuarly free'ing the struct qemud_vm object. Unfortunately in the virDomainCreateLinux codepath this is a problem, because we still need the 'struct qemud_vm' object in certain edge cases, and so the caller has to free it. We currently have a double free() in that scenario. This patch removes the call to qemudFreeVMDaemon from qemudShutdownVMDaemon. Instead it is now always the caller's responsibility to cleanup after transient domains. qemu_driver.c | 39 ++++++++++++++++++++------------------- 1 file changed, 20 insertions(+), 19 deletions(-) Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|

2 2

[Libvir] Remote daemon & virDomainFree interaction
by Daniel P. Berrange 24 Jul '07

24 Jul '07

In looking at a problem with domain object cleanup in virt-manager I came across a problem in the remote driver, well the internal driver API itself actually. Specifically the implmenetation of virDomainFree() never calls into the driver API - it simply uses virFreeDomain() release the memory associated with the virDomainPtr object. Couple this with the remote driver though, and virDomainPtr objects in the remote daemon never get released, because the virDomainFree call is never propagated over the wire to the server. Its quite easy to see this in practice. Simply add a printf to the impl of virDomainLookupByName which prints out the ref count. Then run either virsh or virt-manager for a while Get info QEMUGuest1 69 c7a5fdbd-edaf-9455-926a-d65c16db1809 Get info QEMUGuest1 70 c7a5fdbd-edaf-9455-926a-d65c16db1809 Get info QEMUGuest1 71 c7a5fdbd-edaf-9455-926a-d65c16db1809 We need to make virDomainFree call into the driver API, and also make sure that the remote driver implements it. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|

3 4

[Libvir] [PATCH] virDomainMigrate version 4 (for discussion only!)
by Richard W.M. Jones 24 Jul '07

24 Jul '07

This is version 4 of the virDomainMigrate patch. It includes remote support, but no qemu, virsh or python yet. And it needs lots more testing which I intend to do more of tomorrow. Interface --------- The interface is now this: virDomainPtr virDomainMigrate (virDomainPtr domain, virConnectPtr dconn, unsigned long flags, const char *dname, const char *uri, unsigned long resource); The caller may set dname, uri and resource to 0/NULL and forget about them. Or else the caller may set, in particular, uri to allow for more complicated migration strategies (especially for qemu). https://www.redhat.com/archives/libvir-list/2007-July/msg00249.html Driver support -------------- As outlined in the diagram in this email: https://www.redhat.com/archives/libvir-list/2007-July/msg00264.html migration happens in two stages. Firstly we send a "prepare" message to the destination host. The destination host may reply with a cookie. It may also suggest a URI (in the current Xen implementation it just returns gethostname). Secondly we send a "perform" message to the source host. Correspondingly, there are two new driver API functions: typedef int (*virDrvDomainMigratePrepare) (virConnectPtr dconn, char **cookie, int *cookielen, const char *uri_in, char **uri_out, unsigned long flags, const char *dname, unsigned long resource); typedef int (*virDrvDomainMigratePerform) (virDomainPtr domain, const char *cookie, int cookielen, const char *uri, unsigned long flags, const char *dname, unsigned long resource); Remote support -------------- To make this work in the remote case I have had to export two private functions from the API which only remote should call: __virDomainMigratePrepare __virDomainMigratePerform The reason for this is that libvirtd is just linked to the regular libvirt.so, so can only make calls into libvirt through exported symbols in the dynamic symbol table. There are two corresponding wire messages (REMOTE_PROC_DOMAIN_MIGRATE_PREPARE and REMOTE_PROC_DOMAIN_MIGRATE_PERFORM) but they just do dumb argument shuffling, albeit rather complicated because of the number of arguments passed in and out. The complete list of messages which go across the wire during a migration is: client -- prepare --> destination host client <-- prepare reply -- destination host client -- perform --> source host client <-- perform reply -- source host client -- lookupbyname --> destination host client <-- lookupbyname reply -- destination host Xen URIs -------- Xen recognises the following forms of URI: hostname hostname:port tcp://hostname/ tcp://hostname:port/ Capabilities ------------ I have extended capabilities with <migration_features>. For Xen this is: <capabilities> <host> <migration_features> <live/> <uri_transports> <uri_transport>tcp</uri_transport> </uri_transports> </migration_features> Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903

4 18

[Libvir] OpenVZ XML format and VPS properties get/set interface [long]
by Shuveb Hussain 24 Jul '07

24 Jul '07

Hi, I started a discussion on OpenVZ XML format a while ago. But let me do it again with more explanation about OpenVZ this time, so that others can understand how it is different and how this can best fit into the libvirt model of doing things. Terminology: Virtual Private Server (VPS), Virtual Environment (VE) and Domain are all the same. OpenVZ is a lot about providing QoS to its users. About 20 carefully chosen parameters regarding various resources such as memory, CPU, disk and network are chosen. These are then used to provide minimum guarantee on any system running OpenVZ. Most of the time, these are limits that can be set per Virtual Private Server(VPS). In Xen or QEMU, if a disk image is available(Xen needs an additional kernel), it is possible to run the domain. Then forget all about it after the domain is shutoff. This is not possible in OpenVZ. When a new VPS/VE/Domain needs to be created, it needs a file system. This needs to be created along with its related configuration files in specific locations. Only after this can it be started. There is a "destroy" command available in OpenVZ, which is different from the destroy in libvirt. This will completely erase the file system and remove the related config file as well. Since there are many configurable parameters, the OpenVZ tools provides 2 sample templates or profiles on which newly created Virtual Environments(VEs) can be based. So, during VPS creation, rather than taking a million parameters, the name of the profile is taken as an argument and the variables in the file are used to create the VE. These values can later on be overridden and also be optionally stored in the VE's private config file to ensure persistence across reboots. Since there are many parameters needed during VE creation, using the profile name is practical. So, in the proposed XML file, I'm using the profile name. OpenVZ has its own config file format. We are storing the UUID there in a comment, since UUIDs are not used by OpenVZ. While a VE is created, the easiest way to do it is using a so called template cache. This is just a tar file of a Linux distro FS that is used to create a new file system for a VE. There are no disk images. The VE root fs resides on the host file system as a bunch of files and directories. A few template caches are usually available, say one based on Debian, one based on Fedora Core and another based on Suse. The user can choose which one to use while creating a new VE. However, the name of the template cache is not stored anywhere once the VE filesystem is created. I think one more comment is needed in the per-VE config file for this, just as we are storing the UUID. Here is a sample template. This one is called vps.basic, comes with the OpenVZ tools: ----------------------------------------------------------------- ONBOOT="no" # UBC parameters (in form of barrier:limit) # Primary parameters AVNUMPROC="40:40" NUMPROC="65:65" NUMTCPSOCK="80:80" NUMOTHERSOCK="80:80" VMGUARPAGES="6144:2147483647" # Secondary parameters KMEMSIZE="2752512:2936012" TCPSNDBUF="319488:524288" TCPRCVBUF="319488:524288" OTHERSOCKBUF="132096:336896" DGRAMRCVBUF="132096:132096" OOMGUARPAGES="6144:2147483647" # Auxiliary parameters LOCKEDPAGES="32:32" SHMPAGES="8192:8192" PRIVVMPAGES="49152:53575" NUMFILE="2048:2048" NUMFLOCK="100:110" NUMPTY="16:16" NUMSIGINFO="256:256" DCACHESIZE="1048576:1097728" PHYSPAGES="0:2147483647" NUMIPTENT="128:128" # Disk quota parameters (in form of softlimit:hardlimit) DISKSPACE="1048576:1153434" DISKINODES="200000:220000" QUOTATIME="0" # CPU fair sheduler parameter CPUUNITS="1000" ------------------------------------------------------------ Here is the proposed XML format: <domain type='openvz'> <name>105</name> <uuid>8509a1d4-1569-4467-8b37-4e433a1ac7b1</uuid> <filesystem> <template>gentoo-20060317-i686-stage3</template> <quota level='first'>10737418240</quota> <quota level='second' uid='500'>5368709120</quota> </filesystem> <profile>vps.basic</profile> <devices> <interface> <ipaddress>192.168.1.105</ipaddress> </interface> </devices> <nameserver>192.168.1.1</nameserver> <hostname>fedora105</hostname> </domain> I don't think the "filesystem" tag can fit logically into "devices", since it has quota and other information. The "template" is the name of the template cache used to create the VE. One of the main reasons many people(especially hosting providers) use OpenVZ is since it can be used to provide service level agreements. There must be a way to set/get various VPS parameters from libvirt. I understand concerns about driver specific code in libvirt based clients like virt-manager. The capabilities paradigm will not fit here, since this is simply about various properties of the VE/domain, not the hardware or the VM capabilities. Please correct me, if I am wrong. So, how to we do it? Thanks and Regards, -- Shuveb Hussain Unix is very user friendly. It is just a little choosy about who its friends are http://www.binarykarma.com

5 14

[Libvir] [PATCH] virDomainMigrate (version 5) (for discussion only, but getting there)
by Richard W.M. Jones 23 Jul '07

23 Jul '07

This is a rolled up patch for virDomainMigrate, including virsh and Python fixes. Changes since last time: - VIR_MIGRATE_LIVE is exported to Python - 'resource' parameter is now named 'bandwidth' - there is now an extra domainMigrateFinish step It needs a bit more testing which I can't do today while I'm at the office. Rich.

2 1

[Libvir] [PATCH] Document VIRSH_DEFAULT_CONNECT_URI
by David Lutterkort 23 Jul '07

23 Jul '07

I keep forgetting the exact name of VIRSH_DEFAULT_CONNECT_URI - patch to add it to the man page attached. David

2 1

[Libvir] FW: [et-mgmt-tools] Release 0.200.0 of virtinst
by Daniel P. Berrange 20 Jul '07

20 Jul '07

FYI a new libvirt based tool for cloning VMs... ----- Forwarded message from "Daniel P. Berrange" <berrange(a)redhat.com> ----- > Date: Thu, 19 Jul 2007 03:16:56 +0100 > From: "Daniel P. Berrange" <berrange(a)redhat.com> > To: et-mgmt-tools(a)redhat.com > Subject: [et-mgmt-tools] Release 0.200.0 of virtinst > > I'm happy to announce the release of virtinst version 0.200.0 > > This release introduces the virt-clone tool which provides the ability > to clone an existing inactive guest. The disk images will be copied, > new MAC address, UUID and name will be given to the guest. Documentation > is improved with the addition of manual pages for both virt-install and > virt-clone. Validation of input parameters has been further enhanced, > and re-factored to allow sharing with virt-manager. The virt-install > tool can be used to boot live CD images, with or without underlying > storage. > > It is available for download from the usual place: > > http://virt-manager.org/download.html > > Or directly: > > http://virt-manager.org/download/sources/virtinst/virtinst-0.200.0.tar.gz > > Thanks to everyone who has participated in development & testing of the > code in this new release! > > Regards, > Dan. ----- End forwarded message ----- Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|

2 1

[Libvir] [PATCH]0/3 OpenVZ driver : Some clean ups
by Shuveb Hussain 19 Jul '07

19 Jul '07

Hi, Here are some cleanups as per discussions on the list: Change log: * Make sure we are running on OpenVZ enebled kernel in the driver open() method * Some minor macro cleanups * Use generic UUID parsing rather than own and scanf() * Made private functions static * New files utils.[c,h] added that have 2 functions virExec and virExecNonBlock * Removed popen and used virExec in openvz_driver.c * qemu_driver.c updated to use new virExecNonBlock() functions instead of qemudExec, which is removed Thanks, -- Shuveb Hussain Unix is very user friendly. It is just a little choosy about who its friends are http://www.binarykarma.com

2 3

[Libvir] Xen reboot does not work with Sys::Virt perl binding
by Keck, Christian (ext) 19 Jul '07

19 Jul '07

Hello guys! I am using the perl bindings (Sys::Virt) to manage my virtual xen hosts. Because it directly maps the C api, I thought it's a good idea to ask you instead of the author of this module. Xen version is 3.0 with libvirt 0.1.9 on a red hat box. while calling the reboot method i get following error: libvirt error code: 0, message: Unknown problem In this case the virtual system does not reboot. But with shutdown method, which throw the same error, the system shuts down correctly. Here is my code: my $vmm = Sys::Virt->new(); my $dom = eval { $vmm->get_domain_by_name( $p->{ name } ) }; $dom->reboot(&Sys::Virt::Domain::REBOOT_RESTART); Is this a known issue? Thank you for your help. Best regards, Christian

2 2

[Libvir] RFC: format for mapping host devices to guest
by Daniel P. Berrange 19 Jul '07

19 Jul '07

I'm considering the problem of mapping host USB devices through to the guest as one of the 2 remaining bits of USB support needed (the other being the mapping disks through as USB mass storage). I have previously mentioned some ideas in this mail, though looking back on this I don't much like them https://www.redhat.com/archives/libvir-list/2007-March/msg00205.html Also, there was just the message about a desire to support mapping of PCI devices. The USB stuff I want todo with both Xen and QEMU. In Xen, USB device passthrough is based on: usbdevice=host:[bus id].[device id] eg usbdevice=host:003.001 Or usbdevice=host:[vendor id]:[product id] eg usbdevice=host:0483:2016 In QEMU, USB device passthrough is pretty much the same with command line args: -usbdevice host:[bus id].[device id] eg -usbdevice host:003.001 Or -usbdevice host:[vendor id]:[product id] eg -usbdevice host:0483:2016 Finally, in Xen, PCI device passthrough is done with pci=['pci device id',....] eg pci=['00:1f.3'] So we need some form of element under the <devices> section per device to map through. At minimum this will need the source device info. If we are to support unplugging of USB devices in QEMU it is neccessary to have the target device id - this is generated by QEMU when attaching the USB device. So to attach a device: <host bus='usb'> <source device="003.001"/> </host> Or <host bus='usb'> <source vendor='0483' product='2016'> </host> The first form is useful for live hotplug - where you know the exact device instance. The second form is useful for permanent config - you don't know what device id it'll have since it may be plugged into the host in any order. When splitting the XML back out, QEMU would fill in the target info giving us either: <host bus='usb'> <source dev='003.001'/> <target dev='001.005'/> </host> Or <host bus='usb'> <source vendor='0483' product='2016'/> <target dev='001.005'/> </host> This is suitable for giving to virDomainDetachDevice() - we use the target dev for the QEMU monitor 'usb-detach' command. Now PCI would be similar - no hotplug to worry about here though, and no need (or availability) or target info. So the XML would simply be <host bus='pci'> <source dev='00:1f.3'/> </host> NB I choose 'host' as the element name since we're basically giving the guest an arbitrary host device. My previous email had thought about calling it 'bus' but we're not really defining a bus in this context and there may very well be some scenario in the future where we do need to represent the concept of a 'bus' in the XML directly. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|

2 3

[Libvir] [PATCH]3/3 OpenVZ driver : qemu_driver.c changes
by Shuveb Hussain 19 Jul '07

19 Jul '07

-- Shuveb Hussain Unix is very user friendly. It is just a little choosy about who its friends are http://www.binarykarma.com

1 0

[Libvir] [PATCH]2/3 OpenVZ driver : generic utils
by Shuveb Hussain 19 Jul '07

19 Jul '07

-- Shuveb Hussain Unix is very user friendly. It is just a little choosy about who its friends are http://www.binarykarma.com

1 0

[Libvir] [PATCH]1/3 OpenVZ driver : Cleanups
by Shuveb Hussain 19 Jul '07

19 Jul '07

Cleanup patch, also adds utils.c and utils.h to Makefile.am -- Shuveb Hussain Unix is very user friendly. It is just a little choosy about who its friends are http://www.binarykarma.com

1 0

[Libvir] PATCH: Fix accident close of monitor FD & leak of logfile FD to child
by Daniel P. Berrange 19 Jul '07

19 Jul '07

After the QEMU monitor filehandle has been successfully initialized, we then promptly close it ! It seems a 'return' statement accidentally got removed somewhere during previously refactoring. Second, the QEMU logfile does not have the close-on-exec flag set so the logfile is leaked to child processes. qemu_driver.c | 13 +++++++++++++ 1 file changed, 13 insertions(+) Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|

2 1

[Libvir] XM config <-> XML config
by Arik Raffael Funke 19 Jul '07

19 Jul '07

Hi, I am using Fedora 7 with virt-manager to control my xen domains. I would like to delegate a pci device to one of my domU's. I know how this is done in the XM and sxp config files, but how is it done now? I read that libvirt can convert XM <-> XML and though I could export my current config to XM format, edit it and reimport. How is is done with libvirt? Thanks, Arik

2 3

[Libvir] PATCH: Support input devices in XML format
by Daniel P. Berrange 18 Jul '07

18 Jul '07

This patch is the first step towards supporting USB devices in libvirt XML format. As per the original thread some months back[1], I'm the grouping is being done based on device classes, rather than bus types. So this first patch is actually introducing the concept of 'input' devices. This is best illustrated by examples - PS2 mouse - automatically added when yuou turn on <graphics> in an HVM guest. <input type='mouse' bus='ps2'/> - Xen mouse - automatically added when you turn on <graphics> in a Xen paravirt guest (ie the paravirt input device) <input type='mouse' bus='xen'/> - USB mouse - have to actually ask for this. Not all that useful since its still using relative co-ordinates, but here for completeness. <input type='mouse' bus='usb'/> - USB tablet - have to actually ask for this. Very useful. Windows and Linux can both drive this in absolute co-ordinate mode. <input type='tablet' bus='usb'/> If it possible to omit the 'bus' attribute, in which case it'll automatically set up the device on the most appropriate bus for that type of device. So if you say type='mouse', it'll pick a ps2/xen bus. If you say type='tablet' it'll pick a usb bus. In my previous email[1] I suggested a possible 'model' attribute as well. I since discovered that Xen removed support for the summagraphics tablet completely, so adding a model at this time is a waste of time. We can always choose it add it later if we port to another virt manager here we need to distinguish devices on more than just a (type, bus) pair. As with the previous '<clock/>' element, it is intended that virt-install and virt-manager will automatically add a USB tablet if they you tell them you're installing Windows, or a recent Linux guest. It'll also be possible manally add post-install through the virt-manager UI. For the QEMU driver at least, I intend to make it possible to hot add & remove USB devices. This will appear as impl of virAttach/Detch methods for QEMU at least. Xen doesn't support hot add/remove of USB at this time. Finally, before I actually commit this I think it is well overdue to write some unit tests for the QEMU driver. So I'm going to do a test which chceks XML -> data struct -> QEMU command line, and XML -> data struct -> XML sequences of operations. This should let us exercise all the XML related code in QEMU which is a good start & helpful to avoid regressions. Regards, Dan. [1] http://www.redhat.com/archives/libvir-list/2007-March/msg00205.html -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|

3 6

[Libvir] Asynchronous notifications of domain start/stop
by Richard W.M. Jones 18 Jul '07

18 Jul '07

I had some private discussions with a developer who wants to start using libvirt, but requires asynch notifications of domain start/stop (and other stuff, but this will do for the moment). Right now he's using XenStore watches. The alternative of polling didn't look very appealing for him. A rough API for this might look like this: typedef int virEventHandle; /* Register a callback to catch domain start events. */ virEventHandle virEventDomainStart (virConnectPtr, void (*f) (virConnectPtr, int domid)); /* Register a callback to catch domain stop events. */ virEventHandle virEventDomainStop (virConnectPtr, void (*f) (virConnectPtr, int domid)); /* Unregister any type of callback. */ int virEventCancel (virConnectPtr, virEventHandle handle); Implementation -------------- In the Xen case, we can use XenStore watches[1]. Callbacks from XenStore can be translated directly into event callbacks. In the qemu case, the daemon knows when the qemu instances that it manages come and go. In the qemu/remote case, asynch notifications are nominally supported by the protocol, but I haven't really looked at all the implications. Seems like we'd need to use MSG_OOB to signal the client process, and translate the SIGURG signal received into a callback. This is all tricky and Unix-specific though so if you have any better ideas ... We would also need to avoid mixing ordinary request/response with the notifications, which OOB takes care of. Rich. [1] http://wiki.xensource.com/xenwiki/XenBusDriver -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903

4 17

[Libvir] virDomainConfigureDevice?
by Hugh Brock 18 Jul '07

18 Jul '07

I'm looking at ways to replicate xm block-configure at the libvirt level. xm block-configure is useful in that it allows you to change the back device for an HVM guest while the guest is still running; this permits you for example to change the CDROM without shutting down your guest or poking around in xenstore. Thus we can have an "eject" button on cdrom devices in virt-manager (or "eject" and "load" buttons, I guess), which we really need. The issue of course is that xm block-configure is specifically intended for block devices and takes arguments for the back device and the front device (among others). We would naturally prefer to accept a block of XML just as virDomainAttachDevice does and then parse it, determine if the device in question is of a type we can actually edit, determine if the new backdev is appropriate, and so on. None of this seems terribly hard, but before I go implement it, are there obvious pitfalls I'm not thinking? And given that virDomainAttachDevice is not implemented for qemud in libvirt (is it?), how do we handle the non-xen case? Thanks, --Hugh -- Red Hat Virtualization Group http://redhat.com/virtualization Hugh Brock | virt-manager http://virt-manager.org hbrock(a)redhat.com | virtualization library http://libvirt.org

4 7