similar to: Bug#737905: closed by Bastian Blank <waldi@debian.org> (Bug#737905: fixed in xen 4.4.0-1)

Package: xen-utils-4.3 Version: 4.3.0-3 Severity: important Tags: upstream patch When using Xen compiled with seabios-1.7.4-1 (now in unstable/testing), HVMs fail immediately upon starting with a VCPU triple fault: (XEN) HVM1: Loading SeaBIOS ... (XEN) hvm.c:1253:d1 Triple fault on VCPU0 - invoking HVM shutdown action 1. This is because SeaBIOS can now be greater than 128k, which breaks an

On Wednesday 13 September 2006 16:48, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > #387238: xen-hypervisor: Xen hypervisor reboots when scrubbing ram message > is reached: confirmed on AMD64 and i386, which was filed against the > xen-hypervisor-3.0.2-1-i386 package. Hi Bastian, My conclusion is the same. I think xen-hypervisor

Processing commands for control at bugs.debian.org: > unarchive 649141 Bug #649141 {Done: Bastian Blank <waldi at debian.org>} [xen-hypervisor-4.0-amd64] xen-hypervisor-4.0-amd64: live migration fails with invalid opcode due to nonstop_tsc Unarchived Bug 649141 > End of message, stopping processing here. Please contact me if you need assistance. -- 649141:

On Sun, Dec 11, 2011 at 06:03, Debian Bug Tracking System <owner at bugs.debian.org> > ---------- Forwarded message ---------- > From:?Bastian Blank <waldi at debian.org> > > This is no bug, but actually documented. You can't migrate systems to a > cpu with lower capabilities. Out of interest, where is this documented? The debian examples would seem to indicate you

On 2012-12-11, Debian Bug Tracking System wrote: > #674907: shifts the clock by 50 minutes unexplicably under a Xen dom0 > > It has been closed by Bastian Blank <waldi at debian.org>. What about us poor users on Debian squeeze? Or worse, about the upcoming wheezy release? Is there the possibility to backport this fix to s-p-u? Should I ask release.debian.org for a freeze

@Ian Campbell: you do not receive my email? I have sent some mails to you and pkg-xen-devel at lists.alioth.debian.org reporting this problem since long time ago to some days ago. As Michael Tokarev above wrote also the build-dep should be changed to seabios >= 1.7.4-2~ I saw in git that is missed in your commit:

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

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

Control: reassign -1 src:xen On Sb, 23 aug 14, 18:18:51, Thomas Jepp wrote: > After doing a xen upgrade this morning to 4.4 I hit this same issue. > > I?ve compiled a set of test packages from this commit: http://anonscm.debian.org/cgit/pkg-xen/xen.git/commit/?h=feature/seabios&id=44daa679dc80f2df734e5471476df159bc0ad38d > > My HVM domUs now start as expected so this seems to

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Sat, 09 Aug 2014 13:09:00 +0200 Source: xen Binary: libxen-4.4 libxenstore3.0 libxen-dev xenstore-utils libxen-ocaml libxen-ocaml-dev xen-utils-common xen-utils-4.4 xen-hypervisor-4.4-amd64 xen-system-amd64 xen-hypervisor-4.4-arm64 xen-system-arm64 xen-hypervisor-4.4-armhf xen-system-armhf Architecture: source amd64 all

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Fri, 29 Aug 2014 16:33:19 +0200 Source: xen Binary: libxen-4.4 libxenstore3.0 libxen-dev xenstore-utils libxen-ocaml libxen-ocaml-dev xen-utils-common xen-utils-4.4 xen-hypervisor-4.4-amd64 xen-system-amd64 xen-hypervisor-4.4-arm64 xen-system-arm64 xen-hypervisor-4.4-armhf xen-system-armhf Architecture: source amd64 all

I've uploaded seabios 1.7.4-2 to debian archive which now ships 2 versions of the bios binary -- small 128Kb one and bios-256k.bin (with size = 256Kb, obviously). For now, both are built with Xen support. So for now, it is enough to just rebuild xen with seabios >= 1.7.4-2~ to get this fixed without patching. However, please apply the mentioned patch (or update to xen-4.3.1 version)

Qemu upstream now can be added on xen >=4.2, seabios added support for xen: seabios (1.7.1-1) unstable; urgency=low * updated to new minor upstream release (1.7.1): - native scsi boot support (Closes: #652530) - usb-attached scsi boot support - Xen support (Closes: #678042) - better integration with qemu - some bugfixes * removed fix-==-in-shell.patch (not

Il 18/05/2014 20:11, Fabio Fantoni ha scritto: > Il 17/05/2014 18:54, Fabio Fantoni ha scritto: >> Il 03/05/2014 11:30, Fabio Fantoni ha scritto: >>>> On Thu, 2014-03-06 at 14:05 +0000, Ian Campbell wrote: >>>> > Hi waldi, >>>> > >>>> > Are you planning to update the Xen package too 4.4 soon? Upstream >>>> have

Il 18/05/2014 20:11, Fabio Fantoni ha scritto: > Il 17/05/2014 18:54, Fabio Fantoni ha scritto: >> Il 03/05/2014 11:30, Fabio Fantoni ha scritto: >>>> On Thu, 2014-03-06 at 14:05 +0000, Ian Campbell wrote: >>>> > Hi waldi, >>>> > >>>> > Are you planning to update the Xen package too 4.4 soon? Upstream >>>> have

Dear Xen-Team, after an debian-update (jessie) the hvm do not start: I'm not sure it's a bug or a support-question? If it's a bug I don't know which packet is affected. <http://www.dict.cc/englisch-deutsch/affected.html> I get now response on mailing lists so it look looks like bug fore me. The hvm works fine until I did 'apt-get upgrade' ( I think on Aug 9).

Does anyone know how to view the new source in IE after an AJAX update? When I "view -> source" I get the original page source, not the page source as updated. Thanks in advance, Bill -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060403/e8d96b2e/attachment.html

Hi, When I first built my Debian package, I needed to depend on qemu-system | qemu, since there was no other ways to pull needed BIOS files. It seems the situation changed, and that I could depend on less stuff from the qemu package. Maybe only the package named "etherboot" and "vgabios". To do that, my plan is to simply package a folder named: /usr/share/xen/qemu with in

Hi, When I first built my Debian package, I needed to depend on qemu-system | qemu, since there was no other ways to pull needed BIOS files. It seems the situation changed, and that I could depend on less stuff from the qemu package. Maybe only the package named "etherboot" and "vgabios". To do that, my plan is to simply package a folder named: /usr/share/xen/qemu with in

Dear sirs, I'm trying to build an Opus library for an embedded application to run on a Microchip PIC32MX processor and I get a lot of errors in compilation time. My question is, what should be the minimum files and options needed to have such building, having in mind that only the very basic functionality in fixed point arithmetic is needed? Looking forward to your answer. Kind