Search results

  1. S

    Meltdown and Spectre Linux Kernel fixes

    No idea of your problem. May be PVE dev will understand this. CVE-2017-5715 patched BIOS for your M630 is available...
  2. S

    Meltdown and Spectre Linux Kernel fixes

    Could you please specify the brand/model of hardware server?
  3. S

    Meltdown and Spectre Linux Kernel fixes

    Works for me with PVE 4.x. # dmesg | grep "User page tables isolation" [ 0.000000] Kernel/User page tables isolation: enabled # pveversion -v proxmox-ve: 4.4-103 (running kernel: 4.4.98-3-pve) pve-manager: 4.4-20 (running version: 4.4-20/2650b7b5) pve-kernel-4.4.98-2-pve: 4.4.98-101...
  4. S

    Meltdown and Spectre Linux Kernel fixes

    Meltdown Proof-of-Concept https://github.com/IAIK/meltdown
  5. S

    Meltdown and Spectre Linux Kernel fixes

    Warning: the first kit (PoC) for Spectre 2 is out. Say to run on one KVM and can read memory of other KVM on same host.
  6. S

    Meltdown and Spectre Linux Kernel fixes

    Meltdown available on Jessie. No yet tried. Get:1 http://security.debian.org/ jessie/updates/main linux-image-amd64 amd64 3.16+63+deb8u1 [5,844 B] Get:2 http://security.debian.org/ jessie/updates/main linux-image-3.16.0-5-amd64 amd64 3.16.51-3+deb8u1 [34.0 MB] Get:3...
  7. S

    Meltdown and Spectre Linux Kernel fixes

    For help purpose. Firmware and software Meldown / Spectre mitigation pages. HP: http://h22208.www2.hpe.com/eginfolib/securityalerts/SCAM/Side_Channel_Analysis_Method.html Dell...
  8. S

    Meltdown and Spectre Linux Kernel fixes

    Works. HP DL120-G7 boot fine without error now. And I got: [ 0.000000] Kernel/User page tables isolation: enabled
  9. S

    Meltdown and Spectre Linux Kernel fixes

    Tried on an old HP DL360-G5 with Proxmox VE 4.x with pve-kernel 4.4.98-102. Boot fine.
  10. S

    Meltdown and Spectre Linux Kernel fixes

    Hello! Be carefull, I just tried on one of our server with Proxmox VE 4.x with pve-kernel (4.4.98-102) on an HP DL120 G7 and the server crash at boot. I got this just after Grub selection and screen refresh. Reverted back to 4.4.98-101 with Grub, it work. I feel that this story will cause...
  11. S

    NFS shared directory don't mount at boot

    If someone have the problem, I solved this adding: ASYNCMOUNTNFS=no in /etc/default/rcS Now NFS shared mount at boot!
  12. S

    NFS shared directory don't mount at boot

    I replaced in the Wheezy CT /etc/network/if-up.d/mountnfs with the version used in Debian Jessie. NO change. If someone have an idea where to look as no message in log at all.
  13. S

    NFS shared directory don't mount at boot

    Seems to be a "bug" in Debian Wheezy. I upgraded the CT to Jessie and now the mount at start works. Looking to find where but may be in /etc/network/if-up.d/mountnfs
  14. S

    NFS shared directory don't mount at boot

    Hello! showmount -e and manual "mount 10.10.10.10:/data /home/data" works fine in the container. A mount using "mount /home/data" from fstab works fine too. Only the mount at start using /etc/fstab do not work.
  15. S

    NFS shared directory don't mount at boot

    Sorry if this question have already asked but I've not found the solution. I've a LXC container with Debian Wheezy (converted from OpenVZ). The NFS shared directory don't want to mount at container startup. I've added to /etc/apparmor.d/lxc/lxc-default-cgns: mount fstype=nfs, mount...
  16. S

    Base volume don't show up

    In the interval, I restarted from scratch. I deleted the iSCSI mount with the GUI and unmounted it with iscsiadm in shell. I checked, no active iSCSI sessions, nothing in pvdisplay and vgdisplay. I tried to recreate iSCSI device. The iSCSI target not show up too now... Nothing in...
  17. S

    Base volume don't show up

    Hello! I'm currently testing a server with Proxmox 3.4 with an iSCSI device. The solution is provided by ONLINE.NET, a French provider. http://www.online.net/en/dedicated-server/rpn-san The iSCSI mount / target is ok. But the LVM part don't want to work. The "Base volume" menu don't show...
  18. S

    unable to create CT / already exists

    On the 6 nodes. Node 3 and 4 have a /var/lib/vz/root/120 directory (empty). The other four node do not have the directory. Thanks.
  19. S

    unable to create CT / already exists

    Hello! It seems that my proxmox config is broken somewhere. When I create or try to restore (with another CT ID), I got this message: TASK ERROR: unable to create CT 120 - directory '/var/lib/vz/root/120' already exists ID 120 is the first available number. I curently do not have a CT...