similar to: Shall we release 3.0.1?

As a release manager asked us to do that, we should remove the kernel patch from the packaging... As I said I'm not completely against removing it, if we distribute it on our website and point people to it in some documentation! The internet is just there, so what would the matter be? If nobody is against this course of action I'm going to move the patch outside of the debian directory,

Hi folks With the lack of responses to my restructuring the last weeks, it looks like pkg-xen is dead. Now, what to do? My favorite is to merge it into the kernel repository where I have my infrastructure (archive and autobuilders for snapshots for example) to properly work on it. Bastian -- No one wants war. -- Kirk, "Errand of Mercy", stardate 3201.7 -------------- next part

Hello, I would like to make a point on the current status of the Xen 3.0 package. It seems the current issue that Bastian told are now fixed. So, I would like to heard some report from users about the usability of this package, in order to upload it as soon as possible. If your discover any bug, any strange behaviour or any missing things, please do report it here. -- Julien Danjou

Author: acid Date: 2006-02-16 10:45:13 +0000 (Thu, 16 Feb 2006) New Revision: 3 Modified: trunk/changelog trunk/control Log: - Change maintainer and add uploaders field - Prepare changelog for new upload Modified: trunk/changelog =================================================================== --- trunk/changelog 2006-02-15 23:05:09 UTC (rev 2) +++ trunk/changelog 2006-02-16 10:45:13

Author: ultrotter Date: 2006-02-17 06:56:29 +0000 (Fri, 17 Feb 2006) New Revision: 9 Modified: trunk/debian/changelog trunk/debian/control Log: Change the version and debian revision, as agreed on the ML Start tracking the bugs that need to be closed on upload Modified: trunk/debian/changelog =================================================================== --- trunk/debian/changelog

Hello, We''ve recently started seeing several domUs on multiple machines losing all network connectivity. At least one of these machines (since they are customer machines I can''t verify it for all of them) give the error: $ sudo ifup eth0 eth0: full queue wasn''t stopped! About the only Google hit for this message is:

Hi! This might be fixed by upstream changeset 9669, even though I'm not completely sure... I will test and report back! Guido

Hello, I have set up a build machine for Xen. Currently it builds the version checked out from Subversion with the latest testing version from Xen repository for Sarge every night. deb http://naquadah.org/~jd/debian/xen stable main I plan to upload real and official backports to backports.org as soon as we will upload a version to sid. Any comment welcome, Cheers, -- Julien Danjou

On Tue, Feb 14, 2006 at 10:17:14AM +0100, Guido Trotter wrote: Hello, > Do you mean svn or some other new revision control system, right? Yes, please, use subversion, not CVS anymore :) Reading http://svn.debian.org/, we should ask for a repository. I think the project admin should do this ;) > Anyway, yeah, I think the debian directory should be fine! We can still use > dpatch if we

Hi, One last thought... We haven't heard anything back from Bastian (for which I'm sorry, I would really have liked if he had joined us) and in the meantime consensus seem to have formed on -kernel and -devel, or at least there was no more answers... Which means at least people don't disagree strongly with the conclusions taken... In the meantime, though, there's still the upload

So, let's get started! One of the first changes we might want to do is move away /etc/sysconfig/xendomains... We should put it either in /etc/default/xendomains (since it's an init script configuration) or /etc/xen/xendomains (since it's xen related)... Which one do you prefer? As for the way to do it I propose a dpatch file that changes the two files in the upstream tarball that

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-1 Severity: normal Tags: patch Manpages that are provided with the source are not included with the utilities. Use perl-doc package at build-time to generate appropriate manpages and dh_manpages to install them in the appropriate locations. diff -urN xen-3.0-3.0.3-0/debian/control xen-3.0-3.0.3-0.new/debian/control --- xen-3.0-3.0.3-0/debian/control

Package: xen-utils-common Version: 3.0+hg11624-1 Severity: important The packages fails to install with the following error: Setting up xen-utils-common (3.0+hg11624-1) ... ln: creating symbolic link `/etc/udev/rules.d/z60_xen-backend.rules' to `../xen-backend.rules': No such file or directory dpkg: error processing xen-utils-common (--configure): subprocess post-installation script

Hi! We have a couple more things on our TODO list, it seems... (If we could use the BTS tracking things would be better) (or we could use the issue tracker on alioth, for now) 1. xen-utils: Right now domains get shut down on upgrade... This is ok in a 2.0 -> 3.0 scenario, but it's not in a 3.0.1 -> 3.0.2, where we could avoid that, probably! Should we perhaps try to avoid that,

Package: xen-utils-3.0 Version: 3.0.2+hg9681-1 Severity: normal I get this error with xen after some debug cycles, start / stopping nodes. I found this fix on the net, which fixes the problem: http://lists.xensource.com/archives/html/xen-users/2006-04/msg01070.html in /etc/init.d/xen: start) + modprobe loop max_loop=64 + cd /dev && /dev/MAKEDEV loop xend start

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5204 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20060927/7204cce9/smime.bin

Package: xen-hypervisor-3.0-i386-pae Severity: normal Forwarding a problem reported by Nathan Hawkins. > I ran into a problem with the PAE version of the hypervisor. I'm looking at > xen-hypervisor-3.0-i386-pae_3.0.2+hg9611-1_i386.deb from alioth, and I > ran into a problem with PAE being disabled in the binary: > > $ zcat xen-3.0-i386-pae.gz | strings | grep PAE

Hi folks I propose the following changes for 3.1: - Rename source to xen-3. Upstream stripped one part of the version, so the next should be 3.2. - pygrub as extra package. - Rename i386 to i386-nonpae - Rename i386-pae to i386. PAE is upstream default now and pae images works with a 64bit hypervisor. We should think about supporting libvirt. It provides an AFAIK stable interface on the

Hi! Can anybody explain how Xen deals with time? On traditional, non-virtualized systems I run an ntpd on every system to keep the time accurate. But what to do on xenified systems? Do all the domU''s get the time from dom0 meaning it is sufficient to run an ntpd there or do I have it to setup in every domU? Thanks for your help! Kind regards, Stephan

Hi, I configured dovecot IMAP for MySQL authentification. --- start dovecot.conf --- auth_userdb = mysql /etc/dovecot/dovecot-mysql.conf auth_passdb = mysql /etc/dovecot/dovecot-mysql.conf --- end dovecot.conf --- --- start dovecot-mysql.conf --- db_host = localhost db_port = 3306 db_unix_socket = /var/run/mysqld/mysqld.sock db = users db_user = users db_passwd = xxx db_client_flags = 0