On Wed, Jan 6, 2010 at 1:18 PM, Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:
> On Wed, Jan 6, 2010 at 1:16 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
>> On Wed, Jan 06, 2010 at 11:38:36AM +0000, Andrew Lyon wrote:
>>> On Wed, Jan 6, 2010 at 10:05 AM, Fajar A. Nugraha <fajar@xxxxxxxxx> wrote:
>>> > On Wed, Jan 6, 2010 at 4:56 PM, Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:
>>> >> I have just tested migration of a 64 bit pv domU and had no problem
>>> >> reconnecting the console afterwards, I moved it 10 times to be sure
>>> >> that it works reliably.
>>> >>
>>> >> I will test 32 bit pv domU once I have upgraded the kernel im my test
>>> >> domU.
>>> >
>>> > Weird. Could you send me your .config? At least this will help me
>>> > pinpoint whether the problem is in my config or something else.
>>> >
>>> > --
>>> > Fajar
>>> >
>>>
>>> 32 bit domU also migrates successfully, I have attached the Xen and
>>> kernel config files for both 32 and 64 bit pv domU, and also the 64
>>> bit dom0 config for my Xen server.
>>>
>>> I had not setup a migration capable environment before so I simply
>>> used file backed disks stored on a nfs server, this seems to work but
>>> occasionally a domU will crash during startup complaining that it
>>> cannot mount the root filesystem, I found that when this happens
>>> starting the domain with -p and then unpausing it after a couple of
>>> seconds will enable it to start, but once started I was able to
>>> complete several migrations while processes were running in the domU
>>> and it caused no problems.
>>>
>>
>> Did you try tap:aio: disks instead of file: ?
>>
>> -- Pasi
>>
>>
>
> No, I will give that a try.
>
> Andy
>
tap:aio behaves the same.
Andy
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|