- Devel - libvirt List Archives

[Libvir] Release of libvirt-0.1.8
by Daniel Veillard 16 Oct '06

16 Oct '06

There have been a number of bug raised and fixed since the 0.1.7 release: * Bug for system with page size != 4k * vcpu number initialization (Philippe Berthault) * don't label crashed domains as shut off (Peter Vetere) * fix virsh man page (Noriko Mizumoto) * blktapdd support for alternate drivers like blktap (Daniel Berrange) * memory leak fixes (xend interface and XML parsing) (Daniel Berrange) * compile fix * mlock/munlock size fixes (Daniel Berrange) * improve error reporting The new package is available as usual at ftp://libvirt.org/libvirt/ thanks to everybody who helped by reporting or fixing bugs ! 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] Potential problem on NUMA machines
by Philippe Berthault 13 Oct '06

13 Oct '06

In the virNodeInfo structure, it's assumed that all nodes of multiprocessor systems have the same number of sockets. But on NUMA machines, it's not mandatory that all SMP nodes have the same number of sockets. So there is a potential problem when computing the number of processors by using the informations returned in the virNodeInfo structure. This problem exists also in Xen (in the "xm info" command) but both Xen and libvirt are wrong.

2 1

[Libvir] virDomainGetInfo returns a false result on IA64 systems
by Philippe Berthault 12 Oct '06

12 Oct '06

The maxMem and memory fields of the virDomainInfo structure are false on IA64 systems. The problem is in xen_internal.c at lines 1530,1531: info->memory = XEN_GETDOMAININFO_TOT_PAGES(dominfo) * 4; info->maxMem = XEN_GETDOMAININFO_MAX_PAGES(dominfo) * 4; It's assumed that page size is 4 KB (* 4) but this isn't correct on a IA64 system where the page size is variable. I haven't checked but I suppose this bug exists also with the virDomainGetMaxMemory and virDomainSetMaxMemory functions. Regards.

3 4

[Libvir] Bug correction in virDomainGetVcpus() function
by Philippe Berthault 12 Oct '06

12 Oct '06

