Consider writing a wiki entry or blog about what you did with Xen.
It will help many others.
On Thu, Jun 10, 2010 at 4:40 PM, Daniel <dandadude@xxxxxxxxx> wrote:
> 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!
>
> Regards,
> Daniel
>
>
> 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
>> <xen-users@xxxxxxxxxxxxxxxxxxx>
>> Message-ID:
>> <AANLkTiktQCYJaGo4q6gHwpNwDxDybQha6NMydN00Yn2x@xxxxxxxxxxxxxx>
>> 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.
>>
>> Andy
>>
>>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
--
Tapas
http://mightydreams.blogspot.com
http://wiki.xensource.com/xenwiki/Xen_on_4_app_servers
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home