ccia [mailto:jehan.procac...@it-sudparis.eu]
Sent: Tuesday, January 9, 2018 23:43
To: OpenVZ users ; Konstantin Bukharov ;
Vasiliy Averin
Subject: Re: [Users] X86_BUG_CPU_INSECURE
here is my repolist -v , let me know if I miss some repos ?
thanks
# yum repolist -v
Loading "fastestmirror"
[mailto:jehan.procac...@it-sudparis.eu]
Sent: Wednesday, January 10, 2018 22:59
To: Konstantin Bukharov ; OpenVZ users ;
Vasiliy Averin
Subject: Re: [Users] X86_BUG_CPU_INSECURE
you were right, waiting overnight for mirrors to get updated, now I do
have an kernel update
# uname -a
Linux 3.10.0
ttps://download.openvz.org/virtuozzo/releases/7.0/x86_64/os/repoview/
-Original Message-
From: Jehan Procaccia [mailto:jehan.procac...@it-sudparis.eu]
Sent: Tuesday, January 9, 2018 23:43
To: OpenVZ users ; Konstantin Bukharov ;
Vasiliy Averin
Subject: Re: [Users] X86_BUG_CPU_INSECURE
here is my repolis
4/os/repoview/
-Original Message-
From: Jehan Procaccia [mailto:jehan.procac...@it-sudparis.eu]
Sent: Tuesday, January 9, 2018 23:43
To: OpenVZ users ; Konstantin Bukharov ;
Vasiliy Averin
Subject: Re: [Users] X86_BUG_CPU_INSECURE
here is my repolist -v , let me know if I miss some r
018 à 20:45, Konstantin Bukharov a écrit :
Hello Jehan,
Could you provide output from your system for the next command:
yum repolist -v
From your letter it seems that you have only 'Virtuozzo Linux' repositories
configured and none for 'Virtuozzo' (aka OpenVZ).
Best regar
---
From: users-boun...@openvz.org [mailto:users-boun...@openvz.org] On Behalf Of
Jehan Procaccia
Sent: Tuesday, January 9, 2018 21:54
To: OpenVZ users ; Vasiliy Averin
Subject: Re: [Users] X86_BUG_CPU_INSECURE
Does this concern "free/not-licenced" virtuozzo 7 ?
I don't beneficiate of &
ay, January 3, 2018 6:39:10 PM
*To:* zoo...@gmail.com; OpenVZ users
*Subject:* Re: [Users] X86_BUG_CPU_INSECURE
Оригинално писмо
От: Benjamin Henrion zoo...@gmail.com
Относно: [Users] X86_BUG_CPU_INSECURE
До: "OpenVZ users list. This is THE list you need."
Изпратено на
--
>> *From:* users-boun...@openvz.org on behalf of
>> Hristo Benev
&g
---
> --
> > *From:* users-boun...@openvz.org on behalf
> of Hristo Benev
> > *Sent:* Wednesday, January 3, 2018 6:39:10 PM
> > *To:* zoo...@gmail.com; OpenVZ users
> > *Subject:* Re: [Users]
:* users-boun...@openvz.org on behalf of
>> Hristo Benev
>> *Sent:* Wednesday, January 3, 2018 6:39:10 PM
>> *To:* zoo...@gmail.com; OpenVZ users
>> *Subject:* Re: [Users] X86_BUG_CPU_INSECURE
>>
>>> Оригинално писмо
>>> От:
---
> *From:* users-boun...@openvz.org on behalf of
> Hristo Benev
> *Sent:* Wednesday, January 3, 2018 6:39:10 PM
> *To:* zoo
Greetings,
- Original Message -
> Virtuozzo will release the kernel with fix asap.
> We have it under testing right now
That's great... but... if I understood the LWN article that came out today
entitled, "Notes from the Intelpocalypse" there are three issues:
https://lwn.net/Articles/74
: [Users] X86_BUG_CPU_INSECURE
> Оригинално писмо
>От: Benjamin Henrion zoo...@gmail.com
>Относно: [Users] X86_BUG_CPU_INSECURE
>До: "OpenVZ users list. This is THE list you need."
>Изпратено на: 03.01.2018 03:02
> Hi,
>
> Just reading this:
>
> Оригинално писмо
>От: Benjamin Henrion zoo...@gmail.com
>Относно: [Users] X86_BUG_CPU_INSECURE
>До: "OpenVZ users list. This is THE list you need."
>Изпратено на: 03.01.2018 03:02
> Hi,
>
> Just reading this:
>
> https://amp.reddit.com/r/sysadmin/comments/7nl8r0/intel
On Wed, Jan 3, 2018 at 8:41 AM, Scott Dowdle wrote:
> Greetings,
> ...
> I've also read that while some other CPU arches have hardware specifically to
> avoid the issue, others may also have a similar issue. The fix is said to be
> ported to aarch64 and at least one other arch that I don't reca
Greetings,
- Original Message -
> As I understand from dasunsrule32's post, affected CPUs show a flag
> X86_BUG_CPU_INSECURE (?!).
> Does this mean that Intel is distributing CPUs marking them as
> defective?! ...or is this flag from kernel detection?
It is detected by the kernel and not
On Wed, Jan 3, 2018 at 4:19 AM, Narcis Garcia wrote:
> As I understand from dasunsrule32's post, affected CPUs show a flag
> X86_BUG_CPU_INSECURE (?!).
> Does this mean that Intel is distributing CPUs marking them as
> defective?! ...or is this flag from kernel detection?
>
> + Is somebody listing
As I understand from dasunsrule32's post, affected CPUs show a flag
X86_BUG_CPU_INSECURE (?!).
Does this mean that Intel is distributing CPUs marking them as
defective?! ...or is this flag from kernel detection?
+ Is somebody listing fixed CPU models?
Note: I suppose neither OpenVZ 6 nor LXC are
18 matches
Mail list logo