Search results

I ran the tests again (with and without the discard option) and the results were fairly consistent... :(

Ran some more tests, apparently this drive does not like EXT4... When I formatted the partition as EXT3 on the SSD, this is what I got... BUFFERED READS: 241.19 MB/sec (about the same as EXT4) AVG. SEEK TIME : 0.08ms (about the same as EXT4) FSYNCS/SECOND : 2827.41 (almost 20x the speed...

Re: Speed testing information... I see... No, 330MB/s with 3000+ fsync/sec is NOT bad... I would be happy with that... I'll try mounting mine with the same options and see what kind of speed I get just for comparison.

Re: Speed testing information... Correct me if I am wrong, but both of those ARE using EXT4, correct? I'm not sure I am following you...

Re: Speed testing information... @Udo - I understand, but if EXT3 doesn't support TRIM functionality, what am I support to do?

On the left side of your screen, click on Datacenter, then Click on one of your servers, click one of the drives you store your templates on (usually called 'local'), then click on the content tab, then underneath the content tab click on Templates... It should appear there... Took me forever...

Speed testing information... Some additional information I found which helps explains some things.... root@svr01:/var/lib/vz# dd if=/dev/urandom of=/dev/null bs=1K count=1024000 1024000+0 records in 1024000+0 records out 1048576000 bytes (1.0 GB) copied, 118.12 s, 8.9 MB/s So it looks as...

Ok, just running some tests here, clearly something doesn't make sense... This is on the regular HDD: root@svr01:~# pveperf / CPU BOGOMIPS: 36587.39 REGEX/SECOND: 673156 HD SIZE: 94.49 GB (/dev/mapper/pve-root) BUFFERED READS: 111.93 MB/sec AVERAGE SEEK TIME: 10.56 ms...

@Telesight - I already mentioned that in my post above, step #16 - I format the partition EXT4, step #17 I modify the /etc/fstab... Thanks though! ;)

Ok, just a quick update on what I've done so far (for those interested, and also to get feedback on my procedures). 1. I setup the 2TB drive as the boot drive (/dev/sda) and the 512GB SSD as the secondary disk (/dev/sdb). 2. I installed ProxMox as normal (didn't change any parameters during...

@Telesight - That's good, so it seems to suggest that even though the ProxMox 2.0 kernel is only 2.6.32, it has the TRIM functionality backported to it? Also, it doesn't clearly answer whether or not you have to use EXT4 to get TRIM support, or if it doesn't matter which filesystem you use...

I know I'm not the only one in this group that is looking to do something similar, I've seen lots of questions asked about SSD's, but not too many concrete answers. For now, let's forget I already have 4 ProxMox servers up and running with more than 55 virtual hosts, other than - I'm looking to...

Reading through these forums, it seems that most people prefer the QEMU/KVM solution over OpenVZ containers for their VM's, I was just curious as to why that may be? Doesn't OpenVZ provide a speed advantage, better memory management, and smaller footprint over QEMU/KVM? What are some of the...

How is the development of 2.0 coming along? Obviously we're going to miss the Q3 projection, do you have a new timeframe? Is it close, or months away?

I already know about the --script to vzdump, and I use it regularly to move backups off to our "backup" server, but I have a couple servers (Dell 1950's w/4 drives RAID-10) that don't have any extra disk space locally to make backups. Is there some way (short of NFS mounting the backup...

I supposed, except the rest of the machines on that block are accessible, it's just that one that I can't access, which is why it's wierd. I'll check with Comcast and see what they say.

Well, that's wierd... I didn't try that originally because I've had problems doing tcpdump's on guests in the past, so I just assumed... You know what that makes me.. Never the less, the guest is seeing in the incoming packets and apparently sending replies from the looks of it, but I never...

It is an OVZ machine running debian (all VMs are running debian on this box). I've compared the routing tables and network configuration between this machine and a working machine and they all look the same (sans different IP addresses, but still on the same subnet).

I have a proxmox server sitting at our data center running about 30 VM's, mixed OVZ and KVM. From every ISP I've tried except Comcast, I can access all of my VM's and run traceroutes to each one just fine... From Comcast, I can access all of my VM's except for one. Traceroutes to that VM...

And I agree! It's just not always possible to do that (Ie: Not my choice, Not in the budget, etc)...