Search results

/vz is the default folder for OpenVZ. When you migrate containers over, that is where it puts them, despite that not being where Proxmox uses by default. I manually moved the containers over to /var/lib/vz earlier and changed the conf file to reflect the new location, but now nothing that...

Proxmox also says they're all 0KB and I just copied a 252 meg tar.gz out of one.

ah, apparently the migration tool put them on that partition, but newly created containers are on the big partition. Why?

I'm migrating a bunch of containers off an old server onto a new one. 3 of the 10 failed. I reran them and this is the console output. I'm seeing disk quota exceeded messages. I should have approximately 1.5 TB of storage and I'd wager that I don't pass 100 GB of usage. Why would I be...

I'm not sure if a different Java version would be any different. I'm not sure how to change any of that in Linux, nor if it would negatively affect the application. Well, any more than it already is. 2.6.32 may be the default, but http://pve.proxmox.com/wiki/Proxmox_VE_Kernel says that the...

I really wish people wouldn't code things in Java. I've been working with Zimbra. First I had CentOS with OpenVZ and Java had memory issues. I largely mitigated the issues, but not comfortable for a production environment. I tried CentoS with KVM and had CPU usage issues. I saw some...

I did just upgrade, however, I don't think it affected any of the kernels.

The screen had an alert about IRQ 50 and shut down that IRQ. What does that mean?

I've read a few different Zimbra related threads on here. I set it to 3072/3072 for the installation. I am splitting up my Zimbra operation to 7 different servers (2 LDAP, 2 mailbox, 2 MTA, and 1 proxy). I don't have a high load on them at all. I understand that Java allocates memory...

I did some Googling on why I had a 169.254.0.0 route, despite all interfaces having IPs assigned. I added that to the config, to remove that unnecessary route and eth1 worked as expected.

Add the following line to the end of the /etc/sysconfig/network file: NOZEROCONF=yes

I can't seem to ping out the eth1 port on this VM, but I can on other VMs where the only Ethernet port is on eth1. This is in the container: This is on the host:

The only thing I can come up with is some sort of incompatibility between the OpenVZ kernel and VLANs and the hardware I was using (which included an Intel 100).

It worked fine with standard Linux and other networking hardware off that port.

As some of you may recognize... I've been trying to get VLANs working on ProxMox for well over a year. They worked with straight Linux, but never in ProxMox. I left the project and tried a few other OpenVZ managers. Never got them to work with VLANs either. Finally, I just gave up and...

This got put on the back burner for a bit. I reinstalled with the latest kernel, etc. and am trying to get it to work again. I commented on another thread before realizing I had this one still. How would I check why it isn't processing interfaces.new upon reboot? I didn't recognize...

How do we see why interfaces.new isn't being processed?

Debian 5.03 with PVE kernel and kernel headers, no other PVE packages. Disabled onboard NIC, Intel NIC present. Pings from public Internet showing that it works fine: Since #8 showed that VLANs were working fine on both interfaces, I'll leave this up for a couple hours to make sure that...

I'll start from the top. I was having problems with bridging VLANs in PVE's web GUI to containers I tried creating VLANs inside the container. I installed CentOS and could create VLANs just fine. I installed Debian Lenny and VLANs worked just fine. I installed the PVE kernel and created the...

from dmesg, with seemingly irrelevant sections removed.: