Search results

http://www.tecmint.com/ssh-passwordless-login-using-ssh-keygen-in-5-easy-steps/

Please describe your VM. Is it clean-installed or migrated from some system? Maybe, VM has scheduled shutdown jobs?

Ok, where is my config. UPS is Smart-UPS RT 2000 XL, connected to Proxmox 3.3 host with serial cable. I don't know it uses a 'secret' protocol or not, but it works very well. Set up server (host, which UPS connected to): Step 1. Enable net server mode in /etc/nut/nut.conf: MODE=netserver Step...

APC SmartUPS 1500 and 1000 connected to Proxmox host, all works with NUT. Works just fine, including email or sms notification. NUT over network also great -- notify servers to shut down when power failure occurs.

You may do 'apt get update && apt-get upgrade' and reboot your host. Then watch your VMs.

I have many CentOS 6.6 virtual machines and each of it works just well (KVM machine, not OpenVZ container). Well, let's check some things: Is your VM KVM virtual machine or OpenVZ container? How many VMs you use? Is there are all of it shutting down? How often your VM shutting down? Can you...

I mean log files inside your VMs. What OS do you use in VMs?

Please specify, what do you mean under "no success"? Backup failed? Or you have no backup jobs? Is there are any error messages in virtual machine logs?

Do you have backup jobs? If so, take a look on your backup logs.

BSODs gone. I have several Windows Server VMs (2008, 2008R2, 2012R2) on my Proxmox Server. Windows Server 2008 system crashed with BSOD once or twice in two weeks. Windows Server 2008R2 and 2012R2 was stable, I've got never BSODs with them. Recently I've got a new Supermicro server with 2 x Xeon...

Okay, I think the same way. Thank you.

I have same problem with Windows Server 2008 (not R2). Random BSODs with different error codes (0x3E, 0x101, 0x1E etc.) Tried IDE and VirtIO as disk controller, Intel and VirtIO as network card. C-states are disabled in server BIOS.

You're welcome.

FAT has 4 Gb file size limit. Try to backup on external (USB, eSATA) HDD with NTFS or EXT3/EXT4/XFS. Or try to format your USB stick into NTFS/EXT3/EXT4. Remember to safe remove your USB device.

О блин. А я что-то в мессаги и не смотрю. Давай :) Про русскоязычное сообщество не знаю.

"The easiest solution to this is to avoid NAT entirely. If you have a public IP address available for your call server, use it." That's true. If you have free public IP, you can use it within your Asterisk VM using VLAN.

C1E Support > disabled Intel C-State > disabled 7 days uptime without BSOD

I've moved Windows Server 2003 VM from VMWare server to Proxmox. It runs fine after flatting disk image, just don't forget to apply mergeide.reg to registry. To flatten, use following command in VMWare: vmware-vdiskmanager -r source.vmwarevm/source.vmdk -t 0 flat.vmdk