Search results

please search to forums, this has been discussed several times i would recommend to stop the vm.

Latest drivers: http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers for changing the disk drivers: -add another virtio disk -stop/start -install the new drivers -stop -remove harddisk -change ide0 to virtio in qemu conf files (also change the boot device) and change the...

i checked it on another production server, but the newest virtio drivers did most of the job check out "qemu-img convert" to convert, but stick to newest virtio drivers

i also can't get a USB paging transmitter working inside a windows VM. maybe it's again related to serial bus issues, because it is identified as COM5. i posted in another thread that serial device passthrough also does not work 100%. the vendor of the device does not want to support virtual...

today i converted all windows vms from qcow2 to raw and installed the latest virtio storage drivers. then i changed the disk to virtio and this was a HUGE performance boost at all!

I shut down the Windows XP VM on a bigger machine and like i thought the vzdump backup took only 2 hrs instead of 5 hrs. i have 3 proxmox servers running and two have the latest build installed. two servers have this problem. the bigger machine can cope with the i/o loads because of the better...

The question still is, if there is a configuration issue or a general problem. I feel relieved that the one host is working again, because i really got into trouble with the users. maybe one could try to install a latest proxmox installation without a raid and maybe a slow external USB disk to...

i would love to see an official statement. there are several threads with the same issue. on some hosts the raid controllers do have so much performance that i did not even recognize the problem. the host, which i downgraded yesterday still works. no complaints anymore. now i do not knwo if i...

after 10 hours i see no i/o peaks anymore with this kernel

2.6.24-5-pve runs since 10 hours like a charm!

i replaced the hardware with a physical server and the serial port works like it should be. there is definately a problem with the serial port passthrough. i found several bugs reported on the KVM mailiung list but no solution yet. like mentioned in another thread USB passthrough does not work...

i think 2.6.24-5-pve improved the situation a bit. it still happens, but less.

http://pve.proxmox.com/wiki/Backup_-_Restore_-_Live_Migration use vzdump --restore <filename> <VM_ID> or man vzdump

its charon... 1)use the grub manpage to see how you manage kernel boots 2) i changed the grub conf to use "pve-kernel-2.6.24-7-pve" The server is in use atm, so i could not play around with other kernel stuff. 3)yes, i will start testing plain CentOS 5.4 installations with KVM

ok, the KVM spawns two more threads after a while. this can be seen in iotop. when i shutdown the vm snd start it up again, it will run smoothly for about 15-30 minutes. Then these thread reappear! I can't see much i/o load in dne Windows XP VM itself with the task manager. the problem has...

No i am now not physically at the server, so i won't try chaning kernels. maybe i'll get there next week. # pveversion -v pve-manager: 1.4-9 (pve-manager/1.4/4390) qemu-server: 1.1-8 pve-kernel: 2.6.24-16 pve-qemu-kvm: 0.11.0-2 pve-firmware: 1 vncterm: 0.9-2 vzctl: 3.0.23-1pve3 vzdump: 1.2-5...

same problem here, i can't find out why it is happening

try to find out the bottleneck (CPU/RAM/hdd i/o) and locate the process. for me it were windows VMs. But had do move them to physical servers quickly, so i cannot reproduce it right now.

or run iotop. i had similar issues with a 1.4 beta box.

i think it would be nice to choose during installation. there are servers that need openVZ and other that only need KVM. The proxmox Server without openVZ support could always run on the bleeding edge KVM version.