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

Re: [Xen-users] problem after migration


  • To: George Shuklin <george.shuklin@xxxxxxxxx>
  • From: Paras pradhan <pradhanparas@xxxxxxxxx>
  • Date: Fri, 19 Nov 2010 09:02:46 -0600
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 19 Nov 2010 07:04:28 -0800
  • 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 :cc:content-type:content-transfer-encoding; b=MIeqIebgwh2IKzjpn8RMOvJPPmS55U4aq6Bqm4H3UqLNCm+5Idra9/ivkrX6KU/dat 0j1lU0dgcePXPJYqAj8HcpE0JXOJMIjpUqv6IBtiNTM0CStK18Jjx7ZONq9z3msYVz2Z 9ZMcGgVESlHQNicoBXGh7Kos9V37dM7kk4rf8=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

well arp not might be the case in here.

The problem is  similar to what has already been filed at bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=613513

I am still looking for the temporary solution if its the bug while
waiting for its solution.


Thanks
Paras.

On Thu, Nov 18, 2010 at 5:38 PM, George Shuklin
<george.shuklin@xxxxxxxxx> wrote:
> or switch dom0/domU to bleeding edge new Âkernel.
>
> I found source of information:
>
> http://wiki.xensource.com/xenwiki/XenCommonProblems#head-48cfb34682c0e0868ea836be4372036284463773
> http://lists.xensource.com/archives/html/xen-devel/2010-08/msg01595.html
>
>
> Ð ÐÑÐ, 17/11/2010 Ð 10:12 -0600, Paras pradhan ÐÐÑÐÑ:
>> Any other workaround(s) for this apart from using the old -xen kernel?
>>
>> Paras.
>>
>>
>> On Tue, Nov 16, 2010 at 7:07 PM, George Shuklin
>> <george.shuklin@xxxxxxxxx> wrote:
>> > 90% - arp bug. I don't remember where it was written (somewhere in
>> > xenwiki), but many PV kernels have bug with unsended fake/grace arp
>> > notification to uplink (switch).
>> >
>> > So, or switch to -xen kernel (2.6.18 in centos 5 is about hard and old
>> > as mammoth shit, but working) or switch dom0/domU to bleeding edge new
>> > kernel.
>> >
>> > Ð ÐÑÑ, 16/11/2010 Ð 16:16 -0600, Paras pradhan ÐÐÑÐÑ:
>> >> Hi,
>> >>
>> >> I believe I can post this here.
>> >>
>> >> I have a domU ( Redhat 6) running in Paravirt mode. When I migrate
>> >> this domU to another host, looks like the domU is freezing in the
>> >> other host. When I take it back to original host ,it starts to run
>> >> normally and this is what can see in dmesg of domU :
>> >>
>> >>
>> >> suspending xenstore...
>> >> trying to map vcpu_info 0 at ffff88000434b020, mfn b67660, offset 32
>> >> cpu 0 using vcpu_info at ffff88000434b020
>> >> suspending xenstore...
>> >> trying to map vcpu_info 0 at ffff88000434b020, mfn e278ee, offset 32
>> >> cpu 0 using vcpu_info at ffff88000434b020
>> >>
>> >> domU is redhat 6.0
>> >> dom0 is redhat 5.5
>> >>
>> >>
>> >> I don't have any issue with redhat 5 domUs.
>> >>
>> >> All PV
>> >>
>> >> Thanks in Adv
>> >> Paras.
>> >>
>> >> _______________________________________________
>> >> Xen-users mailing list
>> >> Xen-users@xxxxxxxxxxxxxxxxxxx
>> >> http://lists.xensource.com/xen-users
>> >
>> >
>> >
>> > _______________________________________________
>> > Xen-users mailing list
>> > Xen-users@xxxxxxxxxxxxxxxxxxx
>> > http://lists.xensource.com/xen-users
>> >
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.