libvirt users - Feb 2013 - Can't save domain: unexpectedly failed

I am running libvirt 0.9.8,

virsh -V
Virsh command line tool of libvirt 0.9.8
See web site at http://libvirt.org/

Compiled with support for:
 Hypervisors: Xen QEmu/KVM UML OpenVZ LXC Test
 Networking: Remote Daemon Network Bridging Nwfilter VirtualPort
 Storage: Dir Disk Filesystem SCSI Multipath iSCSI LVM
 Miscellaneous: AppArmor Secrets Debug Readline

in an ubuntu 12.04.1 install. I created a vm client and wanted to save it:

root at vmhost:/tmp# /usr/bin/virsh save test /export/vms/dump/test.dump
error: Failed to save domain test to /export/vms/dump/test.dump
error: operation failed: domain save job: unexpectedly failed

root at vmhost:/tmp# cat /var/log/libvirt/qemu/test.log
2013-02-04 17:06:10.792+0000: starting up
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.14 -cpu
core2duo,+lahf_lm,+aes,+popcnt,+sse4.2,+sse4.1,+cx16,-monitor,-vme
-enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name test
-uuid 82758b52-77e9-494c-8a9d-c666949c978c -nodefconfig -nodefaults
-chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/test.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc
-no-shutdown -boot order=cd,menu=on -drive
file=/dev/mapper/vmhost_vg1-test,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=native
-device
virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0
-drive if=none,media=cdrom,id=drive-ide0-0-0,readonly=on,format=raw
-device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0
-drive if=none,media=cdrom,id=drive-ide0-0-1,readonly=on,format=raw
-device ide-drive,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1
-netdev tap,fd=19,id=hostnet0 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=00:16:3e:6f:9c:6b,bus=pci.0,addr=0x3
-usb -device usb-tablet,id=input0 -vnc 127.0.0.1:1 -vga cirrus -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
root at vmhost:/tmp#

Does anyone know what could have caused this? Is there another log I
can check for what this unexpected failure really is?