Search results

  1. F

    problem after update - pvestatd look for control socket

    OMG, it was the no-kvm-pit-reinjection argument. i removed it and now the server is booting. Thank you for this thought!! ;)
  2. F

    problem after update - pvestatd look for control socket

    args: -no-hpet -no-kvm-pit-reinjection boot: dcn bootdisk: ide0 cores: 2 ide0: images:101/vm-101-disk-1.raw ide1: images:101/vm-101-disk-2.raw ide2: images:101/vm-101-disk-4.raw ide3: none,media=cdrom localtime: 1 memory: 4096 name: mx02 net0: rtl8139=C6:0E:9F:B7:4A:64,bridge=vmbr0 onboot: 1...
  3. F

    problem after update - pvestatd look for control socket

    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.
  4. F

    problem after update - pvestatd look for control socket

    i am familiar with the kill-command. i killed the vm with this command, but it's still the same error(s).
  5. F

    problem after update - pvestatd look for control socket

    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)...
  6. F

    problem after update - pvestatd look for control socket

    tried that, too, still the same. Aug 16 15:33:42 imp02 pvedaemon[40998]: WARNING: unable to connect to VM 101 socket - Resource temporarily unavailable Aug 16 15:33:43 imp02 pvedaemon[48551]: command '/bin/nc -l -p 5900 -w 10 -c '/usr/sbin/qm vncproxy 101 2>/dev/null'' failed: exit code 2 Aug...
  7. F

    problem after update - pvestatd look for control socket

    anything i can do to help? i know, this won't help, but it's a bit urgent :(
  8. F

    problem after update - pvestatd look for control socket

    Network isn't responding to ping/rdp/ssh etc. :(
  9. F

    problem after update - pvestatd look for control socket

    i can't login. console isn't working on these windows-guests. i get an "Network error:remote side closed connection"-error.
  10. F

    problem after update - pvestatd look for control socket

    root@imp02 /var/log/pve/tasks # pveversion -v pve-manager: 2.1-14 (pve-manager/2.1/f32f3f46) running kernel: 2.6.32-14-pve proxmox-ve-2.6.32: 2.1-73 pve-kernel-2.6.32-10-pve: 2.6.32-63 pve-kernel-2.6.32-14-pve: 2.6.32-73 lvm2: 2.02.95-1pve2 clvm: 2.02.95-1pve2 corosync-pve: 1.4.3-1 openais-pve...
  11. F

    problem after update - pvestatd look for control socket

    Aug 16 11:56:53 imp02 pvedaemon[18413]: start VM 101: UPID:imp02:000047ED:000A791E:502CC3E5:qmstart:101:root@pam: Aug 16 11:56:53 imp02 pvedaemon[15649]: <root@pam> starting task UPID:imp02:000047ED:000A791E:502CC3E5:qmstart:101:root@pam: Aug 16 11:56:53 imp02 kernel: device tap101i0 entered...
  12. F

    problem after update - pvestatd look for control socket

    this does not help, too. I only have this with Windows-Guests (only 2k8 R2, W7, SBS2011) but the other Windows-Guest (W8, 2k12) or ok.
  13. F

    problem after update - pvestatd look for control socket

    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.
  14. F

    Time running fast after upgrading to PVE 2 final

    this solved the problem on both windows-guests, thank you!!!! :) :cool:
  15. F

    Time running fast after upgrading to PVE 2 final

    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!
  16. F

    Time running fast after upgrading to PVE 2 final

    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:
  17. F

    Time running fast after upgrading to PVE 2 final

    With deactivated ACPI i can't boot anymore: https://forums.virtualbox.org/viewtopic.php?f=2&t=37628 :mad:
  18. F

    Time running fast after upgrading to PVE 2 final

    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...
  19. F

    Networking issues with Windows 2008 R2

    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.
  20. F

    Networking issues with Windows 2008 R2

    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.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!