public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: "DERUMIER, Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com>
Cc: pve-devel <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] maybe a windows reboot hang fix
Date: Tue, 16 Aug 2022 11:37:28 +0200	[thread overview]
Message-ID: <20220816093728.nh2r5kx5wpw3t4ih@casey.proxmox.com> (raw)
In-Reply-To: <bf35a2fb-c2e8-230b-a725-0e8c4a4655c5@groupe-cyllene.com>

On Mon, Aug 15, 2022 at 07:00:51AM +0000, DERUMIER, Alexandre wrote:
> Hi,
> I'm still trying to fix windows reboot hang after windows update (I also 
> have the problem in production).
> 
> 
> I have found a related bug in redhat bugzilla
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1975840#c151
> 
> 
> https://access.redhat.com/solutions/6836351
> Issue Microsoft Windows guests hang while rebooting, the bootscreen 
> shows the Windows log and the boot circle endlessly.
> 
> Resolution There is no resolution or workaround at this time, please 
> power off the Guest and power on again.
> 
> Root Cause This is Bug 1975840 - Windows guest hangs after updating and 
> restarting from the guest OS
> 
> and is caused by a TSC (Time Stamp Counter) issue in Guest when it 
> overflows during boot time i
> f the value provided by the virtualization platform is already high. It 
> tends to affect Guests with longer uptimes.
> 
> 
> A patch has been in qemu master
> https://github.com/qemu/qemu/commit/5286c3662294119dc2dd1e9296757337211451f6

Seems like qemu 7.0 already contains this, I just forwarded a 7.0
package to the pvetest repo if you'd like to play around with it :-)




  reply	other threads:[~2022-08-16  9:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15  7:00 DERUMIER, Alexandre
2022-08-16  9:37 ` Wolfgang Bumiller [this message]
2022-08-16  9:46   ` DERUMIER, Alexandre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220816093728.nh2r5kx5wpw3t4ih@casey.proxmox.com \
    --to=w.bumiller@proxmox.com \
    --cc=Alexandre.DERUMIER@groupe-cyllene.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal