Search results

By sincere appreciation to the Proxmox team before anything else. I am posting a couple of issues that could be only applicable to my set up but I am posting it in case there is a known issue: 1. The SSH using putty to the Proxmox server is quite slow and times out. This might be because of my...

I have a Proxmox version 3.4 that is connected to a Direct Access Storage and while it was accessing the file system it rebooted without leaving any traces in syslog or messages. Can any one give me some pointers to diagnose this strange behavior? It is quite puzzling. Thanks in advance.

Hello, I have once again ran into a issue installing Windows Server 2012 R2 on my Proxmox 3.4 system. The error I'm getting says: No new devices drivers were found. Make sure the installation media contains the correct drivers, and then click OK. I have the hard drive set as virtio, but have...

Microsoft is announcing end of life for Windows 2008 Server and we have not been able to install any flavors of Windows 2012 as they do not recognize any of the drive/storage. What version of Windows Server later than 2008 would you recommend and any resolution with the problem? Thanks

I have had no problems so far running a test KVM with Windows 2008 R2. This KVM has been running for a couple of weeks so far on a test Dell 2950 2 X dual core cpu with 12 GB of RAM. I am using raw disk format. Proxmox version is 3.4. What version of Proxmox are you running?

This is very unusual so I am posting this to the forum to see if others know why. The system that ran into this reporting issue is running: proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve) pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4) pve-kernel-2.6.32-26-pve: 2.6.32-114...

I found out what the problem was and fixed. The problem was Me! I had to correct the hostname after install and did not make the changed name in /etc/hosts. Regards,

Per my examination of syslog: Oct 7 13:20:08 vpshost20 pveproxy[2691]: worker 13503 finished Oct 7 13:20:08 vpshost20 pveproxy[2691]: starting 1 worker(s) Oct 7 13:20:08 vpshost20 pveproxy[2691]: worker 13506 started Oct 7 13:20:08 vpshost20 pveproxy[13506]: /etc/pve/local/pve-ssl.key...

Did an install of 3.3 and cannot reach through the browser: https://The-host-ip:8006 I tried Chrome, Firefox and IE all same result. Am I missing something? Thanks

Hi ticboy. Yes you are right and thanks so much for your reply. I posted my version to help Proxmox team to come up with fixes in the future.

Selecting e1000 as the bridge device is working without any drivers updates for now. I am copying a test 32GB directory through the network and see what happens. Just for the records I am posting my version for the Proxmox team info as well as people who have similar issues: pve-manager...

Thanks for your post tincboy. Where exactly did you download the e1000 driver for Windows 2008 R2? From Intel's site? Do you have the link?

This is getting very critical and we need to find a fix. A few mentioned here to update the driver for e1000 from Intel's site. Before trying to do so has it worked for any one?

I have the same issue. Have not tried virtio driver. Before making an effort to do so any one got e1000 working? This happens to me when I try to copy a large directory.

I am trying to understand qcow2 format better. In theory if it is copied from one VM to another it should be able to read/write without any problem right? That is not the case I am experiencing.

While I was testing the backup result of Proxmox system by simply trying to restore I noticed the following: INFO: restore QemuServer backup 'vzdump-qemu-104-2013_02_02-09_06_02.tgz' using ID 104 INFO: extracting 'qemu-server.conf' from archive INFO...

Is it important which file format you use for Windows 2008 with large data? I have used qcow2 in Proxmox 1.9 for small storage Windows 2008 system and have not experience any problems however recently noticed issues with Proxmox 2.2 testing with Windows 2008. Any other technical tips would be...

I have seen this issue with 1.xx however same in Proxmox 2.x: When we restore a VPS from a backup even though it is using a different bridged network interface as well as different IP address/subnet the original VPS becomes inaccessible. Why is that?

Udo, I see what I missed. Below which is yours is a different mirror than mine: deb http://ftp.de.debian.org/debian squeeze main contrib # PVE packages provided by proxmox.com deb http://download.proxmox.com/debian squeeze pve # security updates deb http://security.debian.org/...

Here is what does not work: deb http://ftp.us.debian.org/debian squeeze main contrib # PVE packages provided by proxmox.com deb http://download.proxmox.com/debian squeeze pve # security updates deb http://security.debian.org/ squeeze/updates main contrib