I've been trying to pass a trunk port directly to a VM, however the incoming traffic does not seem to reach the bridge.
My config looks like this:
iface vmbr11 inet manual
The machine runs as a single proxmox node.
Ballooning device is enabled, but i'm using minimum memory = memory
One idea would be that i'm using writethrough for VM disk cache and that would increase the ram cache making the VM unable to start.
I've started having this error recently when i try to start a KVM. The server has enough memory available, although it seems to be used in cache.
ioctl(KVM_CREATE_VM) failed: 12 Cannot allocate memory
kvm: failed to initialize KVM: Cannot allocate memory
# free m
I'm having a problem with pvesh.
I was using the following command to create the backup jobs:
pvesh create /cluster/backup -all 1 -compress lzo -dow sun -dow tue -dow thu -enabled 1 -mode snapshot -starttime 03:00 -storage backup
However, currently it's giving the following error...
I'm trying to create a GRE tunnel so i can transfer, temporarly, some VMS from one dc to another.
I have created a gretap interface between the servers and bridged it to the vmbr1 bridge which is used on the VMs. So far so good, the traffic seems to pass well between the servers.
After i have...
How can we start or debug the start of a VM witout qm?
Because qm doesn't provide more info on what/where the issue is.
# qm start 101
malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before "(end of string)") at /usr/share/perl5/PVE/Tools.pm...
I'm having the following situation:
# zpool list
NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
rpool 3.62T 3.51T 119G - 54% 96% 1.02x ONLINE -
rpool 3.51T 2.35M 104K /rpool
rpool/ROOT 1.47G 2.35M...
Downgrading the novnc to the 4.x version seems to solve this issue, so i don't think there's any issue with the nginx, vncproxy or vncwebsocket. It seems to rest entierly on something added in the new novnc code.
Considering ebtables has been addded to proxmox, what options do we have to restrict an IP to specific IPs. Does the 5.2 version have any API option to update the ebtables for a specific VM interface?
Is there any way to use the "ipfilter" option to block everything if IP does not match...
The simplest solution is this:
iptables -A FORWARD -m physdev --physdev-out bond0.+ -p tcp -m tcp --syn --dport 25 -m hashlimit --hashlimit-above 10/min --hashlimit-mode srcip --hashlimit-name smtp-limit -j DROP
Not perfect, but stops the massive spam.
Replace bond0 with your physical...