Search results

Just got back from vacation, and happy to see I'm not the only one interested in using SSDs with Proxmox. :-) Udo, it sounds like you've had good luck with them so far, however, if you've got a lot of free space on the SSDs and low traffic, that would explain why things haven't slowed down...

So, after a bit of research, it looks like Proxmox 2.0 (if you want to use the OpenVZ kernel) will not support TRIM, which I believe is needed to use SSD in a production environment. I have recorded the rest of my notes in a related thread...

One final follow up here. I tested for TRIM support in Debian Squeeze and it still does not work with that version. Too bad... I guess that means SSD performance under Proxmox 2.0 will suffer performance degradation and probably will not be viable in a production environment. I tested TRIM...

Here's my follow up on this. Proxmox 1.8 did allow me to use the "discard" parameter in fstab, which seemed to take ok because when running "mount" it showed that the discard parameter was recognized... # mount|grep discard /dev/sdb1 on /var/lib/vz type ext4 (rw,noatime,discard)...

I just realized... Proxmox 1.8 uses the 2.6.32-33 kernel... so it seems to me that I should already be able to get ext4 and TRIM support without waiting for Proxmox 2. Seems all I would need to do is install Proxmox 1.8 on a standard HDD, and then move the /var/lib/vz over to the ext4 partition...

That's great news. We're definitely looking forward to trying out Proxmox 2 when it becomes available. :-)

Unfortunately, I just realized that Debian Squeeze is only running the 2.6.32 kernel... so, even though Proxmox 2.x will support ext4, I believe TRIM support was added in 2.6.33. So, I think this means no SSD support for Proxmox any time soon. :-(

Will OpenVZ be supported on ext4 at that point? Thanks, Curtis

I'm assuming these live migrations were KVM VMs? At least based on what I've read, live migrations no longer work for OpenVZ unless you downgrade the kernel to 2.6.18. Curtis

Fast forward to 2011... Any word on whether OpenVZ supports ext4... or whether ext3 now supports TRIM? I've done lots of googling, but mostly just confusing and conflicting advice is all I've been able to find on these questions. Curtis

Anyone have experience enabling TRIM support for SSDs under Proxmox? I am using version 1.7 at the moment... if it is supported, I would be interested to know what version it was added. This will be for OpenVZ containers... Thanks, Curtis

I was just digging around in this forum to see if the Proxmox 1.7 kernel supports trim... so far I haven't been able to confirm one way or another. But, your post does seem to imply that some version proxmox does support it... or are you just assuming that it does? Thanks, Curtis

That's great news... I've seen some describe OpenVZ as a glorified chroot (which apparently is exploitable http://www.bpfh.net/simes/computing/chroot-break.html), so that's great to hear that OpenVZ is more secure than chroot. Curtis

Can anyone tell me if OpenVZ offers any protection for the host node from a malicious user that has root access to a container? Below is a thread regarding LXC that suggests that with LXC, containers do not provide much protection, but that's LXC...

Nice work... I missed that 1.8 was released. :-) Although, the bug fix says it's being included in vzctl >= 3.0.27 so I don't think it made it into 1.8 release. However, it's not critical... I can wait until the next release. I just wanted to provide feedback on whether the bug fix worked...

Well the proposed patches are for files that do not exist on my installation... e.g. vz-gentoo.in, vz-redhat.in. Based on the content of these files, I suspect that I should choose one of these and apply them to my /etc/init.d/vz ...and since Proxmox is based on Debian, my guess is that...

Hello, Kir Kolyshkin was kind enough to create a patch for a small issue I reported here: http://bugzilla.openvz.org/show_bug.cgi?id=1814 However, I'm not entirely certain how to apply the proposed patch (http://bugzilla.openvz.org/attachment.cgi?id=1478) in a Proxmox environment. Ideas...

I'll answer my own question. I created a clean XenServer CentOS 5.4 guest, made a backup copy of it, and installed XenServer Tools on it, and then compared it to the backup and found that the following files had changed: /etc/rc.d/init.d/xe-linux-distribution...

I've successfully moved a few XenServer CentOS guests to OpenVZ containers using the P2V migration instructions. However, one question that lingers for me is whether there is any performance penalty due to the fact that the guests I migrated had XenServer Tools installed (which is supposed to...

What type of problem would it cause? Does the interface have a limit on the number of IPs it can handle? I can't think of why it would be a problem otherwise.