Search results

Sorry, I can't help you with the solution of the problem. For me it look like a issue relating to KVM, Qemu or Ubuntu. Have you tried to post this on the KVM or Qemu board? Look here: http://www.linux-kvm.org/page/Bugs

You can try "bcdedit /set {default} USEPLATFORMCLOCK on" and see if that helps you.

Maby this do not work well with KVM right now? Have you tried to post the problem on the KVM board?

Seems like the display is running in graphics mode not text mode. Probably unrelated to your problem. But I have seen the same problems on some physical windows clients when the display driver was not installed. Have you tried to close the console so it don't need to write graphics output to...

This is a very little timedrift. Very easy to correct. After investigation the problem on KVM, Xen, Microsoft and Vmware solutions I have come up with following: - It can help to add a "/usepmtimer" flag on the virtual Windows 2003 servers. Maby something similar can solve problems on Windows...

I miss the option of using Vmware Migration tool. It's a easy choice which works with all physical and virtual windows servers.

I have a virtual raw Windows 2003 drive with a lot of unpartitioned empty space. Have used VMware Migration tool to shrink this virtual drive to a lesser drive and then converted it back to raw with qemu-img command and it works. But I wonder. Is it possible to use the dd command instead? And how?

Why not try e1000 or a virtio driver?

I have upgraded to 1.6/2.6.32. So far i works well. I basically run Windows 2003 Servers in KVM. So far I works well this week. But it's to early to say. If you ask me in 6 months I will give you a better answer. :) The performance is about equal to 2.6.24. And now Windows 2008 Servers with...

Finally solved the problem. Tried installing another timekeeper, upgrading to 2.6.32 and /usepmtimer. All this didn't work. Finally found that the problem about clock ticking too fast in the guest Windows 2003 R2 Server os startet when when above 10-13 users was logged on the terminal server...

The situation have changed. I have actually upgraded the kernel to 2.6.32 since last time. Didn't understand before that 2.6.32 was the stable kernel in the 1.6 release. The main reason for the upgrade was the KVM Windows servers. Now I understand that the removal of KSM is because of the openvz.

2.6.32 is not made for production use. So the Proxmox VE team is free to do whatever they want with it. Stick to the 2.6.18 version if you don't want surprises or don't upgrade. 2.6.18 follows the newest Red Hat kernel which is good since the virtio drives is built for it. Personally I...

Update: Tried something else first. That is to use the /usepmtimer switch in boot.ini. Did run some CPU stability tests and BurnInTest with no issue. Hope this solves the problem.

I have been wondering if this have something to do with a bug in the Qemu 0.9.1 driver. Before the downgrade I used Qemu 0.11 driver. Shall try to upgrade again and see if this helps to solve the problem. The reason I did the downgrade was to get the server running on a more stable kernel. I...

Hi! I have a virtual 2003 windows terminalserver which suddenly started to behave strangely after I downgraded the Proxmox VE kernel from 2.6.24 to 2.6.18. Everything is working fine. Have had no problem now for serveral days. Suddenly the virtual windows server starts to run faster. If you...

Hi! Have upgraded to 1.5 and are now running the 2.6.24 kernel. The problem is that Windows 2008 R2 installation don't see the virtio partition even when I load the virtio drivers. Found a solution to the problem. That was to downgrade the kernel to 2.6.18. That fixed the problem but now all...

Re: Proxmox VE 1.5 released A quick question. Is this the last version of the virtio disk driver? :)-|algeir

Re: Proxmox VE 1.5 released Thank you! The new version have all I wanted! I hope I can get the windows servers on kvm to run more stable with the new version. Have experienced some unstability with the network performance and also issues with the guest clock. Looking forward to the next...

I also disabled the policy which showed the shutdown/restart button and it still worked (used that before). Thank you for help! This was really a great tip.

On my Windows 2003 servers the "qm shutdown ... " command works. But on the new Windows 2008 R2 server the shutdown command don't work. Anyone else with the same problem or a possible solution? |-|algeir