search for: badsys

...espond to you question about "whether it fails", hivexsh is unable to open the hive file and it prints this message and exits. I've attached the verbose logs as requested This extract from the logs shows that the hivexsh complains content after file offset 0x77c000 is garbage hivex: badsys: trailing garbage at end of file (at 0x77c000, after 1849 pages) So, I went ahead and truncated the contents of the file after that file offset and hivex was able to successfully open the new hive file The sizes of the different hive files shown here [root@ip-10-66-209-246 ~]# ls -als bads* 7664...

...hivex: %s: trailing garbage at end of file (at 0x%zx, after %zu >pages)\n", filename, off, pages); > break; I wanted to understand the behavior of hivex when we wrote to the end of the hive file (added a new entry under ControlSet001\services). When I do that I get the following error badsys-1-win-add-reg\ControlSet001\services> ls hivex: _hivex_get_children: returning EFAULT because: subkey_lf is not a valid block (0x780020) ls: Bad address badsys-1-win-add-reg\ControlSet001\services> quit Obviously the add/modify was not successful. But regedit parsed the hive successfully. I...

Is there a reason why a previous version of hivex ignored this condition while more recent ones throw an error? I do have some hive files that are failing (I'm yet to validate if they are good or were corrupted some other way). I will do so and share my findings Thanks ~ Hari On 9/24/13 5:20 PM, "Richard W.M. Jones" <rjones@redhat.com> wrote: >On Tue, Sep 24, 2013 at

...; verbose logs as requested > >OK, I understand it now. It is in fact failing, setting >errno = ENOSYS and returning an error. > >> This extract from the logs shows that the hivexsh complains content >>after >> file offset 0x77c000 is garbage >> >> hivex: badsys: trailing garbage at end of file (at 0x77c000, after 1849 >> pages) >> >> So, I went ahead and truncated the contents of the file after that file >> offset and hivex was able to successfully open the new hive file > >I guess if the hive comes from a real guest we can...

...age and exits. I've attached the > verbose logs as requested OK, I understand it now. It is in fact failing, setting errno = ENOSYS and returning an error. > This extract from the logs shows that the hivexsh complains content after > file offset 0x77c000 is garbage > > hivex: badsys: trailing garbage at end of file (at 0x77c000, after 1849 > pages) > > So, I went ahead and truncated the contents of the file after that file > offset and hivex was able to successfully open the new hive file I guess if the hive comes from a real guest we can change this to warn but...

Hi, Is the http://xenbits.xensource.com/linux-2.6-xen.hg tree still being updated? if not, what''s the preferred Linux tree to track that has all of the Xen bits? Thanks, Muli _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel