From: De Leeuw Guy <G.De_Leeuw@eurofer.be>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu debian etch
Date: Mon, 16 Jan 2006 20:59:31 +0100 [thread overview]
Message-ID: <43CBFB23.4060604@eurofer.be> (raw)
In-Reply-To: <Pine.LNX.4.61.0601162121560.2319@home.oyster.ru>
malc a écrit :
> On Mon, 16 Jan 2006, De Leeuw Guy wrote:
>
>> Hello all,
>>
>> I'm new with qemu.
>> I install qemu and kqemu by download and compile the sources
>> qemu-0.8.0 and kqemu-0.7.2 on a debian testing
>> I try to install windows xp pro upgrade version (official) , the boot
>> start and after different stages
>> windows ask me to change the cdrom and put a valid version of windows
>> (aka xp home, winme, ect...)
>> I upgrade from my official xp home
>> I switch to the qemu console (ctrl-alt-shift-2) and I run these
>> commands :
>> eject cdrom (and I change the media xp pro by my xp home)
>> change cdrom /dev/cdrom
>> ctrl-alt-shift-1
>> enter
>> and the install xp tools go back to the same message (the cdrom led
>> still inactive)
>> How can I force the change of the cdrom for xp ?
>>
>> I test this couple of media on a pc test and the install work.
>>
>> I try to copy via dd the two cdrom on my harddrive and launch qemu with
>> the two images, but same: not working
>>
>> When I trie to install a full version of windows xp pro, ok work fine.
>>
>>
>> Can you help me ?
>
>
> Linuxs VFS is blissfuly unaware that the physical media has changed and
> therefore when QEMU tries to read from the fd that corresponds to
> /dev/cdrom it gets old (cached) data.
>
> To workaround you can dump the contents of your physical CDs on disk and
> install from them.
>
Thanks, but I try that have you a particular example to process ?
Guy
prev parent reply other threads:[~2006-01-16 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 14:08 [Qemu-devel] qemu debian etch De Leeuw Guy
2006-01-16 18:25 ` malc
2006-01-16 19:59 ` De Leeuw Guy [this message]
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=43CBFB23.4060604@eurofer.be \
--to=g.de_leeuw@eurofer.be \
--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).