similar to: "No module named xs" while I ran xm-test for Xen testing

Hi men, I compiled and installed Xen 3.3.0 on Fedora 8, and it worked fine. However, after installing virt-manager, it goes wrong: # xm Traceback (most recent call last): File "/usr/sbin/xm", line 8, in <module> from xen.xm import main File "//usr/lib/python/xen/xm/main.py", line 52, in <module> from xen.xm import console File

Hi, this is about iterating over any data type/object 'xs' in the for-loop constructor: for (x in xs) { ... } >From help("for"), on can read that 'xs' has to be "An expression evaluating to a vector (including a list and an expression) or to a pairlist or NULL. A factor value will be coerced to a character vector". If you have a data type/class that

Hi Rich, While I was looking at hivex today I ran coverity on it. It spotted one problem but missed a similar one nearby. The following are from Hivex.xs: (generated by generator.ml) void node_set_values (h, node, values) hive_h *h; int node; pl_set_values values = unpack_pl_set_values (ST(2)); PREINIT: int r; PPCODE: r = hivex_node_set_values (h, node,

I'm using Search::Xapian XS from Debian stable and I'm getting what appears to be an unwrapped C++ exception: terminate called after throwing an instance of 'Xapian::DatabaseModifiedError' Using `eval' from Perl5 doesn't seem effective in catching it. I'm using postlist_begin, postlist_end and ++ to iterate a PositionIterator, and reading XS/*Iterator.xs, I see the

On Mon, Mar 27, 2023 at 11:46:04AM +0000, Eric Wong wrote: > I'm using Search::Xapian XS from Debian stable and I'm getting what > appears to be an unwrapped C++ exception: > > terminate called after throwing an instance of 'Xapian::DatabaseModifiedError' > > Using `eval' from Perl5 doesn't seem effective in catching it. > > I'm using

Tristan, could you please run your xattr test against it? xs->base used to be allocated a 4K size and all the contents in the bucket are copied to the it. So in ocfs2_xattr_bucket_set_value_outside, we are safe to use xs->base + offset. Now we use ocfs2_xattr_bucket to abstract xattr bucket and xs->base is initialized to the start of the bu_bhs[0]. So xs->base + offset will overflow

I have a new APC Back-UPS XS 1200. It is detected properly by the Linux kernel (2.6.16): # dmesg usb 5-3.4: new low speed USB device using ehci_hcd and address 9 usb 5-3.4: new device found, idVendor=051d, idProduct=0002 usb 5-3.4: new device strings: Mfr=3, Product=1, SerialNumber=2 usb 5-3.4: Product: Back-UPS XS 1200 FW:8.g1 .D USB FW:g1 usb 5-3.4: Manufacturer: American Power Conversion usb

Hello All I just discoverd NUT and I'm lovin' it. I was very successful getting nut to monitor a CyberPower UPS along with having a Linux slave for a friend of mine. I've come to a snag on my personal system though. I currently have two Back-UPS XS 1200 APC UPSs, and I'm seeing notifications of low battery on both units. Now, both units are not showing 'low battery' on

hello, in trying to build xen-unstable (up to changeset 9238) under x86_64 sles10 beta 7, gcc-4.1.0-3, python-2.4.2-9, i''m getting the following error during the build: building ''xs'' extension creating build/temp.linux-x86_64-2.4/xen/lowlevel/xs gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -g -O2 -f omit-frame-pointer

Hi Chad, Thanks for your report. Everything seems fine, apart from the battery.date (2052/00/36), which vaguely recall me something... I've added this info to the Testing and trunk driver.list Arnaud -- Please note my new email address: arnaudquette at eaton.com -- Linux / Unix Expert R&D - MGE Office Protection Systems - http://www.mgeops.com Network UPS Tools (NUT) Project Leader -

HI: when I run "sudo xm list", I got following error messages Traceback (most recent call last): File "/usr/sbin/xm", line 5, in <module> from xen.xm import main File "/usr/lib/python2.6/dist-packages/xen/xm/main.py", line 52, in <module> from xen.xm import console File "/usr/lib/python2.6/dist-packages/xen/xm/console.py",

The new merged qemu no longer has the ability to spawn a vnc viewer process in the bowels of the xend/qemu stack. In this patch we provide support for this use case in a different manner - one more akin to the mechanism used for `xm console'' and `xm create -c''. We introduce new xm options: xm create --vncviewer [--vncviewer-autopass] xm vncviewer [--vncviewer-autopass]

Greetings, I'm new to the list, and didn't find an archive, so please bear with me: I have a new APC Back-UPS XS 1200 model BX1200. The USB cable attaches with an RJ-45 on the UPS side. I'm using the hidups driver, and the default log format gives me lines like this: 20060317 041353 100 NA 0 [OL] NA NA 20060317 041454 100 NA 0 [OL] NA NA Can I do better than that with (a

Where can I download the file xs-tools.iso (to install on VM windows)... I''ve searched but did not come with the debian7 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

Hello! I installed NUT with "apt-get install nut" (v2.0.2-1). I hooked the new APC Back-UPS XS BX1500 unit to the Debian (Kernel 2.6.12-1-K7) computer with the provided USB cable (has an ethernet jack on the end connected to UPS) and ran dmesg command: usb 1-2: new low speed USB device using uhci_hcd and address 2 usb 1-2: device descriptor read/64, error -110 usbcore: registered new

On May 11, 2017, at 1:51 PM, Jesse Molina <jmolina at swoncology.net> wrote: > > I suspect this is a driver problem because while NUT claims the battery isn't plugged in, it's giving me battery runtime/charge info. Both can't be valid at the same time. > > I am at a remote location from the computer and UPS, so I can't physically go over and check. I asked a

I have a new-ish APC Back-UPS XS 1500G connected via USB. It's giving me a "ups.alarm: No battery installed!" error. I also installed and configured apcupsd to give that a try and it's giving me the same error. I suspect this is a driver problem because while NUT claims the battery isn't plugged in, it's giving me battery runtime/charge info. Both can't be valid

I''ve noticed that after I create 83 domains on a server, ''xm create'' will create domains without a valid console tty value. This corresponds approx. to 256 file descriptors. I''ve bumped up the limits for all daemon processes to 1500 file descriptors, so I''m really puzzled where xen is hitting a resource limit. Where is the code that creates the xs

I''ve noticed that after I create 83 domains on a server, ''xm create'' will create domains without a valid console tty value. This corresponds approx. to 256 file descriptors. I''ve bumped up the limits for all daemon processes to 1500 file descriptors, so I''m really puzzled where xen is hitting a resource limit. Where is the code that creates the xs

Seems currently xenstore transaction provides confusing message in different places: a) comment of xs_transaction_start says "You can only have one transaction at any time." However do_transaction_start allows up to 10 transactions created, as long as all other existing transaction channel is idle at the time (conn->transaction == NULL) b) when multiple transactions can be