similar to: Bug#366216: Possible fix

Greetings Debian Xen team, I spent a weekend getting 3.0.2-testing building and thought i'd share the love. Manoj and I are already working to update make-kpkg for the new Xen architecture. My repo is at: http://debian.thoughtcrime.co.nz/debian/ I have posted a Breezy-centric howto for this build at: http://debian.thoughtcrime.co.nz/debian/README.txt Hope you enjoy it, and hope we can

Package: xen-utils-3.0 Version: 3.0.2+hg9656-1 Severity: normal My setup is a basic one. No changes to the /etc/xen/* files. Network in a domU works perfectly fine. But, after shutdowning a domU, I can see the following lines in /var/log/debug: May 6 10:31:45 vaio logger: /etc/xen/scripts/vif-bridge: offline XENBUS_PATH=backend/vif/18/0 May 6 10:31:46 vaio logger: /etc/xen/scripts/vif-bridge:

# xm create -c vm01.cfg Error: Cannot open config file "vm01.cfg" www:/var/log/xen# xm create -c /etc/xen/auto/vm01.cfg Using config file "/etc/xen/auto/vm01.cfg". Error: (22, 'Invalid argument') # xm log [2006-10-24 16:16:30 xend.util.security 29229] INFO (__init__:1072) Resource label file not found. [2006-10-24 16:16:30 xend.util.security 29229] INFO

Package: ftp.debian.org Severity: normal Hello, Please consider removing xen. New xen-3.0 splited packages are upcoming, making this one obsolete. Cheers, -- Julien Danjou // <julien@danjou.info> http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD // The more we fly, the more we climb, the more we know that heaven is a lie. -------------- next part

Hi everybody! At least xen 3.0 packages seem to be working, tested, and in a pretty good shape... (I haven't personally tested xen-unstable, so I cannot say) I propose releasing rev150 in unstable or at least experimental in the next few days... No, this is not a late april's fool... :D Comments? Ideas? Suggestions? Rants? Guido

Dear Debian Xen Team, The following possible problem(s) were detected in the package(s) you maintain in Debian: === xen-unstable: = This package has not been in testing for 353 days. = This package has not been able to migrate from unstable to testing for 353 days. See <http://bjorn.haxx.se/debian/testing.pl?package=xen-unstable> This is an automated mail. These mails are sent

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

Okay since we have a few more people on the list now I see I wanted to get peoples input on a couple things. First of all, I'd like to work on general consensus so I'd like to see what people think of having the list setup to reply back to the list. I know some lists use this and some don't so I'd like to get input on the matter. I'd also like to get input on choice

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

Hi folks There are still some solutions missing in both trunk trees: - Patches from trunk (3.0) - udev symlink handling (both) A package is not allowed to put symlinks into /etc/udev/rules.d, it have to create it on the first installation and remove it on purge. - postint script needs to create /var/lib/xenstored (both) - initscript needs to create /var/run/xenstored (both) /var/run may be

I am using the "tha" Xen packages from http://packages.debianbase.de/sarge/amd64/xen3/ However, I noticed that some new packages have been uploaded into the NEW queue. What I am wondering is if/when/where the Sarge packages will be made available. If there is no current plan to make them available, I would be happy to help in any way that I can. -Roberto -- Roberto C. Sanchez

xen-3.0_3.0.2+hg9611-1_i386.changes uploaded successfully to localhost along with the files: xen-3.0_3.0.2+hg9611-1.dsc xen-3.0_3.0.2+hg9611.orig.tar.gz xen-3.0_3.0.2+hg9611-1.diff.gz xen-docs-3.0_3.0.2+hg9611-1_all.deb xen-hypervisor-3.0-i386_3.0.2+hg9611-1_i386.deb xen-hypervisor-3.0-i386-pae_3.0.2+hg9611-1_i386.deb xen-utils-3.0_3.0.2+hg9611-1_i386.deb Greetings, Your Debian

Dear all, If I want to build a box which is mainly full of packages from the stable distribution but for the minor addition of this crazy Xen 3.x thing, what's the best way to go about it ? I think I'll need to compile my own kernels, but do I need to compile the userland Xen stuff too, or is there a semi-official backport ? Reading the archives suggests various packages in various

http://lists.alioth.debian.org/pipermail/pkg-xen-devel/2006-April/000462.html The above url hows 3.0_3.0.2+hg9646-1 being accepted, but http://pkg-xen.alioth.debian.org/ shows 3.0_3.0.2+hg9611-1 as the latest .deb, and https://alioth.debian.org/project/showfiles.php?group_id=30894 shows 3.0.2+hg9629 patches. Where can I get 3.0_3.0.2+hg9646-1? -- Bob Tanner <tanner@real-time.com>

Hi Debian Xen Maintainers! Thank you for the former work. The 3.0 Version of Xen works flawlessly. When can I exspect the 3.1 version in say experimental ? Please give me a roadmap ? Best Regards Volker -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herlo?sohnstr. 12 0 4 1

Hi there, I've done an apt-get source linux-image-2.6.18-4-xen-686 and would very much like to build a package with NFS root enabled. From what I've read, I need to run split-config, which I got from SVN (it doesn't seem to exist anywhere else) I've fooled around with split-config to produce a config to my spec but this doesn't seem to actually work. Usage:

I've noticed that with NetworkManager running in dom0, there is a lot of bad behaviour on the bridge interface After xend creates the bridge (using the sample network-bridge script in the package), the real interface is known as peth0 NetworkManager starts dhclient on peth0, which means the following: - peth0 gets it's own IP, maybe not the same as the bridge IP - a second default route

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-hypervisor-3.0.3-1-i386 Version: 3.0.3-0-1 Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, When you have a HVM domain running, if you try to boot a regular paravirtualized domain, dom0 (or maybe the hypervisor) crashes immediately (reboot). The opposite (trying to boot a HVM domain while a regular paravirtualized domain is running) crashes the system as well. I

Hi, I've tried to get my sarge desktop booting under the xen hypervisor, and have been having some problems. I've asked about it on the xen-users mailing lists, the #xen irc channel with oftc, and on the sage-au mailing lists, but not had any answers at all. I can boot into the system, but the boot process seems to freeze during the /etc/rc2.d/S* scripts. It used to freeze while