Search results

is that an unprivileged container ?

Can you check if from your host the command pct console <my_container_id> brings you a login prompt ?

this message is part of the normal boot sequence when the physical device attached to the switch is boot in promiscuous mode: [Thu Jun 22 09:10:25 2017] vmbr0: port 1(eno1) entered blocking state [Thu Jun 22 09:10:25 2017] vmbr0: port 1(eno1) entered disabled state [Thu Jun 22 09:10:25 2017]...

NB: anything urgent should be treated via the enterprise support where Developpers will provide you business day reponse guaranteed. the messages you see are only the normal activity when a VM/CT goes up and down you need to be more precise about what you mean with " server goes down often"...

hi the showmount command has to work for the NFS store to be active on the Proxmox side (we use it to check for NFS availability ) try this command pvesm nfsscan <IP_OF_NFS_SERVER> it needs to work properly ( this uses showmount in the background) if the command times out, try to execute the...

is the proxmox host meant to be the gateway, so outgoing traffic VM is traffic is supposed to reach the outside via Nic 2 ? In that case you need something similar to https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#_masquerading_nat_with_span_class_monospaced_iptables_span replace the...

you mark this thread as closed

26526KB ->25MB/s is really not that fast I got better throughput with a laptop disk connected over usb (35 MB/s)

our default configuration includes a bridge, where eth0 is attached to, what you see is the default and perfectly normal. cf https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_network_configuration now to debug your network: * try to ping the gateway * if you can ping the gateway...

> This is not a Proxmox issue, I know Thank you. Many people assume their storage problem to be Virtualization problems :) I am benchmarking ZFS with fio and the following command line fio --size=9G --bs=64k --rw=write --direct=1 --runtime=60 --name=64kwrite --group_reporting | grep bw and...

@jazzlOver 1. Having I/O wait just means: storage is the currently bottleneck for 44 % of you overall processes. When you have processes, like backup jobs, who do more reading/writing that computing this processes will always be waiting for IO. For instance this command will produce I/O wait...

he 1. you said eth1 was used for the local network in the original post ? 2. OVS is a virtual switch technology to connect the virtual NICs of the VM to your physical network, it has nothing to do with DHCP and IP adresses 3. for this you should set up a DHCP server like isc dhscp, or the...

1. are you sure the LXC NIC is on the right bridge ? (vmbr1 in your setup, and vmbr1 should contain eth1 as port member) 2. nothing special here, as long as the bridge is properly done, containes having their interface connected to the bridge will be able to connect to a DHCP server located in...

since you're using bridging mode your VM and your gateway are all connected to the same LAN, and you do no need post-up echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp post-up echo 1 > /proc/sys/net/ipv4/ip_forward also you need to add eth2 to the vmbr0 as a bridge port then * restart the...

please put the output of /etc/network/interfaces of the host and the config of the guest VM (qm config <my_vmid>)

there is the more orthodox method of calling on the command line qm rescan -vmid <VMID> to update the disk size info :) NB: I guess you understood by now that the size displayed is informative only

if you're not absolutely dependant on IPsec, I suggest your to have a look to OpenVPN in Bridge Mode, which is very well integrated in pfSense (it has a client manager) In OpenVPN bridge mode, your vpn client directly gets an IP on the LAN subnet, so you don't need to add static routes.

LVM cannot know how is the real size of the filesystems because it doesn't know about filesystems, it just knows about bytes area on the hard disk which are grouped and associated to a logical name. But you could set a target size inside the VM ( resizing from 140 to 120 GB for instance)...

I would suggest to configure your VLAN a bit simpler: * on your switch/ router, defines a trunk port, who will get all your Ethernet packets, with or without VLAN headers * on the PVE side, you do not need to configure any VLAN on the host, just make sure vmbr0 has a physical port connected to...

for this info you should have a look at the log of the backup task usually it boils down to disks where the read are slows