similar to: Bug#726827: Still present in 4.3.0-3

Package: xen-utils-4.1 Version: 4.1.4-4 Severity: important Tags: patch Dear Maintainer, * What led up to the situation? Trying to start Xen on a Asus X53S laptop (which has dual Intel + Nvidia Geforce 610M Optimus graphics card) xend.log contains: [2013-10-19 17:14:26 4239] INFO (SrvDaemon:332) Xend Daemon started [2013-10-19 17:14:26 4239] INFO (SrvDaemon:336) Xend changeset: unavailable.

FYI: The status of the xen source package in Debian's testing distribution has changed. Previous version: 4.1.4-4 Current version: 4.3.0-3 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information.

I've tracked down the issue to the seabios package being updated to 1.7.4-1 from 1.7.3-3. When Xen is built with the older version, everything works fine. In fact, I bisected the issue down to the following SeaBIOS commit: http://review.coreboot.org/gitweb?p=seabios.git;a=commit;h=e144bb7af49ca8756b7222a75811f3b85b0bc1f5 I don't know if this group is interested in tracking down the

When using the 4.3.0-3/4.3.0-3+b1 xen packages from the Debian archive, things work fine. However, when we compile the xen=4.3.0-3 source package ourselves, we run into an issue launching an HVM. As soon as the HVM bios is loaded, VCPU0 gets a triple fault and the HVM is destroyed (this is with "loglvl=all guest_loglvl=all hvm_debug=3" boot options). (XEN) HVM1: Multiprocessor

Processing commands for control at bugs.debian.org: > found 751894 4.3.0-3 Bug #751894 [xen] xen: CVE-2014-4021 / XSA-100 There is no source info for the package 'xen' at version '4.3.0-3' with architecture '' Unable to make a source version for version '4.3.0-3' Marked as found in versions 4.3.0-3. > thanks Stopping processing here. Please contact me if you

Processing commands for control at bugs.debian.org: > close 726827 4.4.0-1 Bug #726827 [xen-utils-4.1] xen-utils-4.1: Xen doesn't start on a laptop with Nvidia Optimus graphics There is no source info for the package 'xen-utils-4.1' at version '4.4.0-1' with architecture '' Unable to make a source version for version '4.4.0-1' Marked as fixed in versions

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important Tags: security patch 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: http://lists.xen.org/archives/html/xen-devel/2011-09/msg01289.html I also think it's a security issue,

Processing commands for control at bugs.debian.org: > reassign 780227 src:xen Bug #780227 [xen-hypervisor-4.1-amd64] XSA-123 / CVE-2015-2151 Hypervisor memory corruption due to x86 emulator flaw Bug reassigned from package 'xen-hypervisor-4.1-amd64' to 'src:xen'. No longer marked as found in versions xen/4.1.4-1 and xen/4.1.4-3+deb7u4. No longer marked as fixed in versions

>>> On 20.01.16 at 16:01, <andreas.pflug at web.de> wrote: > Initially reported to debian > (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810964), redirected here: > > With AMD Opteron 6xxx processors, half of the memory controllers are > missing from /sys/devices/system/edac/mc > Checked with single 6120 (dual memory controller) and twin 6344 (2x dual >

Processing commands for control at bugs.debian.org: > found 570066 4.1.4-2 Bug #570066 [xen-utils-common] xen-utils-4.1: should depend on python-lxml Bug #487165 [xen-utils-common] [xen-utils-common] xm create requires python-xml to work Bug #489325 [xen-utils-common] [xen-utils-common] xm new requires python-xml to work Bug #593741 [xen-utils-common] xen-utils-4.1: should depend on

Processing commands for control at bugs.debian.org: > reassign 745419 src:xen 4.1.4-3+deb7u1 Bug #745419 [xen-utils-4.1] xen-utils-4.1: Pygrub fails to boot from LVM LV when something installed in the volume boot record Bug reassigned from package 'xen-utils-4.1' to 'src:xen'. No longer marked as found in versions xen/4.1.4-3+deb7u1. Ignoring request to alter fixed versions of

Source: xen Version: 4.3.0-1 Severity: serious Justification: FTBFS Hi New uploaded xen 4.3.0-1 FTBFS, see [1] for build log for i386. [1] https://buildd.debian.org/status/fetch.php?pkg=xen&arch=i386&ver=4.3.0-1&stamp=1378426577 Regards, Salvatore

Processing commands for control at bugs.debian.org: > found 780227 4.1.4-1 Bug #780227 [xen-hypervisor-4.1-amd64] XSA-123 / CVE-2015-2151 Hypervisor memory corruption due to x86 emulator flaw Marked as found in versions xen/4.1.4-1. > fixed 780227 4.1.4-3+deb7u5 Bug #780227 [xen-hypervisor-4.1-amd64] XSA-123 / CVE-2015-2151 Hypervisor memory corruption due to x86 emulator flaw Marked as

Package: xen-utils-4.1 Version: 4.1.4-4 Severity: normal User: mayhem at forallsecure.com Usertags: mayhem xenbaked crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/, we

Package: xen-utils-4.1 Version: 4.1.4-4 Severity: normal User: mayhem at forallsecure.com Usertags: mayhem xenctx crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/, we include

Package: xen-utils-4.1 Version: 4.1.4-4 Severity: normal User: mayhem at forallsecure.com Usertags: mayhem xentrace_setmask crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/,

Package: xen-utils-4.1 Version: 4.1.4-4 Severity: normal User: mayhem at forallsecure.com Usertags: mayhem xentrace_setsize crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/,

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Package: xen-linux-system-amd64 Version: 3.2+46 Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Package: xenwatch Version: 0.5.4-3 Package: xenstore-utils Version: 4.1.4-3+deb7u1 Package: xen-tools Version: 4.3.1-1 I installed Debian 7 (amd64) in a HX5 blade server (IBM Bladecenter H) 32 GB RAM, 2 Intel Xeon SixCore 2.Ghz, Internal

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: important Dear Maintainer, Just upgraded a Supermicro server (X9SCM-F motherboard) from Squeeze to Wheezy. And now the IPMI serial console no longer work as it used to. It hangs like this: [...] (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) Platform timer

Package: xen-utils-4.1 Version: 4.1.4-2 Severity: normal -- System Information: Debian Release: 7.0 ? APT prefers testing ? APT policy: (990, 'testing'), (500, 'testing-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages