Search results

Hello JBB, As far as I understood, probably yes. Here is my understanding of your configuration: The host configuration will look like: auto lo iface lo inet loopback iface eth0 inet manual auto vmbr0 iface vmbr0 inet static address xx.xx.40.157 netmask 255.255.255.0...

Hello jherazob My understanding I collected in a short diagram you find as attachment - please verify if it´s correct. Assuming "yes": So, in order to not mix it up, I defined an "outside 0" for the Proxmox´s "Own LAN" and "outside1,2,3" for the 3 extra VLANs. From the above I understood...

Hello jherazob, difficult to say without having more details. Could be considered better when available: - your LAN requirements in detail (which VMs resp. containers should use and reach which addresses) - the (current) /etc/network/interfaces from the host - the (current) configuration...

Hello proxmox_user Yes, don´t use the ovs-vsctl commands for configuring but always the web portal or the related advices in /etc/network/interfaces. Depends what you need in particular. I don´t know a tutorial, but look here...

Hello MArco No! Recently I made 10 (linked) clones from a debian using (same) LVMs. Works fine. The only one thing I had to adapt (but it´s neither a problem for/frompve nor related to LVM) was the certificate for ssl, because other connected machines in the networked complained that they used...

Hello curlingcanteen vente0 is a virtual NIC which is accessible from both host nd all containers on it. If it can be used only for internal (= host to Container and back) or for external (where host is physically conected to) connection too depends on the assigned addresses. Examples...

Hello mztriz Sorry, I made a small mistake in my previous post: if you separate wlan0 and bridge the bridge must have a different IP (Why? they are in different LANs now: one is the wlan with the default router somewhere to internet, the other your local to the VMs, which is just a virtual...

Hello vinc, You can have only one default gateway - if you want it to put it to vmbr2 delete first from vmbr1. You can name it as you like - also "xyz1" or "krixkrax", also "eth1" of course. No relation to any other NIC in any other VM /CT or host. Kind regards Mr.Holmes

Hello milkymouse, It´s just a change in terminology: Backups = VZDump backup file Can be used for both KVMs and CTs - "vzdump" is the name of the backup-program which is the same for both types. Kind regards Mr.Holmes

Hello milkymouse, Cannot imagine, I use currently 3.3-7: Yes, on command line; if you e.g. want to backupo VM 199 to directory /home/mydir/dumps it looks like: vzdump -dumpdir /home/mydir/dumps 199 Kind regards Mr.Holmes

Hello offerlam Have a look at the end of the following part of your error message kvm: -drive file=/mnt/pve/Storage01_Vms/images/116/vm-116-disk-1.qcow2,if=none,id=drive-virtio0,format=qcow2,aio=native,cache=none: could not open disk image...

Hello mrkhoros Did you have a look here: http://wiki.hetzner.de/index.php/Proxmox_VE/en ? Kind regards Mr.Holmes

Hello mztriz Regarding wlan in general: I know from my experience that wireless is always problematic in any kind of bridges - from which type ever (LINUX, OVS, VMware, VBox,...). Therefore I avoid them categorically. Even I don´t know if and how it may work in your case. Have a look here...

Hello vinc In the GUI Yes - note: if you have only containers with direct IP address you don´t need vmbr2; but I prefer also for containers use bridged virtual NICs (veth) - with venet0 sometimes unexpected effects occur. Success! Mr.Holmes

Hello offerlam, What I would do: 1. Check if cluster communication works well (by "clustat", "pvecm status" and "pvecm nodes") 2. Figure out where the VMs are really located currently, e.g. by ls /etc/pve/nodes/*/qemu-server/ and qm list at all nodes. 3. Check if the assigned...

Hello rumix, Quite understandable. "should" - but the OpenVZ developers implemented like this. If you think it is a bug report it here: https://bugzilla.openvz.org/ Honestly, I am not optimistic that it will succeed.... On the other hand: to make your own start script containing both...

Hello vinc Not quite clear how Proxmox host is connected to the router - I conclude via eth0 and an address in 10.147.42.0/24 Then the answer will be: NO - there is an overlapping between 10.147.42.0/24 and 10.147.42.192/26 Why not make a simple change from 42 to e.g. 43, like this: #...

I would not use NFS - it´s designed for LANs but not for WANs; sshfs would be a good choice (but also smb / cifs would work). In Proxmox it´s seen then simply as "Directory" storage. The topic with firewall will not be so complicate - access to port 22 (or any other, it´s configurable) to the...

Exactly! Monitor these interfaces and that´s it!

Hello rumix, No, works fine - your problem seems to be a different one Because you have a problem with your storage: /mnt/r1/prrivate/103 - probably the location of your container - is currently not availabe Container start fails immediately, i.e. before there is any opportunity to...