ok, i killed the process with kill -9 PID, then started the VM again and then copied the text above, but i still have the same issues with these two Windows-VMs.
root@imp02 ~ # qm start 101
VM 101 already running
root@imp02 ~ # qm stop 101
unable to connect to VM 101 socket - Resource temporarily unavailable
VM quit/powerdown failed - terminating now with SIGTERM
root@imp02 ~ # qm list
VMID NAME STATUS MEM(MB) BOOTDISK(GB)...
I have the same problem, but an restart does not help to fix this. I only have problems with my Windows-Guest.
Any other idea? Any workaround? The Windows-Guest won't start and i need them.
Regards,
f.
still the same issue :(
Next week i will setup a new pve-host with 2.0-from-scratch and attach the guest there to check if there's the same problem.
Maybe there's another option... :mad:
Thanks in advance!
it's "Microsoft Windows 7/2008r2 (win7)". Time was correct with PVE 1.9, i have this problem since the upgrade to 2.0.
The Parameter is correct.
Any other ideas? :confused:
I have the same problem on my two Windows Guests (1x Windows 2008 Server R2 and 1x Windows 7 x64), the clock is about 5mins+ faster. On two Linux Guests i have a delay on the Guest which is 4-6secs.
The Time on the Host is correct.
I tried the "no-kvm-pit-reinjection"-Paramenter on the...
fun fact: i am a (skilled) windows admin ;)
i created an iso-image with the nic-driver, uploaded it to the host and installed it from the mounted iso image :rolleyes:
Will try the Safe-Mode next time.
Thank you for help.
Regards,
F.
i tried, then windows is looking for a driver, but can't find anything. After that i have a device called "Ethernet Controller" (with the yellow !) but still no working network interface.
Any other idea's?
That's strange because my other windows guest's are working properly.
Regards,
f.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.