Search results

  1. Y

    Really impressed

    Can I just say a massive _thank_you_ to the Proxmox team. Compared to when I last used it years ago, it is significantly improved. Great job!
  2. Y

    Listing Names not CIDs

    Ah `pct` is the magic source, not `lxc` - got it. (and yes, I did `man lxc-attach` :-))
  3. Y

    Listing Names not CIDs

    Hi, i am using `lxc-attach --name CID` quite a bit bt it is getting tedious remembering the CID for the instance I want. I have given each container a memorable name (e.g. 'rclone' for the container which, you guessed it, rclones various things offsite). Is there a magic sequence of keys that...
  4. Y

    Monitoring proxmox health

    Thanks for the link. I remember researching a bunch of these a few years ago and zabbix came out the clear winner. However, OpenSource years are longer than dog years so it is worth reviewing again.
  5. Y

    Monitoring proxmox health

    Thanks udo. icinga2? - I remember when nagios was a new thing, that makes me feel old :-).
  6. Y

    Both bridge and NAT for home server?

    excellent question - of all the things I could care about this probably shouldn't be that high, but hey :-). Thanks again Jim.
  7. Y

    Both bridge and NAT for home server?

    This all comes from the fact I will have lots of little containers, add in to that the ridiculous number of electronic devices my kids and their friends (and grandparents etc) and you quickly get to the point where you have 100s of IPs floating around. It is much cleaner (to me anyway) if the...
  8. Y

    Both bridge and NAT for home server?

    Thanks Jim. The reason I want NAT is because I tend to prefer many little containers, each doing one thing, and each one wanting its own IP is getting painful. So it sounds like Proxmox has no special requirements here and another bridge with its own IP space which my real bridge...
  9. Y

    Monitoring proxmox health

    Hi, I have installed Proxmox 5 on a single server and everything looks great. I have configured backups and receiving emails about those. My question is, will proxmox also email me on smart (disk) failures/temperature warnings etc.? What about diskspace, running out of memory etc.? Thanks!
  10. Y

    Both bridge and NAT for home server?

    Nope, it is an IP assigned from my local router which itself NATs out to the internet.
  11. Y

    Both bridge and NAT for home server?

    Hi, I have installed Proxmox on top of an existing Debian server (so I can encrypt all the disks) at home and the bridged network is working well: auto lo iface lo inet loopback iface eno1 inet manual auto vmbr0 iface vmbr0 inet static address 192.168.0.31 netmask...
  12. Y

    Removal of KSM in 1.6 was a bad idea (my opinion)

    Nope - worst case is that the VMs won't start because the total memory required by the VMs is greater than the physical + swap. This is the case on my server - I have tiny hard disk but lots of SAN.
  13. Y

    Removal of KSM in 1.6 was a bad idea (my opinion)

    Yep, I have one production box whose VMs use more than the physical RAM + swap space. The others don't, but ironically I was planning on doing a re-gig of the VMs to utilise KSM - I have lots and lots of small mostly-bored Ubuntu VMs (web-servers, one-per-client). There are spread onto...
  14. Y

    Removal of KSM in 1.6 was a bad idea (my opinion)

    Please read my post again (sigh). The point is that if I did an upgrade now (or in a few days whenever) my VMs would not start because there is not enough memory or swap. That cannot correct - upgrades should do no harm. If I have to wait a different variation of the product has been...
  15. Y

    Removal of KSM in 1.6 was a bad idea (my opinion)

    Hi Dietmar, Nope, I haven't for a couple of reasons: - my servers have loads of free CPU capacity and I expect (although haven't verified!) that KSM performance being CPU and memory bound will be much faster than utilising swap on the host which is disk IO bound - my servers have a tiny...
  16. Y

    Removal of KSM in 1.6 was a bad idea (my opinion)

    However we skin it, I still think they should have handled this better. I would argue that it is a different *product* not a different version of the same product. This might be considered semantics, but it is pretty important. I don't expect to apt-get upgrade to a different product, but...
  17. Y

    Removal of KSM in 1.6 was a bad idea (my opinion)

    That is my point :) - if I cannot use the next release of a product because it has removed working functionality then that, by definition, is a step backwards. For example, I would be pretty miffed if the next version of Microsoft Word could no longer open any documents created by a previous...
  18. Y

    Removal of KSM in 1.6 was a bad idea (my opinion)

    Hi Dietmar and Tom, First off - I am not moaning - this is meant as constructive criticism. I was going to email you but I think this forum (given the recent posts) is a more appropriate place. First off, I think Proxmox is great. The work you have done is fantastic and I am very...
  19. Y

    Is the 1.6 urgent? (currently on 1.5 using the .32 kernel)

    Hi all, I have a cluster of 1.5 proxmox hosts using the .32 kernel and everything is fine. The only relevant thing that I can see on the release notes is "bug fixes"? Upgrading these hosts will be a pain because the (almost 80 VMs) need to be restarted in a certain order (i.e. the vyatta...