Search results

Hi, Just looking at the new fw feature in 3.3. My set ups are standalone non clustered instances of proxmox host. Normally: fw Host: I use shorewall, its what i'm use to. fw Guest: My guest have there own fw installed either shorewall or CSF with & without LFD, as I like the management &...

Hi, Hey! what raid card did u end up using in the R410 Thanks Garry

Hi Mylesw & udo, thanks for the replies & advice.

Hi, Just doing a fresh install of VE 2.2, standard install from iso, 2 x hdd raid 1 array. Installing a 3rd hdd for backups, non lvm - single patition drive incase of a raid or lvm issue, so I can still quickly get backups locally to the machine. I noticed a few older references relating...

Thanks for the reply Tom. But I guess the is know real benefit? as with proxmox ve being on an LVM its already giving the advantages of the LVM for snapshots & extending/adding additional drive space etc.

Just installing CentOS 5 and as a KVM guest & not paying too much attention, so default install set it up on an LVM: Q, Is this OK or should it be avoided? I'm not too switched on to LVM management & trying to learn a bit now that I'm using proxmox, as its install uses LVM for all the great...

Finally resolved with the install of the 2.6.24 kernel. :D I nearly went over to that kernel last week, before I noticed this issue, but decided to stick with the stable .18. I've confirmed this on three of my PC's, all have a different gigabyte PC type MB's. Perhaps something I may not of...

If This is only happening to me, I'm guessing it has to be a hardware driver issue, as: Both PC's run very similar hardware - Both PC's do not have this problem running Debain 5 with 2.6.31 kernel So will try moving from proxmox-ve-2.6.18 to proxmox-ve-2.6.24 kernel and see what happens...

Hi Dietmar, thanks for the reply, its a Realtek RTL8111B.

Your result is much the same as I get with both of my machines booted into a standard Debian install, standard partitioning, non LVM. But when booted in Proxmox VE, both machines produce the same slow file cp or mv speeds, they drop to about 1MB/s Appreciate any suggesting, things to look &...

see below

Hi Tom, thanks for the reply. After reading your reply I did a new install on a different PC with a new SATA drive, but I have only produced the same result. Just tested by rsync 5.1G file from /root > /var/lib/vz and will only avg a little over 1MB/s. One thing I noticed when shutdown...

I'm guessing this is an LMV issue, ProxmoxVE 1.5 default install partitions & sets up an LMV - but if I'm the only one seeing this issue, it could mean know one else has performed the default install to a single SATA drive, or that the problem is specific to me alone. I guessing that you can...

Thanks for the reply giner. I tried changing bios setting for SATA, made no difference.

Have ProxmoxVE installed & running a couple of test vm's for past 2 weeks, with no observed problems. Today converted a vmdk to .raw 10G file on our vmware server, then spc it to proxmox in the / partition by mistake, no probs, just mv it to /var/lib/vz/images , But its taken over 90 minutes...

Thanks for the reply Tom, hmm 'a quite usable OpenVZ' so not as usable as .18 ?

New to Proxmox & just setting up a few servers I normally run with vmware server. Should I install the 2.6.24 kernel ? is it regarded as stable with Proxmox ? or stick with the ProxmoxVE 1.5 standard install kernel 2.6.18 ? I intend to use both OpenVZ & KVM Thanks Garry PS The other day...