Search results

  1. A

    Several VLANs on single virtual LAN in KVM

    Hello, I wonder if it is possible to create some vmbr, attach it to KVM-based VM, and, inside this VM, to use it as eth0.1, eth0.8, so I can see VLAN ID in its name? See, I use several VLANs in my VM but each of it attached to separate vmbr and from inside VM I see it as separate eth's. Due to...
  2. A

    Offline migration and where settings are stored at?

    Hello, I'm in process of testing 2.0 branch. As far, everything looks nice, but I got a few questions to check before I consider migrating from my current 1.9 servers: 1. Is there are way to read and edit VM settings not from GUI? In 1.9 I can find VM config at /etc/qemu-server/*.conf file...
  3. A

    full-upgrade given strange situation

    After I removed kernel (apt-get remove ...), download pve-kernel-2.6.32-6-pve_2.6.32-53_amd64.deb (not pve-kernel-2.6.32-6-pve_2.6.32-55_amd64.deb, which is the freshest here), the system returned into working condition. But as I issue apt-get update && aptitude safe-update, it become unusable...
  4. A

    full-upgrade given strange situation

    If I was able to save all of my VM on it I'd reinstall right at that moment. How can I backup VM with settings? As I've written above I don't know where Proxmox 2.0 stores per-VM settings (nics, disks etc) What I don't understand, all versions are the same for your an my setup, so it looks...
  5. A

    full-upgrade given strange situation

    When I try to install pve-cluster and pve-manager, I see error that it cannot restart pve cluster filesystem due to lack of fuse module in kernel. Tom, please tell me how to fix it!
  6. A

    full-upgrade given strange situation

    Frankly, I missed that, thanks for pointing that out! Ok, so what can I fix the problem? I'm simply lost, please advice!
  7. A

    full-upgrade given strange situation

    Noop, I did reboot (at least 4 times) and everytime the picture is still the same. Grub given me the only choice of kernel to boot, so maybe the new kernel somehow won't update everything as intended. I tried to remove the pve-headers-2.6.32-6-pve and pve-kernel-2.6.32-6-pve, and reinstall it...
  8. A

    full-upgrade given strange situation

    Oh, sorry. Here is is: root@prox:/# pveversion -v pve-manager: not correctly installed (pve-manager/2.0/16283a5a) running kernel: 2.6.32-6-pve proxmox-ve-2.6.32: 2.0-55 pve-kernel-2.6.32-6-pve: 2.6.32-55 lvm2: 2.02.88-2pve1 clvm: 2.02.88-2pve1 corosync-pve: 1.4.1-1 openais-pve: 1.1.4-1 libqb...
  9. A

    full-upgrade given strange situation

    I tried to update Proxmox 2.0 to last version with aptitude full-upgrade, and finally got a lot of 'disagrees about version of symbol module_layout' and 'invalid module format' messages on boot, and a lot of modules won't load at startup. Both modules and kernel are 2.6.32-6-pve, and I simply...
  10. A

    VLANs won't work

    I am lucky then. But now I'm aware of that, thank you! Anyway, the solution suggested helped 100%, the only downside is that I can't setup proxmox that way from GUI (so visiting 'network setup' GUI page and pushing 'save' there will destroy network setup), hope sometime in 2.x that will be...
  11. A

    VLANs won't work

    Thank you, finally I've done what you and also udo told me, and put VLAN 1 as tagged one - ALL IS WORKING NOW! BTW any switch that "understand" VLANs can do VLAN 1 as tagged. At least I havn't seen any that can't. Thank you guys for helping me!
  12. A

    VLANs won't work

    Ok, I've tested that. tcpdump says that pings are go well from outside in and from inside out. I did ping from outside PC (10.90.90.1) to IP (10.90.90.196) that was assigned by one of VM to its internal eth NIC, and I see "arp who-has" packets from outside PC to given IP ("who-has...
  13. A

    VLANs won't work

    The story won't show its end... Now I got a lot of eth's and vmbr's (that's what I wanted), and if I want to allow some VM to communicate to VLAN 7 then I add network device linked to vmbr 7 to it and it should work... But no, it won't! I've just create linux based VM, attached several...
  14. A

    VLANs won't work

    Ok, here is the result of my findings: --- iface eth0 inet manual auto eth0.20 iface eth0.20 inet static ..address 0.0.0.0 ..netmask 0.0.0.0 auto eth0.21 iface eth0.21 inet static ..address 0.0.0.0 ..netmask 0.0.0.0 # etc for each VLAN we'll use # then...
  15. A

    VLANs won't work

    Do you mean I can not put IPs on bridges that goes to VLAN's at all? I don't need it unless from VMs, and VMs will assign their own IPs anyway... Upd: Noop, just tested that. If I remove IPs from vmbr definition then such an vmbr can not be chosen in GUI when I create new VM. Appears like I...
  16. A

    VLANs won't work

    That is, you put 0.0.0.0 on all eth's interfaces? I've seen that before but decided you've done that for security (for not showing yours IPs). Yes, I've done as you showed me and it looks like it works fine! Thank you, now will try to use it inside VMs! (Frankly maybe it worth to include such...
  17. A

    VLANs won't work

    Looks like I've made it work. If I'm right, the solution is simple: put the same IP both on eth0.X and on vmbrX interface that uses that eth0.X as bridge device. I'll try to check that once again now, but as far it sounds too fantastic for me.
  18. A

    VLANs won't work

    Just done that. Here is the config (just in case) # network interface settings auto lo iface lo inet loopback #iface eth0 inet manual auto eth1 iface eth1 inet static address 10.255.255.1 netmask 255.255.255.252 auto eth0 iface eth0 inet static address...
  19. A

    VLANs won't work

    I mean I don't have any ethX definitions in /etc/network/interfaces. Mine simple contains auto vmbr0 iface vmbr0 inet static and yours contains first auto eth0.20 iface eth0.20 inet static address 0.0.0.0 netmask 0.0.0.0 and then auto vmbr20 iface vmbr20 inet manual...
  20. A

    VLANs won't work

    Will try to, but I got no idea why VLANs won't work regular way (1 VLAN untagged and many tagged) as it works perfectly on any Linux I see. What's strange, my such a file (/etc/network/interfaces) is different, and mine was made by Proxmon GUI, I didn't edit it myself. Your refers to eth0.X...