Search results

Bump. Same issue. Pretty deadly issue to not have multicast working briefly result in total shutdown of the web interface/requiring reinstall. I dont know that mulitcast was blocked for certain, but I modified something that may have allowed it. I now see multicast traffic from the master on...

Was trying to convert a qcow2, and accidentally followed old instructions that suggested installing qemu-utils - question is why can't I reinstall the removed packages now? I removed qemu-utils and reinstalled, but the failure as above.

I accidentally didn't pay enough attention trying to get qemu-utils on the server. TL;DR: DONT INSTALL QEMU-UTILS in 4.4 I installed pve from proxmox-ve_4.4-eb2d6f1e-2.iso # pveversion pve-manager/4.4-5/c43015a5 (running kernel: 4.4.19-1-pve) # apt-get install qemu-utils Reading package...

This page refers to proxmox 2.0 and talks of ZFS in 3.4 "beta state". Not so useful. Wondering how to install an existing qcow2 vm image for prox 4.3

to make things easier for all: https://pve.proxmox.com/wiki/Package_Repositories the PVE 3.x test repo for wheezy is listed lower down and pve-kernel package has today's date.

I see for some of my containers that var/lib/vz/private/$CTID is deleted, but the containers are operational as their mounts exist in /var/lib/vz/root. The dirs under private/ are empty (but exist). $ grep 114 /proc/mounts /var/lib/vz/private/114 /var/lib/vz/root/114 simfs rw,relatime 0 0...

This is still not solved - anyone running any internal monitoring services on the CT will not be able to monitor their diskspace without direct cooperation/exposure from the host. Is there any work around for this?

This also affects google containers and is related to the veth interface structure. So this doesn't affect PVE at all? Consider this: "Our patch has been reviewed and accepted into the kernel, and is currently being backported to -stable releases back to 3.14 in different distributions (such as...

Though this is already old, can't find a thread on it here. https://tech.vijayp.ca/linux-kernel-bug-delivers-corrupt-tcp-ip-data-to-mesos-kubernetes-docker-containers-4986f88f7a19

(ie, he cant. which is a reduction in features from a VZ container where df showed the proper limit.)

How can the CT admin inside the container see his limit readily?

Sure - outside the container, but this is inside -- will the container be limited at 12GB? And even if it is, why can't the users of the container see that they're limited to 12GB in the df, like with openVZ containers in 3.4?

according to this https://forum.proxmox.com/threads/convert-physical-machine-to-lxc.23924/ you cant.

so many changes moving to proxmox 4.x wow. (Ive got some legacy Centos 4.8 and 5 here that cant easily be upgraded). Guess it's back to 3.4...

Finally figured out how to create a container on pve 4.1. (I had installed PVE4.1 on a ZFS mirror, not sure if that has anything to do with it, but I had to go and create myself another datastore, which I did as ZFS). The datastore is CTDATA: enabled, active, content = disk image,container...

My node is already online (I think, I mean, what does 'online' mean? the server is powered up and I can hit webconsole on https:8006..) - why is a reboot necessary?

When pinning many proxmox consoles in firefox or chrome, the favicon is all thats shown for the browser tab. Hard to differentiate different machines consoles til you actually load the tab fully. For unloaded/dormant tabs this becomes a heavyweight procedure to go through 4-5 tabs+ to find what...

Re: firewall not working on vm with firewall=1 on nic and fw on in firewall -> option uh turning on the firewall blocks :8006 webconsole?

Re: firewall not working on vm with firewall=1 on nic and fw on in firewall -> option Thanks!! Wow that's buried. Didnt think to look there. Esp when you hit the Firewall tab and it shows an empty list, and the tabs are at bottom (not anywhere near the top where Im clicking on my giant monitor...

Set "firewall on" on in the vm Firewall -> Options tab, and in Hardware -> NIC, and restarted VM. no go. dont see any rules in iptables -L or iptables-save. I do see rules in /etc/pve/firewall/100.fw. Pve-firewall stop && start doesnt work however. running pve-manager/3.4-6/102d4547 (running...