is the globally defined standard on my
system and thus fully expected. A few obviously had package specific
additions (i.e. python added -fPIC -fwrapv), but nothing really strange
in my view.
Any more information you require or would you want to see any such build
log for yourself?
Am 20.11.15 um 00:53 schrieb Andrew Cooper:
On 19/11/2015 20:02, Atom2 wrote:
Am 19.11.15 um 02:06 schrieb Andrew Cooper:
Thanks! That is what I was looking for.
Sadly, it is less useful than I was hoping. The guest is not appearing
to do anything interesting which causes the bad state; it
compressed, but I am sure
your are able to immeditately spot what to look for.
Thanks Atom2
build.log.gz
Description: application/gzip
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
(which you have
stripped off the suggested minimal command line) to be available.
Failing to see those devices puts those domUs into an unconfigured state
and they re-start their initial setup process.
Thanks Atom2
___
Xen-devel mailing list
Xen-devel
nd has hit the guard
page.
This means:
1) There is some bug in the stack overflow detection in the #DF handler.
2) Whatever options Gentoo compiles Xen with is sufficient to overflow
the 8K hypervisor stack.
Thanks Atom2
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Am 19.11.15 um 00:17 schrieb Andrew Cooper:
On 18/11/2015 22:51, Atom2 wrote:
Am 17.11.15 um 00:10 schrieb Atom2:
[big snip]
Hi Andrew,
as promised I have again tried with a debug build and the results are
very mixed. I initially tried to better understand what the debug USE
flag actually
Am 17.11.15 um 00:10 schrieb Atom2:
Am 17.11.15 um 00:01 schrieb Andrew Cooper:
On 16/11/2015 19:16, Atom2 wrote:
Am 16.11.15 um 16:31 schrieb Konrad Rzeszutek Wilk:
Your analysis was absolutely spot on. After re-thinking this for a
moment, I thought going down that route first would make a
Am 17.11.15 um 00:01 schrieb Andrew Cooper:
On 16/11/2015 19:16, Atom2 wrote:
Am 16.11.15 um 16:31 schrieb Konrad Rzeszutek Wilk:
Your analysis was absolutely spot on. After re-thinking this for a
moment, I thought going down that route first would make a lot of
sense
as PV guests still do
ystem up and running. Since then (January 2015) I did not find any
reason to revert the USE flag back to -system-seabios as everything was
working as expected - obviously up until now.
Thanks Atom2
emerge --info: Please see the attached file
I'm not too familiar with the xen ebuilds but I wa
ealize you will not
receive any support if you have compiled your own SeaBIOS. Virtual
machines subtly fail based on changes in SeaBIOS.
end warning from ebuild =
In any case thanks for your support, your humour (:-) and I am glad you
at least were not shocked by this infor
tributable to the missing
CONFIG_XEN option?
Andrew: I havent't gotten around to run the debug version of the
hypervisor again, but if the current suspicion turns out to be true,
there's probably not much value in that anyways. Would you agree?
Thanks Atom2
My next step was to d
Am 15.11.15 um 21:12 schrieb Doug Goldstein:
On 11/14/15 6:14 PM, Atom2 wrote:
Am 14.11.15 um 21:32 schrieb Andrew Cooper:
On 14/11/2015 00:16, Atom2 wrote:
Am 13.11.15 um 11:09 schrieb Andrew Cooper:
On 13/11/15 07:25, Jan Beulich wrote:
On 13.11.15 at 00:00, wrote:
Am 12.11.15 um 17:43
happy to give this a try as well. Would this just be a
straightforward test to see whether it works at all or would you require
debug symbols as well?
Many thanks again and best regards Atom2
[0.00] PAT configuration [0-7]: WB WT UC- UC WC WP UC UC
[0.00] Linux versi
Am 14.11.15 um 21:32 schrieb Andrew Cooper:
On 14/11/2015 00:16, Atom2 wrote:
Am 13.11.15 um 11:09 schrieb Andrew Cooper:
On 13/11/15 07:25, Jan Beulich wrote:
On 13.11.15 at 00:00, wrote:
Am 12.11.15 um 17:43 schrieb Andrew Cooper:
On 12/11/15 14:29, Atom2 wrote:
Hi Andrew,
thanks for
Am 13.11.15 um 11:09 schrieb Andrew Cooper:
On 13/11/15 07:25, Jan Beulich wrote:
On 13.11.15 at 00:00, wrote:
Am 12.11.15 um 17:43 schrieb Andrew Cooper:
On 12/11/15 14:29, Atom2 wrote:
Hi Andrew,
thanks for your reply. Answers are inline further down.
Am 12.11.15 um 14:01 schrieb Andrew
Am 12.11.15 um 17:43 schrieb Andrew Cooper:
On 12/11/15 14:29, Atom2 wrote:
Hi Andrew,
thanks for your reply. Answers are inline further down.
Am 12.11.15 um 14:01 schrieb Andrew Cooper:
On 12/11/15 12:52, Jan Beulich wrote:
On 12.11.15 at 02:08, wrote:
After the upgrade HVM domUs appear
ether prior to enabling the debug USE flag it
might make sense to re-compile with gcc-4.8.5 (please see my previous
list reply) to rule out any compiler related issues. Jan, Andrew - what
are your thoughts?
Many thanks Atom2
___
Xen-devel mailing lis
Hi Jan,
many thanks for your reply. Answers are further down inline.
Am 12.11.15 um 13:52 schrieb Jan Beulich:
On 12.11.15 at 02:08, wrote:
After the upgrade HVM domUs appear to no longer work - regardless of the
dom0 kernel (tested with both 3.18.9 and 4.1.7 as the dom0 kernel); PV
domUs, howe
which also crashes with a similar message.
Prior to the upgrade this has all worked flawlessly for a number of
months on 4.5.1. Any insight on what's going on and how to return to
proper operation would greatly be appreciated.
Many thanks in advance, Atom2
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Am 14.05.15 um 10:41 schrieb Ian Campbell:
Thanks Atom2, thanks for the refs, I've added the Debian bug and the
submitter back to the CC.
Unfortunately those recipients originally seem to have escaped my eye
... but they are included now.
On Wed, 2015-05-13 at 22:11 +0200, Atom2 wrote
h the (required)
cpio option "-H newc".
Regards Atom2
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 documenta
re).
I think that resubmission will end up being to the new colo at this
point.
Hi Ian,
wouldn't the following snippet of code actually achieve what you want:
mylink="$(readlink -f /boot/xen)"
relpath="${mylink#$(stat -c "%m" "$mylink")}"
Regards Atom2
Am 18.02.15 um 16:24 schrieb Ian Campbell:
create ^
thanks
On Thu, 2015-02-12 at 20:47 +0100, Atom2 wrote:
Hi guys,
I am forwarding this message after initially having confirmed with Ian
Campbell on the user list that there's really an issue - please see
further below.
I am currently ru
sting patches on my
version.
Thanks Atom2
Weitergeleitete Nachricht
Betreff: Re: [Xen-users] BUG? vif RX/TX byte counters limited to 32-bit
values on 64 bit systems
Datum: Mon, 9 Feb 2015 11:09:08 +
Von: Ian Campbell
An: Atom2
Kopie (CC): xen-us...@lists.xen.org
On Mon,
Ian,
Thanks again for your reply.
Am 10.11.14 um 12:16 schrieb Ian Campbell:
On Thu, 2014-11-06 at 16:11 +0100, Atom2 wrote:
Is it at all possible to recompile at least the Xen toolstack bits with
these extra gcc features disabled? Either by using the old compiler or
somehow (CFLAGS
Am 28.10.14 um 17:04 schrieb Ian Campbell:
On Tue, 2014-10-28 at 16:39 +0100, Atom2 wrote:
Please can you run the command under gdb and grab a back trace.
I have now re-compiled a few more pieces with debugging support, namely
gcc-8.4.3 and glibc and again run the command
xl create
26 matches
Mail list logo
