I just got a server and one of the options was to run proxmox on it, so I chose that.
I found this guide on low-end talk which had some great tips on it. Most importantly was the interfaces entry and network info, which I'm gonna re-print here in the event that link dies.
Put this in /etc/networks/interfaces to create a working bridge entry:
auto vmbr2
iface vmbr2 inet static
address 192.168.0.254
netmask 255.255.255.0
bridge_ports none
bridge_stp off
bridge_fd 0
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -t nat -A POSTROUTING -s '192.168.0.0/24' -o vmbr0 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -s '192.168.0.0/24' -o vmbr0 -j MASQUERADE
Then restart the server.
Use these settings when configuring VM networks:
ip : 192.168.0.1 to 192.168.0.250
subnet mask 255.255.255.0
gateway : 192.168.0.254 (ip vmbr2 on the host)
DNS: your server's DNS or google's (8.8.8.8, 8.8.4.4)
It's weird to delete proxmox virtual machines, what I do is:
ssh as root
1)delete the configuration file under /etc/pve/qemu-server
2)delete the disk image file under /var/lib/vz/images/
The web interface will refresh and the vm will be gone, as an added bonus you'll be able to re-use the node number for a new vm.
Subscribe to:
Post Comments (Atom)
automating zfs mounts -a quick and very dirty script
#!/bin/sh for x in obj xsrc src pkgsrc pkgsrc/distfiles pkgsrc/packages pkg do zfs create ext/$x zfs set mountpoint=/usr/$x ext/$x ...
-
Two days after I decided to test the -currents: --- iso_image --- mkdir -p -m 0755 /usr/src/obj/releasedir/images /usr/src/obj/tooldir.Net...
-
KVM commandline (on host): screen -S qemu06 /usr/local/bin/qemu-system-x86_64 -enable-kvm -cpu host -smp 4,cores=4,maxcpus=8 -m 2048 -net ...
-
make iso-image started at: Thu Feb 25 20:50:56 AKST 2021 make iso-image finished at: Thu Feb 25 20:51:03 AKST 2021 ===> Successful make ...
No comments:
Post a Comment