On Fri, Jul 29, 2016 at 01:26:22PM +0200, Bastian Blank wrote:
> Hi Guido
>
> On Fri, Jul 29, 2016 at 01:13:33PM +0200, Guido Günther wrote:
> > * the complete removal of tools/ioemu-qemu-xen - guess this was unused
> > anyway since quiet some time, right?
>
> I have no idea and found not one
On Fri, Jul 29, 2016 at 10:56:28PM +, Holger Levsen wrote:
> while I'm glad that the xen upload will finally happen soon…
oh, the joys of catching up on mails and reading not all mail before
replying… in other words: thanks for the upload, Waldi! (+sorry for
assuming the worst.)
--
cheers,
Hi,
while I'm glad that the xen upload will finally happen soon…
On Fri, Jul 29, 2016 at 01:26:22PM +0200, Bastian Blank wrote:
> > If Brian has no objections feel free to upload, Please let me know once
> > done so I can then release the DLA (in case you don't want to handle it
> > youself).
>
Hi Guido
On Fri, Jul 29, 2016 at 01:13:33PM +0200, Guido Günther wrote:
> * the complete removal of tools/ioemu-qemu-xen - guess this was unused
> anyway since quiet some time, right?
I have no idea and found not one reference to that folder.
> * there are some XSA related patches in
Hi Hyacinthe
On Wed, Jul 27, 2016 at 05:41:47PM +0200, Hyacinthe Cartiaux wrote:
> I've tested in PV mode under wheezy x86_64:
Thanks about the tests.
Regards,
Bastian
--
Each kiss is as the first.
-- Miramanee, Kirk's wife, "The Paradise Syndrome",
stardate
Hello,
2016-07-26 14:22 GMT+02:00 Bastian Blank :
> I'm missing any test on Intel hardware. If this works I'll make a
> release.
I've tested in PV mode under wheezy x86_64:
* I've deployed 2 fresh dom0 (2x Intel E5-2630L) with the updated xen
packages
Hi Guido
I fixed the problem with i386. Turns out it was I way too large shift.
Fixed sources:
https://korte.credativ.com/~bbl/xen/xen_4.1.6.lts1~f5a8dc19-1.dsc
On Mon, Jul 25, 2016 at 06:57:13PM +0200, Guido Günther wrote:
> Can you give us an idea what you tested and what would be needed to
Hi Bastian,
On Mon, Jul 25, 2016 at 01:04:52PM +0200, Bastian Blank wrote:
> On Fri, Jul 22, 2016 at 10:24:27AM +0200, Raphael Hertzog wrote:
> > Why does
> > https://github.com/credativ/xen-lts/blob/lts-status/security-status.md
> > still have lots of question marks?
> > What are we waiting to
Bastian Blank writes:
> Did you get the chance to look at this source?
I think I need to see Debian sources to look at...
Actually I suspect you are not getting emails from me for some reason,
because you haven't responded to any of my recent emails to you. They do
seem to be
Hello Bastian,
On Fri, 15 Jul 2016, Bastian Blank wrote:
> On Tue, Jul 12, 2016 at 12:13:01AM +0200, Raphael Hertzog wrote:
> > On Mon, 11 Jul 2016, Bastian Blank wrote:
> > > In my tests this backport works with live migration. Can someone else
> > > give it a try?
> > >
Hi Raphael, Brian
On Fri, Jul 15, 2016 at 02:59:00PM +0200, Bastian Blank wrote:
> > So I would suggest that you go for this and provide some Xen tree free
> > of known security issues, then Brian (or someone else) can build test
> > packages and we can ask some users to test the update.
> All
Hi Bastian,
On Mon, 11 Jul 2016, Bastian Blank wrote:
> In my tests this backport works with live migration. Can someone else
> give it a try?
> https://github.com/credativ/xen-lts/tree/lts-4.1-xsa-97
If you expect people to test, you should provide packages ready to install.
But I would
On Wed, Jun 22, 2016 at 08:23:10AM +1000, Brian May wrote:
> Just wondering if you included this in version 4.1.6.1-1+deb7u2 by any
> chance?
The provided patches are incomplete, remove previous security fixes and
does not compile.
I'm currently backporting a larger bunch of the locking changes,
Brian May writes:
> It appears that we need an extra patch to get the fix for xsa97 working
> properly. See the linked Ubuntu bug report.
>
> https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1515145
>
> Just wondering if you included this in version 4.1.6.1-1+deb7u2 by any
>
; Just to be clear; you replied to the thread on version
>> xen_4.1.6.1-1+deb7u2.dsc; however I never uploaded that version. It has
>> known problems on i386.
>>
>> Maybe you meant to say you have version 4.1.6.1-1+deb7u1 ?
>>
>
> yes. i've checked. the info is abou
rror. Dom0 and Domu are Wheezy amd64.
>
> Just to be clear; you replied to the thread on version
> xen_4.1.6.1-1+deb7u2.dsc; however I never uploaded that version. It has
> known problems on i386.
>
> Maybe you meant to say you have version 4.1.6.1-1+deb7u1 ?
>
yes. i've c
Hello,
i just want to inform you, that i had a very serios regession after
upgrading to 4.1.6. Live-Migration of XEN-HVM guests ends in a dom0
crash or CPU Stuck Error. Dom0 and Domu are Wheezy amd64.
--
Best Regards
Stephan Helas
17 matches
Mail list logo