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@lists.xensource.com http://lists.xensource.com/xen-users
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@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@gmail.com> 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@lists.xensource.com >> http://lists.xensource.com/xen-users > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@gmail.com> 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@lists.xensource.com > >> http://lists.xensource.com/xen-users > > > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@gmail.com> 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@gmail.com> 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@lists.xensource.com >> >> http://lists.xensource.com/xen-users >> > >> > >> > >> > _______________________________________________ >> > Xen-users mailing list >> > Xen-users@lists.xensource.com >> > http://lists.xensource.com/xen-users >> > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users