Re: [Xen-users] Live Migration Problems

[Asim <linkasim@xxxxxxxxx>]

Hi,

After migration my machine would behave erratic and ping etc. would
stop after 1 packet. I fixed the timing issue and thought it to work.
But now I see that the ping exactly stops after 14 packets. Any ideas
what is going on here? Anybody faced the same issue?

I changed the time with the date command and the time gets reset to
old value after 14 pings.


Thanks,
Asim

On 8/7/08, Asim <linkasim@xxxxxxxxx> wrote:
> Thanks guys for pointing out. The time was indeed skewed on both machines.
>
> Cheers,
> Asim
>
> On 8/7/08, John Haxby <john.haxby@xxxxxxxxxx> wrote:
>>
>>> On Mon, Aug 4, 2008 at 7:49 PM, Asim <linkasim@xxxxxxxxx> wrote:
>>>
>>>> I have problems post migration. After migration of the domU from
>>>> server1 to server2, the domU starts to behave abnormally. Even when I
>>>> issue shutdown, it hangs.
>>>>
>>>> The system is going down for system halt NOW!
>>>> INIT: Switching to runlevel: 0
>>>> INIT: Sending processes the TERM signal
>>>> [root@fedora_pristine driver]# Stopping atd:
>>>>
>>>>
>>>> ping also hangs after sending one packet. Any ideas?
>>>>
>>>>
>>
>> Time no longer marches forward :-)
>>
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1282
>>
>> Anything which does a sleep() never returns from the sleep so, for
>> example, ping will send a packet and then never come back from the
>> sleep(1) before it sends the next packet; at various stages during the
>> shutdown process things sleep() waiting for something to die and the
>> sleep() never returns.  You'll also find that date reports a date that
>> never changes and may well be substantially different to the wall clock
>> date.
>>
>> The good news is that if you migrate back to the original machine, time
>> may well start again.  Also the bug is being actively worked on.
>> jch
>>
>

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