okay, so now TigerVNC fails with authentication failure, but I have supplied both my own account credentials and root credentials, it still will not let me log in. Any idea why?
I tried using http://pve.proxmox.com/wiki/Vnc_2.0 and it doesnt work properly for me.
I have this line in inetd.conf
10101 stream tcp nowait root /usr/sbin/qm vncproxy 101
and telnetting to that port gives me the same as running this command by hand
root@dkproxmoxve1:/etc# /usr/sbin/qm...
I have had the same issue, but changing the CPU type to qemu64 as in this post seems to work http://forum.proxmox.com/threads/16379-can-t-install-windows-server-2012?p=89722#post89722
Hi
I would like to use snapshot based backup as well as rsync for efficiency and being able to scan the rsync copy with rkhunter, clamscan and such to detect problems with the guests from a safe known environment.
Okay, so create a special KVM guest for that, and edit the...
I use both KVM and OpenVZ. I use OpenVZ for uncomplicated Linux guests, I have one linux KVM guest, our VPN server, but that is because I ported it from VMware. I plan to use KVM for all the Windows guests. I like having the choice between full virtual machine virtualization and shared kernel...
I also have a server from www.supermicro.com I like them for being "bring your own disk".
CHASIS: SuperMicro CSE-216E26-R1200LPB 2U, 2x1200W PSU, 24 x 2,5", 2xSAS2 expander
MAINBOARD: SuperMicro X9DRI-LN4F+ LG2011 Retail, Dual Xeon E5-2600, Intel C602, 4xGBLAN
CPU: 2x Intel Xeon...
You are very welcome to provide a kernel package, the machine is still in burnin fase so I do not have to schedule downtime. I have changed GRUB_CMDLINE_LINUX_DEFAULT="quiet", run update-grub2 and rebooted.
I had a problem with my server. It constantly flipflopped on the connection to the NUT (Network UPS Tools) server. Also, my SSH connection to my proxmoxve server (10 meters away) was laggy and scrolled in jumps. I noticed that something in dmesg had crashed, so I rebooted and it seems like the...
My reason for setting up HA was such that if it died, then HA would automatically start it again. I have now removed the "managed by HA" and now it can start when I do it manually. Will try rebooting. After rebooting it started normally. Will manage without HA until I get a 2. server.
Before Wednesday 2012-07-25 where I applied the update http://forum.proxmox.com/threads/10408-KVM-1-1-and-new-Kernel my single OpenVZ virtual guest machine would start after a reboot. And I could start and stop it manually. After applying that update I can not even start the single OpenVZ...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.