Search results

is this a module you need to load: iptables_openvpn?

i get the following email each time my backup cron runs as well as the backup email this email is from the Cron Daemon Warning: Unknown iptable module: ipt_recent, skipped however ipt_recent is working correctly within the containers so its just an annoyance in my inbox. is anyone able...

running the command you reccomended in shell provided the following issue -bash: mail: command not found i resolved my issues by reconfiguring postfix to relay via our mailserver rather than default to error

i know that and would have preferred to run the installer myself, however i was limited in that we couldnt get physical access when we needed the server installed and the only available method was PXE/Netboot which is not yet implemented by PVE so had to do a debian lenny install have resized...

ok this is slightly confusing the drive has over 1TB free, do you mean that PVE doesnt allocate about 4gb space so its unusable by the "system" but available for the lvm snapshots can you tell me the commands i need to run to resize the lvm down to make 4gb at least free space not confident...

ok so my install is on top of lenny for limitations of where our server is hosted i set up backups and they haven't been running, i looked at one of the backup logs and this is what is in it Sep 10 00:00:02 INFO: Starting Backup of VM 104 (openvz) Sep 10 00:00:02 INFO: status = CTID 104...

basically you will assign your gateway/router/firewall all the public IP's on its "WAN" interface on its lan interface you will assign a private subnet. on the router you setup direct nat/1:1 NAT so that for example vm1 with ip 192.168.1.2 gets ip 94.94.94.2 and vm2 with private ip 192.168.1.3...

you should be able to do direct nat, or 1:1 nat meaning that each private IP, will have a matching public IP i know pfsense can do 1:1 nat but cant remember about the accounting

i think the idea and the right one for proxmox is that they load the minimum needed drivers and kernel modules so that processor speed and performance is maximised for the most people.

thank you, good to know

i know with some versions of kvm you can map pci devices through to the guest so i would assume you can map serial interfaces through as well if not usb would work as well :)

i get the following entries everytime i stop or start a vm Sep 7 08:25:25 proxmox kernel: ioctl32(mount:14267): Unknown cmd fd(3) cmd(80041272){t:12;sz:4} arg(bfc6eee8) on / Sep 7 08:25:25 proxmox kernel: ioctl32(mount:14267): Unknown cmd fd(3) cmd(00001260){t:12;sz:0} arg(bfc6eef0) on /...

with this setup it would work if the host node knew what to do with the traffic sent from vm's to it you have set the gateway of the vm's to the server itself so they will be able to ping each other but without setting up some actual routing between the 2 interfaces the host node wont do...

i am stumped on this one too my thoughts would be to setup proxmox in kvm mode to take over eth0 with your main ip and provide DNAT routing for the rest of the vm's on a second virtual interface (using internal ip's and mapping them with 1:1 nat) thinking about it i am not sure how possible...

change VMID with the vm number of your problem VM eg if its 101 it should be 101.conf i think your kernel is wrong mine (latest pve version) is Linux 2.6.24-7-pve

Re: The Alias directive will probably never match because it overlaps an earlier Alia i was forced down the pve on top of lenny route so when it did its dependancy check and install it must have installed them automatically, good to know its not needed and deleting the file is no problem

Re: The Alias directive will probably never match because it overlaps an earlier Alia ah someone beat me to the question, i just deleted the symlink (as that is what it is) so that it can be reinstated if needed later on after a further update, a PVE dev maybe able to shed some light on this

if you have direct access to the machine you might be able to use one of the many recovery CD's available on the internet, if you dont have physical access to the machine then i am not sure how it is possible if you did an install on top of debian you should have the non priveleged account...

your anwser is here: http://pve.proxmox.com/wiki/Network_Model use the routed setup and plug your IP's into it

yeah i had worked that much out, really strange why adding the extra HD causes the mapping to go wrong and why it doesnt rescan (its like the scan gets interupted) anyway i solved my problem - i had to reinstall, annoyingly because there is no way of doing a PXE install of proxmox i had to...