On Tue, 14 Aug 2018, Andrew Cagney wrote:
Hugh used 'make kvm-purge' expecting it to force the VMs to be
upgraded, but it didn't. Should it.
This is how things currently work:
Too many targets. Keep it simpler.
make kvm-clean:
just clean up OBJ
make kvm-purge:
Zap all guests
make
Hugh used 'make kvm-purge' expecting it to force the VMs to be
upgraded, but it didn't. Should it.
This is how things currently work:
make kvm-clean:
zaps the local directory's test and build domains; 'make kvm-install'
will then rebuild those domains from 'clone' and since 'clone' isn't
On Tue, 14 Aug 2018 at 13:23, Paul Wouters wrote:
>
> On Tue, 14 Aug 2018, Andrew Cagney wrote:
>
> > Hugh used 'make kvm-purge' expecting it to force the VMs to be
> > upgraded, but it didn't. Should it.
> >
> > This is how things currently work:
>
> Too many targets. Keep it simpler.
>
> >
I sometimes make mistakes that cause a simple problem that shows up in a
lot of these (you've seend that today).
I would like to be able to edit the OUTPUT/*.verbose.txt files and the
OUTPUT/*.pluto.log files and have the results analyzed again.
I don't know how to do that now. I've spent a
I suspect kvmresults.py is doing what you want. It's default
behaviour is to ignore the previously generated OUTPUT/*.console.txt
and OUTPUT/*.console.diff files and instead perform the analysis using
the raw input files (the reference .console.txt, .pluto.log, and
.console.verbose.txt).
The
For test systems, we probably want to mark the guests as trusted to prevent
further slowdowns.
Paul
https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html
L1TF - L1 Terminal Fault
L1 Terminal Fault is a hardware vulnerability which allows unprivileged
speculative access to data which
On Sun, 12 Aug 2018 at 16:53, Paul Wouters wrote:
>
> On Wed, 1 Aug 2018, Andrew Cagney wrote:
>
> > Paul Wouters
> >
> > 2008-02-17 0239d2c4a bad-nexthop-01
>
> To be written (see description.txt) should get a code fix in future.
> Please leave in the list as failing
as in add it to TESTLIST as
-- Forwarded message --
Date: Tue, 14 Aug 2018 10:48:13
From: Paul Wouters
Cc: ip...@ietf.org
To: Valery Smyslov
Subject: Re: [IPsec] Fwd: [Security] Cisco Patches Its Operating Systems Against
New IKE Crypto Attack
On Tue, 14 Aug 2018, Valery Smyslov wrote:
after
Hello,
Thank you for the comments.
I have tried to address the ??? comments in ikev2_parent.c mentioned in
commit d7eb264
Please find the updated code here:
https://github.com/sahanaprasad07/libreswan/tree/rsa-sha2-plus-sha1
Let me know if any further change has to be made.
Thank you,
| From: Andrew Cagney
| (to upgrade the domains use 'make kvm-upgrade' or 'make kvm-purge
| kvm-upgrade-base-domain')
Darn.
I kicked of a test last night with only "make kvm-purge". So I guess
I still get the old version of Strongswan.
I thought kvm-purge was as hard as you could hit it.
On Tue, 14 Aug 2018 at 09:53, D. Hugh Redelmeier wrote:
>
> | From: Andrew Cagney
>
> | (to upgrade the domains use 'make kvm-upgrade' or 'make kvm-purge
> | kvm-upgrade-base-domain')
>
> Darn.
>
> I kicked of a test last night with only "make kvm-purge". So I guess
> I still get the old
On Sun, 12 Aug 2018 at 13:16, D. Hugh Redelmeier wrote:
>
> | From: Paul Wouters
>
> | This means that if you don't upgrade the guests to this, the strongswan
> | tests will fail in swan-prep since it refuses to run the test (to avoid
> | people pingponging output when they have different
I've pushed this change.
On Thu, 26 Jul 2018 at 13:11, Andrew Cagney wrote:
>
> Currently, by default, kvm-install does the following:
>
>east: make base
>east, west, north, ...: make install-base
>
> if you've lots of domains then this quickly gets very slow. However,
> with
13 matches
Mail list logo
