similar to: Bug#659642: is this still the case in Wheezy?

Ian Campbell <ijc at hellion.org.uk> writes: #Was that with the Jessie or Wheezy dom0 kernel? Actually tried both kernels. 3.13 on Jessie and 3.2 on Wheezy. The keyboard failed on any xen 4.3 boot. If it was nonxen, or xen 4.1 on any kernel the keyboard worked normal. Thanks for your help troubleshooting. Cheers, Mike -------------- next part -------------- An HTML attachment was

Hi Maykel, Does this still happen with the 4.1 hypervisor in Wheezy? Or more importantly (since I suspect this is more likely a kernel side thing) does this still happen with the 3.2 dom0 kernel in Wheezy? If this still happens then I would suggest reporting this, apparently largely cosmetic issue, upstream (xen-devel at lists.xen.org and linux-kernel at vger.kernel.org) Ian.

On 18 February 2013 16:32, Ian Campbell <ijc at hellion.org.uk> wrote: > On Mon, 2013-02-18 at 13:51 +0000, Gavin wrote: > > > <stumped! /> > > If the kernel hasn't changed and you are 100% sure the network > configuration before and after the reboot is the same then so am I. > > All I can suggest is to reinstall the previous version of Xen. > Thanks

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.

Package: src:xen Severity: important Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-2 I recently upgrade from Squeeze to Wheezy on a system which had the xen-linux-system-686-pae metapackage (one of two which Provides: xen-linux-system). After dist-upgrade I had the new xen-utils-common and xenstore-utils (and a few others) but not the xen-utils-4.1 or xen-hypervisor-4.1-i386 or xen-hypervisor-amd64

On Thu, 2014-05-15 at 12:44 -0700, Mike Egglestone wrote: > FWIW, > I also tried a fresh wheezy install. > Dist-upgraded to Jessie, and installed the xen-hypervisor package. > Then rebooted into the XEN 3.2 kernel that comes with wheezy. > Keyboard still doesn't work. Was that with the Jessie or Wheezy dom0 kernel? Ian.

Hi, "Ian Campbell" <ijc at hellion.org.uk> ?rta 2013-10-22 11:17-kor: > On Tue, 2013-10-22 at 11:52 +0200, PASZTOR Gyorgy wrote: > > When you use xl toolstack, you can't reboot domUs. > > When you switch back to xm toolstack, than reboot works again. > > I think the problem with the debian packaged version is the same as in > > this thread: > >

Hi Russell, Was there an underlying issue here (e.g. failure to boot or crash?) or were you just concerned by the messages? Are you able to test if this still happens with the 4.1 based hypervisor in Wheezy? Ian.

Ian Campbell <ijc at hellion.org.uk> writes: > On Sun, 2014-06-15 at 11:03 +0200, lee wrote: >> Hi, >> >> how could I get better debugging output from the dom0 kernel? > > Either configure a serial console [0] or add "noreboot" to your > *hypervisor* command line, so you can see (and perhaps > transcribe/photograph) the crash before manually

This should have gone here and not to #706233. Patch will obviously need rebasing by now... ----- Forwarded message from Ian Campbell <ijc at hellion.org.uk> ----- Date: Fri, 16 Aug 2013 14:56:49 +0100 From: Ian Campbell <ijc at hellion.org.uk> To: 706233 at bugs.debian.org Cc: control at bugs.debian.org Subject: move core dumps to /var/lib/xen/dump X-Spam-Status: No, score=-4.9

Hi Orazio, Is "NoneType object is unsubscriptable" the full and complete error message? I'd have expected some sort of accompanying backtrace, if not on the console then in /var/log/xen/* Is this issue by any chance fixed by installing the xen-qemu-dm-4.0 package? Lastly, does this happen with the packages from Wheezy? Thanks, Ian.

There's a couple of patches in 4.1 which might plausibly be the fix for this. changeset: 23246:8f927378135a user: Jan Beulich <jbeulich at suse.com> date: Wed Mar 07 08:35:58 2012 +0000 files: xen/arch/ia64/xen/domain.c xen/arch/x86/domain.c xen/arch/x86/domctl.c description: passthrough: release assigned PCI devices

Package: xcp-xapi Version: 1.3.2-9 Severity: normal Hi guys, Just a couple of things I noticed running through /usr/share/doc/xcp-xapi/README.Debian.gz as referenced by http://wiki.debian.org/XCP In "4/ Configuring Xen and XCP": sed -i "s/TOOLSTACK=/TOOLSTACK=xapi/" /etc/default/xen should be sed -i "s/TOOLSTACK=.*/TOOLSTACK=xapi/" /etc/default/xen Otherwise

Processing commands for control at bugs.debian.org: > forcemerge 587090 588888 Bug #587090 {Done: Ian Campbell <ijc at hellion.org.uk>} [xen-utils-4.0] xen-utils-4.0: Exception starting xend ('NoneType' object has no attribute 'rfind') Unable to merge bugs because: package of #588888 is 'xen-utils-common' not 'xen-utils-4.0' Failed to forcibly merge

Dropping users and adding pkg-xen-devel and debian-kernel. On Tue, 2012-11-06 at 15:43 +0100, Stephan Seitz wrote: > On Mon, Nov 05, 2012 at 06:12:53PM -0200, Henrique de Moraes Holschuh wrote: > >I would like to bring to your attention the improved support for system > >processor (CPU) microcode updates, for x86/i686/x86-64/amd64 systems > >that was recently added to

On Sun, 2014-06-15 at 13:35 +0200, lee wrote: > Ian Campbell <ijc at hellion.org.uk> writes: > > > On Sun, 2014-06-15 at 11:03 +0200, lee wrote: > >> Hi, > >> > >> how could I get better debugging output from the dom0 kernel? > > > > Either configure a serial console [0] or add "noreboot" to your > > *hypervisor* command

Processing commands for control at bugs.debian.org: > unarchive 763102 Bug #763102 {Done: Ian Campbell <ijc at debian.org>} [xen-utils-common] xen-utils-common: xen-init-list fails to parse xm output -> cannot shutdown domains with service xendomains Unarchived Bug 763102 > reopen 763102 Bug #763102 {Done: Ian Campbell <ijc at debian.org>} [xen-utils-common] xen-utils-common:

Hi Eric, I see that this happened with 3.1 kernel. Wheezy now has 3.2 which it will be releasing with, can you try that please? I'm afraid that because your kernel command line contained the "quiet" option there isn't much to go on in your video. If you can reproduce then even if you can't do serial console please do remove the quiet option. Ian.

Hi, Thanks for your answer. During the Debian jessie installation, I had a problem at grub step. The os-prober part was stuck : grub was at 66 % (os-prober tried to browse all the VM on LVM partitions) After more than 15 minutes, os-prober seems to be stuck, so I rebooted the server. I had to boot in rescue mode, then, reinstalled grub and modified it to add

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: important Dear Maintainer, We are having a problem on several Supermicro servers (I'll include more details on the configuration later) : when booting Linux 3.2 linux-image-3.2.0-4-amd64 (Wheezy) as a DOM0 on Xen 4.1 (xen-hypervisor-4.1-amd64 from Wheezy), the system hangs after : [ 3.716174] scsi1 : ata_piix [