From: "Christian MICHON" <christian.michon@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Windows Vista
Date: Mon, 12 Jun 2006 22:46:40 +0200 [thread overview]
Message-ID: <46d6db660606121346q7b8cc241v4305e3aed7e67d82@mail.gmail.com> (raw)
In-Reply-To: <46d6db660606121256l6d183bf0v511d5b8c6ddb3b9a@mail.gmail.com>
http://www.h7.dion.ne.jp/~qemu-win/download/qemu-0.8.1-win32-imgover4g.patch
apparently fixes this. maybe Natalia mentionned no problem on qcow images,
not raw.
On 6/12/06, Christian MICHON <christian.michon@gmail.com> wrote:
> qemu-img.exe create -f raw test.raw 2G
>
> should take a couple of minutes to run, yet completes in
> less than 1s and test.raw is 0 bytes long.
>
> On 6/12/06, Natalia Portillo <claunia@claunia.com> wrote:
> > I'm sure you're doing something bad.
> > I used qemu-img and qemu with mingw32 and files not just bigger than
> > 2Gb but bigger than 6Gb even.
> >
> > El 12/06/2006, a las 20:33, Christian MICHON escribió:
> >
> > > interestingly enough, qemu-img is compiled with large file support,
> > > yet
> > > on win32/mingw (gcc 3.4.5) qemu-img cannot manage images bigger
> > > than 2Gb
> > >
> > > anyone ever succeded this on win32 host ? large file support using
> > > mingw ?
> > >
> > > On 6/9/06, Paul Brook <paul@codesourcery.com> wrote:
> > >> On Friday 09 June 2006 21:41, Christian MICHON wrote:
> > >> > ok, I'll try that. But I also suspect a win32/mingw limitation
> > >> on files
> > >> > bigger than 2Gb, since "gcc -dumpspecs" does not show anything
> > >> > related to -m64, which I'd expect to have to add to CFLAGS to
> > >> > be able to use iso or qcow images bigger than 2Gb.
> > >>
> > >> -m64 has nothing to do with large file support.
> > >>
> > >> Paul
> > >>
> > >
> > >
> > > --
> > > Christian
> > >
> > >
> > > _______________________________________________
> > > Qemu-devel mailing list
> > > Qemu-devel@nongnu.org
> > > http://lists.nongnu.org/mailman/listinfo/qemu-devel
> > >
> >
> >
> >
> > _______________________________________________
> > Qemu-devel mailing list
> > Qemu-devel@nongnu.org
> > http://lists.nongnu.org/mailman/listinfo/qemu-devel
> >
>
>
> --
> Christian
>
--
Christian
next prev parent reply other threads:[~2006-06-12 20:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 12:04 [Qemu-devel] Windows Vista Hetz Ben Hamo
2006-06-08 14:47 ` Christian MICHON
2006-06-09 0:11 ` Nigel J. Terry
2006-06-09 7:55 ` René Korthaus
2006-06-09 8:20 ` René Korthaus
2006-06-09 12:08 ` Brian Wheeler
2006-06-09 12:25 ` René Korthaus
2006-06-09 12:41 ` Brian Wheeler
2006-06-09 12:55 ` René Korthaus
2006-06-09 13:11 ` RE : " Sylvain Petreolle
2006-06-09 13:20 ` Christian MICHON
2006-06-09 14:05 ` Christian MICHON
2006-06-09 15:35 ` Christian MICHON
2006-06-09 20:27 ` Natalia Portillo
2006-06-09 20:41 ` Christian MICHON
2006-06-09 20:47 ` Paul Brook
2006-06-09 20:59 ` Christian MICHON
2006-06-12 19:33 ` Christian MICHON
2006-06-12 19:39 ` Natalia Portillo
2006-06-12 19:49 ` Christian MICHON
2006-06-12 19:56 ` Christian MICHON
2006-06-12 20:46 ` Christian MICHON [this message]
2006-06-15 1:36 ` Joseph Miller
2006-06-09 20:48 ` RE : " Natalia Portillo
2006-06-09 20:50 ` René Korthaus
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=46d6db660606121346q7b8cc241v4305e3aed7e67d82@mail.gmail.com \
--to=christian.michon@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).