2 files changed, 116 insertions, 0 deletions
diff --git a/results/classifier/108/other/1257 b/results/classifier/108/other/1257
new file mode 100644
index 00000000..b3037496
--- /dev/null
+++ b/results/classifier/108/other/1257
@@ -0,0 +1,18 @@
+semantic: 0.814
+device: 0.776
+other: 0.749
+socket: 0.558
+performance: 0.531
+graphic: 0.383
+vnc: 0.376
+boot: 0.280
+files: 0.250
+PID: 0.237
+debug: 0.224
+permissions: 0.202
+network: 0.177
+KVM: 0.100
+
+Windows guest agent shutdown requires user response to complete
+Additional information:
+The shutdown operation triggered by the Windows Guest Agent should prevent the system from waiting for a user response concerning unsaved work of open desktop applications. Instead, applications and services should be closed as gracefully as possible automatically, in advance of  the power down event on the emulated hardware.
diff --git a/results/classifier/108/other/1257334 b/results/classifier/108/other/1257334
new file mode 100644
index 00000000..2bfe9246
--- /dev/null
+++ b/results/classifier/108/other/1257334
@@ -0,0 +1,98 @@
+permissions: 0.789
+other: 0.760
+semantic: 0.754
+device: 0.740
+performance: 0.723
+PID: 0.657
+files: 0.651
+graphic: 0.624
+debug: 0.612
+socket: 0.538
+network: 0.526
+vnc: 0.407
+boot: 0.402
+KVM: 0.390
+
+diffuse handling of image creation from another path
+
+see attachement!
+
+
+
+On Tue, Dec 03, 2013 at 03:22:28PM -0000, Florian Miksch wrote:
+Hi,
+This does not look like a bug.  Please see the explanation below...
+
+Inlining Florian's reproducer script so we can discuss it via email:
+
+> #!/bin/bash
+> # This script does create a backing image and overlay to
+> # reproduce the reported bug.
+> #...
+>  
+> mkdir a
+> # Create an image from another path e.g. in the directory 'a'
+> qemu-img create -f qcow2 a/blob.img 10G
+>  
+> # Create an overlay image from another path in the same directory
+> qemu-img create -f qcow2 -b a/blob.img a/ovl.img
+>  
+> # Get Info in the new directory
+> cd a
+> qemu-img info ovl.img
+> # Output:
+> #       image: ovl.img
+> #       file format: qcow2
+> #       virtual size: 10G (10737418240 bytes)
+> #       disk size: 196K
+> #       cluster_size: 65536
+> #       backing file: a/blob.img
+>  
+> # Get the Info from another directory
+> cd ..
+> qemu-img info a/ovl.img
+> # Output:
+> #       image: a/ovl.img
+> #       file format: qcow2
+> #       virtual size: 10G (10737418240 bytes)
+> #       disk size: 196K
+> #       cluster_size: 65536
+> #       backing file: a/blob.img (actual path: a/a/blob.img)
+>  
+> # Bug:
+> #       Compare 'image'
+> #       Compare 'backing file'
+> #       Look at 'actual path'
+
+The behavior you are showing here is explained as follows:
+
+Backing file paths can be relative or absolute and are stored inside
+the image file.  In this case you are providing a relative backing
+file path.
+
+Relative backing file paths are interpreted against the image filename.
+In other words:
+
+  join_path(dirname('a/ovl.img'), 'a/blob.img') -> 'a/a/blob.img'
+
+>  
+> # 'qemu-img info' takes the recommended path as name of the image
+> # and the actual path is then: a/a/blob.img    
+>  
+> qemu-img commit a/ovl.img
+> # Now commit fails  
+> # --> ERROR "No such file or directory
+
+The problem was:
+> qemu-img create -f qcow2 -b a/blob.img a/ovl.img
+
+If you want to use a relative backing file path, remember that it is
+relative to the image file:
+
+cd a && qemu-img create -f qcow2 -b blob.img ovl.img
+
+Then 'qemu-img commit a/ovl.img' will work as expected.
+
+Stefan
+
+