Re: A non-responsive guest problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I found the clock of guest OS has been changed. For example, today was Aug
22, but I found the time of guest was Mar 22 from the VNC desktop. The clock
source of guest was kvm-clock. Was it related to KVM clock bug? How about it
if I changed the clock to tsc?

Thanks,
Paul

On Fri, Aug 19, 2011 at 9:18 PM, Stefan Hajnoczi <stefanha@xxxxxxxxx> wrote:
>
> On Thu, Aug 18, 2011 at 8:42 AM, Paul <flypen@xxxxxxxxx> wrote:
> > Today I saw the guest OS hung and was no responsive. In the host, I
> > found the guest was running via virsh command. But I couldn't use ssh
> > to connect the guest, and even couldn't ping it. I could use VNC saw
> > the desktop of VNC, but I couldn't move the mouse pointer. In the
> > host, the qemu-kvm process occupied almost 100% CPU.
> >
> > The host was Redhat Enterprise Linux 6 64bit (not SP1).  The CPU was
> > Intel quad-core Q9550S. The guest was SUSE Linux Enterprise Server 11
> > SP1 64bit. The guest had been running for two weeks before it hung.
>
> Any interesting messages in dmesg on the host?
>
> Stefan
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux