Search results

Having issues with "kernel:BUG: soft lockup - CPU#X stuck for 67s! [umount:xxxx]", being caused by PMX UI calling "vzctl stop xxx --fast" Container, when "shutdown -h" inside container, shuts down fine. When stopped via UI, tends to hang box. Is there any way to change the UI behavior to NOT...

On this thread ( http://forum.proxmox.com/threads/10884-USB-3-Compatibility-for-Proxmox-2-1 ) I tried to get several devices working under 2.x, and wasn't able to. I'm looking for a list of supported devices for USB3 under Proxmox 3.0 {2.6.32-20-pve} I looked under the kernel-headers, and...

I was using this guide ( http://florianjensen.com/2013/01/02/adding-flashcache-to-proxmox-and-lvm/ ) which has it working under 2.3, older kernel. Tonight I finally read the flashcache readme, and it talks about explicitly naming the kernel header path. Once I did that, magic! make...

one of the PMX3 boxes I help support is acting strange on shutdown, need to clarify function. When shutdown WITHIN the VM (vzctl enter - shutdown -h) then reboot PMX box, all is fine. When shutdown initiated from PMX (which should shutdown the containers) box will hardlock and not reboot...

Try this instead: auto bond0 iface bond0 inet manual slaves eth0 auto bond1 iface bond1 inet manual slaves eth1 auto bond2 iface bond2 inet manual slaves eth2 auto vmbr0 iface vmbr0 inet static address 10.10.10.123 netmask 255.255.255.0...

Anyone have this working yet, want to share? (Would be great to see flashcache/bcache as an install option.. seems used a lot)

Looking for kernel source (not headers) for 3.0 (pve-kernel-2.6.32-20-pve)? Where do I find them, and what are they called?

If one could start over... I'd mirror the SAS drives, install PMX there, then use the SATA drives for VM's.

Thanks for the replies.. it is something systemic to debian 7. I did a fresh db7 install into a VM, and checked the behavior of mount -n, and it works the same (the mounts show in the mtab) as proxmox3 is right now. I'll try what you suggested in the VM, see if it breaks anything. (Ironically...

I'm sorry, I feel like I'm either being unclear or talking in circles. If you look at the man page for "mount" you'll see the following entry: -n is not working in 3.0. It's writing to /etc/mtab or /proc/mounts -n worked correctly in 2.3. I'm doing research trying to figure out why, but...

The problem is not what the containers see, but what debian sees underneath. Bind mounts don't show in DF or /etc/mtab in pmx2.3, but do in pmx3.0.

You're right, that's what I see:y lrwxrwxrwx 1 root root 12 May 31 00:11 mtab -> /proc/mounts On this machine I only have a dozen or so bind mounts.. I can't imagine how crowded it must be on virtual hosting platforms with hundreds of bind mounts.... This seems like a bug, since I...

Hate to reply to my own post, but it looks like the "-n" or "--no-mtab" options are being ignored under Proxmox3 -- not sure why yet.

in pmx2.3 'bind' mounts (IE passthroughs for containers) didn't show up in the 'df'. Now, they do. makes DF kinda confusing.. any way to suppress them being listed, or am I doing this wrong? IE: /var/lib/vz/private/200 8388608 573428 7815180 7% /var/lib/vz/root/200 /dev/sda1...

[[EDIT :: after about 20 minutes, it finally started/mounted 203 and 204.. files are all there, containers started... :: ]] did the 2.3 to 3.0 upgrade, changed the network config, took a couple of reboots, but box is up, vlans are working. However, I notice that one of the openVZ containers...

Yes, thank you, that works. It appears something changed from debian6 to debian7, breaking the old way of doing dot1q/vlans. Now if I can just get 802.3ad working again.. WORKING CONFIG: <snip> auto eth1 iface eth1 inet manual auto bond1 iface bond1 inet manual slaves eth1 auto...

Because 802.3ad is broken, I had to decouple eth0/eth1, and assign eth0/bond0/vmbr0 to management so I could get back into the box while I fight with the vlans not working. root@pmx3:/etc/network# brctl show bridge name bridge id STP enabled interfaces vmbr0...

root@pmx3:~# pveversion -v pve-manager: 3.0-20 (pve-manager/3.0/0428106c) running kernel: 2.6.32-20-pve proxmox-ve-2.6.32: 3.0-100 pve-kernel-2.6.32-11-pve: 2.6.32-66 pve-kernel-2.6.32-20-pve: 2.6.32-100 pve-kernel-2.6.32-19-pve: 2.6.32-95 lvm2: 2.02.95-pve3 clvm: 2.02.95-pve3 corosync-pve...

If you're doing bonding/bridging be careful. I'm seeing issues with tun/tap interfaces after an upgrade on two different nodes in my lab. None of the KVM's will start as a result.

not to muddy the waters, but what I mean by "doesn't handle correctly" is doing something as simple as setting vmbr66 to be active on boot, then rebooting. After reboot, nothing is reachable,pingable, and the Catalyst switch it's attached to says