Search results

Hello felipe I understand your configuration as follows: - LINUX VM @host1 (the router) has some virtual NICs - all are connected to vmbr1, but specified (in proxmox GUI) with different vlan tags - eth1@vmbr1@host1 is connected to eth1@vmbr1@host2 - Windows VMs @host2 have (one or more)...

When I make in WEB-GUI "Create" -> "OVS Bond" the field "OVS Bridge" is obligatory. That means the OVS Bridge has to be configured first. I didn´t think to much why - because it wasn´t a problem for me to follow this. Note: In real life both is set up at the same time - in fact after the next...

Hello felipe, Can you give more details? The best would be to post - /etc/network/interfaces from the two hosts - how the VMs are connected to the hosts - ifconfig from the VMs - which pings (specified by IP addresses) work and which don´t work In general: With Linux bridges and vlans I...

Hello vikozo, There are different modes provided by OVS Bond and Linux Bond. And they are only partial compatible. To combine OVS Brigdes/Bonds with Linux Bridges/Bonds is partially possible (but I don´t recommend it). What you choose depends from the modes your network supports. In general I´d...

Hello 3bola, Following actions can be done via WEB-GUI: 1. go to your host-node symbol, select Network tab and Create -> Linux Bridge, e.g. vmbr1 (no further parameters) 2. stop virtual machines (if they are running) 3. go to each virtual machine, select HW tab and - Add -> Network...

Hello Airidas 1. install openvswitch - important: /etc/apt/sources.list must contain "deb http://download.proxmox.com/debian wheezy pvetest" - by apt-get install openvswitch-switch Following steps by WEB-GUI: 2. If you continue using existing physical NICs at host and IP address: remove...

Hello proxmon 1. proxmox seems to be installed definitely on /dev/sda = SSD 2. the bootloader grub is also there Suggestion: now check the installation - I recommend for this NOT to use the proxmox installation media but a powerful LINUX live media (I prefer lubuntu 14.04) 1. create a...

Hello proxmon, Note that the first device in boot order is not necessarily /dev/sda! In your case I think SSD is /dev/sda - wondering why your 1st attempt did not work - because, yes, grub-bootloader is always installed at /dev/sda - did you remove the SSD? So it should work if you boot...

Hello yetanotheruser, In general: I also have some proxmox as VM - but since proxmox is much better than vbox I use "proxmox in proxmox". In other words: My "main server" is a proxmox, and simply everything I need (workstations, servers, different OSes etc.) for my experiments are VMs in...

Hello vikozo, connect to console and define a new user (e.g. "mrholmes") as follows: useradd mrholmes passwd mrholmes <specify password> pveum useradd mrholmes@pam pveum aclmod / -roles Administrator -users mrholmes@pam Now it should be possible to login at WEB-GUI and have full access...

Hello hermelin it seems very probable that the problem is in the provider network - it blocks somehow the ARP response. To ensure this assumption tcpdump in both physical eth0 NICs would help. Obviously provider´s switches have restriction in accepting certain MAC-addresses respectively in...

Hello hermelin, do you have only one LAN connecting all VMs and nodes in the cluster, connected by eth0 resp. vmbr0? If so, traffic between guest(node1) and guest(node2) is as follows: eth0(guest-node1) ---- vethxx(node1) ---- vmbr0(node1) ---- eth0(node1) ----- eth0(node2) ---- vmbr0(node2)...

Hello 1nerdyguy An HA managed CT/VM can also be located on a local storage, you have only to ensure that it can be accessed from all nodes in the cluster by the same name, e.g. defining it as NFS share, it can be accessed as NFS also by the "localhost" (but it´s not visible as "localhost" but...

Hello paxuist, The above shows that something is not ok. But I have to declare I cannot interpret it.... What I experienced already a lot of times: changes on the "main" network-interface (i.e. which you define during installation with IP-address, hostname etc.) cause potential problems...

Hello ladmini, Unfortunately I can confirm your observation. I made an experiment as follows: In an existing wee-working cluster I "moved" (note: it´s not a physical move, just a logical one) the cliúster-node-IP from eth0 to an internal OVS port which was member of the same OVS bridge as...

Hello ladmini If you have connected a physical NIC to an ovs-bridge assigning an IP address to that NIC does not work properly any more (don´t know why, but that´s it). You have to use an internal OVS port instead (or assign the IP address to the bridge). In the current case I would change the...

Hello Andreas Get access to a qcow2 image as follows (example VM 607 disk1 on local storage, mount partition 1 in /mnt/temp): qemu-nbd --connect=/dev/nbd0 /var/lib/vz/images/607/vm-607-disk-1.qcow2 mount /dev/nbd0p1 /mnt/temp For checking repair etc. use qemu-img Have a look at...

Hello Googling "ERR_SSL_PROTOCOL_ERROR" I´ve got the impression there is a problem with SSL certificate. I am not familiar with that stuff but maybe https://pve.proxmox.com/wiki/HTTPSCertificateConfiguration from proxmox-wiki helps. For an (SSL-) expert a trace (both server and client side)...

Hello paxuist, Did you adapt /etc/hosts (and /etc/hostname) accordingly? What says netstat -l | grep 8006 ? Kind regards Mr.Holmes

Hello vincent, I guess you mean you don´t have these entries in the CT´s /etc/network/interfaces Not needed! venet0 is a peer-to-peer connection and all traffic will use this channel It´s a virtual peer-to-peer NIC and appears in both host and CT (see also my answer to your next post). I...