Re: [pve-devel] Updated qemu pkg needed for Meltdown and Spectre?

seem that for spectre, cpumodel=qemu64|kvm64 is ok. but not for the 2 others cve On 04/01/2018 19:13, Alexandre DERUMIER wrote: > Thanks Paolo ! > > Do we need to update guest kernel too, if qemu use cpumodel=qemu64 ? > > (For example, I have some very old guests where kernel update is not >

Re: [pve-devel] Updated qemu pkg needed for Meltdown and Spectre?

Here we go - attached is the relevant patch - extracted from the opensuse src.rpm. Greets, Stefan Am 04.01.2018 um 19:37 schrieb Alexandre DERUMIER: > seem that for spectre, cpumodel=qemu64|kvm64 is ok. > > but not for the 2 others cve > > On 04/01/2018 19:13, Alexandre DERUMIER wrote: >>

Re: [pve-devel] Updated qemu pkg needed for Meltdown and Spectre?

ubuntu have announced kernel patch for the 9th january (4.4 && 4.13) https://insights.ubuntu.com/2018/01/04/ubuntu-updates-for-the-meltdown-spectre-vulnerabilities/ - Mail original - De: "Stefan Priebe, Profihost AG" À: "pve-devel" ,

Re: [pve-devel] Updated qemu pkg needed for Meltdown and Spectre?

On Thu, Jan 04, 2018 at 07:17:54AM +0100, Stefan Priebe - Profihost AG wrote: > Hello, > > as far as i can see at least SuSE updated qemu for Meltdown and Spectre > to provide CPUID information to the guest. > > I think we need to patch qemu as well asap? Has anybody found the > relevant

[pve-devel] Patch about Intel processors flaw

Hi list Is there any patch to PVE Kernel about Intel processors flaw?? --- Gilberto Ferreira (47) 3025-5907 (47) 99676-7530 Skype: gilberto.nunes36 ___ pve-devel mailing list pve-devel@pve.proxmox.com

Re: [pve-devel] Updated qemu pkg needed for Meltdown and Spectre?

From Paolo bonzini on qemu-devel -- _posts/ 2018-01-04 -spectre.md | 60 1 file changed, 60 insertions(+) create mode 100644 _posts/ 2018-01-04 -spectre.md diff --git a/_posts/ 2018-01-04 -spectre.md b/_posts/ 2018-01-04 -spectre.md new file mode

Re: [pve-devel] Updated qemu pkg needed for Meltdown and Spectre?

Thanks! But that means we can update the kernel on the host which makes the host and vm jumping safe BUT multi user guests are still vulnerable as long as there are no qemu patches even if the guest has a current kernel. Greets, Stefan Excuse my typo sent from my mobile phone. > Am 04.01.2018

[pve-devel] [PATCH jslint] improve jslint

include 'Proxmox' into global variables (from widget toolkit) and check all files and show the errors together at the end Signed-off-by: Dominik Csapak --- rhino.js | 31 +-- 1 file changed, 21 insertions(+), 10 deletions(-) diff --git

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

I think we basically have two kinds of networks: 1.) local networks: This is what we already have in /etc/network/interface. Access to local network is usually restricted to admins. 2.) virtual networks: Basically a linux bridge where we can connect VM to. One can connect such virtual network