Hi,
after upgrading tonight to the latest proxmox, a windows (win7) guest stopped to work. kvm simply hanged directly during startup. I tracked down the problem by removing always one command line parameter from the kvm command:
If "-no-kvm-pit-reinjection" is only once at the command line, everything works fine. If it's twice there (which is for som reason true for my win7 proxmox guest), kvm freezes.
Minimal test:
kvm -vnc :99 -no-kvm-pit-reinjection -> shows the bios screen
kvm -vnc :99 -no-kvm-pit-reinjection -no-kvm-pit-reinjection -> never starts the vnc
Update: This is not a bug in proxmox itself, rather than in kvm. The parameter was in the config file, so since new proxmox releases adds the parameter automatically, this causes the parameter to be there twice. So after upgrading, one should double-check that this parameter is in none of the guest's configs! (changed the topic subject accordingly)
after upgrading tonight to the latest proxmox, a windows (win7) guest stopped to work. kvm simply hanged directly during startup. I tracked down the problem by removing always one command line parameter from the kvm command:
If "-no-kvm-pit-reinjection" is only once at the command line, everything works fine. If it's twice there (which is for som reason true for my win7 proxmox guest), kvm freezes.
Minimal test:
kvm -vnc :99 -no-kvm-pit-reinjection -> shows the bios screen
kvm -vnc :99 -no-kvm-pit-reinjection -no-kvm-pit-reinjection -> never starts the vnc
Update: This is not a bug in proxmox itself, rather than in kvm. The parameter was in the config file, so since new proxmox releases adds the parameter automatically, this causes the parameter to be there twice. So after upgrading, one should double-check that this parameter is in none of the guest's configs! (changed the topic subject accordingly)
Last edited: