Search results

no, not using nfs storage, this is a local disk that everything gets dumped too.. as others have mentioned, it seems to be hit or miss.. some VMs work during a scheduled backup, others do not. *sniffle* kinda makes me miss 3.4, but it is what it is and i'm sure proxmox dev team is working the issue.

was this ever solved by chance? i've just upgraded to proxmox 4.1-2 and my backups freeze my lxc containers. The backups are configured for snapshots at first, but after the first freeze i changed them to suspend, with the same issue; INFO: suspend vm ... and it hangs there.. never times out...

can you actually resolve ipv6.google.com on the host? make sure you can actually resolve ipv6.google.com first. if not, openDNS has some public IPv6 DNS servers. another thing i notice is your routes look a little wonky. specifically your default route (::/0) on your vmbr0 interface, which...

ahhhh, ok that makes sense. thanks for the clarification on that.. any idea about the console issue ? its not a big deal, i'm sure if i bang my head against it i'll figure it out...

hello folks, just upgraded from 3.4 to 4.1 and everything went rather smoothly. honestly i was expecting a late night but alas, well written directions produce excellent results.. never the less i have some issues specific to some new LXCs migrated from openVZ.. each of the 5 (restored) LXC's...