[Qemu-devel] qemu-gnemul tarball moved?

2008-01-11 Thread VMiklos
hi,

there was a tarball at
http://fabrice.bellard.free.fr/qemu/qemu-gnemul-0.5.3.tar.gz which
contained several test binaries for sparc, ppc, and other archs. where
this has been moved to? i find it very useful.

thanks,
- VMiklos




[Qemu-devel] qemu 0.8.1 && sparc-user && x86_64

2006-05-19 Thread VMiklos

hi

qemu 0.8.1 (0.8.0, too) fails to compile on x86_64 if sparc-user is
enabled:

gcc-3.3 -Wall -O2 -g -fno-strict-aliasing -I. -I..
-I/var/tmp/fst/src/qemu-0.8.1/target-sparc -I/var/tmp/fst/src/qemu-0.8.1
-I/var/tmp/fst/src/qemu-0.8.1/linux-user
-I/var/tmp/fst/src/qemu-0.8.1/linux-user/sparc -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-I/var/tmp/fst/src/qemu-0.8.1/fpu -I/var/tmp/fst/src/qemu-0.8.1/slirp -c
-o translate-op.o /var/tmp/fst/src/qemu-0.8.1/translate-op.c
In file included from /var/tmp/fst/src/qemu-0.8.1/translate-op.c:36:
op.h: In function `dyngen_code':
op.h:3759: error: syntax error before '.' token
op.h:3761: error: syntax error before '.' token
make[1]: *** [translate-op.o] Error 1
make[1]: Leaving directory `/var/tmp/fst/src/qemu-0.8.1/sparc-user'
make: *** [all] Error 1

is this a known issue?

thanks,
VMiklos

--
Developer of Frugalware Linux, to make things frugal - http://frugalware.org


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


[Qemu-devel] initrd & kernel panic

2006-06-24 Thread VMiklos

hi

currently i'm using qemu in the following way to test our installer on x86:
1) build the kernel
2) build the initrd
3) build a mini iso with a grub that boots the kernel

it would be nice if i could avoid the 3rd step

what i've tried:

http://frugalware.org/~vmiklos/logs/qemu-initrd.log

if i generate the iso and boot this kernel & initrd with the same
parameters from grub, it works fine

have i missed something?

thanks,
VMiklos

--
Developer of Frugalware Linux, to make things frugal - http://frugalware.org


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] initrd & kernel panic

2006-06-25 Thread VMiklos

hi,

2006/6/24, Paul Brook <[EMAIL PROTECTED]>:

> what i've tried:
>
> http://frugalware.org/~vmiklos/logs/qemu-initrd.log
>
> if i generate the iso and boot this kernel & initrd with the same
> parameters from grub, it works fine
>
> have i missed something?

You're telling it to load the initrd from floppy, which is obviously wrong.
qemu already loaded the initrd. Remove all the broken initrd/ramdisk kernel
commandline bits.


initrd=initrd-i686.img.gz -> dropped
load_ramdisk=1 -> dropped
prompt_ramdisk=0 -> dropped
ramdisk_size=33888 -> dropped
rw -> kept
root=/dev/ram -> dropped
console=ttyS0 -> kept as you requested

now it panics with:
"RAMDISK: Couldn't find valid RAM disk image starting at 0.
VFS: Cannot open root device "" or unknown-block(33,2)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(33,2)"

ok, let's append root=/dev/ram again, still panics:
"RAMDISK: Couldn't find valid RAM disk image starting at 0.
XFS: bad magic number
XFS: SB validate failed
No filesystem could mount root, tried:  reiserfs ext3 ext2 xfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)"

have i missed something?

thanks,
VMiklos

--
Developer of Frugalware Linux, to make things frugal - http://frugalware.org


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] initrd & kernel panic

2006-06-26 Thread VMiklos

2006/6/26, Ed Swierk <[EMAIL PROTECTED]>:

What format is your initrd? It should be either a gzipped cpio archive
(initramfs) or an uncompressed filesystem image file.

See http://lxr.linux.no/source/Documentation/initrd.txt and
http://lxr.linux.no/source/Documentation/early-userspace/README.


as i said the kernel&initrd is ok if i boot them (using grub) from an
iso image. anyway i've tried to uncompress the gzipped initrd, and it
didn't help (same "RAMDISK: Couldn't find valid RAM disk image
starting at 0." error message)

if grub is able to boot the kernel & initrd and qemu isn't then the
kernel & initrd should be ok, just the parameters may be wrong or
there should be some problem with qemu itself. or am i wrong?

thanks,
VMiklos

--
Developer of Frugalware Linux, to make things frugal - http://frugalware.org


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


[Qemu-devel] [PATCH] fix i386-softmmu with newer kernel headers

2007-01-23 Thread VMiklos

hi

with newer kernel-headers, i get the following compile error:
gcc-3.3 -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I.
-I.. -I/var/tmp/fst/src/qemu-0.8.2/target-i386
-I/var/tmp/fst/src/qemu-0.8.2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -I/var/tmp/fst/src/qemu-0.8.2/fpu -DHAS_AUDIO
-I/var/tmp/fst/src/qemu-0.8.2/slirp -c -o usb-linux.o
/var/tmp/fst/src/qemu-0.8.2/usb-linux.c
/var/tmp/fst/src/qemu-0.8.2/usb-linux.c:29:28: linux/compiler.h: No
such file or directory
make[1]: *** [usb-linux.o] Error 1
make[1]: Leaving directory `/var/tmp/fst/src/qemu-0.8.2/i386-softmmu'
make: *** [subdir-i386-softmmu] Error 2

is this a known issue?

a trivial patch is here:

http://darcs.frugalware.org/repos/frugalware-current/source/xapps-extra/qemu/qemu-0.8.2-include.diff

i'm not sure about what would require that inclusion. i mean in case i
would know, of course i would send some
#ifndef FOO
#include 
#endif
patch :)

thanks,
VMiklos

--
Developer of Frugalware Linux, to make things frugal - http://frugalware.org


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


[Qemu-devel] weird errors on x86_64 target (i686 host)

2005-05-18 Thread VMiklos
hi
i just tried out the new x86_64 target (version 0.7.0), wanted to 
install a gentoo system.

i downloaded the install livecd:
http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/releases/amd64/2005.0/installcd/install-amd64-minimal-2005.0.iso
here are the first problem. most commands works fine, but for example if 
you try to 'ssh someserver', it'll fail

the full installation works fine, you can boot the target system, but 
major upgrades (gcc, glibc compilations) fails with internal compiler error

yes, i checked that if i do the same on a real x86_64 host, it compiles 
without any problem

if you need any additional info pls let me know
udv / greetings,
VMiklos
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] weird errors on x86_64 target (i686 host)

2005-05-29 Thread VMiklos

VMiklos wrote:
i just tried out the new x86_64 target (version 0.7.0), wanted to 
install a gentoo system.


i downloaded the install livecd:

http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/releases/amd64/2005.0/installcd/install-amd64-minimal-2005.0.iso 

here are the first problem. most commands works fine, but for example if 
you try to 'ssh someserver', it'll fail


the full installation works fine, you can boot the target system, but 
major upgrades (gcc, glibc compilations) fails with internal compiler error


yes, i checked that if i do the same on a real x86_64 host, it compiles 
without any problem


if you need any additional info pls let me know


any ideas?

udv / greetings,
VMiklos


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel