qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mateusz Loskot <mateusz@loskot.net>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Linux as VirtualBox quest OS with QEMU running	Solaris
Date: Wed, 12 Jan 2011 12:30:18 +0000	[thread overview]
Message-ID: <4D2D9EDA.8050600@loskot.net> (raw)
In-Reply-To: <4D2D92CF.2050204@loskot.net>

[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]

On 12/01/11 11:38, Mateusz Loskot wrote:
> On 10/01/11 22:18, Stefan Weil wrote:
>> Am 10.01.2011 18:59, schrieb Mateusz Loskot:
 >>>
>>> I quickly tried your binaries and it looks I have to run them from
>>> within MSYS environment, isn't it?
>>> I'm getting runtime error reporting msys-z.dll is missing.
>>
>> The missing dll(s) are now available at http://www.weilnetz.de/qemu/.
>
> I grabbed the recent version from http://www.weilnetz.de/qemu/2011-01-10/
> and the three DLLs from the http://www.weilnetz.de/qemu/
> but the msys-z.dll is still reported as missing.

I managed to run your binaries inside MSYS shell and the msys-z.dll 
complain disappeared. However, when I try to use qmake-img, funny things
happen. It looks the size parameter is not parsed properly.

For example:

- these commands work

qemu-img.exe create hda.img 10M
qemu-img.exe create hda.img 2000M

- these don't work

qemu-img.exe create hda.img 10G
qemu-img.exe create hda.img 2500M


Screenshot attached.

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Member of ACCU, http://accu.org

[-- Attachment #2: msys-qemu-img-create-size.jpg --]
[-- Type: image/jpeg, Size: 44641 bytes --]

  reply	other threads:[~2011-01-12 12:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07 17:28 [Qemu-devel] Linux as VirtualBox quest OS with QEMU running Solaris Mateusz Loskot
2011-01-07 17:36 ` Michal Suchanek
2011-01-10 11:17   ` Mateusz Loskot
2011-01-07 18:15 ` Stefan Weil
2011-01-10 11:19   ` Mateusz Loskot
2011-01-10 17:08     ` Stefan Weil
2011-01-10 17:59       ` Mateusz Loskot
2011-01-10 21:04         ` Artyom Tarasenko
2011-01-12 11:47           ` Mateusz Loskot
2011-01-12 11:57             ` Artyom Tarasenko
2011-01-12 12:32               ` Mateusz Loskot
2011-01-12 14:28                 ` Mateusz Loskot
2011-01-12 14:40                   ` Artyom Tarasenko
2011-01-12 15:21                     ` Mateusz Loskot
2011-01-12 16:48                       ` Michal Suchanek
2011-01-12 17:15                         ` Mateusz Loskot
2011-01-12 19:00                           ` Blue Swirl
2011-01-12 23:34                           ` Mateusz Loskot
2011-01-13 10:13                             ` Michal Suchanek
2011-01-13 12:40                               ` Mateusz Loskot
2011-01-13 16:01                                 ` Mateusz Loskot
2011-01-10 22:18         ` Stefan Weil
2011-01-12 11:38           ` Mateusz Loskot
2011-01-12 12:30             ` Mateusz Loskot [this message]
2011-01-12 19:05               ` Stefan Weil
2011-01-12 19:17                 ` Stefan Weil
2011-01-12 21:37                   ` Michal Suchanek
2011-01-12 21:46                     ` Stefan Weil
2011-01-07 20:37 ` Blue Swirl
2011-01-10 11:22   ` Mateusz Loskot
2011-01-13 15:32 ` [Qemu-devel] " Mateusz Loskot

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=4D2D9EDA.8050600@loskot.net \
    --to=mateusz@loskot.net \
    --cc=qemu-devel@nongnu.org \
    --cc=weil@mail.berlios.de \
    /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).