Re: [Xen-users] xen save error

[john bryant <bryant.johan@xxxxxxxxx>]

Hi,

I am able to save my virtual machines in Xen 2.0.7. But restoring virtual machine give me error

Here is my sequence of event :


xm save 10 test10

xm restore test10


Error: errors: transfer daemon (xfrd) error: 22


xm list does show newly restored domain 


Name             
Id  Mem(MB)  CPU  State  Time(s)  Console

Domain-0          
0       92    0 
r----    
58.5        

ttylinux          11
     256    0 
-b---      0.8    9610


xm list -l gives following output ( No console information ) . I am not able to go to restored virtual machine.


(domain

    (id 0)

    (name Domain-0)

    (memory 92)

    (maxmem -1)

    (state r----)

    (cpu 0)

    (cpu_time 65.475292894)

    (devices)

)

(domain

    (id 11)

    (name Domain-11)

    (memory 255)

    (maxmem 256)

    (state -b---)

    (cpu 0)

    (cpu_time 0.008907453)

    (devices)


XFRD Log for restoration is as follows ( tail -f /var/log/xfrd.log ): 


Reloading memory pages:   6%

 12%

 17%

 23%

 28%

 34%

 39%

 45%

 50%

 56%

 62%

 67%

 73%

 78%

 84%

 89%

 95%

 95%[1126619778.790150] Received all pages


Received all pages

100%


100%

[1126619778.808769] Memory reloaded.


Memory reloaded.

Decreased reservation by 8 pages

[1126619778.810456] Domain ready to be built.


Domain ready to be built.

[1126619778.810637] Domain ready to be unpaused


Domain ready to be unpaused

[1126619778.811179] DOM=11


DOM=11

2437 [ERR] XFRD> Error adding op field.

2437 [INF] XFRD> Xfr service err=-22

-John

PS: Solution to all problem is refered as upgrading xen 2.0.5 to xen
2.0.7. Further upgrading may also solve the problem. It is my request
that developers please explain the root cause of problem and solution
that has been used to fix. It is benefiical for xen development as well
as all new users. Also, there is  need to update document
substantially.

On 9/14/05, Steven Hand <Steven.Hand@xxxxxxxxxxxx> wrote:

>I can get xen-2.0-testing to fail on live migrations with virtually no
load about 10% of the time with live migration :-)  Seems it becomes
>unable to suspend the user domain kernel - kernel gets the message, but
>never gets a chance to process it.  I'm not saying 2.0-testing won't
>resolve the problem John is seeing, but I'm not sure I would quite make
>the statement that it has been 'battle tested' :-)

So as the one who did the 'battle testing' I should speak up :^)

I did test tens of thousands of save/restore/migrations, but on 2.0.7-patch
i.e. on a version of the 2.0.7 tree with the save/restore fixes applied.
This was not checked in directly to 2.0.7 since we aim to filter stuff
through 2.0-testing and make a release that way.

So it's extremely interesting to us if you have observed errors in 2.0-testing
since this might mean that something else is to blame ( e.g. the upgrade from
2.6.11 to 2.6.12). This will delay our release of 2.0.8 which we were hoping
to do RSN.

Can you possibly post some more details about what you observe? And what is
in xend.log / xend-debug.log / xfrd.log? Is there a relatively small test
case that allows you to reproduce?


thanks,

S.

(p.s. as to the OP, I'm pretty sure the error he was seeing is fixed in
both 2.0.7 and 2.0-testing )

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