similar to: Bug#385934: xen-hypervisor-3.0.2-1-i386: still seeing this issue

Package: xen-hypervisor-3.0.2-1-i386 Version: 3.0.2-3+hg9762-1 Severity: wishlist Hello! Shouldn't `update-grub' be run automatically after installing a `xen-hypervisor-*' package? -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to

Package: xen-hypervisor-3.0.2-1-i386 Version: 3.0.2-3+hg9762-1 Followup-For: Bug #387238 This happens on a PIII as well. Looks similar to an earlier bug report I filed (bug #385934). -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell:

Package: xen-3.0 Version: 3.0.2-3+hg9762-1 Severity: wishlist There was an error while trying to autobuild your package: > Automatic build of xen-3.0_3.0.2-3+hg9762-1 on caballero by sbuild/ia64 85 > Build started at 20060922-0812 [...] > ** Using build dependencies supplied by package: > Build-Depends: debhelper (>= 5.0.37.2), libcurl3-dev | libcurl-dev, python-dev, python

Package: xen-hypervisor-3.0.2-1-i386 Version: 3.0.2-3+hg9762-1 Severity: normal xm fails to find xen-utils, the error apears with other parameters, such as xm create. The error also apears when running "/usr/lib/xen-common/bin/xen-utils-version". Best Regards /Lars Staun Knudsen #xm list WARING! Can't find version 3.0.2-3-1 of xen utils, fallback to default version! Name

Package: xen-hypervisor-3.0.2-1-i386 Version: 3.0.2-3+hg9762-1 Severity: grave Justification: renders package unusable When booting Xen Dom0 on my Dell 2950, the kernel panics. I have been unable to get the serial console working under xen (works under normal kernels), so the best debugging info I can provide is a screenshot of the console when it dies. I will attach that after the bug is

xen-3.0_3.0.2-3+hg9762-1.diff.gz to pool/main/x/xen-3.0/xen-3.0_3.0.2-3+hg9762-1.diff.gz xen-3.0_3.0.2-3+hg9762-1.dsc to pool/main/x/xen-3.0/xen-3.0_3.0.2-3+hg9762-1.dsc xen-3.0_3.0.2-3+hg9762.orig.tar.gz to pool/main/x/xen-3.0/xen-3.0_3.0.2-3+hg9762.orig.tar.gz xen-docs-3.0_3.0.2-3+hg9762-1_all.deb to pool/main/x/xen-3.0/xen-docs-3.0_3.0.2-3+hg9762-1_all.deb (new)

FYI: The status of the xen-3.0 source package in Debian's testing distribution has changed. Previous version: 3.0.2+hg9697-2 Current version: 3.0.2-3+hg9762-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+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-i386 Version: 3.0.2+hg9697-2 Severity: grave Justification: renders package unusable Hypervisor reboots system after printing: (XEN) Xen trace buffers: disabled >From what I've found online, Xen should start booting the linux kernel at this point, but never does so. I've booted the hypervisor with the options 'noreboot' and 'sync_console' -

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-hypervisor-3.0-amd64 Version: 3.0.2+hg9697-2 Severity: normal Hi DDs, I tried to install the binaries for Xen3, AMD64 flavour on Etch. Everything seemed ok - even the menu.lst got updated nicely and autmagically. Still, after a reboot into the Xen Dom0, the machine just reboots again and again. I added 'noreboot' and made a screenshot named 'xenboot.jpg', which

Package: xen-utils-3.0.2-1 Version: 3.0.2-3+hg9762-1 Hi, while trying to get xen work, I encountered two problems: 1. I don't know if its really an error, but I think something is messed up with the subdir-name /usr/lib/xen-3.0.2-1 because the version-number of the package suggests that it is an other version, than the subdir says. Every time when I call xm for example I get: WARING!

Processing commands for control at bugs.debian.org: > reassign 389320 xen Bug #389320 [xen-3.0] xen-3.0_3.0.2-3+hg9762-1(ia64/unstable): FTBFS: please add ia64 support Warning: Unknown package 'xen-3.0' Bug reassigned from package 'xen-3.0' to 'xen'. Bug No longer marked as found in versions 3.0.2-3+hg9762-1. > thanks Stopping processing here. Please contact me if

Dear Lorenzo, Dear R list,[a] to all recipients: sorry, this email is html-against my own believes and because of inevitable constraints so far.[b] to Lorenzo: "...and I have recently update my R environment" sounds as that would be a gift of heaven! How did you manage to update and how exactly went the process of updating the whole R environment, as you put it? I turn to you since I

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

I think I remember some discussion of something in this area not too long ago on xen-devel. CC-s added. Konrad, do you know of any issues with ucode=scan in 4.4? On Wed, 2015-05-13 at 10:27 +0200, Stephan Seitz wrote: > Package: xen-hypervisor-4.5-amd64 > Version: 4.5.0-1 > Severity: normal > > Dear Maintainer, > > according to the documentation the option ucode=scan

Thanks Atom2, thanks for the refs, I've added the Debian bug and the submitter back to the CC. On Wed, 2015-05-13 at 22:11 +0200, Atom2 wrote: > Am 13.05.15 um 15:41 schrieb Ian Campbell: > > I think I remember some discussion of something in this area not too > > long ago on xen-devel. CC-s added. > I assume you refer to this discussion which happend to be on the >

Package: xen-utils-3.0.2-1 Version: 3.0.2-3+hg9762-1 >From /usr/lib/xen-3.0.2-1/lib/bin/pygrub: > sys.path = [ '/usr/lib/python' ] + sys.path > > import grub.GrubConf > import grub.fsys But grub.GrubConf, for example, is at /usr/lib/xen-3.0.2-1/lib/python/grub/GrubConf.py. Fix: change the added sys.path entry to point to /usr/lib/xen-3.0.2-1/lib/python.

Package: xen-hypervisor-4.1-amd64 Version: 4.1.3-7 Severity: important Tags: patch Dear Maintainer, The PMU may be enabled on the Dom0 although the needed MSRs are not accessible, causing at least major noise on the xen messages ring buffer. I suspect there might also be a performance decrease, because the MSR write is trapped by Xen. Once the PC is in that state, a reboot won't help. This

Package: xen-hypervisor-3.2-1-i386 Version: 3.2.0-2 Severity: normal I'm afraid this bug report will be somewhat unspecific. Please let me know what I need to do in order to extract more useful information out of xen. I have done the following to install xen: installed xen-hypervisor-3.2-1-i386, xen-utils-3.2-1, linux-image-2.6.23-1-xen-686 fixed /usr/sbin/update-grub (see bug #455706)