similar to: Proper XML for compareCPU method

Hi, Is there a rule or guideline about what Python versions must be supported for scripts in the LLVM tree? I am working on some patches to some scripts in LLVM to use features in Python 2.7, so that these scripts can run under Python 2.7 and Python 3.x Is that OK? For example, here is a patch to use print as a function, so that the scripts can work in Python 2.7 and Python 3.x -- Craig

So, I just tried, and basically it's difficult to make progress due to the print statements (since they induce an immediate syntax error). Since 2.4 doesn't support `from __future__ import print_function`, the only alternative I guess is shimming in a print function. This is a maintenance effort that I don't want to do right now (and, TBQH, I feel that the proper maintainer should be

Dear R users I'm having problems in putting special characters (like 佱, 併, 佺 ) in my plots, as much in titles, as in axis names, as in legend...when I save them as a pdf document. They don't appear... I don't know if it is because I'm using a linux platform... The script is the following: library(grDevices) jpeg(file="Fronteira/FronteiraNova.jpeg",

Hi Sean, If there was a concrete need to move to a newer Python version in order to make lit Python 3 compatible, I would view that as a good reason to move forward. I have little experience writing Python 2 & 3 compatible code, so I'd need to see the patch to make lit Python 3 compatible before I could comment more. - Daniel On Tue, Dec 4, 2012 at 9:15 AM, Sean Silva <silvas at

Hi everyone. I rebuild a plugin, based on zlib plugin. The changes between this plugin and zlib, is the zlib stuffs is replaced by open, read, lseek, close. With "plain-text" files, its works ok. So, my file is encrypt, and the result from decrypt file is different from fread. Like zlib, i read from fread the size variable, but the value added in seek_offset and pos is the result from

> several people already asked what are the concrete benefits of breaking support for end-of-life python versions? Generally I think the only compelling argument is "for a given level of maintenance effort, you either sacrifice support for old-dead versions, or new versions", and obviously new versions should be preferred. The question is how much does it cost to interoperate. On

Hello everybody, I am a new user discovering libvirt with KVM software. During my first VM creation, I saw an issue with virsh that I can't understand. I wanted to emulate another CPU than the classical qemu32 using virsh. So I used the virsh capabilites command to detect how is detected my CPU host which is an Intel Xeon E5410 and my problem is that this CPU is detected only with the

> If there was a concrete need to move to a newer Python version in order to > make lit Python 3 compatible, I would view that as a good reason to move > forward. The concrete need is that users on platforms which ship with Python 3 by default have to put in a workaround (install python2 and patch their $PATH) just to run the test suite. Off the top of my head I know this includes Ubuntu

On Wed, Dec 05, 2018 at 09:44:17PM +0530, ROHIT SINGH wrote: >Hi Martin, > >Could you please help me with below issue, I am not sure what’s wrong here. >Please find below code and error snippet. > >Thanks for help. > >Code Snippet: - > >from __future__ import print_function >import sys >import libvirt >SASL_USER = <username> >SASL_PASS =

Hi Martin, Could you please help me with below issue, I am not sure what’s wrong here. Please find below code and error snippet. Thanks for help. Code Snippet: - from __future__ import print_function import sys import libvirt SASL_USER = <username> SASL_PASS = <password> def request_cred(credentials, user_data): for credential in credentials: if credential[0] ==

Hi, I've been working on trying to figure out why my virtual machine keeps crashing when I don't believe I have a hardware problem, and I believe I might know why. As I'm relatively new to this, I believe I may have misconfigured the XML file to try and maximize the CPU features that are available to the guest from the host. I have an Intel Xeon E3-1240 3.3Ghz quad-core. How can I

On Tue, Dec 4, 2012, at 03:23 AM, Sean Silva wrote: > > several people already asked what are the concrete benefits of breaking support for end-of-life python versions? > > Generally I think the only compelling argument is "for a given level > of maintenance effort, you either sacrifice support for old-dead > versions, or new versions", and obviously new versions

Thanks Martin, It’s working now. Could you please help me with role of xml in libvirt api and what if I don’t want use of xml in my code. Please let me know. Thanks for help!! Regards Rohit Singh On Thu, 6 Dec 2018 at 11:24 PM, ROHIT SINGH <rohit.singh0908@gmail.com> wrote: > Thanks Martin for help. I will give it a shot. > > Regards > Rohit Singh > > On Thu, 6 Dec 2018

Dear R gurus and users, in order to provide the local users of R with a printed copy of the ample documentation provided with R and the optional packages installed, I have introduced a minor change to the R/doc/manual/Makefile. Using GNU find, GNU sed, and features of GNU make, the LaTeX documentation found in the subdiretories of .../R/library/ is copied to .../R/doc/manual, and appropriate

Thanks Martin for help. I will give it a shot. Regards Rohit Singh On Thu, 6 Dec 2018 at 2:55 PM, Martin Kletzander <mkletzan@redhat.com> wrote: > On Wed, Dec 05, 2018 at 09:44:17PM +0530, ROHIT SINGH wrote: > >Hi Martin, > > > >Could you please help me with below issue, I am not sure what’s wrong > here. > >Please find below code and error snippet. > >

On Wed, Dec 12, 2018 at 03:03:41PM +0530, ROHIT SINGH wrote: >Thanks Martin, It’s working now. >Could you please help me with role of xml in libvirt api and what if I >don’t want use of xml in my code. >Please let me know. > Libvirt uses XML for most of the APIs. Depends what you need to do you can transform it with xmltodict or use some higher level API. I'm not sure I can

On aarch64 with -M virt, the default CPU model is cortex-a15 (a 32 bit CPU). This is IMHO a stupid default, but there we are. Therefore most users will need to pass the `-cpu cortex-a53' or `-cpu cortex-a57' flag to qemu, depending on a complex formula of their host CPU and if they are using TCG or not. However I cannot work out how to pass this through libvirt. The obvious one would

Hi Andrea Thanks for the reply. Below is some more information regarding the same.. uname -a Linux t1040rdb 3.12.37-rt51-QorIQ-SDK-V1.8+gf488de6 #2 SMP Mon Jul 20 14:43:02 IST 2015 ppc GNU/Linux libvirtd --version libvirtd (libvirt) 1.2.13 cat /usr/share/libvirt/cpu_map.xml </arch> <arch name='ppc64'> <model name='POWERPC_e5500'> <vendor

Hi, all. I posted this message to libvir-list last night, but just realized that was geared toward development rather than support. Apologies to those who are subscribed to both for the dupe. I'm having a weird problem where libvirt/qemu/kvm won't let me use the model processor I have defined in my domain's config file. Instead, I get the error message in libvirtd.log that:

On Mon, Mar 03, 2014 at 02:15:43PM +0000, Struan Bartlett wrote: > > > On 03/03/2014 13:42, Martin Kletzander wrote: > > On Mon, Mar 03, 2014 at 11:15:51AM +0000, Struan Bartlett wrote: > >> On 03/03/2014 10:55, Martin Kletzander wrote: > >>> On Mon, Mar 03, 2014 at 10:47:03AM +0000, Struan Bartlett wrote: > >>>> On 03/03/2014 10:44, Martin