similar to: Bug#591456: (no subject)

> Agreed, the severity should be bumped up on this, I spent many hours > after a lenny to squeeze upgrade figuring out what the problem was. I > request that the previously attached patch (a simple one liner) be > applied for a squeeze update. Also agreed. It's disappointing to see that Xen is so buggy in Squeeze. The sooner these bugs get fixed the sooner people can start

Agreed, I have the the same problem after upgrading from Lenny to Squeeze and the only option for me is tu use routing networking for xen. Among this there are another bug in /etc/xen/scripts/vif-common.sh which trigger a kernel error regarding routing for which exist a patch at http://xenbits.xensource.com/xen-unstable.hg?rev/b0fe8260cefa This is very annoying because debian multimedia

Could this fix be included in a squeeze point release, i.e. uploaded to stable-proposed-updates, please? I have a production server running lenny using the block-drbd scripts, which this bug breaks, so I can't really upgrade the server to squeeze until this problem is fixed. Thanks, Owen

xm save lenny3 /tmp/lenny3.save The guest console says: Suspending xenbus... and detaches. Restore the guest (paused to attach its console before continuing): xm restore -p /tmp/lenny3.save xm console lenny3 xm unpause lenny3 The console starts spewing out "BUG: recent printk recursion" and the domain spins until destroyed. The same thing happens on (live or not) migration. The

xm save lenny3 /tmp/lenny3.save The guest console says: Suspending xenbus... and detaches. Restore the guest (paused to attach its console before continuing): xm restore -p /tmp/lenny3.save xm console lenny3 xm unpause lenny3 The console starts spewing out "BUG: recent printk recursion" and the domain spins until destroyed. The same thing happens on (live or not) migration. The

It's been some time since I didn't send an update about samba packages in Debian. Here it is. Fairly long, sorry for this. As preliminary facts: Debian entered a full freeze in Mid-August, in preparation of the next release, codename "squeeze". It means that packages uploaded to Debian unstable no longer migrate to testing (which is "the next release", so squeeze right

Hi, We normally run Lenny dom0 with 384 MB of RAM in our production server. But as we did few trials with Squeeze, I had the very bad finding that a Squeeze dom0 requires at least 1024 MB of RAM. As soon as I do something like "xm mem-set Domain-0 800", my server crashes: OOM starts killing processes, starting with sshd, then mdadm and so on, then the server reboots by itself. This

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: serious Tags: squeeze Hi there! Upgrading from Lenny to Squeeze left my box with xen-hypervisor-3.2-1-amd64 installed, and I had to "apt-get install xen-hypervisor-4.0-amd64" manually to have it installed after a dist-upgrade. This for sure, isn't the expected behavior. Also, after the dist-upgrade, I did: apt-get

FYI: This bug also breaks user supplied scripts (/etc/xen/scripts/block-*) that are needed to handle block device mounting other than "phy:" and "file:" disks. See attached email from debian-user mailing list. cheers -henrik -------------- next part -------------- An embedded message was scrubbed... From: Henrik Langos <hlangos-debian at innominate.com> Subject: Re:

Hello, Not sure this is the right place to ask Xen user-questions. I am running Lenny and try to upgrade a domU to Squeeze. After the installation of a new xen-kernel in the domU and upgrading udev I did a reboot but then the kernel does not find the root anymore, and it's dropping me to a shell. When I look into /dev/ I don't see any disks or partions. Is here somebody who can help me

Hi, I''m having issues on intel and amd, when booting it doesn''t assemble the raid devices. It seems to work ok in Lenny but when you upgrade to squeeze it won''t boot. Anyone else with same issue? Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Is there a fix for this in the works/coming for squeeze or do I have to patch the package myself? If so, how? Thanks, a grateful Debian user that hasn't patched packages yet! Steve -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20101122/8433308c/attachment.htm>

Hi, I have a machine that was previously running the lenny-packaged hypervisor. I upgraded it to squeeze recently and it failed to complete a boot of the dom0 kernel. I reported this on xen-devel? and was advised to try building a hypervisor from the tip of 4.0-testing. I did this and this seems to work for me. I'm guessing that since wheezy will be released soon there is little interest in

Package: xen-hypervisor-4.0-i386 Version: 4.0.1-4 This is the same machine referenced in http://bugs.debian.org/665413. It is an HP d530 SFF workstation (model DG784A) with 4GiB of RAM. It has run for years on the lenny xen + linux stack. If my notes are correct, it also ran smoothly for about a year with the lenny hypervisor + kernel and the squeeze userland. Rebooting into squeeze xen +

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Severity: normal -- System Information: Debian Release: 6.0.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash

Hi, I believe the package is ready: http://ftparchive.gplhost.com/debian/pool/lenny/main/x/xen-qemu-dm-3.4/xen-qemu-dm-3.4_3.4.2-1.dsc I asked Ian Jackson to sponsor it (he works for Citrix and is a DD), but it's been 2 weeks, and he seems busy with work. I'd be glad if someone was sponsoring the upload of this package in Debian SID, soon enough so that people will be able to test it

Hi, to make transitions more convenient, I've done this by using uuid instead of device names. If you ls -l /dev/disk/by-uuid inside your domU, you'll see something like lrwxrwxrwx 1 root root 10 5. Mai 07:38 39a2a64b-0716-47ad-92f4-a7437cac54ee -> ../../sda2 lrwxrwxrwx 1 root root 10 5. Mai 07:38 e8b97b59-a790-417c-8231-fe8da8b6e6ee -> ../../sda1 In /etc/fstab inside the domU,

Hi, I realise this might be a Debian-specific question. I've got access to two hosts which have IPv6 connectivity, both of which are running Icecast 2.3.2. One is still running Debian Lenny and can be reached via IPv6 just fine, but the other is running Debian Squeeze and cannot. In addition, my local server which does not have IPv6 conectivity to the Internet but which can be reached

Hello! This is my first email to this list, let me give a brief of myself... I'm a brazillian, a Linux user since 1996 (using Slackware), a Debian user since Potato and of the Xen, since 2006. I am the maintainer of Xen Live CD, hosted at: http://wiki.xensource.com/xenwiki/LiveCD - http://xen.org Me at the member spotlight - The Xen Live CD is a Lenny system builded with the live-helper.

Hi, I'm new in this List, but I have 6 years using Dovecot on my debian from etch,lenny and now squeeze Package: dovecot-imapd Version: 1:1.2.15-4 Tags: squeeze -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/24 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8