similar to: Bug#532603: xen-utils-3.2-1: incorrectly calls network-script

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-common Version: 3.4.2-4 Severity: normal Tags: patch xen-version does not include the "extra" component, only major.minor. This keeps makes /etc/init.d/xend bail out with xen 3.2-1 from lenny. patch attached. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (600, 'testing'), (600, 'stable'), (500,

Hello everyone, Recently I have been testing my customized Xen 4.2 networking setup. It works pretty good and I would like to share it with anyone who is interested. The relevant files can be found here: https://github.com/slacks42/xenscripts Benefit: configure the Xen related networking devices with one understandable bash script. Please note that this is all still work in progress. For

Package: xen-utils-common Version: 4.1.2-1 Severity: grave Justification: renders package unusable (Grave because dash is the default /bin/sh) With dash 0.5.5.1-7.4 as /bin/sh, /usr/sbin/xm enters an infinite loop of reexcuting itself. When run with bash, it works correctly. I traced that to /usr/lib/xen-common/bin/xen-toolstack; here's the diff between "/bin/sh -x /usr/sbin/xm"

Package: xen-utils-common Version: 3.0+hg11624-2 Severity: normal I'm running etch with xen 3.0.3 with a hand-compiled 2.6.18.1 kernel. The /etc/xen/scripts/network-bridge fails to run, because it (effectively) does this: set -e modprobe netloop > /dev/null 2>&1 As I do not have a netloop module (where is it supposed to come from ? The 2.6.18.1 xen-patched kernel doesn't

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-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 /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 Under this Xen setup, (Linux) HVM guests fail to have network active when running with *routed* networking, as some hosting providers require (in my case, OVH). In this scenario: * the host is a described below * the guest runs as HVM. * the guest runs exclusively with ioemu; virtual network drivers are not available (vanilla lenny

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Please can you add python-xml as a dependancy for xen-utils-3.2-1 on lenny and above. Without python-xml a dependancy for "xm new" isn't satified. Thanks, Matthew Millar -- System Information: Debian Release: 5.0.7 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: grave Justification: renders package unusable qemu-dm sends out this: - supported machines are: pc Standard PC (default) isapc ISA-only PC - instead of: - Supported machines are: xenfv Xen Fully-virtualized PC (default) xenpv Xen Para-virtualized PC - this renders any tries to use HVM fail. -- System Information:

A huge thank you to mario from the ''openvswitch on Xen 4.1'' post. I was having some trouble with using openvswitch with Xen 4.1 (I''m currently migrating from 4.0.1) until I saw his post and noticed that the xl.conf needed the full path to the networking script. Made this change and all is good now. Thank you. I would like to contribute what I have for using

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Once installed, the python library of Xen are not in the python search path. Concequently, it's impossible to import anything from the xen-utils in another application. The only way to fix it is to do: cd /usr/lib/python2.5/site-packages ln -s /usr/lib/xen-3.2-1/lib/python/xen xen xen-utils-3.2-1 should in fact use the folder

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal When my domU uses this configuration: --- root = '/dev/sda2 ro' disk = [ 'phy:/dev/volume0/lenny.vandervlis.nl-swap,sda1,w', 'phy:/dev/volume0/lenny.vandervlis.nl-disk,sda2,w', ] --- Pygrub gives the error "Error: Boot loader didn't return

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: grave I tried to start an HVM guest to setup Windows 2003 64 bits entreprise R2, and I spent a long time figuring out that there is no /usr/lib/xen folder by default, and this is where Xen is searching for it's file when using HVM, VNC and all. Doing a simple symlink with ln -s /usr/lib/xen-3.2.1 /usr/lib/xen made it working, if it's not

Hello. I need your help, DomU xen network diconnects randomly, how do you monitoring this? When I connect to vnc server in the hosts, DomU is running, then I open the DomU, after that guest network responds. DomU Debian 6.03 over Centos 5.7 and Xen 3.03. My network configuration: eth0 Link encap:Ethernet HWaddr 68:B5:99:78:AA:6D inet addr:192.168.5.230 Bcast:192.168.5.255

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-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 The xm command has an option to define a domain in Xen: xm new vm_config_file.cfg Using default dependences it isn't working: :~# xm new oromigration-oromail.cfg Unexpected error: <type 'exceptions.ImportError'> Please report to xen-devel at lists.xensource.com Traceback (most recent call last): File

Hi, what to do with this? thanks in advance [serge@rex serge]$ wine write.exe Invoking /opt/wine/bin/wine.bin write.exe ... For language 'fr' several language ids were found: fr_FR - 040C; fr_BE - 080C; fr_CA - 0C0C; fr_CH - 100C; fr_LU - 140C; Instead of using first in the list, suggest to define your LANG environment variable like this: LANG=fr_FR Wine exited with a successful status