Search results

I am talking about booting a sane system without any failed disks but with changed (reordered) boot drives in BIOS. On a failed disk, I get your point. But if all disks are running, Grub should be able to boot from all of them. I thought Grub goes by disk UUID and BIOS boot ordering should not...

Ok, so this is on purpose. I totally understand the reason and writing Grub to a second disk in a stripe actually is unnecessary. Still, I would argument it's better to write Grub to all disks - it makes the boot process less error prone. It looks like there are already a couple of people...

It might just be a matter of wrong partitioning and bad luck in BIOS boot drive order. Please check my post about this issue with the Proxmox VE 3.4 installer under ZFS RAID-10 in a 4 disk setup...

Hi there We have now installed Proxmox VE 3.4 with ZFS RAID-1 on more than 6 servers with 2 disks each (attached to LSI 9207-8i HBAs), without any issues. On several other servers with 4 disks and ZFS RAID-10 we are experiencing the same issue as described under...

Great, Tom! Thank you very much for the fast response and working solution. I would just like to correct a terribly important word in your sentence (don't want any other readers to format their disks by mistake...): Once I'm on the shell after pressing the "Abort" button, I managed to complete...

Before we are going to switch to ZFS in production, we would like to know exactly how to recover from a failed Grub2 boot. Previously, with ext3/ext4, we could simply boot from a standard Debian netinst USB-stick, select "Rescue mode" and boot into the rescue system. The Debian netinst does even...

Hi there Are there any plans for a OpenVZ kernel 042stab094.8 release which fixes the rather nasty CVE-2014-9322? https://twitter.com/_openvz_/status/545320846621818880 https://openvz.org/Download/kernel/rhel6/042stab094.8 Thanks & Merry Christmas! Philip

Hi there When can we expect an updated OpenVZ kernel 042stab094.7 which is supposed to fix this nasty security issue?: [security] fix access to the host filesystem from inside a container (#PSBM-29594) https://twitter.com/_openvz_/status/530506859862822912...

Thanks Dietmar for reacting so fast to this vuln. Kernel is working so far for us. It's already installed on 8 of our Proxmox host nodes.

FYI: I'm running kernel 2.6.32-30-pve already since last Saturday (2014-06-21) on 10 different Proxmox VE host nodes, at two webhosting companies, without any issues! We are running 100% OpenVZ containers, no KVM so far. Thanks for your great support. Best regards, Philip

Thanks Dietmar! I just noticed you already released 2.6.32-30-pve in pve-no-subscription repository. I have tested the kernel on one server and it's working fine. Can you tell me when you're going to push this kernel into the Proxmox pve-enterprise repository. As this is security relevant, I'd...

Hi Dietmar Great, OpenVZ kernel 042stab090.4 was uploaded today. Did you already find time to build and test a new pve kernel (2.6.32-31-pve)? Best regards, Philip

Thanks Dietmar, So your recommendation is to rather wait for this to be fixed? It sounds like futex calls are completely broken. Personally I don't care about Gnome/X11 but am afraid futex is used elsewhere. Best Regards, Philip

Hi Any plans when you are going to release an updated kernel with CVE-2014-3153 fixed? CVE-2014-3153 is pretty nasty. According to OpenVZ this was fixed on 2014-06-06 in kernel 042stab090.3, https://twitter.com/_openvz_/status/474989972663988224

very very nice! Thank you for the great support. And no, I haven't tried it out yet as I'm just considering buying the LSI 9271 controller. I just wanted to make sure it won't be a hassle. Best regards, Philip

I forgot to mention I'm running Proxmox VE 3.0 on a bare metal Debian Wheezy. As recommended, I initially installed the Proxmox kernel like this: # apt-get install pve-firmware pve-kernel-2.6.32-22-pve How do I install a more recent kernel from your stable repository? Couldn't find any...

Thanks, Tom. But how about the current kernel of Proxmox VE 3.0, 2.6.32-22-pve. Will that work as well? # modinfo megaraid_sas filename: /lib/modules/2.6.32-22-pve/kernel/drivers/scsi/megaraid/megaraid_sas.ko description: LSI MegaRAID SAS Driver author: megaraidlinux@lsi.com...

re-opening that thread... What about the newly released Proxmox VE 3.0 kernel? Is there any built-in support for LSI 9271? Current stable Proxmox kernel is 2.6.32-22-pve. In the Proxmox VE 3.0 release notes I found "pve-kernel-2.6.32 2.6.32-100" - does this mean the kernel is based on the RHEL...