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
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...
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...
I'm getting the following error on proxmox 5, when trying to access rrd.
pvesh get /nodes/jx213-s20/lxc/105/rrd -ds cpu -timeframe day
RRD error: Could not save png to ''
It's working well on proxmox 4.
I've just dist-upgrade today, but did not solve the issue.
Anyone's got an idea?
I've seen some vulnerabilities in qemu-kvm, that were recently patched.
For ex, CVE-2017-7980
In the redhat announcements, i saw they require a stop of all VMs for the update to take effect.
Do we need to follow the same procedure when proxmox updates the qemu? Or it's patched in...
Is there any way to filter the ARP replies?
Ex: 09:45:12.141931 ARP, Reply xx.xx.xx.xxis-at b2:cb:9f:21:38:a8, length 46
I've had today a customer attempting to use another user's IP. The firewall blocked tcp/udp etc, but he still managed to answer ARP requests making the other...
On one of my nodes, i'm unable to start few containers (that used to work).
The logs show:
lxc-start 20170413215245.766 ERROR lxc_conf - conf.c:send_fd:3794 - Too many references: cannot splice - Error sending tty fd to parent
lxc-start 20170413215245.766 ERROR lxc_conf -...
I'm periodically having issues with the lxc containers crashing the host node.
The errors on the node are the classic nmi_watchdog stuck and i believe so far i was treating the symptom instead of the cause.
Today, i had a very interesting "customer". His container was using 100% of his cpu (1...
Since few days ago, daily, i'm getting such errors. Once they start, in few minutes, the whole node crashes. I cannot run any commands, i was logged from both idrac console and ssh. The only solution so far is a reboot (but this affects my uptime a lot)
Message from syslogd@dx411-s09 at Feb 12...
I'm running the latest proxmox version on a 6 node cluster.
Today and yesterday, the cluster degraded and in all the nodes, i see this messages:
Dec 23 04:39:06 dx411-s06 kernel: [82074.269775] INFO: task pve-firewall:2668 blocked for more than 120 seconds.
Dec 23 04:39:06 dx411-s06 kernel...
I am using NAT in the provisioning part of my VM-s.
I am trying to add a public IP to access the proxmox cluster/node, however i am unable to use both public IP and NAT.
This is my configuration:
iface lo inet loopback
iface eth0 inet manual
iface eth1 inet manual
I am trying to restrict NAT guests from accessing the private network (running a NFS)
I have tried to block it via iptables, but no luck:
iptables -A FORWARD -i guest -d 10.0.0.0/8 -j DROP