All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jbrown106@phreaker.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Stupid question?
Date: Sun, 5 Sep 2004 09:43:42 -0400	[thread overview]
Message-ID: <20040905134342.GA15938@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <Pine.LNX.4.56.0409051438390.15517@halef.NotaMusica.com>

On Sun, Sep 05, 2004 at 02:41:24PM +0200, Johannes Martin wrote:
> Hi,
> 
> On Sun, 5 Sep 2004, Dieter Schicker wrote:
> > How can I mount the "virtual harddisk file" in Linux?
> > mount -t vfat -o loop /data/win98.img /mnt/win   fails!
> >
> > Any suggestions?
> Hetz already told us how to do this in his last email...
> 
> As to 'why' the above doesn't work: I assume it's because mount expects a
> hard disk partition while /data/win98.img is a complete disk (including
> the master boot record, partition table, etc), i.e. about 64 extra sectors
> at the beginning (depending on disk geometry). Right?
> 

Right. lomount gets around this by passing the offset= option to mount
(which passes it to losetup). You don't need lomount for this, you can
calculate the offset yourself. If you want to.

> BTW, has anybody worked on making it possible to mount 'cow' images on the
> host?

Sparse images should work fine w/ lomount. qemu cow images will never work,
and to use those you'd have to convert them to a regular image first.

(I lied above. There is one way to make them work, but it is fairly contorted
and twisted and not at all trivial. It'd be a massive project in itself ...
bsaicly you'd need to write a daemon that pretended to be a user-space NFS
server, and have it read/write to the cow image on the kernel's behalf. This is
extra hard because it would have to know what a FAT/NTFS/ext2/etc file system
looks like in a cow image. Easier just to convert the cow into a regular image
and use that.)

> 
> 	Johannes
> 
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

  reply	other threads:[~2004-09-05 13:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-05 12:11 [Qemu-devel] Stupid question? Dieter Schicker
2004-09-05 12:15 ` Hetz Ben Hamo
2004-09-05 12:41 ` Johannes Martin
2004-09-05 13:43   ` Jim C. Brown [this message]
2004-09-05 14:05     ` Tim
2004-09-06  7:56 ` Marcello 'R.D.O.' Magnifico
2004-09-06  8:03   ` Dieter Schicker
  -- strict thread matches above, loose matches on Subject: below --
2011-02-26 22:15 Frans de Boer
2011-02-26 22:22 ` Dushyant Bansal
2011-02-26 22:33   ` Frans de Boer
2011-02-27  6:22   ` Amos Kong
2011-02-27 16:15     ` Avi Kivity
2011-02-27 17:00     ` Stefan Hajnoczi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040905134342.GA15938@jbrown.mylinuxbox.org \
    --to=jbrown106@phreaker.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.