The KVM virtual FAT drive does not work with -snapshot. For instance: $ kvm -fda fat:/tmp/foo -cdrom rescue.iso -boot d -snapshot qemu: could not open disk image fat:/tmp/foo Without -snapshot, it works fine. - Josh Triplett
You filled the bug http://bugs.debian.org/504049 in Debian BTS against the package kvm. I'm closing it at *unstable*, but it will remain open for older distributions. For more information about this package's removal, read http://bugs.debian.org/562620. That bug might give the reasons why this package was removed and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. Thank you for your contribution to Debian.
reopen 498093 reassign 498093 qemu-kvm retitle 498093 Please provide package for all architectures, not just amd64 and i386 reopen 504049 reassign 504049 qemu-kvm retitle 504049 Virtual FAT drive doesn't work with -snapshot reopen 507068 reassign 507068 qemu-kvm retitle 507068 Please support -tftp, -smb, and -redir without outgoing access # already done by Marco #reopen 540686 #reassign 540686 qemu-kvm retitle 540686 /etc/init.d/qemu-kvm: Stop action seems unnecessary thanks [...] Argh. This and a pile of kvm bugs got closed because kvm got removed from Debian in favor of qemu-kvm. In general, these bugs still apply to qemu-kvm, which pretty much just represents a rename of the same upstream source. Reopening and reassigning my own bugs, but the remainder of the bugs closed due to this removal also need reopening and reassigning (and retitling). - Josh Triplett
tags 504049 + confirmed upstream thanks Josh Triplett wrote at Thu, 30 Oct 2008 13:03:28 -0700: Yes, that seems broken, and it is still broken in current qemu-kvm-0.12.3 in -unstable. Tagging as such, even that fat: disk "format" is not documented... I'll ping upstream with this. Thanks! /mjt
severity 504049 wishlist thanks I'm downgrading severity of this bug to wishlist. Reason is that it's quite rare to use virtual fat to start with (actually it isn't even documented in qemu-kvm anymore), and especially with -snapshot. Also, upstream isn't willing to work on this "corner case" and apparently fixing it isn't exactly trivial. In any way, working around the bug is trivial: just use absolute path for the fat:dir, i.e., fat:$PWD/dir instead of fat:dir. (I'm keeping this bug around still, ofcourse). /mjt
If that works around the bug, then I'd have no objection to a documentation-only fix: document (in the manpage) that fat: requires an absolute path and close the bug. Thanks for following up. - Josh Triplett