|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-devel
RE: [Xen-devel] Re: [PATCH]: kexec: framework and i386
 
 
> In summary, for kdump "linux crashdump=64M@16M"
> becomes "xen kdump_megabytes=64 kdump_megabytes_base=16"
Please can you explain a bit about how kdump works, and why a physically
contiguous region with known base address is required. What actually
gets written out in the crash dump and in what format? 
> The other main point to note for users is that while the 
> following transition is possible: xen -> linux.  But xen -> 
> xen and linux -> xen is currently not possible.  This is 
> because kexec-tool, the user-space component of kexec does 
> not understand enough about xen, and thus needs to be 
> enhanced in order to make this possible.
Tim Deegan submitted a patch to add support for multiboot images (such
as Xen) to kexec a couple of years ago, and I believe it has been part
of the standard package for some time.
Thanks,
Ian
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 
 |   
 
| <Prev in Thread] | 
Current Thread | 
[Next in Thread>
 |  
- RE: [Xen-devel] Re: [PATCH]: kexec: framework and i386,
Ian Pratt <=
 
 
 
 |  
  
 | 
    | 
  
  
    |   | 
    |