On Thu, Jun 07, 2012 at 01:13:50PM +0100, Stefan Hajnoczi wrote: > >> >> The 1st bad commit in your attached list is abc551bd > >> >> More detailed info: > >> >> 171d2f2249a360d7d623130d3aa991418c53716d good > >> >> fd453a24166e36a3d376c9bc221e520e3ee425af good > >> >> abc551bd456cf0407fa798395d83dc5aa35f6dbb bad > >> >> 823ccf41509baa197dd6a3bef63837a6cf101ad8 bad > >> > > >> > Thanks, this points to the qcow2 v3 changes. Let's try to find the exact > >> > culprit. I have rebased the qcow2 patches on top of that good merge > >> > (fd453a24). Please apply the attached mbox on top of this merge: > >> > > >> > git checkout fd453a24 > >> > git am qcow2v3.mbox > >> > > >> > You can then start a git bisect between your new HEAD and fd453a24. > >> > >> Another thing you could try is if reverting e82dabd and bef0fd59 fixes > >> the problem for you. > >> > > After reverting bef0fd59, it can work fine. > > I'm unable to reproduce this with qemu-kvm.git/master > (18b012756fd041556764dfa2bb1f307b6923fb71) or the commit you > 3fd9fedb9fae4517d93d76e93a2924559cacf2f6 reported as bad. The RHEL 6 > guest boots without any issues. My host kernel is Linux 3.2 (Debian > 3.2.0-2-amd64). The guest is Linux 2.6.32-71.el6. > > Since the guest sees a disk read error, it may be useful to add > printfs to hw/ide/core.c:ide_sector_read_cb(). Let's find out why the > disk read is failing. Any news on this problem? -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
