Qemu says :
CDROM boot failure code : 0003
Boot from CD-Rom failed
FATAL : Could not read the boot disk
Is this unsupported at the moment or am I using the wrong command line
?
From rombios.c:
- CD-ROM booting is only available if ATA/ATAPI Driver is available
Since the bios lacks support f
Hi,
before talking about the bad things, I have to remark, that qemu is a
great program. I like it for it's simplicity and I cherish the
integrated gdb-stub, wich avoided a lot of headaches in my early
kernel-develpment phase, when no own serial debugger stub existed. And
secondly, I hope thi
I'm having the same problem over CVS's HEAD but my kernel is newer and I don't
have linux/compiler.h ... any hint? please :(
Thanks,
Alejandro Mery
CVSROOT:/cvsroot/qemu
Module name:qemu
Changes by: Blue Swirl 08/03/14 21:09:15
Modified files:
target-sparc : translate.c
Log message:
Eliminate some uses of T2
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/target-sparc/translate.c?cvsroot=qemu&r1=1
I am trying to boot an iso image (taking the tomsrtbt for example) from an SCSI
cdrom drive.
Qemu is current HEAD.
There is my command line :
qemu -drive file=/mnt/hdb/isos/tomsrtbt-2.0.103.iso,if=scsi,media=cdrom
Qemu says :
CDROM boot failure code : 0003
Boot from CD-Rom failed
FATAL : Could
CVSROOT:/cvsroot/qemu
Module name:qemu
Changes by: Blue Swirl 08/03/14 19:42:42
Modified files:
target-sparc : op.c translate.c
Log message:
Convert udivx and sdivx to TCG
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/target-sparc/op.c?cvsroot=qemu&r
CVSROOT:/cvsroot/qemu
Module name:qemu
Changes by: Blue Swirl 08/03/14 17:37:12
Modified files:
. : exec.c
Log message:
Allow op_opt for all targets
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/exec.c?cvsroot=qemu&r1=1.123&r2=1.124
CVSROOT:/cvsroot/qemu
Module name:qemu
Changes by: Blue Swirl 08/03/14 17:35:03
Modified files:
target-sparc : translate.c
Log message:
Use memory globals for G registers
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/target-sparc/translate.c?cvsroot=
Hi,
On Mon, Mar 3, 2008 at 8:28 PM, Rob Landley <[EMAIL PROTECTED]> wrote:
> Quick and dirty patch to teach qemu application emulation how to chroot (and
> drop privs), so you don't have to pollute a target filesystem with host code,
> and/or figure out how to build qemu static in order to run a
On Friday 14 March 2008 09:08:57 Edgar E. Iglesias wrote:
> > Even then, attempting to deal with things like symlinks that point to
> > absolute paths would be quite a headache, and considering the default
> > busybox install does exactly that, it's not exactly an unheard of corner
> > case...
>
>
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Edgar E. Iglesias08/03/14 14:11:05
Modified files:
linux-user : mmap.c
Log message:
Use TARGET_FMT_lx.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/linux-user/mmap.c?cvsroot=qemu&r1=1.20&r2=1.21
On Thu, Mar 06, 2008 at 12:47:12AM -0600, Rob Landley wrote:
> On Wednesday 05 March 2008 01:54:08 Edgar E. Iglesias wrote:
> > On Wed, Mar 05, 2008 at 12:51:36AM -0600, Rob Landley wrote:
> > > On Tuesday 04 March 2008 05:22:12 you wrote:
> > > > On Mon, Mar 03, 2008 at 06:28:22PM -0600, Rob Landl
Philip Boulain wrote:
> Well done, guys. Someone's trying to build CVS QEMU on gcc4, and you're
> flaming them. This'll really encourage people to work on making
> development versions of QEMU work with gcc4.
May I recommend to everybody involved to cool down a bit?
Working on converting more o
On Friday 14 March 2008 07:59:28 am Rick Vernam wrote:
> And it is necessary to have configure require a special step to build with
> gcc4 anyway.
necessary, as in a very good idea.
necessary to inform those who might not otherwise know...
On Friday 14 March 2008 06:07:37 am Andreas Färber wrote:
> > So I absolutely _fail_ to understand what you thought, implying that
> > I was
> > restricting platform variability.
>
> So in fact you do agree with Rick on that part and replied to the
> 'wrong' message, creating minor confusion: I
> WTF? Rick suggested removing that configure message that you need to
> explicitely override its quite sane default to refuse work with gcc4,
> because at least one platform (the most common one) has problems with it.
I did? where? when? You might have mis-read something.
>
> I was against rem
Well done, guys. Someone's trying to build CVS QEMU on gcc4, and
you're flaming them. This'll really encourage people to work on
making development versions of QEMU work with gcc4.
On 14 Mar 2008, at 10:53, Johannes Schindelin wrote:
WTF?
The point at which you start using profanity on a -
Hi,
Am 14.03.2008 um 11:53 schrieb Johannes Schindelin:
On Fri, 14 Mar 2008, Markus Hitter wrote:
Am 14.03.2008 um 00:32 schrieb Johannes Schindelin:
On Thu, 13 Mar 2008, Rick Vernam wrote:
[gcc4] Not supported? Okay, fine. But don't tell me it can't
work.
The fact of the matter is t
Hi,
On Fri, 14 Mar 2008, Markus Hitter wrote:
>
> Am 14.03.2008 um 00:32 schrieb Johannes Schindelin:
>
> >On Thu, 13 Mar 2008, Rick Vernam wrote:
> >
> > >[gcc4] Not supported? Okay, fine. But don't tell me it can't work.
> > >The fact of the matter is that I use it daily.
> > >
> > >Make c
Am 14.03.2008 um 00:32 schrieb Johannes Schindelin:
On Thu, 13 Mar 2008, Rick Vernam wrote:
[gcc4] Not supported? Okay, fine. But don't tell me it can't work.
The fact of the matter is that I use it daily.
Make configure fail horribly? Well, that seems a bit counter-
productive,
don't y
20 matches
Mail list logo
