Description of problem:

A guestmounted filesystem.  Note the bogus symlink:

$ ll mnt/
total 1834729
-rwxrwxrwx. 1 root root         24 Jun 10  2009 autoexec.bat
-rwxrwxrwx. 1 root root         10 Jun 10  2009 config.sys
lrwxrwxrwx. 2 root root         60 Jul 14  2009 Documents and Settings -> /sysroot//Users
-rwxrwxrwx. 1 root root  804986880 Mar 29 13:08 hiberfil.sys
-rwxrwxrwx. 1 root root 1073741824 Mar 29 13:08 pagefile.sys
drwxrwxrwx. 1 root root          0 Jul 14  2009 PerfLogs
drwxrwxrwx. 1 root root       4096 Jul 14  2009 ProgramData
drwxrwxrwx. 1 root root       4096 Dec 14 19:03 Program Files
drwxrwxrwx. 1 root root          0 Dec 14 18:40 Recovery
drwxrwxrwx. 1 root root          0 Dec 14 18:41 $Recycle.Bin
drwxrwxrwx. 1 root root       4096 Dec 15 09:32 System Volume Information
drwxrwxrwx. 1 root root       4096 Dec 14 18:41 Users
drwxrwxrwx. 1 root root      16384 Dec 15 09:34 Windows

Version-Release number of selected component (if applicable):

guestmount 1.3.20

How reproducible:

Always.

Steps to Reproduce:
1. guestmount a filesystem that has an absolute symlink
2. note the symlink points to the wrong place
3.
  
Additional info:

We should rewrite absolute symlinks as relative ones in the
FUSE layer.