Re: [Xen-ia64-devel] New tree issues (domU restartanddomVTibootissues)

[Tristan Gingold <tgingold@xxxxxxx>]

On Fri, Jun 15, 2007 at 01:06:53PM +0800, Zhang, Xing Z wrote:
> >>    I can see now why you wanted to store the nvram based on disk
> image
> >> path, it's a similar idea to storing the nvram in the guest EFI
> >> partition.  If the nvram is stored in the dom0 fs, using domain name
> >> seems like the easiest approach, but I still like the idea of having
> the
> >> nvram stored in the guest image.
> >
> >I don't really like the idea of saving NVRAM on the disk.  Real
> machines
> >don't do that so why should we do that.
> >If you really want to save NVRAM, an EFI tool can do the work.
> >
> [Zhang, Xing Z] 
> Do you mean save NVRAM to guest image then use EFI tool to do load/save
> ? It's the best way if we can get the tool and integrate it into our
> GFW. 

I think the current method is right (ie qemu save and restore nvram from a
file) although I'd prefer the user to be able to set the filename.

Now, if we want to make virtual machine move (or duplication) easier, we
can write an EFI tool to save and restore nvram to a file.

EFI can't automatically write the NVRAM to a file, because once the OS has
booted EFI features are very restricted.

Tristan.

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