similar to: Bug#402081: xen-utils-3.0.3-1: xen-utils missing xfrd

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: normal Since this package installs python modules in /usr/lib/xen-3.0.3-1/lib/python/, and uses them directly from there, not following the python policy, once xend has started up, lots of .pyc files are created there, which will not be removed if the package is purged. These pyc files may also cause problem for future python upgrades, I

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-4 Severity: normal Rebooting from inside domU hangs in initrd: Begin: Waiting for root file system... ... Root file system is not available because underlying DRBD device got deactivated during reboot: $ cat /proc/drbd version: 8.0.13 (api:86/proto:86) GIT-hash: ee3ad77563d2e87171a3da17cc002ddfd1677dbe build by phil at fat-tyre, 2008-08-04

Source: xen Version: 4.0.1~rc3-1 Severity: serious From my pbuilder build log: ... fakeroot debian/rules clean if [ -f debian/control ] && [ -f debian/control.md5sum ] && [ -f debian/rules.gen ]; then \ if md5sum debian/changelog debian/bin/gencontrol.py debian/templates/control.hypervisor.in debian/templates/control.main.in debian/templates/control.source.in

Hi all, I''ve been trying to figure out a way to trigger the balloon driver for a domain from within xfrd (specifically, libxc). So far, it doesn''t look like there''s a straightforward way. Is this even possible given the current structure of the system? Thanks, -A. -- Aaron Marks ajmarks@cis.upenn.edu Distributed Systems Lab University of Pennsylvania

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: wishlist Xen can run 32bit domU clients on 64bit (amd64) dom0. Unfortunately only amd64 linux-image-xen packages are available on arch amd64. Please provide 686 packages as well (if possible). This would enable the installation of 32bit clients without the need to manually compile a kernel. Feel free to reassign this bug to the correct

Hi, I had a problem trying to migrate domains, in trying to locate it I noticed that saving domains doesn''t work either, which I believe explains why the receiving xfrd doesn''t actually receive anything. So here it goes... xenone:/tmp# xm list Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 123 0 r---- 900.6 sky 9

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-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.0.3-1 Version: 3.0.3-0-2 Severity: normal It seems that the blktap module is not included. As loopback images are deprecated in Xen, theis module is vital for using file backed VBDs in Xen. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable'), (200, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-3 Severity: grave Tags: security Justification: user security hole Xen versions 3.x, and 3.1 contain a tool for processing Xen trace buffer information. This tool uses the static file /tmp/xenq-shm insecurely allowing a local user to truncate any local file when xenbaked or xenmon.py are invoked by root. Sample session: # setup. skx

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

Hi, I'm new to NSD and would really appreciate if someone can point me to the right direction. I have like 8 NSD servers (secondary) serving around 30,000 zones. Zone updates are transferred from the primary DNS servers by AXFR/IXFR. The 8 NSD servers do not save the zones file on disk but are only held in memory. Therefore after NSD service is restarted zone transfer requests are being

Hi all, I want to do live migration of domains using DRBD block devices for synchronisation between the two Xen hosts with Xen 2.0.7. I''ve written a script ( block-drbd ) which binds / unbinds DRBD devices for specific domains (with DRBD, only one host can write on a drbd device at the same time). This script sets the current host as master (bind) or secondary (unbind) in a DRBD

Processing commands for control at bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.5 > close 402081 Bug#402081: xen-utils-3.0.3-1: xen-utils missing xfrd 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to "Andrew D. Clark" <andrew.clark at ucsb.edu> > End of

Hi, I am trying to migrate a domain (testDomain) from node1 to node2. Here is some information about the problem: node1#: xm migrate testDomain node2 After the command is executed, there is some communication between the node1 and node2 Xen hosts. xfrd daemon (which is forked by xend) is primarily responsible for vm migration and there is error in its log (/var/log/xfrd.log) The exact

Hi list, We are observing strange behavior of nsd v3.2.9 acting as slave DNS server. The environment is set up as follows: 0. We are using 172.16.0.0/16 subnet; 1. Primary Master server at 172.16.100.114; 2. Slave server at 172.16.100.115. The config file is in /etc/nsd-dns-slave.conf; 3. There may be also other Master servers im the given subnet. Now I want to permit DNS NOTIFY messages to

Package: xen-utils-common Version: 3.0.3-0-2 Severity: important I have installed all the packages I can think of to get Xen going and it still fails with the following : /var/log/xen/xend-debug.log: Exception starting xend: (111, 'Connection refused') er.py", line 463, in process_request_thread self.finish_request(request, client_address) File "SocketServer.py",

Package: xen-hypervisor-3.0.3-1-i386 Version: 3.0.3-0-2 Severity: important When I try to start a domU with more than 6 vdb it crash. The first time the vm does not launch and aparently wait for the loop device creation (some scripts/block add, udev --daemon and sleep 1 process running). And nothing happen until I Ctrl+C the xm create. My loop module is loaded with 64 loops. After this first

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 26/04/15 10:45, Bastian Blank wrote: > Hi Daniel > > On Sun, Apr 26, 2015 at 10:35:01AM +0200, Daniel Pocock wrote: >> This should probably be released in an update to wheezy. > > Well, if you can pursuade the release team. We have grub2 for Xen > in Jessie now and it can be used on Wheezy as well. > Can you be

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: normal # xentrace /usr/lib/xen-3.0.3-1/bin/xentrace: error while loading shared libraries: libxenctrl.so: cannot open shared object file: No such file or directory It seems that we need a /etc/ld.so.conf.d/xen file that includes directory /usr/lib/xen-3.0.3-1/lib . -- System Information: Debian Release: 4.0 APT prefers testing APT