similar to: Bug#572147: RM: xen-unstable; RoM

Package: xen-hypervisor-3.0-amd64 Version: 3.0.2+hg9656-1 Severity: wishlist Hello, it would be nice to have the amd64-Hypervisor for the i386 arch for installations with amd64 kernel and i386 user space. Thanks, Torsten

Package: ftp.debian.org Version: N/A Please remove xen-3.0 from unstable. It has been replaced by xen-3. Bastian -- Star Trek Lives! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url :

Package: ftp.debian.org Severity: normal Hi, Writting this message saddens me, but no choice... Because upstream authors (eg: Citrix) have explained that they cannot maintain the current version of XenAPI, or upgrade it to a newer version, we have no choice but to remove completely XenAPI from both Unstable and Testing. Quoting Euan Harris from Citrix (it's not needed for the FTP masters

[This email is either empty or too large to be displayed at this time]

Hi, I try to build wine-1.1.26 on debian unstable (amd64) linked to ia32 libs. I installed ia32-apt-get and nvidia-glx-ia32 and all ia32-lib*, which are buildependencies for wine-1.1.23 in experimental on i386. The configure ends successfully but the build finished with gcc -m32 -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_NTSYSTEM_ -D_REENTRANT -fPIC -Wall -pipe

FYI: The status of the xen-unstable source package in Debian's testing distribution has changed. Previous version: 3.0-unstable+hg11292-2 Current version: 3.0-unstable+hg11561-1 -- This email is automatically generated; henning@makholm.net is responsible. See http://people.debian.org/~henning/trille/ for more information.

FYI: The status of the xen-unstable source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 3.0-unstable+hg11292-2 -- This email is automatically generated; henning@makholm.net is responsible. See http://people.debian.org/~henning/trille/ for more information.

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

Anyone else seeing problems with this combo? I'm running: linux-image-2.6.18-4-xen-686 2.6.18.dfsg.1-9 linux-modules-2.6.18-4-xen-686 2.6.18.dfsg.1-9 xen-hypervisor-3.0-unstable-1-i386-pae 3.0-unstable+hg11561-1 xen-utils-3.0-unstable-1 3.0-unstable+hg11561-1 xen-utils-common 3.0.3-0-2 When I try to fire up xend, it bombs.. doing some

Package: xen-ioemu-3.0-unstable Version: 3.0-unstable+hg11561-1 Severity: normal When trying to create an HVM domain with vif settings enabled (as default) qemu-dm fails to start the virtual machine claiming that the tap device cannot be found. This is because qemu-dm tries to execute /etc/xen/qemu-ifup which is instead located in /etc/xen/scripts/qemu-ifup. As a side note qemu-dm seems to be

Package: xen-ioemu-3.0-unstable Version: 3.0-unstable+hg11561-1 Severity: normal Hi, in #393609 /etc/xen/scripts/qemu-ifup is wrongly placed/referred. This script is missing from the amd64 package, making network enabled HVM domain not startable. Regards, L -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture:

Package: xen-utils-4.0 Version: 4.0.0-1 Severity: normal xen-utils-4.0 needs to be built to work with the version of Python in Unstable. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386

Package: xen-unstable Version: 3.0-unstable+hg11561-1 Followup-For: Bug #399700 The included patch overcomes the old build dependency on linux-support-2.6.17-2, and replaces it with linux-support-2.6.22-3. I filed a previous bug #453912 - but I guess it doesn't apply? -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable')

(new) xen-hypervisor-unstable-amd64_3.3-unstable+hg17192-1_amd64.deb extra misc The Xen Hypervisor on AMD64 The hypervisor is the "core" for XEN itself. It gets booted by the boot loader and controls cpu and memory, sharing them between your administrative domain (Domain 0) and the virtual guest systems. . In order to boot a XEN system along with this package you also need a

(new) xen-docs-3.0-unstable_3.0-unstable+hg11218-1_all.deb extra misc documentation for XEN, a Virtual Machine Monitor This package contains all the large documentation files for XEN. This includes a description interface(both the api, and a nice explanation of how XEN works). It also contains the VBD and Xeno howtos. (new) xen-hypervisor-3.0-unstable-1-amd64_3.0-unstable+hg11218-1_amd64.deb

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

With a bit of a struggle, I have managed to construct a patchset based on the Debian xen-unstable SVN from Alioth which applies against the current Xen upstream tip and actually works. I have smoke tested it with both PV and HVM guests. The diff against svn 502 is attached. You should also apply my patch in bug #463121 to make PAE hypervisors build correctly. Various patches have become

tag 502123 patch severity 502123 serious thanks Confirmed. This regression was introduced by a copy-and-paste error in debian/patches/tools-python-xen-xm-relative-path.diff (svn://svn.debian.org/pkg-xen -r531). Please apply this fix. --- debian/changelog 2008-12-04 16:50:04.000000000 -0500 +++ debian/changelog 2008-12-04 16:59:09.000000000 -0500 @@ -1,3 +1,10 @@ +xen-unstable

I've resolved the conflicts between the xen-unstable svn tree's patchset and xen-unstable 16319 (which was the tip a few days ago). The result is below, as the output of `svn diff' - so a series of interdiffs, unfortunately. Also, I noticed that after installing the resulting packages, it wasn't able to correctly select the xen-unstable tools; instead, it fell back to the default.

retitle 502123 xen-utils-unstable: Debian patch breaks paravirtualized guest initrd thanks I see that this bug is still present in pkg-xen svn: http://svn.debian.org/wsvn/pkg-xen/trunk/xen-unstable/debian/patches/tools-python-xen-xm-relative-path.diff?op=file Perhaps I wasn?t clear how severe this problem is. Using the current Debianized xen-utils-unstable, it is impossible to boot any