Search results

Hi Tyler, Yes, if you can, I'd like to have some details on what has been removed. It is certainly components that are normally running, not some that could be installed optionnally. The gain in memory usage is rather impressive, but I wonder if useful components have not been removed (it...

It is very surprising to see such a low memory usage for windows 2008 R2 machines. I installed my VMs from the vanilla microsoft 2008 R2 DVD iso. Do you have a special installation setup, which strips a lot of things from standard installation ? For every 2008 machine that I installed, the...

One thing I notice is that your configuration is not up to date, for example, my pve-manager is 1.8-18. But I don't think it is the cause of the problem. I am running 2.6.35 kernel. It can make a difference... Here some remarks : With windows 2008, it is best to use e1000 (or virtio) for NIC...

Hi Tyler, I have several (~15) VMs running Windows 2008 and 2008 R2. I just tested, and no problem to acces them through VNC console or Remote Desktop. I am using Proxmox 1.8 with kernel 2.6.35, and KVM of course, on four nodes. It should be a problem with your configuration. Can you give more...

Tom, thanks for your answer. I understand that it is useless to developp such migrations scripts before 2.0 developpement stabilizes. Alain

I have a question myself, as the lab is "full of 2.0 machines". Has the migration from 1.8 to 2.0 been already tested ? It is my main concern, as I have a 1.8 cluster in production at this moment, and fear it will not be an easy migration... Alain

See Storage Model, in the Howtos : http://pve.proxmox.com/wiki/Storage_Model Alain

CentOS or Fedora use Xen (was the case up to CentOS 6) or KVM, not openvz, if you use KVM, it is the same solution, you can transfer the VM files, modulo some configuration (bridge...). Proxmox is based on Debian. It is not configured by default, but you can configure it afterwhile. Proxmox...

I installed recently a bunch of windows 2008 R2 VM, with Proxmox 1.8, and each time installing SP1 (not by windows update, but from a service pack I downloaded), and everything went OK. So, no, I did not experienced any problem with SP1 and 2008 R2.

Hi all, As the release of Proxmox 2.0 has been posponed to Q3 (for a beta without all features...), perhaps I can make again a suggestion I made a few months ago : release à 1.9 version of current Proxmox, based on Squeeze. All the features announced for 2.0 release are very ambitious, and I...

Hi all, I just installed network virtio drivers, from iso (in latest) virtio-win-0.1-mm34.iso. So the iso name scheme is not the same, it was virtio-win-1.1.16.iso previously. I only found the network drivers under Vista subfoder (amd64 in my case). The version number is also different. It was...

Re: Ubuntu 10.04.2 KVM fresh install, inoperable w/ high events/1 usage due to virtio I hit the problem recently, with several machines running Ubuntu 10.04.2, and using virtio NIC, after a new kernel update. As was said by a previous post, converting to another NIC type, in my case, e1000...

Hi Udo, Good you have found the problem. Concerning I/O slowness, I read this link recently, for RHEL 6, which may be of interest in this context too : http://www.ilsistemista.net/index.php/virtualization/11-kvm-io-slowness-on-rhel-6.html It seems that in latest kvm/qemu the default for image...

Hi Udo, I don't know if I can help you, but perhaps can make things clearer. You said first 'All disks are on local lvm-storage', then 'If i copy the disk to local storage...'. Are your images on an external SATA disks attached on an eSATA port for example ? There can be a problem in the way...

Re: Ubuntu 10.04.2 KVM fresh install, inoperable w/ high events/1 usage due to virtio Hi, I see the same problem with an Ubuntu 10.0.4.2 VM. It's a KVM VM and I use 2.6.35 kernel. I was using it in 1.7 and upgraded with this kernel to 1.8. But it seems to not be always slow. At this moment, it...

I notice that you use "i7-2600", and not i7-2600k, as stated in first post. That is a better choice as 2600k does not support vt-d (direct i/o). See : http://ark.intel.com/Product.aspx?id=52214 and : http://ark.intel.com/Product.aspx?id=52213 But I wonder if Sandy Bridge is ready for serious...

Yes, it's not a problem with the drivers, and I had to report that. Alain

Yes, Tom said they would provide a supported path from 1.x to 2.0 : http://forum.proxmox.com/threads/5583-When-can-we-expect-a-new-proxmox-ve-version-based-on-Debian-Squeeze?p=31637#post31637 Alain

Just a follow up and an end to this thread. I just discovered a stupid error : I put the same IP address, 192.168.100.2, on the iSCSI interface (eth1) for the two nodes where the errors were happening : the PE R610 and R710. It is just a copy/paste error. My only excuse is that I did not see in...

I come back to this thread, because today, I tried to add a VM on my new node (R610), using the iSCSI storage. Until now, I had had no more error messages... As soon as I added the machine to the iSCSI storage (not even started it), the network error messages re-appeared. And, as the first...