qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: Cloop-Driver, was Re: [Qemu-devel] QEMU with KNOPPIX
Date: Sat, 28 Aug 2004 00:32:27 +0200	[thread overview]
Message-ID: <412FB67B.4070705@bellard.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0408271844500.12292@wgmdd8.biozentrum.uni-wuerzburg.de>

I'll merge your cloop patch ASAP.

Fabrice.

Johannes Schindelin wrote:
> Hi,
> 
> On Fri, 27 Aug 2004, Johannes Schindelin wrote:
> 
> 
>>On Fri, 27 Aug 2004, Piotr Krysik wrote:
>>
>>>It can work in Windows, if you implement support
>>>of cloop-compatible image format in Qemu executable.
>>>
>>>Just look at qcow compressed image format. Qemu
>>>doesn't require any additional services from host
>>>OS. The decompression is implemented by Qemu and
>>>is transparent for guest.
>>
>>Hint: for space reasons, the cloop image is an ISO9660 formatted Linux
>>system, so you probably have to have an ISO9660 enabled (not module)
>>kernel, and you probably have to specify the kernel separately via
>>"-kernel", as the cloop image (at least to my knowledge) does not contain
>>a valid boot loader.
> 
> 
> Okay, so I hacked together a driver which is able to read at least the
> newest Knoppix image (from 3.6EN).
> 
> Only problem: When you start it with
> 
> qemu -hda /cdrom/KNOPPIX/KNOPPIX \
>   -kernel /cdrom/boot/isolinux/linux24 \
>   -initrd /cdrom/boot/isolinux/minirt24.gz \
>   -append root=/dev/hda
> 
> Knoppix believes it runs from the HD (installed version) and does not
> recreate /etc/fstab, and then just stops.
> 
> Any Knoppix hackers out there? Maybe one can trick Knoppix into recreating
> all these files nontheless?
> 
> Ciao,
> Dscho
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel

  parent reply	other threads:[~2004-08-27 22:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25  7:09 [Qemu-devel] QEMU with KNOPPIX Kuniyasu Suzaki
2004-08-25 10:02 ` John R. Hogerhuis
2004-08-26  5:19   ` Kuniyasu Suzaki
2004-08-26  6:13     ` John R. Hogerhuis
2004-08-26  7:57       ` Kuniyasu Suzaki
2004-08-26  9:34         ` John R. Hogerhuis
2004-08-27  5:58           ` Kuniyasu Suzaki
2004-08-26 11:41         ` Johannes Schindelin
2004-08-26 12:56       ` Piotr Krysik
2004-08-26 15:49         ` Johannes Schindelin
2004-08-27  6:06         ` Kuniyasu Suzaki
2004-08-27  8:35           ` Piotr Krysik
2004-08-27 10:08             ` Johannes Schindelin
2004-08-27 17:00               ` Cloop-Driver, was " Johannes Schindelin
2004-08-27 20:40                 ` Juergen Lock
2004-08-29 13:52                   ` Johannes Schindelin
2004-08-30  4:32                     ` coLinux and " Kuniyasu Suzaki
2004-08-27 22:32                 ` Fabrice Bellard [this message]
2004-08-27 22:40       ` Fabrice Bellard
2004-08-28  3:53         ` Kuniyasu Suzaki

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=412FB67B.4070705@bellard.org \
    --to=fabrice@bellard.org \
    --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).