similar to: Bug#385934: xen-hypervisor-3.0-i386: Hypervisor reboots before starting Dom0

after upgrading to 3.0.2+hg9697-2 I experience the same problem! I switched to xen-hypervisor-3.0-amd64, but it shows the same effect! AMD Athlon64 3800+ machine - was running fine with 3.0.2+hg9697-1 until last saturday... MfG Sebastian Rieger

Package: xen-utils-3.0 Version: 3.0.2+hg9697-2 Severity: grave Justification: renders package unusable Below you find the output of apt-get install xen-utils-3.0 . /usr/sbin/xend tries tom import the python scripts from /usr/lib/python as well as from /usr/lib64/python ; both directories do not exist on my system, I have python2.4 installed. (With both python2.3 and python2.4 installed I had the

Package: xen-3.0 Version: 3.0.2+hg9697-1 Severity: important Hello, There was a problem while autobuilding your package: > Automatic build of xen-3.0_3.0.2+hg9697-1 on avidan by sbuild/i386 0.49 > Build started at 20060725-0410 > ****************************************************************************** ... > CFLAGS="-O2 -fomit-frame-pointer -DNDEBUG -m32 -march=i686 -Wall

Package: xen-hypervisor-3.0-unstable-1-amd64 Version: 3.0-unstable+hg11292-2 Severity: important My server is a dell 2950 server. Before the dom0 rebooting bug ocurred, xen was well even for hvm domU. By now i have tried xen-hypervisor-3.0-amd64 (3.0.2+hg9697-2) and xen-hypervisor-3.0-unstable-1-amd64 (3.0-unstable+hg11292-2), but both of them are unusable for me. for

Package: xen-hypervisor-3.0.2-1-i386 Version: 3.0.2-3+hg9762-1 Followup-For: Bug #385934 Hello! For me, the new upload of xen-hypervisor-3.0.2-1-i386, version 3.0.2-3+hg9762-1, does _not_ fix this issue. I'm still seeing the same problem as it was originally reported in this very bug report. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900,

Package: xen-utils-3.0 Version: 3.0.2+hg9697-1 Severity: normal On unstable, xen-utils-3.0 can't be installed, due to dependencies. Reproducable: yes. Just install unstable and try to install xen-utils-3.0. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash

Hi, I got exactly, the same problem. I tryed installing xen-hypervisor-3.0-unstable-1-i386. It seems to have fixed the problem. I have no idea what the original issue is but this might be of use to people that need to get going again. Regards -- Tom

Package: xen-3.0 Version: 3.0.2+hg9697-1 Severity: important Hi, your package has been detected as generating a (for most of that mass bug fill: private) python module/extension that may need an upgrade to the new Python Policy[1]. A wiki page[2] explains what has to be done to upgrade your packages to the new Policy. This bug may be a false positive, in that case, please just close the bug.

Package: xen-utils-3.0 Version: 3.0.2+hg9681-1 Severity: normal In the tls section: it fails to mention the better solution (apt-get install libc6-xen) In the kernel section: where it says "for now we cannot provide precompiled Linux kernels with the xen patch applied", that's not true either. apt-get install linux-image-2.6-xen-k7 or some such. -- System Information: Debian

Hi, I''ve run into the same issue as: http://lists.xensource.com/archives/html/xen-users/2006-07/msg00599.html In that, running the network bridge script kills networking completely, trying to ping the gateway gives me destination host unreachable. The card is: 09:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 11) Using the bnx2 module:

Package: xen-utils-3.0 Severity: wishlist Please include support for HVM-based guests. This allows hardware virtualization on systems with Intel's chips with VT (IE, Pentium D 930), and AMD's future chips with Pacifica. HVM allows you to run unmodified operating systems under Xen, such as Windows XP/2003. The following files are needed: /usr/lib/xen/bin/qemu-dm

Package: xen-utils-3.0 Version: 3.0.2+hg9697-1 Severity: critical The xen-backend.rules file is stored in /dev/udev, but it is not correct. I made the symlink into /dev/udev/rules.d/ so it works. It is also mentioned at the following place: http://www.debian-administration.org/articles/396 -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-386 Locale:

Hello, I'm tasked with establishing a persistent SSH connection across a very unreliable link, for a remote port forward (always port 2217). I figured I'd use ServerAliveInterval to make sure that the ssh(1) process dies when the connection appears down, and I use systemd to restart it in this case. This works fine. What does not work fine, however, is the server-side. If the connection

Hello, I am using virt-manager 0.9.4 on a Debian unstable system (libvirt 0.9.12) to connect to a libvirtd via SSH running on a Debian testing system (also version 0.9.12), and I have a problem using virt-manager, which first takes ages to connect, then freezes. The SSH connection is top-quality, the hosts are next to each other and connected by Gigabit Ethernet. virsh connections work fine.

Hi list, I understand that dovecot's deliver does a little more than deliver: it also updates the dovecot metadata stored with each Maildir. Thus, if I use deliver as opposed to procmail's internal Maildir delivery, it seems that the IMAP server later has less work to do since the metadata is can use are up to date. Doing this, however, incurs an extra process for each mail delivered. I

Hey folks, As most of everyone, I use OpenSSH for almost everything and whenever I can: backups, sync, Git, configuration management, and of course console sessions. So much for an intro ;) My laptop and I roam between three networks, though sometimes I leave the laptop at the office overnight, or hop over to the third site for an hour or two. I'd like to find a way to configure OpenSSH (or

Dear list, I am running dovecot 1.2.15 on a Debian server. One user reports continuous problems synchronising her mailbox via IMAP (offlineimap, via SSH tunnel or SSL socket). It seems that she has a large, locally-created message, but the uplink bandwidth seems to be not enough to push it before dovecot times out the APPEND command. The error/exception happens inside offlineimap's Python

I am having the same problem. But, I cannot access to the following link for solution http://wiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround Can someone send me the content of this link? Thanks. Pete, This may be relevant: http://wiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround - Mike At 8/18/2006 09:40 AM Friday, Peter McEvoy wrote: Hi, I''ve run

That's a good point. DHCP allows you to set DNS search parameters. So as long as each location sets different search, "ssh fishbowl" will in fact resolve to the proper local FQDN. On Monday, December 22, 2014, Nico Kadel-Garcia <nkadel at gmail.com> wrote: > On Mon, Dec 22, 2014 at 4:26 AM, martin f krafft <madduck at madduck.net > <javascript:;>> wrote:

Hi, we are using dovecot IMAP in a complex virtual setup with almost 4000 accounts; postfix hands over to deliver for local delivery into a home directory as stored in the SQL database. That's /srv/vmail/$DOMAIN/$LOCALPART for most of them, but I'd rather not hardcode this scheme anywhere as it's in SQL. By a policy change, we need to insert a filter in this chain and the filter must