Search results

vi is broken on all debian versions including jessie. if you cant fix it by installing "vim-runtime", you may need to use "set nocompatible". you can either put "set nocompatible" into your $HOME/.vimrc or enter it manually after starting vi :set nocompatible (use this to edit the .vimrc)

I find people tend to shy away from the complecity and harsh limitations of DRBD in favour of better scaling and better automated storage solutions like ceph or multi-node database clusters (instead of master-slave DRBD/heartbeat replicated mysql setups). Its not that DRBD wouldnt be usable (for...

Hi, sorry if this seems a little weird, but I haven't been able to keep up with recent developments sadly. What I'm wondering is: assuming I know all the ins and outs of Ceph and want to be able to do literally everything you can do with a normal ceph cluster - can I use pveceph for this now...

you might also want to look at clusterssh/cssh: its basically input multiplexing into multiple ssh sessions. i.e. you can do the same mistake/typo on all your systems at once!

for question 1: if you have an application that requires so much CPU power, you dont want virtualisation. what you want is a HPC cluster or if you absolutely must, you could use the powerPC architecture (with either AIX or linux).

if somebody has already replaced the sshd binary.. do yourself a favour and save a lot of time by just taking the server offline. You might then want to take out all the disks and either analyse them yourself or give them to a forensics company. Theres almost no chance of getting the system...

according to the roadmap: http://pve.proxmox.com/wiki/Roadmap the newest kernel is and thats probably all we need to know. I agree that a container breakout is not a great prospect, but for anybody to able to exploit that, he would have to get access to the container first, i.e. find an...

Hi, I'm seeing a weird issue where I cannot live-migrate one specific container, all the others work just fine. The error I'm seing: Oct 22 16:00:44 Setting up checkpoint... Oct 22 16:00:44 join context.. Oct 22 16:00:44 dump... Oct 22 16:00:44 Can not dump container: Invalid...

I'm afraid this is a major design flaw in both linux and windows alike: if you give it swap space, it'll use it, regardless of the amount of free ram available. For linux this even tends to happen if you mess around with the swappiness tunable.

Of course, you just need a DHCP server in the same network the VMs end up in. Make sure to ALWAYS configure dhcp servers for static mode, i.e. MAC<->IP pairs are static.

The proxmox "operating system" does not benefit from SSDs. You only speed up the boot process, but with reboots once or twice a year that won't really matter. I.e. you can use the most basic 2x 40GB IDE drives you can find to put proxmox onto it (via RAID1). SSDs for VM storage via Ceph does...

precisely. you can virtualise loadbalancers just fine (thats why LBaaS exists) , but running an application server that needs load balancing in a VM is contradictory (due to the mentioned overhead of virtualisation)

I wasn't talking about 10GBit ethernet. The quorum disk is literally what I said: a random file on a random linux system, with a total size of 10MB, that has to be exported via iscsi.

itd probably make sense to follow up on the mailing list thread I had linked and ask there why ist not working for you since I cant see a reason why the mons should die from an altered crush map unless its got syntax errors. Also like I had mentioned, in the later post of that thread they...

IIRC is has been mentioned recently within these forums that the qemu guest agent is on the roadmap (i.e. being looked into). Ah here it is:

whoa, wait a minute. You're confusing RBDs and objects. Objects in ceph are 4MB in size by default. one RBD therefore consists of many objects. Even though this is fairly pointless since an RBD consists of so many objects that it is almost guaranteed to make use of all the placement groups...

would adding a quorum disk be feasible for your setup? thats a MUCH better solution to clustering than running a 2node cluster with expected_votes=1 Details: https://pve.proxmox.com/wiki/Two-Node_High_Availability_Cluster#Quorum_Disk_Configuration TL/DR: you need a 10MB iscsi export on a...

if you plan on getting a test setup, you're probably looking at getting 3 boxes already. If so, then just skip raid controllers and go for ceph. better, cheaper, more reliable... and generally awesome.

not true: https://security-tracker.debian.org/tracker/CVE-2014-7169

why not use the official squeeze packages? much easier solution