Re: making sense of virtualbox .sav files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




----- Original Message -----
> 
> 
> 
> Yes, unless you know another way to convert it to something crash can use.
> 
> Regards,
> 
> Scott.

Sorry, no, I don't know the first thing about the .sav file format,
nor have I ever heard of anybody attempting such a conversion.
This is the first time it's even been brought up on this list.

Dave

> On Oct 24, 2011 5:12 PM, "Dave Anderson" < anderson@xxxxxxxxxx >
> wrote:
> 
> 
> 
> 
> ----- Original Message -----
> > 
> > Hello,
> > 
> > I suspect the open source edition of vbox and the oracle non foss
> > edition use the same format for the save state files (ram and
> > device
> > info dumps). The bulk of /proc/kcore equiv is in here, with other
> > metadata. file(1) just whines this is data...
> > 
> > If you have any information leading to use of this save state data
> > with crash, please advise. I've scoured all the places I can think
> > of. For better or worse, I'm not sure I can pull this off by using
> > the ose code - it's just a bit too far above my head to know I'm
> > making a reliable export of .sav files to kcore equiv outputs.
> > 
> > Regards,
> > 
> > Scott Edwards
> 
> VirtualBox .sav files are certainly not one of the dumpfile formats
> recognized by the crash utility, if that's what you're asking?
> 
> Dave Anderson
> 
> --
> Crash-utility mailing list
> Crash-utility@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/crash-utility
> 
> --
> Crash-utility mailing list
> Crash-utility@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/crash-utility
> 

--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility


[Index of Archives]     [Fedora Development]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]

 

Powered by Linux