On 10/01/2015 10:51 AM, Gilou wrote: > Le 01/10/2015 10:44, Alexandre DERUMIER a écrit : >> hi, >> >> I think this bug has been fixed for proxmox 4.0 >> >> https://git.proxmox.com/?p=pve-qemu-kvm.git;a=commit;h=68b7e74b8d9817bc10558faf009956053ee1ea8b >> https://git.proxmox.com/?p=pve-qemu-kvm.git;a=commit;h=3a0076907edf0c90869eff3b3bac45346c4ad49c >> >> I don't known if it's planned to backport them to 3.4. >> (maybe as to pve-devel mailing list) > > OK, not sure if it fixes it, I'll try it on Proxmox 4 later on and > report back then... >
Unfortunately the problem stills appears randomly in some corner cases and we're still working in sorting this out. @gilles: can you confirm the problem on your side only happens with Windows VMs ? What is the output of the VNC Console in this case ? Can you also post here the configuration of your VM ? (qm config <myVMID>) If you manage to reproduce the bug with Proxmox 4.0 ( and only in that case), please post your pve4.0 qm config in https://bugzilla.proxmox.com/show_bug.cgi?id=694. We use this bugzilla entry to track the issue for Proxmox 4.0 Thank you Emmanuel _______________________________________________ pve-user mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
