similar to: Bug#681376: Xen hypervisor package not upgraded on dist-upgrade Squeeze to Wheezy

Processing commands for control at bugs.debian.org: > reopen 678923 Bug #678923 {Done: George Shuklin <george.shuklin at gmail.com>} [xcp-xapi] xcp-xapi: host-disable and host-reboot make host disable forever Bug reopened Ignoring request to alter fixed versions of bug #678923 to the same values previously set > End of message, stopping processing here. Please contact me if you need

Hi. On the release version of Debian Wheezy, I am missing symbols for left and right brackets in plotmath. Anybody see similar trouble while reviewing demo(plotmath)? This is a completely clean, fresh install. I've not installed any peculiar libraries or packages, except R, the installation of which still puzzles me. I configured a CRAN mirror for packages using squeeze-cran3 folder, and

Package: xcp-xapi Version: 1.3.2-8 Severity: important During startup /etc/init.d/xendomains script is called. That script is installed with xen-utils-common witch xcp-xapi is depends on. That script calls /usr/sbin/xen as xen list &> /dev/null This 'xen' seems to call xapi: xen list ^Z [1]+ Stopped xen list root at lab-xh3:~# ps f PID TTY STAT TIME

Subject: xen-utils-4.1: /usr/lib/xen-default missing Package: xen-utils-4.1 Version: 4.1.3-1 Severity: important Dear Maintainer, when using paravirtualization with xen and libvirt the path for pygrub is: /usr/lib/xen-default/bin/pygrub But this path is not provided with xen-utils-4.1 and will brake upgrades to wheezy. With xen-utils-4.0 and debian squeeze this path is provided with

Package: xcp-xapi Version: 1.3.2-8 Severity: minor During upgrade from 1.3.2-7 to 1.3.2-8 got follwing message on slave host (upgrade was simulatanious on slave and master): ... Setting up xcp-xapi (1.3.2-8) ... The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: INTERNAL_ERROR: [

Package: xcp-xapi Version: 1.3.2-7 Severity: normal xcp-xapi fails to eject host from pool with following error: xe pool-eject host-uuid=a6806a39-442d-f17d-b7a0-59161d18f56f WARNING: Ejecting a host from the pool will reinitialise that host's local SRs. WARNING: Any data contained with the local SRs will be lost. Type 'yes' to continue yes The server failed to handle your request,

Package: xen-hypervisor-4.1-amd64 Version: 4.1.2-2 When installing xen-linux-system on a new Dell R810 server, Wheezy, Squeeze and Ubuntu server 11.10 all boot fine when booted directly into the standard kernel, but when booting through Xen (after installing the package xen-linux-system) the boot process hangs as soon as Xen passes control to the Dom0 kernel: "Gave up waiting for root

Source: xen Version: 4.1.2-2 Severity: critical Tags: security Justification: allows PV domains to escape into the dom0 context Hi, I realize you're most likely pretty well aware of that problem already, but Debian's Xen versions are vulnerable to a PV privilege escalation [1]. The issue is tracked as CVE-2012-0217 and public as of today. Therefore I am filing this bug for coordination

Hello, in Squeeze Asterisk 1.8.23.1 is installed, in Wheezy older version 1.8.13.1~dfsg1-3+deb7u3. With version 1.8.13.1 I have some problems so I would like to install version 1.8.23.1 used in Squeeze whats running fine for me. How I can do this? thanks for help Thomas

tags 671018 +patch thanks This issue has been fixed upstream for 4.2 by using the same hotplug scripts for tap devices as for vif devices rather than using a special qemu-ifup script. I don't think this is an appropriate thing to backport to 4.1 for wheezy so therefore I think the right fix is as Pierre suggests to set the MAC address in the qemu-ifup script. In terms of a patch to the

Package: xcp-xapi Version: 1.3.2-8 Severity: important Tags: patch Found race condition (specific only to slave hosts): xcp-xapi can start earlier than xcp-networkd due lack of dependency in init.d script. Syptoms: After reboot slave's xcp does not work: xe (anything): The host failed to acquire an IP address on its management interface and therefore cannot contact the master. log:

Processing commands for control at bugs.debian.org: > close 587090 4.1.0~rc6-1 Bug #587090 [xen-utils-4.0] xen-utils-4.0: Exception starting xend ('NoneType' object has no attribute 'rfind') There is no source info for the package 'xen-utils-4.0' at version '4.1.0~rc6-1' with architecture '' Unable to make a source version for version

Package: xen-hypervisor-4.1-amd64 Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-5 Severity: important I updated from xen-hypervisor-4.0-amd64 to xen-hypervisor-4.1-amd64 and the system did not boot anymore (Xen panic). A downgrade made the system work again. I cannot paste the boot error messages but the main message was: Xen BUG at pci_amd_iommu.c:33 The bug appears for Linux images 3.2.0.2

Package: xen-hypervisor-4.1-amd64 Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-5 Severity: important I updated from xen-hypervisor-4.0-amd64 to xen-hypervisor-4.1-amd64 and the system did not boot anymore (Xen panic). A downgrade made the system work again. I cannot paste the boot error messages but the main message was: Xen BUG at pci_amd_iommu.c:33 The bug appears for Linux images 3.2.0.2

Package: xcp-xapi Version: 1.3.2-9 Severity: normal Hi guys, Just a couple of things I noticed running through /usr/share/doc/xcp-xapi/README.Debian.gz as referenced by http://wiki.debian.org/XCP In "4/ Configuring Xen and XCP": sed -i "s/TOOLSTACK=/TOOLSTACK=xapi/" /etc/default/xen should be sed -i "s/TOOLSTACK=.*/TOOLSTACK=xapi/" /etc/default/xen Otherwise

Package: xcp-xapi Version: 1.3.2-9 Severity: normal Function wait_for_xapi in /etc/init.d/xcp-xapi does not work as intented. Symptoms: (on slave) /etc/init.d/xcp-xapi restart [....] Restarting The XenAPI server: xapiThe host toolstack is still initialising. Please wait. Cause: Line 'xe pif-scan host-uuid=${INSTALLATION_UUID}' called before xapi is fully synced with master.

Package: xen-utils-common Version: 4.1.2-7 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, The script /usr/lib/xen-common/bin/xen-toolstack improperly aborts if *either* `xm` or `xl` cannot be found in the xen-dir (/usr/lib/xen-4.0/bin). This means that a default installation (e.g. following Debian wiki on the subject, namely installing xen-linux-system and

Package: xcp-xapi Version: 1.3.2-9 Severity: grave Justification: renders package unusable I've following mostly the xcp-xapi/README.Debian instructions after installing it with apt-get -t wheezy network.conf is configured for bridge, xenbrN are functioning and shown with xe network-list A single SR is present, created with ext on a local LVM. For debugging purposes, all ISO and local ISO

Accepted: libxen-4.1_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb to main/x/xen/libxen-4.1_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb libxen-dev_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb to main/x/xen/libxen-dev_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb libxen-ocaml-dev_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb to

After turning off hibernation this issue did not occur anymore in Squeeze. Now we've turned on hibernation again, ran the test to reproduce this issue and this issue occurred within 10 minutes on Squeeze with Hibernation on. Then we've upgraded our test environment from Squeeze to Wheezy and ran the test to reproduce this issue again on Wheezy with hibernation turned on. This test