Description of problem:
Trying to run an unrelated systemtap script shows two parse errors with these lines:

in = $arg3;
next = $arg1;

Identical errors are shown for qemu-kvm.stp, qemu-system-i386.stp and qemu-system-x86_64.stp, showing a total of six.

Version-Release number of selected component (if applicable):
qemu-system-x86-1.0-17.fc17.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. run stap -e ''
2. check for any parse errors relating to qemu
  
Actual results:
$ stap -e ''
Input file '<input>' is empty or missing.
parse error: expected statement
	saw: keyword at /usr/share/systemtap/tapset/qemu-kvm.stp:1139:3
     source:   in = $arg3;
               ^
parse error: expected literal string or number
	saw: operator '=' at /usr/share/systemtap/tapset/qemu-kvm.stp:2078:8
     source:   next = $arg1;
                    ^
2 parse errors.


Expected results:
$ stap -e ''
Input file '<input>' is empty or missing.

Additional info:
Already reported against RHEL 6 as bug #720979, bug #798676 and #820320.  These only report the "next" error, not the "in" error though.

See bug #820320, comment #2 for a list of all reserved keywords.