This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Re: Xen-users Digest, Vol 64, Issue 52

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: Xen-users Digest, Vol 64, Issue 52
From: Daniel <dandadude@xxxxxxxxx>
Date: Thu, 10 Jun 2010 13:10:44 +0200
Delivery-date: Thu, 10 Jun 2010 04:12:31 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=hWj5MQvRHidBOJZ9lSP7tOvwrtIOd1+LMmJ+FaaCgyE=; b=mChUDXoW07CjBpsYzVoOZoFFTGC0QQ1GBPgU+sISGkBdmAivM0awCNeTNPG036SJZT OJby7FtRqoFJlPo691QcY/49YP3p9a9kocwUjrvQlJBnKBebex24V/3x1IDy/9MFh6K2 m0rRYUhOP/I7xUN3fhxQ6InV3sceeJkeEX93A=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Sp9PPGgUQbGiu67QrDICnSXJWkXbvPvViFqUbsNXPvpBHNJFpoy+jUCUwhUiNmLdNR g7zogO89ptBmG1H/1Rf2qGpY2folSg9OxzyuFdYBYPiHgxocGX+gpZnsceA3arFQGLY/ IN8Nkm5zHXDzXwREPrL5uSFj0zKvTvn4icOyw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4c0fd4e6.121c730a.5808.2187SMTPIN_ADDED@xxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4c0fd4e6.121c730a.5808.2187SMTPIN_ADDED@xxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Dear James and Andrew!

Thanks much for the help, it seems that viridian=1 solved my problem!
I forced a heavy load last night and no reboots were issued!

I confirm that I had multiple cpus assigned and dom0 heavy load started the reboot problema, but with viridian=1, everything is OK!

Thanks again for everything!


Message: 3
Date: Wed, 9 Jun 2010 15:55:13 +0100
From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
Subject: Re: [Xen-users] windows 2k8 rebooted by itself several times,
       perhaps         dom0 heavy load?
To: Daniel <dandadude@xxxxxxxxx>,       xen-users List
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jun 9, 2010 at 9:57 AM, Daniel <dandadude@xxxxxxxxx> wrote:
> Hi!
> I have a Win2k8 R2 running under my Gentoo dom0.
> Sunday night I started compressing a large file on the dom0 linux, and next
> day I saw that during the compression period, the Win2k8 restarted several
> times.
> Logs:
> xend.log:
> [2010-06-06 21:31:36 4034] INFO (XendDomainInfo:1903) Domain has shutdown:
> name=mkts id=14 reason=reboot.
> [2010-06-06 21:31:36 4034] DEBUG (XendDomainInfo:2732)
> XendDomainInfo.destroy: domid=14
> [2010-06-06 21:31:38 4034] DEBUG (XendDomainInfo:2207) Destroying device
> model
> [2010-06-06 21:31:38 4034] INFO (image:556) mkts device model terminated
> qemu-dm-mkts.log:
> region type 1 at [c100,c200).
> region type 0 at [f3001000,f3001100).
> squash iomem [f3001000, f3001100).
> reset requested in cpu_handle_ioreq.
> Issued domain 15 reboot
> This is very frustrating, because the server is a live server, and reboot is
> not preferred just randomly. And I must say that PV drivers are installed
> too, it didn't even reboot nicely (with shutdownmon) as I can make it reboot
> manualy.
> I have Xen 3.4.2 running with 2.6.32 kernel.
> What can I do to avoid this reboot? It is ok if it slows down, but it
> shouldn't reboot.
> Thanks in advance!
> Regards,
> Daniel
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

If you have multiple cpus assigned and the crash only happened when
dom0 is under load then you probably need viridian=1 in the domU
config, otherwise it will bugcheck if timer interrupts are delayed for
too long.


Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>