Search results

I've found patched version of bash for Squeez in link below, is it safe to be installed on Proxmox ? wget ftp://ftp.fr.debian.org/debian/pool/main/b/bash/bash_4.1-3+deb6u1_amd64.deb

Thanks, I've successfully upgrade bash to use 4.2+dfsg-0.1+deb7u1 which is Debian's officail patch for Proxmox 3 But on Proxmox 2, I'm not able to install 4.1-3+deb6u1 which is official Debian's patch via `apt-get update && apt-get upgrade` command...

https://securityblog.redhat.com/2014/09/24/bash-specially-crafted-environment-variables-code-injection-attack/ I've both Proxmox 2 and 3 in public internet, would you please let me know if there's any risk for me using Proxmox?

Does anyone applied Crashdump on Proxmox ? it's required to log panic cause in enterprise env. https://wiki.ubuntu.com/Kernel/CrashdumpRecipe

no, nothing in syslog or kern.log

It's probably a routing issue in your dedicated server, Please checkout the `route -n` and try to separate KVM IPs from OpenVZ via different subnets

I've a server which it's hardware test shows safe hardware, Temperature is fine, but server goes down everyday, When it's down the connected monitor is not showing anything, so is there any way to log panic causes?

Is there any plan on testing OvS beside Proxmox?I guess it's something that worse considering.

I've upgrade PVE to 3.2 and it's the output of my pveversion -v, but after that every API call is empty: proxmox-ve-2.6.32: 3.2-126 (running kernel: 3.2.0-4-amd64) pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1) pve-kernel-2.6.32-19-pve: 2.6.32-96 pve-kernel-2.6.32-29-pve: 2.6.32-126...

It helped so much, Would you please let me know what cache method is better for this kind of attach device?

-device virtio-blk-pci,drive=drive-virtio0,id=virtio0,.......,x-data-plane=on . I was not able to use this switch, would you please let me know complete sample of it's usage with Proxmox 3.2 ?

I was not able to use this switch, would you please let me know complete sample of it's usage with Proxmox 3.2 ?

Guest is using ext3 too, and I'm using the same dd command to perform the test It's hardware raid and it's model is: "Supermicro AOC-USAS2LP-H8iR"

It's Supermicro RAID 10, I don't guess it's something wrong with RAID controller. because in the host OS, Performance is fine.

I'm using CentOS 6 x64 as guest OS, and the VM has 16GB memory with 16 cores of Xeon CPU, I guess if I could make the VM to have direct IO access to underlying storage device the issue can be fixed, isn't it? Is it possible in proxmox to directy connect the device to VM?

No, I'm using ext3, which one is better for SSD performance?

I've just installed Proxmox on my new server which has a RAID 10 containing 4 ADATA 256 GB SSD drives, I've tried to test out write speed on my new server which wrote by speed of 538 MB/s, but running the same test on a KVM VM on top of the same disk, show 1/4 performance I'm using VIRTIO for...

I've server which today has been rebooted after 210 days of uptime,After reboot I can see only Windows 2003 guests have trouble booting up and they are showing blue screen,In syslogs I can see right after reach bluescreen there is a line like belowkvm: 21390: cpu0 unhandled rdmsr: 0x2cmy...

I've Proxmox VE server which goes down randomly, I've changed it's hardware and I'm sure there's no temperature issue with the server, so my guess is there's a software issue maybe, How can I make proper logs to find out what is the problem with kernel?

Where I can find the CA cert to install on my PC?