Quoting Jamie Strandboge ([email protected]): > I don't, I just used the options that our uvt command uses. I downgraded > to saucy's qemu in the meantime so I can do my work. Do you need me to > try some new test?
sigh, maybe. I will keep trying. > I'm not sure it makes any difference, but note that I am using a trusty > host and kernel. Right, that's what I'm using. Have others on your team (who are not on the same thinkpad model :) seen this as well? Have you seen it on different types of machines? Does it happen more often if the machine is already working hard? I wonder if I can reproduce it manually with qemu-img and qemu-nbd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292234 Title: qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1292234/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
