Search results

See also this thread : http://forum.proxmox.com/threads/3312-iscsi-storage-How-to-access-logical-volume-and-raw-files?highlight=alain Alain

Hi doknet, Do you have LVM partitions inside your VM ? Then you have to use kpartx multipath tool to access logical volumes inside the VM. See for example the CentOS (Red Hat) documentation : http://www.centos.org/docs/5/html/Virtualization-en-US/ch-virt-accessing-data.html I already did...

I downloaded and installed the latest Intel driver, and indeed all is OK now. The problem with this approach is that you don't have a fully functionnal network interface after the first reboot, where you are asked to update your server. You would think with such a common interface, that windows...

Yes, the device manager shows it working, and no, I did not download the latest drivers from Intel, as I thought it was working out of the box (due to the advice to choose this device preferentially). I can try to find the latest divers and test... Alain

Hi all, I have a bunch of windows 2003 R2 (SP2) servers to migrate from Virtual server 2005 to Proxmox, two of them being domain controller, so I am cautious. I first tried with an unimportant server (applying mergeide.reg to support IDE disk, uninstalling virtual machine addition, then detect...

I am afraid you are right. I did some research. It seems you can determine if your processor is 64 bits by searching flag lm in cat /proc/cpuinfo. For example, this PE 1850 (5 years old, Xeon 3 GHz) has 64 bits support : # cat /proc/cpuinfo |grep flags flags : fpu vme de pse tsc msr...

Hi VulcanRidr, I may be wrong, bu it seems to me very unlikely that a HP DL360 with Xeon 3.2 GHz has no 64 bit support. I have myself rather old Dell PE1850 (some are 6 years old) with Xeon 3 GHz that have 64 bit support. What is the exact model of your processors ? Alain

Then, there was a problem previously. ksmd was using a lot of CPU on my three servers, even if there was a lot of memory available. I am not sure it was the default behaviour...

It is exactly the same. I don't know why it works differently in my case than in yours. Perhaps you are using relatively more memory for your VMs ? Perhaps something changed in newer releases, not using KSM when there is a lot a of memory still available ? Alain

Same versions here, but KSM is running with default configuration : # ps aux |grep ksm root 150 0.0 0.0 0 0 ? SN May23 0:00 [ksmd] root 16836 0.0 0.0 17396 904 ? S May23 0:01 /bin/bash /usr/sbin/ksmtuned But in top : PID USER PR NI VIRT...

I was using previous 2.6.32 kernel with ksmd, and saw KSM using 50-60% of CPU. I recently upgraded to new proxmox 2.6.32-2 kernel with KVM 0.12.4, and I hardly see ksmd now in top (so less than 0.1%), as reported in another thread. Perhaps new kernels solved a bug, use a different...

I also noticed (see my previous post), that ksmd, which was previously eating 50-60% of CPU is now hardly seen in top (less than 0.1%). Was there a change in this respect in the new kernel ? Alain P.S (for Ibrahim) : do you use new kernels 2.6.24 or 2.6.32 ? If you are new to proxmox, you have...

Hi everybody, Just upgraded to Kernel 2.6.32-2 and KVM 0.12.4 : # apt-get update # apt-get upgrade # apt-get dist-upgrade (for new kernel) reboot All went fine. I just had to re-activate one of my Win 2008 server (it saw hardware changes), without problem. I just noticed in the release notes...

I don't think it is the source of the problem, but it would be better and more natural to choose as ostype : ostype: w2k8 Alain

If I am correct, the 'Idle Process' is just meaning that the system is doing nothing for 98% or 99% of the load of the CPU. That is, the load is very low. See for example : http://en.wikipedia.org/wiki/System_Idle_Process Alain

Network Speed is very good, but Disk IO is disappointing. Could you post the proxmox-ve configuration you used, particularly the kernel you used (proxmox 1.5, kernel 2.6.18 ?) pveversion - v ? Could you also post the results of Proxmox proper test : pveperf -v ? Alain

vkeven, You cannot say that KVM per se is slow. I am sure that if you reproduce your tests with with a Linux machine, and virtio network and storage, you will have much better results. But I agree that virtio-win drivers should be made available, as they are under GPL. And they could be...

vkeven, I think the problem is not with KVM, but rather with the availability of signed paravirtualized drivers for Windows 2008/7. You don't precise but I think you are using paravirtualized drivers on Xen, ESX or Hyper-V for these tests ? Such Network and block device drivers exist. They...

For KVM Zero Downtime Live Migration, you need shared storage (iSCSI, Fibre Channel, NFS...). So, you don't move the image file, only the memory. Alain

Tom, Thanks for sharing this important information. So, if I understand correctly, Squeeze with new udev could only boot on kernels > 2.6.26. So you plan to stay on lenny and 2.6.18, even after Squeeze release, and go to Squeeze and 2.6.32 only when openvz is, if it is, ready for 2.6.32 ? Alain