similar to: Bug#711420: Xen not booting over Wheezy

Control: tag -1 +moreinfo Hi Marco, Thanks for your report. Unfortunately the logs you've provided are from a system booted without Xen, and due to the nature of the bug it is unlikely that any relevant logs made it onto the disk in order to survive the resulting reboot. Please could you try setting up a serial console and collect the full boot log.

Does anyone know how to get CID working in AEL2 ? In extensions.conf you can do: exten => 111/666,1,PlayBack(demo-congrats) exten => 111/666,2,Hangup() exten => 111,1,PlayBack(demo-moreinfo) exten => 111,2,Hangup() and if callerid 666 dialed 111, they would get demo-congrats, everyone else gets demo-moreinfo. In AEL: 111 => { Playback(demo-moreinfo);

>From the documentation I have found, it seems that one of the functions from package plyr, or a combination of functions like split and lapply would allow me to have a really short R script to analyze all my data (I have reduced it to a couple hundred thousand records with about half a dozen records. I get the same result from ddply and split/lapply: >

The data.frame is constructed by one of the following functions: funweek <- function(df) if (length(df$elapsed_time) > 5) { rv = fitdist(df$elapsed_time,"exp") rv$year = df$sale_year[1] rv$sample = df$sale_week[1] rv$granularity = "week" rv } funmonth <- function(df) if (length(df$elapsed_time) > 5) { rv =

Package: xen-hypervisor-3.0.3-1-i386 Version: 3.0.3-0-2 Severity: important When I try to start a domU with more than 6 vdb it crash. The first time the vm does not launch and aparently wait for the loop device creation (some scripts/block add, udev --daemon and sleep 1 process running). And nothing happen until I Ctrl+C the xm create. My loop module is loaded with 64 loops. After this first

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-2 Hi, Hvm domU does not starts up afer dom0 reboot. Bridge br0 is set up manually. Dom0: Debian Wheezy 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux DomU: Debian Squeeze 2.6.32-5-amd64 #1 SMP Sun Sep 23 10:07:46 UTC 2012 x86_64 GNU/Linux config: ===<======== kernel = '/usr/lib/xen-4.1/boot/hvmloader' builder = 'hvm'

Package: xen-utils-common Version: 4.4.0-5 Severity: important Tags: patch Hello, xen-init-list fails to parse output of xen list -l when using XM toolstack. Therefore, /etc/init.d/xendomains stop fails to shutdown any guests still running on shutdown. xen-init-list fails with the following message: /usr/lib/xen-common/bin/xen-init-list Traceback (most recent call last): File

Hi, See below: # getent group adm adm:x:4:root,adm,daemon And: # ls -l /var/log total 20384 -rw-r----- 1 root adm 43310 Jun 21 16:00 auth.log -rw-r----- 1 root adm 128247 Jun 19 06:47 auth.log.0 -rw-r----- 1 root adm 10318 Jun 12 06:47 auth.log.1.gz -rw-r----- 1 root adm 9508 Jun 5 06:47 auth.log.2.gz -rw-r----- 1 root adm 12475 May 29 06:47 auth.log.3.gz

Package: logcheck-database Version: 1.2.40 Severity: normal Tags: patch There are one line that is not properly ignored. I include in the report a better version. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (400, 'testing'), (300, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-k7 Locale:

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: important I've a Debian Lenny AMD64 as production server, where it has important HVMs that runs correctly. The problem occurs when i try to create a HVM from a Debian Squeeze AMD64 iso file. At first, the VNC display specified shows perfectly the Debian Installer menu, but when I choose an option (Install or Graphical Install),

Package: logcheck Version: 1.2.69 Severity: normal Tags: patch Logcheck's reports contains many messages like: Feb 7 19:03:57 srv dhcpd: DHCPREQUEST for 172.21.0.126 from 00:19:7e:9f:cc:32 (Hostname Unsuitable for Printing) via eth0 Feb 7 19:03:57 srv dhcpd: DHCPACK on 172.21.0.126 to 00:19:7e:9f:cc:32 (Hostname Unsuitable for Printing) via eth0 I create file

Package: logcheck Version: Version: 1.2.3 Severity: wishlist The subject line is not correct, if any of these options 'ATTACKSUBJECT', 'SECURITYSUBJECT' and 'EVENTSSUBJECT' are combined in a report. The subject line only include the first event of a report. This is not so good for report mail filtering. The patch in the attachment correct this. -- Bill Gates said:

Patch attached. Steve -- --- Makefile-orig 2006-09-04 14:37:18.000000000 +0100 +++ Makefile 2006-09-04 14:37:34.000000000 +0100 @@ -57,7 +57,7 @@ .PHONY: ioemu ioemuinstall ioemuclean ifndef XEN_NO_IOEMU ioemu ioemuinstall ioemuclean: - [ -f ioemu/config-host.h ] || \ + ( test -f ioemu/config-host.h ) || \ (cd ioemu; ./configure --prefix=usr) $(MAKE) -C

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: important the xen-utils packages lack xfrd, which is required for live domain migrations using xm migrate. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-686 Locale:

Package: xen-hypervisor-4.3-amd64 Version: 4.3.0-3+b1 Severity: normal Dear Maintainer, After booting into kernel 3.13 dom0, the keyboard no longer works. All other aspects work, ssh is needed to login to the system to start working with the domU's. They keyboard works at the grub menu just fine, and works normal when booting into the non xen kernel. -- System Information: Debian Release:

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal When my domU uses this configuration: --- root = '/dev/sda2 ro' disk = [ 'phy:/dev/volume0/lenny.vandervlis.nl-swap,sda1,w', 'phy:/dev/volume0/lenny.vandervlis.nl-disk,sda2,w', ] --- Pygrub gives the error "Error: Boot loader didn't return

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: grave Justification: renders package unusable qemu-dm sends out this: - supported machines are: pc Standard PC (default) isapc ISA-only PC - instead of: - Supported machines are: xenfv Xen Fully-virtualized PC (default) xenpv Xen Para-virtualized PC - this renders any tries to use HVM fail. -- System Information:

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: normal Since this package installs python modules in /usr/lib/xen-3.0.3-1/lib/python/, and uses them directly from there, not following the python policy, once xend has started up, lots of .pyc files are created there, which will not be removed if the package is purged. These pyc files may also cause problem for future python upgrades, I

Here is the function that makes the data.frames in the list: funweek <- function(df) if (length(df$elapsed_time) > 5) { res = fitdist(df$elapsed_time,"exp") year = df$sale_year[1] sample = df$sale_week[1] mid = df$m_id[1] estimate = res$estimate sd = res$sd samplesize = res$n loglik = res$loglik aic = res$aic bic = res$bic chisq =

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal When a DomU is defined as using a file: device the loopback driver will be used to make it appear to be a regular block device. The loopback driver will by default only support 8 nodes so this is a limited resource. http://etbe.coker.com.au/2008/10/22/kernel-issues-with-debian-xen-and-centos-kernels/ If there is a problem that prevents