similar to: Bug#391448: xen-hypervisor-3.0-unstable-1-i386: dom0 crashes when starting the 3rd domU

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')

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

# 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: 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

Processing commands for control at bugs.debian.org: > close 396556 Bug #396556 [src:xen] Please build gdbserver-xen in the xen-utils package Marked Bug as done > forcemerge 446114 396556 Bug #446114 {Done: Ian Campbell <ijc at debian.org>} [src:xen] xen-utils-3.1-1: build gdbserver Bug #396556 {Done: Ian Campbell <ijc at debian.org>} [src:xen] Please build gdbserver-xen in the

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.

Package: xen-hypervisor-3.0-unstable-1-amd64 Version: 3.0-unstable+hg11561-1 Severity: important The HVM domU won't start. The following is the config (comments stripped). --------------------begin-------------------- import os, re arch = os.uname()[4] if re.search('64', arch): arch_libdir = 'lib64' else: arch_libdir = 'lib' kernel =

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-unstable Version: 3.0-unstable+hg11561-1 Severity: serious Build-depends on linux-support-2.6.17-2, which is no longer available in sid. -- Stephen R. Marenka If life's not fun, you're not doing it right! <stephen@marenka.net> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size:

Hello ext3-users, we have an oopsy situation here: we have 4 machines: 3 client nodes, 1 master: the master holds a fairly big repository of small files. The repo's current size is ~40GB with ~1.2 M files in ~100 directories. Now, we like to rsync changes from the master to the client nodes, which is working perfectly for 2 nodes, but our 3rd node oopses "sometimes", rendering

Hello, I''m running a standard Debian Etch Xen server for testing. Today I ran a Debian update and it installed some new kernel-related packages. The install scripts said something about deleting unused symlinks, but I was in a hurry, so I can''t remember exactly. Now I''ve the problem that the server will not boot any more. After loading the hypervisor, the system

hi, I'm trying out xen on an etch base system install. I'm not using lvm at the moment, I have a biproc amd and I'm using the package xen-linux-system-2.6.17-2-xen-k7 and other stuff I've read to be installed from: http://audiens.de/installation_notes_on_xen_3_0_2_on_debian_etch what I get as result is that on appearing of this message at boot time: Xen trace buffers: disabled

FYI: The status of the xen-unstable source package in Debian's testing distribution has changed. Previous version: 3.0-unstable+hg11561-1 Current version: (not in testing) Hint: <http://ftp-master.debian.org/testing/hints/luk> Bug #395332: xen-unstable - not suitable for a release The script that generates this mail tries to extract removal reasons from comments in the

Source: xen-unstable Version: 3.0-unstable+hg11561-1 Severity: grave Tags: security Hi, the following CVE (Common Vulnerabilities & Exposures) id was published for xen-unstable. CVE-2007-3919[0]: | (1) xenbaked and (2) xenmon.py in Xen 3.1 and earlier allow local | users to truncate arbitrary files via a symlink attack on | /tmp/xenq-shm. If you fix this vulnerability please also include

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-hypervisor-4.0-i386 Version: 4.0.1-4 Severity: normal Tags: squeeze -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash xen-hypervisor-4.0-i386 depends on

user debian-release at lists.debian.org usertag 469013 -goal-python2.5 retitle 469013 Python API memory handling bug in unused code path found 469013 3.0-unstable+hg11561-1 thanks Hi, the code that exhibits the buggy PyObject_NEW/PyMem_DEL behaviour (in xen-unstable-3.0-unstable+hg11561/tools/pygrub/src/fsys/ext2/ext2module.c) is not actually compiled and the results shipped[1]. As such,

Hi.. i have an expression of the form: model1<-nls(y~beta1*(x1+(k1*x2)+(k1*k1*x3)+(k2*x4)+(k2*k1*x5)+(k2*k2*x6)+(k3*x7)+(k3*k4*x8)+(k3*k2*x9)+(k3*k3*x10)+ (k4*x11)+(k4*k1*x12)+(k4*k2*x13)+(k4*k3*x14)+(k4*k4*x15)+(k5*x16)+(k5*k1*x17)+(k5*k2*x18)+(k5*k3*x19)+