In the virXen_getvcpusinfo() function of xen_internal.c source file, the vcpu number stored in the virVcpuInfo structure is the xen domain id instead of the vcpu id. Here the patch of the correction. --- libvirt-0.1.7/src/xen_internal.c 2006-09-29 10:18:17.000000000 +0200 +++ libvirt-0.1.8/src/xen_internal.c 2006-10-12 11:29:40.000000000 +0200 @@ -1012,7 +1012,7 @@ ret = xenHypervisorDoV2Dom(handle, &op); if (ret < 0) return(-1); - ipt->number = id; + ipt->number = vcpu; if (op.u.getvcpuinfo.online) { if (op.u.getvcpuinfo.running) ipt->state = VIR_VCPU_RUNNING; if (op.u.getvcpuinfo.blocked) ipt->state = VIR_VCPU_BLOCKED; @@ -1054,7 +1054,7 @@ ret = xenHypervisorDoV1Op(handle, &op); if (ret < 0) return(-1); - ipt->number = id; + ipt->number = vcpu; if (op.u.getvcpuinfo.online) { if (op.u.getvcpuinfo.running) ipt->state = VIR_VCPU_RUNNING; if (op.u.getvcpuinfo.blocked) ipt->state = VIR_VCPU_BLOCKED; @@ -1078,7 +1078,7 @@ ret = xenHypervisorDoV0Op(handle, &op); if (ret < 0) return(-1); - ipt->number = id; + ipt->number = vcpu; if (op.u.getvcpuinfo.online) { if (op.u.getvcpuinfo.running) ipt->state = VIR_VCPU_RUNNING; if (op.u.getvcpuinfo.blocked) ipt->state = VIR_VCPU_BLOCKED;

2 1

[Libvir] [PATCH] libvirt incorrectly reports crashed domains as shutoff
by Peter Vetere 11 Oct '06

11 Oct '06

Hi, I've noticed that libvirt seems to report crashed domains as shutoff. Here's an example: [root@XXXXX ~]# virsh list Id Name State ---------------------------------- 0 Domain-0 running 27 test03 blocked 34 test01 shut off 36 onetwentyeight blocked [root@XXXXX ~]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 356 1 r----- 3655.4 onetwentyeight 36 128 1 -b---- 16.7 test01 34 256 1 ----c- 7.4 test03 27 256 1 -b---- 231.7 The reason is because xen_internal.c does not interpret the additional shutdown flags when it checks the domain's state. Attached is a patch which correctly checks these flags and reports the crashed state. I wasn't sure of the best way to react to the other shutdown flags, so I just defaulted to "SHUTOFF" for everything else. Pete

3 2

[Libvir] Supporting new Xen 3.0.3 blktap backend for file devices
by Daniel P. Berrange 06 Oct '06

06 Oct '06

When defining a guest's block device in the libvirt XML we currently allow the dev to be backed by either a file or block device in the host system. This is done by specifying the 'type' attribute when defing the block device XML. eg <disk type='file'> Or <disk type='block'> This is all fine & dandy for Xen 3.0.2, but in 3.0.3 we now have a choice of drivers for the 'file' backed block devices. We can either use the traditional loopback mounted system, or the new blktap system. To complicate things further still, blktap itself has man different drivers - one uses a raw file with Async-IO, another uses the QCow sparse format with AIO, and all sort of other possibilities are available... This means the easy option of just making all file devices use blktap in 3.0.3 is not practical. This in turns means we need to come up with a way to express the new driver methods in libvirt XML. There are a few options I can think of : - Allow more values in the 'type' attribute, eg file, block, blktap:aio, blktap:qcow, etc. This feels wrong because the blktap:* entries are really still 'file' types. - Introduce a new attribute 'driver' where you can specify 'loop', 'blktap:aio', 'blktap:qcow', etc - Introduce a new element 'driver' where you can specify the same <disk type="file"> <driver type='blktap:aio'/> </disk> - Same as above, but normalize the driver type further <disk type="file"> <driver type='blktap' backend='aio' /> </disk> My preference is probably option 3 or 4. 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 7

Re: [Libvir] Xen Routed
by Daniel P. Berrange 04 Oct '06

04 Oct '06

On Wed, Oct 04, 2006 at 08:09:27AM -0600, Nick Devito wrote: > On Wed, 2006-10-04 at 14:06 +0100, Daniel P. Berrange wrote: > > On Tue, Oct 03, 2006 at 07:15:23PM -0700, Sargun Dhillon wrote: > > > Does the XML file format support routed? > > > If so, what would the <interface> clause look like? > > > > I'm not familiar with the way routed networking is setup with Xen. If you > > can provide the example VIF device config params from /etc/xen/<some guest> > > which are needed for routing I'll check if they map through to libvirt > > XML format in neccessary manner. > > > Xen routed requires the ip= configuration variable, and, I think thats > it. I don't see any reason why it shouldn't work correctly. Ok, looking at the XML parsing routines we don't currently support the 'ip' property. Fortunately, it looks as if one of Michel Ponceau's patches from a thread last week ought to solve this problem, so we ought to be able to get this working for next release. 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 -=|

1 0

[Libvir] Xen Routed
by Sargun Dhillon 04 Oct '06

04 Oct '06

Does the XML file format support routed? If so, what would the <interface> clause look like? -- Sargun Dhillon President Atarack Communications, Inc. (925)-202-9485

2 1

[Libvir] Problem with hypercall
by Jim Fehlig 02 Oct '06

02 Oct '06

Stumbled across a problem trying to list domains with libvirt-0.1.5. Using virsh I get errors such as xen81:/tests/jim # virsh list Id Name State ---------------------------------- 0 Domain-0 running libvir: Xen Daemon error : GET operation failed: No such domain 16 xm shows xen81:/tests/jim # xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 2048 4 r----- 815825.8 vm1 1 512 2 -b---- 0.3 I found that the buffer provided for XEN_V1_OP_GETDOMAININFOLIST hypercall differs slightly from the buffer in xen/dom0_ops.h. Attached is a patch against current cvs that works for me, but I'm not familiar with this part of the code so not sure if this is the proper fix. I'm using xen 3.0.2 that shipped with SLES10. Regards, Jim

3 8

[Libvir] Proposal for virtual devices described in XML
by michel.ponceau＠bull.net 02 Oct '06

02 Oct '06

Proposal modified after comments from Daniel P. Berrange: /* Create a virtual device attachment to backend */ int virDomainAttachDevice(virDomainPtr domain, char *xml); /* Destroy a virtual device attachment to backend */ int virDomainDetachDevice(virDomainPtr domain, char *xml); /* @domain: pointer to domain object * @xml: pointer to XML description of one device * Returns 0 in case of success, -1 in case of failure. */ The XML would be in same form as the part of domain description for a single device, either <disk.../disk> or <interface.../interface>. In Detach function, the device is identified by its target name for "disk", and its MAC address for "interface". When the MAC address has not been assigned by Libvirt user at device creation, it must be retrieved from Xen using virDomainGetXMLDesc function.

1 0