Description of problem:
As part of the rebase to libvirt 0.8.7 in RHEL 6.1, libvirt gained the ability to have better support for guests with spaces in their names.  However, this support is incomplete, and an attempt to snapshot such a domain causes a shell syntax error.

Version-Release number of selected component (if applicable):
v0.8.7-6.el6

How reproducible:
100%

Steps to Reproduce:
1. create and run a guest named "a b" (note: virt-manager might not allow this, so it may require manual creation of an xml file and 'virsh define file.xml')
2. try 'virsh managedsave "a b"
  
Actual results:
/var/log/libvirt/qemu/a\ b.log:
  sh: -c: line 0: syntax error near unexpected token `b'
  sh: -c: line 0: `cat | { dd bs=4096 seek=1 if=/dev/null && dd bs=1048576; }

Expected results:
should work

Additional info:
Reported and patched upstream:
https://www.redhat.com/archives/libvir-list/2011-February/msg00360.html
commit f370fc37f964984ba40584dab1de340ce7e44bac
Author: Philipp Hahn <hahn>
Date:   Fri Feb 11 13:59:11 2011 +0100

    qemu: Fix escape_monitor(escape_shell(command))
    
    Suspending a VM which contains shell meta characters doesn't work with
    libvirt-0.8.7:
    /var/log/libvirt/qemu/andreas_231-ne\ doch\ nicht.log:
      sh: -c: line 0: syntax error near unexpected token `doch'
      sh: -c: line 0: `cat | { dd bs=4096 seek=1 if=/dev/null && dd bs=1048576; }
    
    Although target="andreas_231-ne doch nicht" contains shell meta
    characters (here: blanks), they are not properly escaped by
    src/qemu/qemu_monitor_{json,text}.c#qemuMonitor{JSON,Text}MigrateToFile()
    
    First, the filename needs to be properly escaped for the shell, than
    this command line has to be properly escaped for qemu again.
    
    For this to work, remove the old qemuMonitorEscapeArg() wrapper, rename
    qemuMonitorEscape() to it removing the handling for shell=TRUE, and
    implement a new qemuMonitorEscapeShell() returning strings using single
    quotes.
    
    Using double quotes or escaping special shell characters with backslashes
    would also be possible, but the set of special characters heavily
    depends on the concrete shell (dsh, bash, zsh) and its setting (history
    expansion, interactive use, ...)
    
    Signed-off-by: Philipp Hahn <hahn>