Search results

I reinstalled the system from the ProxMox bare metal ISO. The first two quotes are from the host. The second two are from the container. It could ping out to the public Internet for a while. As I did more tests to make sure everything was flowing right, it stopped and hasn't worked again...

After a bunch of getting involved with Linux's internals... I have VLANs working properly when the PVE kernel is installed into a regular Debian installation. They are recognized in the ProxMox web interface. There are plenty of misc issues with this installation, so I don't feel comfortable...

I'll give it a try in the morning. Too tired to unrack that box at 1:30 AM. ;-)

It is the integrated network controller in an Asus M2N68-VM. The chipset is NVIDIA GeForce 7050PV/nForce 630a.

I used dpkg -i to install the file you linked me to and chose it in GRUB. No network interfaces present. This contrasts with a regular ProxMox installation where the network functions without VLANs.

I followed the instructions in http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Lenny I chose the PVE kernel on reboot and not it doesn't recognize the network interfaces. I rebooted into the stock kernel and thought maybe I needed to install the kernel headers, but got this error:

I'm not sure what you need to know. Well, I'm grasping for a solution to the problem, so I'm trying different things. In another thread I was trying to create it as I am now. There are no error messages. I attempt to ping an IP address assigned to the interface. When using straight...

Is there any paid support available? Being told, "I don't know, I don't feel like looking into it, go jump off a cliff." is getting kinda old. Surely I can't have encountered 2 - 3 unexplained out there problems that no one else has had. Your site claims free enterprise class support...

I install ProxMox and setup the VLAN in the web config... no go. The vlan package is installed. 8021q is listed in lsmod, the config files are in the correct locations. This is what I did in straight Debian that worked just fine. It doesn't work on ProxMox. I even removed it from the GUI...

I have since then installed CentOS 5.4 and Debian 5.03 from DVD. In both cases, VLANs worked exactly how they were supposed to. Later today I'll reinstall ProxMox to figure out why VLANs just don't work in ProxMox.

RAID 5 is the traditional way to run enterprise class RAID. It is cost and disk space efficient compared to mirroring.

A Windows KVM that I wasn't ever able to finish installing because of the lockups uses 100% of the CPU core. I can't console in. Every time I try to install Windows, it does the same thing. I can't stop the container. I tell it to restart, and I get this:

Ideas? I'm tempted to go back to straight OpenVZ because back then, the system would work. ;-)

As far as I know, there's no way to avoid this condition. I've been battling this for about two months now through a few reinstalls and a few versions (1.3, 1.4B, and 1.4). It didn't exist when I was running 1.1. I rebooted the machine about an hour ago and I can't get into it. Second time...

I just upgraded to 1.4, since it's stable now. However, it seems to be doing the same thing. events/3 is still using 100% CPU. The system refuses to complete a restart while this condition exists.

Interesting that my response disappeared... Why is the system load at 10 and events/3 is using 100% CPU?

Ideas?

I'm not sure what that has to do with VLANs.

I reinstalled from a 1.3 CD and it ran for a few days. I didn't change anything. I added a VLAN that didn't work, so now I'm back to upgrading it again. It didn't crash after adding the VLAN. I just did an apt-get upgrade. Hopefully it stays on this time.

Same problem after installing 1.3 from CD, though I upgraded and restored the VE. Maybe I'll reinstall from CD and just leave it alone for a while. I'd like to note that I had no such trouble in 1.1.