- Devel - libvirt List Archives

[libvirt] Error while adding volume through virsh
by varun bhatnagar 16 Aug '13

16 Aug '13

Hi, I was trying to add volume...I got one xml snippet and I modified it according to my node configuration: < volume> <name>testNode/cluster.vmdk </name> <allocation>0 </allocation> <capacity unit='G'>2<capacity> </volume> Now when I executed "virsh vol-create datastore1 /local/new_volume.xml" one error message came saying: "Error: Failed to create volume from /local/new_volume.xml" Error: internal error: Creation of raw volumes is not supported" Can anyone tell me what is going wrong here? Regards, Varun

1 0

[libvirt] [PATCH] Fix qemuProcessReadLog with non-zero offset
by Ján Tomko 15 Aug '13

15 Aug '13

This restores the error message when QMP probing is not used. https://bugzilla.redhat.com/show_bug.cgi?id=991334 --- src/qemu/qemu_process.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/src/qemu/qemu_process.c b/src/qemu/qemu_process.c index 0dccac3..31de759 100644 --- a/src/qemu/qemu_process.c +++ b/src/qemu/qemu_process.c @@ -1435,18 +1435,17 @@ qemuProcessReadLog(int fd, char *buf, int buflen, int off) ssize_t bytes; char *eol; - buf[0] = '\0'; - while (off < buflen - 1) { bytes = saferead(fd, buf + off, buflen - off - 1); if (bytes < 0) return -1; - else if (bytes == 0) - break; off += bytes; buf[off] = '\0'; + if (bytes == 0) + break; + /* Filter out debug messages from intermediate libvirt process */ while ((eol = strchr(filter_next, '\n'))) { *eol = '\0'; -- 1.8.1.5

2 2

[libvirt] [PATCH] Update polkit examples to use 'lookup' method
by Daniel P. Berrange 15 Aug '13

15 Aug '13

From: "Daniel P. Berrange" <berrange(a)redhat.com> Feedback from the polkit developers indicates that the "_detail_XXXX" attributes are a private implementation detail. Our examples should be recommending use of the "action.lookup('XXX')" method instead. Signed-off-by: Daniel P. Berrange <berrange(a)redhat.com> --- docs/aclpolkit.html.in | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/docs/aclpolkit.html.in b/docs/aclpolkit.html.in index 3f0689e..1a09139 100644 --- a/docs/aclpolkit.html.in +++ b/docs/aclpolkit.html.in @@ -344,10 +344,8 @@ dealing with local clients connected via the UNIX socket). On the <code>action</code> object, the permission name is accessible via the <code>id</code> attribute, while the - object identifying attributes are exposed via a set of - attributes with the naming convention <code>_detail_[attrname]</code>. - For example, the 'domain_name' attribute would be exposed via - a property <code>_detail_domain_name</code>. + object identifying attributes are exposed via the + <code>lookup</code> method. </p> <h3><a name="exconnect">Example: restricting ability to connect to drivers</a></h3> @@ -359,7 +357,7 @@ use the <code>QEMU</code> driver and not the Xen or LXC drivers which are also available in libvirtd. To achieve this we need to write a rule which checks - whether the <code>_detail_connect_driver</code> attribute + whether the <code>connect_driver</code> attribute is <code>QEMU</code>, and match on an action name of <code>org.libvirt.api.connect.getattr</code>. Using the javascript rules format, this ends up written as @@ -369,7 +367,7 @@ polkit.addRule(function(action, subject) { if (action.id == "org.libvirt.api.connect.getattr" && subject.user == "berrange") { - if (action._detail_connect_driver == 'QEMU') { + if (action.lookup("connect_driver") == 'QEMU') { return polkit.Result.YES; } else { return polkit.Result.NO; @@ -386,8 +384,8 @@ polkit.addRule(function(action, subject) { full read-write mode. The goal is to only allow them to see the domain called <code>demo</code> on the LXC driver. To achieve this we need to write a rule which checks - whether the <code>_detail_connect_driver</code> attribute - is <code>LXC</code> and the <code>_detail_domain_name</code> + whether the <code>connect_driver</code> attribute + is <code>LXC</code> and the <code>domain_name</code> attribute is <code>demo</code>, and match on a action name of <code>org.libvirt.api.domain.getattr</code>. Using the javascript rules format, this ends up written as @@ -397,8 +395,8 @@ polkit.addRule(function(action, subject) { polkit.addRule(function(action, subject) { if (action.id == "org.libvirt.api.domain.getattr" && subject.user == "berrange") { - if (action._detail_connect_driver == 'LXC' && - action._detail_domain_name == 'demo') { + if (action.lookup("connect_driver") == 'LXC' && + action.lookup("domain_name") == 'demo') { return polkit.Result.YES; } else { return polkit.Result.NO; -- 1.8.1.4

2 1

[libvirt] Refactored previous patch into 5 patches
by Dan Walsh 15 Aug '13

15 Aug '13

[sandbox PATCH 1/5] Add virt-sandbox -s inherit, to execute the [sandbox PATCH 2/5] Unit files only exist in Systemd Containers. [sandbox PATCH 3/5] -S is not supported by virt-sandbox [sandbox PATCH 4/5] Fix SEE ALSO lines to be multi-line [sandbox PATCH 5/5] virt-sandbox needs to mention LIBVIRT_DEFAULT_URI

2 10

[libvirt] Updated patch for virt-sandbox -s inherit
by Dan Walsh 15 Aug '13

15 Aug '13

> -s static,label=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 Well running "virt-sandbox -s inherit" would run as unconfined_t for most users. I the future we need to add a check to libvirt to ask SELinux if it is ok for a user to transiton to the label, rather then just to do it. Imagine a confined admin which is allowed to generate containers, he should only be allowed to generate containers with processes labels that he can transition into, not that libvirt can transition into. [sandbox PATCH 1/2] Add virt-sandbox -s inherit, to execute the [sandbox PATCH 2/2] Unit files only exist in Systemd Containers.

3 6

[libvirt] [PATCH] modify the subtitle of usb node
by Xuesong Zhang 15 Aug '13

15 Aug '13

--- docs/formatnode.html.in | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/formatnode.html.in b/docs/formatnode.html.in index 5f57a5a..b424c96 100644 --- a/docs/formatnode.html.in +++ b/docs/formatnode.html.in @@ -136,11 +136,11 @@ <dl> <dt><code>number</code></dt> <dd>The device number.</dd> - <dt><code>number</code></dt> + <dt><code>class</code></dt> <dd>The device class.</dd> - <dt><code>number</code></dt> + <dt><code>subclass</code></dt> <dd>The device subclass.</dd> - <dt><code>number</code></dt> + <dt><code>protocol</code></dt> <dd>The device protocol.</dd> <dt><code>description</code></dt> <dd>If present, a description of the device.</dd> -- 1.7.11.7

2 1

[libvirt] [test-API][PATCH] Add display of cases result to log.xml
by Hongming Zhang 15 Aug '13

15 Aug '13

The original log.xml only display the testrun result, the patch add display of case result to log.xml. modified: src/generator.py -Perserver case result list and pass it to log_generator class. modified: src/log.xsl -Read from xml and display case result modified: src/log_generator.py -Create case result xml and add it to log.xml --- src/generator.py | 5 +++-- src/log.xsl | 23 ++++++++++++++++++++--- src/log_generator.py | 16 ++++++++++++++-- 3 files changed, 37 insertions(+), 7 deletions(-) diff --git a/src/generator.py b/src/generator.py index 0cdc9de..208fa7b 100644 --- a/src/generator.py +++ b/src/generator.py @@ -87,7 +87,6 @@ class FuncGen(object): env_logger = envlog.env_log() casenumber = len(self.case_name_list) start_time = time.strftime("%Y-%m-%d %H:%M:%S") - env_logger.info("Checking Testing Environment... ") envck = env_inspect.EnvInspect(self.env, env_logger) @@ -103,6 +102,7 @@ class FuncGen(object): # retflag: [pass, fail, skip] retflag = [0, 0, 0] + case_retlist = [] for i in range(casenumber): clean_flag = False @@ -165,7 +165,7 @@ class FuncGen(object): retflag[2] += 1 self.fmt.print_end(mod_case, ret, env_logger) - + case_retlist.append(ret) # close hypervisor connection envck.close_hypervisor_connection() end_time = time.strftime("%Y-%m-%d %H:%M:%S") @@ -179,6 +179,7 @@ class FuncGen(object): self.log_xml_parser.add_test_summary(self.testrunid, self.testid, result, + case_retlist, start_time, end_time, self.logfile) diff --git a/src/log.xsl b/src/log.xsl index 577a0a5..0ca6afe 100644 --- a/src/log.xsl +++ b/src/log.xsl @@ -119,9 +119,10 @@ <tr> <th width="5%">No.</th> <th width="5%">Result</th> - <th width="12%">Start</th> - <th width="12%">End</th> - <th width="66%">Test Procedure</th> + <th width="10%">Start</th> + <th width="10%">End</th> + <th width="65%">Test Procedure</th> + <th width="5%">Case Result</th> </tr> </thead> <tbody> @@ -164,6 +165,22 @@ </xsl:for-each> </table> </td> + <td> + <table class="pro" cellspacing="1" cellspan="0" > + <xsl:for-each select="caseresult/case"> + <tr> + <td> + <xsl:if test="self::node()[text()='FAIL']"> + <tr class="fail"><xsl:value-of select="current()"/></tr> + </xsl:if> + <xsl:if test="self::node()[text()='PASS']"> + <tr class="pass"><xsl:value-of select="current()"/></tr> + </xsl:if> + </td> + </tr> + </xsl:for-each> + </table> + </td> </tr> </xsl:for-each> </tbody> diff --git a/src/log_generator.py b/src/log_generator.py index be483d6..de18654 100644 --- a/src/log_generator.py +++ b/src/log_generator.py @@ -93,7 +93,7 @@ class LogGenerator(object): self. __write_to_file(xmldoc, self.logxml) - def add_test_summary(self, testrunid, testid, result, + def add_test_summary(self, testrunid, testid, result, case_retlist, start_time, end_time, path): """ add a test summary xml block into log xml file """ xmldoc = minidom.parse(self.logxml) @@ -101,6 +101,8 @@ class LogGenerator(object): resulttext = self.doc.createTextNode(result) testresult.appendChild(resulttext) + caseresult = self.doc.createElement('caseresult') + teststarttime = self.doc.createElement('start_time') starttimetext = self.doc.createTextNode(start_time) teststarttime.appendChild(starttimetext) @@ -126,10 +128,20 @@ class LogGenerator(object): test.childNodes.insert(0, testendtime) test.childNodes.insert(0, teststarttime) test.childNodes.insert(0, testresult) + test.childNodes.insert(0, caseresult) + for ret in reversed(case_retlist): + retstr = '' + if ret == 0: + retstr = 'PASS' + else: + retstr = 'FAIL' + itemresult = self.doc.createElement('case') + caseresulttext = self.doc.createTextNode(retstr) + itemresult.appendChild(caseresulttext) + caseresult.childNodes.insert(0,itemresult) self. __write_to_file(xmldoc, self.logxml) - def add_testrun_summary(self, testrunid, passnum, failnum, totalnum, start_time, end_time): """ add a testrun summary xml block into log xml file """ -- 1.7.1

4 6

[libvirt] Please help confirm this upsream issue
by Zhenfeng Wang 15 Aug '13

15 Aug '13

Hi I just try to verify the bug 828546 with the latest libvirt version on rhel7, and found an issue that the on_crash element on guest's xml didn't support the "rename-restart" events on the upsteam. I discussed this issue with eric before, he said that this feature was implemented by fujitsu first, he didn't backported this and he just backported what upstream does, also he was not sure if Fujitsu implemented the "rename-restart" events either, so can you help me confirm that should we support the "rename-restart" events on the upstream? thanks

3 4

[libvirt] [PATCH v4 0/2] libxl: implement some chuncks of the NUMA interface
by Dario Faggioli 15 Aug '13

15 Aug '13

Hi and sorry for being so late at this. :-( This is the leftover of my NUMA series for the libxl driver. Basically, all the patches have been checked in but the one actually building the <topology> capability, which is patch 2/2 of this series. I think I addressed all Daniel's comments about VIR_*ALLOC* and error handling. Patch 1/2 is a bugfix to how the range of available NUMA nodes was being handled in a previous patch (more in the changelog). --- Dario Faggioli (2): libxl: fix node ranges in libxlNodeGetCellsFreeMemory() libxl: implement NUMA capabilities reporting src/libxl/libxl_conf.c | 140 ++++++++++++++++++++++++++++++++++++++++++++++ src/libxl/libxl_driver.c | 14 ++--- 2 files changed, 146 insertions(+), 8 deletions(-) -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

2 5

[libvirt] Xen Developers Summit 2013, CfP (24-25 October, Edinburgh)
by Dario Faggioli 15 Aug '13

15 Aug '13

== Call for Proposals == We are pleased to announce that the Call for Proposals (CFP) for the first Xen Project Developer Summit is now open! The event is being held in Edinburgh, UK from October 24-25. All submissions need to be submitted by 11:55pm (BST) on August 30th. The Xen Project Developer Summit will feature content for developers, integrators and power users of the Xen Project. We are looking for presentations related to development, such as development proposals, updates on feature development, project updates, etc. We are also looking for insight into best practices in deploying Xen at scale, case studies by Xen users and other topics that large scale users of Xen care about. == Submit a Speaking Proposal == by visiting this URL: http://events.linuxfoundation.org//events/xen-project-developer-summit/prog… == Proposals == The program committee will be looking for presentations and workshops related to working with the Xen Project. Topics related to Xen Development include development proposals, updates on feature development, project updates, discussions and proposals on the architectural evolution of Xen, best practices of Xen development, studies and benchmarks of system characteristics such as performance/scalability/security/ease of use/power consumption, lessons learned, interfacing with other open source projects, making Xen easier to consume by distros, etc. We are also interested in proposals that provide insight into best practices in deploying Xen, case studies by Xen users and other topics that large users and integrators of Xen care about. This includes everything from deploying Xen or its sister projects at scale, best practices for working with Xen, case studies by users of Xen, Xen benchmarks, tips and tricks in securing Xen based clouds, topics related to managing Xen based environments, open source projects that are related to Xen and deliver benefits to Xen users, 3rd party Xen integrations, etc. As a Xen user, a proposal that catches the developers attention, is your chance to spark a debate that will influence what is developed by the Xen Project. In short, if it’s relevant to Xen development, integration and usage we are interested in what you might have to say. == Timeline and Deadlines == You can submit a proposal at any time for Xen Project Developer Summit. Please keep in mind that the deadline is August 30, 2013. == Presentation Types == Presentations should be for 25 or 50 minutes. Chose the length of your submission based on the content that you have. Note that we have been overwhelmed with talk proposals in the past and have thus asked speakers to modify talks to fit into a shorter slot. == Travel Sponsorships == Not sure if you can afford the airfare and lodging to attend the summit? Please don’t let that stop you from submitting your best proposal. We may be making a number of travel sponsorships available for speakers who have useful information to share with the Xen Project community. Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

1 0