search for: daemos

...under a SUNOS 5.5.1 operative system. This SUN machine was the server of a number of Lynux (Mandrake) and Windows (95,98, XP) computers in a TCP/IP network with fixed IP numbers. We were oblied to change to DHCP recently. As our network has a huge number of computers I am running the smbd and nmbd daemos of the Samba with an identification in such a way that only those windows computers having the WINS protocolo with the same identification were able 'to see' this machine. Under DHCP, at least for Windows 98, there is no any configuration for this protocol in such a way that now although m...

Package: xen-utils-4.0 Version: 4.0.1-1 Severity: normal Due to license issues this version of Xen does not include the blktap2 backend (tapdisk2) and associated utilities (vhd-util, etc.). The decision was made to disable the blktap v1 kernel module (the default is now blktap2). As a result we can't use any tap devices which means worse performance than previousl. Since blktap1 was available

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal Tags: patch Hi, There is a bug xen-3-3.2.1/tools/libfsimage/reiserfs/fsys_reiserfs.c, it is using "unsigned long" which is 64 bits on amd64 arch and 32 bits on i386 arch. This makes pygrub can't work on reiserfs on amd64 arch. You can easily reproduce it. A patch is included for fixing this problem. diff

Package: xen-utils-common Version: 4.0.0-1 Severity: important If using ethernet bonding and network-bridge with xen the network-bridge scripts breaks the network. I have run through the commands manually in irder to establish the culprit. In the op_start function (Starting on line 214) everything is fine up until line 251. At this point the bridge has been created, devices renamed and the

I need to look more into it, but before I start the long and arduous "googling my life away" process, I figured someone might know the answer. I've read the man pages several times and they didn't change! :-( As normal, while looking at one thing, something else bites my butt. I tuned on the swap field in top and sort on it. Here's an edited snippet of the results. Mem:

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-4 Severity: normal Booting with pygrub doesn't work. First problem is the path to libraries (/usr/lib/python is used instead of /usr/lib/xen-3.0.3-1/lib/python): $ /usr/lib/xen-3.0.3-1/bin/pygrub Traceback (most recent call last): File "/usr/lib/xen-3.0.3-1/bin/pygrub", line 25, in ? import grub.GrubConf ImportError: No module

Package: xen-utils-3.2-1 Version: 3.2.1-2 Followup-For: Bug #477525 I have the same problem after updating from etch to lenny. (Thus updating Xen from 3.0 to 3.2) Does anyone know how to fix this? -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-xen-amd64 (SMP w/2 CPU cores) Locale:

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-4 Followup-For: Bug #485598 Please rebuild against python2.5, this will probably solve it. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.18-5-xen-amd64 (SMP w/1 CPU core) Locale: LANG=pt_BR.UTF-8,

Package: xen-utils-common Version: 3.2.0-2 Severity: normal When I was trying to migrate (xm migrate) a guest from one host to another, it simply fails. On the source host the virtual machine gets destroyed without any warning message - on the destination host I see the following error message in /var/log/xen/xend.log [2009-03-10 08:01:22 9846] ERROR (XendCheckpoint:52) read_exact: EOF trying

Package: xen-utils-common Version: 3.2.0-2 Followup-For: Bug #511579 My system is a Dell PowerEdge SC1435. As most of the servers of this category, it comes with 2 network interfaces. Both based on a Broadcom Corporation NetXtreme BCM5721 chip, set up via tg3 module. Does multiple NIC's triggers the bug? This link helped me a lot: https://systemausfall.org/wikis/howto/XenUpgrade3.2 --

Package: xen-utils-unstable Version: 3.3-unstable+hg17961-1 Severity: important if I try to start or restart xend, I get this errors: /etc/init.d/xend restart Restarting XEN control daemon: xendTraceback (most recent call last): File "/usr/lib/xen-unstable/bin/xend", line 146, in <module> sys.exit(main()) File "/usr/lib/xen-unstable/bin/xend", line 123, in main

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important /usr/lib/xen-3.2-1/bin/blktapctrl searches for tapdisk executable in /usr/bin while is in /usr/lib/xen-3.2-1/bin this makes tap:aio unusable I've linked to /usr/bin and everything went fine perhaps the idea is to patch sources to pick executable from the right directory Regards -- System Information: Debian Release: 5.0

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal *** Please type your report below this line *** When live migrating a PV guest from one Lenny dom0 to another, the migration fails with the following error: libvir: Xen Daemon error : POST operation failed: xend_post: error from xen daemon: (xend.err '/usr/lib/xen-3.2-1/bin/xc_save 28 39 0 0 1 failed') The kernel messages

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Intel processors have a bug with Vt that causes problems with Xen real-mode emulation. This renders FreeBSD (and possibly other OS'es) unbootable in Xen with HVM. Later versions of Xen 3.2 (and 3.3) emulate real-mode instructions so this problem doesn't exist. I would provide the relevant patches, but I do not have much

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: important the xen-utils packages lack xfrd, which is required for live domain migrations using xm migrate. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-686 Locale:

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: normal pygrub can't work with this package, because the fsys filesystem modules included in the source package are missing. As a workaround, I downloaded the xen-3.0 source package, went into tools/pygrub/src/, installed e2fslibs-dev and libreiserfs0.3-dev, ran "make", and copied stuff from

Package: xen-utils-common Version: 3.0.3-0-2 Severity: minor When I try to read the man page of xm, these warnings show up: Manual page xm(1) line 1/tmp/zmanA5668G:641: warning: can't find numbered character 160 /tmp/zmanA5668G:643: warning: can't find numbered character 160 /tmp/zmanA5668G:651: warning: can't find numbered character 160 /tmp/zmanA5668G:652: warning: can't find

Package: xen-utils-3.0-unstable-1 Version: 3.0-unstable+hg11561-1 Severity: grave Justification: renders package unusable with the recent unstable kernel, the evtchn device should be created with major/minor 10, 63. Instead, it's being created with 10, 201. If fixed manually, xenstored will re-create it with the wrong minor number. This causes Xen to be entirely unusable, as xenstored is

Package: xen-utils-common Version: 3.0.3-0-2 Followup-For: Bug #401249 I don't mean to "me too", but I thought I might inform that this is not a one-off occurence. Please advise how I can assist with further debugging. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to

Package: xen-utils-common Version: 3.0.3-0-2 Severity: wishlist I had an error in the disk configuration of a VM (typo in the LVM volume group name) and got this error: # xm create test.cfg Using config file "test.cfg". Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. # I would be nice to have an error message that clarifies things. -- System