* [Qemu-devel] Nothing happens @ 2005-05-18 19:17 Rudi Lippert 2005-05-18 20:55 ` Hetz Ben Hamo 2005-05-21 12:07 ` [Qemu-devel] " Per-Erik Kristensson 0 siblings, 2 replies; 17+ messages in thread From: Rudi Lippert @ 2005-05-18 19:17 UTC (permalink / raw) To: qemu-devel Hi! I keep wondering why QEMU does not do anything when I start it. First of all: yes, I know how to use QEMU. When I use it on my other PC, it works like a charm. The major difference between the two systems is, that this one is an AMD64. And here is what happens when I start QEMU: Nothing. No output, no CPU activity. I know that this is not a whole lot of information, but I will provide any further information that is requested. Thanks in advance! Rudi Lippert (Herzogenaurach, Germany) ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [Qemu-devel] Nothing happens 2005-05-18 19:17 [Qemu-devel] Nothing happens Rudi Lippert @ 2005-05-18 20:55 ` Hetz Ben Hamo 2005-05-18 21:32 ` [Qemu-devel] " Rudi Lippert 2005-05-21 12:07 ` [Qemu-devel] " Per-Erik Kristensson 1 sibling, 1 reply; 17+ messages in thread From: Hetz Ben Hamo @ 2005-05-18 20:55 UTC (permalink / raw) To: qemu-devel How about starting with trivial details such as: * Which host OS do you use? * Which QEMU version? * binaries downloaded or did you compile it? Thanks, Hetz On 5/18/05, Rudi Lippert <Rudi@lyrikpage.de> wrote: > Hi! > I keep wondering why QEMU does not do anything when I start it. > First of all: yes, I know how to use QEMU. When I use it on my other PC, it > works like a charm. > The major difference between the two systems is, that this one is an AMD64. > And here is what happens when I start QEMU: > Nothing. No output, no CPU activity. > I know that this is not a whole lot of information, but I will provide any > further information that is requested. > Thanks in advance! > > Rudi Lippert (Herzogenaurach, Germany) > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel > ^ permalink raw reply [flat|nested] 17+ messages in thread
* [Qemu-devel] Re: Nothing happens 2005-05-18 20:55 ` Hetz Ben Hamo @ 2005-05-18 21:32 ` Rudi Lippert 2005-05-18 21:57 ` Struan Bartlett 0 siblings, 1 reply; 17+ messages in thread From: Rudi Lippert @ 2005-05-18 21:32 UTC (permalink / raw) To: qemu-devel My OS: GNU/Linux (Gentoo) QEMU Version: 0.7.0, compiled using the standard ebuild; no kqemu or qvm86 I'd include the exact build options, but they're rather lengthy. I've experienced the same problem with 0.6.1 and CVS somewhere in between 0.6.1 and 0.7.0. Cheers, Rudi Hetz Ben Hamo wrote: > How about starting with trivial details such as: > > * Which host OS do you use? > * Which QEMU version? > * binaries downloaded or did you compile it? > > Thanks, > Hetz > > On 5/18/05, Rudi Lippert <Rudi@lyrikpage.de> wrote: >> Hi! >> I keep wondering why QEMU does not do anything when I start it. >> First of all: yes, I know how to use QEMU. When I use it on my other PC, >> it works like a charm. >> The major difference between the two systems is, that this one is an >> AMD64. And here is what happens when I start QEMU: >> Nothing. No output, no CPU activity. >> I know that this is not a whole lot of information, but I will provide >> any further information that is requested. >> Thanks in advance! >> >> Rudi Lippert (Herzogenaurach, Germany) >> >> _______________________________________________ >> Qemu-devel mailing list >> Qemu-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/qemu-devel >> ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [Qemu-devel] Re: Nothing happens 2005-05-18 21:32 ` [Qemu-devel] " Rudi Lippert @ 2005-05-18 21:57 ` Struan Bartlett 2005-05-19 9:23 ` [Qemu-devel] " Rudi Lippert 0 siblings, 1 reply; 17+ messages in thread From: Struan Bartlett @ 2005-05-18 21:57 UTC (permalink / raw) To: qemu-devel How do you mean 'nothing'? Can you be more precise? Does it display the network interface configuration? open the guest window? Or really is does it just hang immediately? With the '-monitor stdio' option does it give you a monitor prompt? Have you tried running qemu with: strace qemu <your normal options> 2>/tmp/qemu.log On Wed, 18 May 2005, Rudi Lippert wrote: > My OS: > GNU/Linux (Gentoo) > QEMU Version: > 0.7.0, compiled using the standard ebuild; no kqemu or qvm86 > I'd include the exact build options, but they're rather lengthy. > > I've experienced the same problem with 0.6.1 and CVS somewhere in between > 0.6.1 and 0.7.0. > > Cheers, > Rudi > > Hetz Ben Hamo wrote: > > > How about starting with trivial details such as: > > > > * Which host OS do you use? > > * Which QEMU version? > > * binaries downloaded or did you compile it? > > > > Thanks, > > Hetz > > > > On 5/18/05, Rudi Lippert <Rudi@lyrikpage.de> wrote: > >> Hi! > >> I keep wondering why QEMU does not do anything when I start it. > >> First of all: yes, I know how to use QEMU. When I use it on my other PC, > >> it works like a charm. > >> The major difference between the two systems is, that this one is an > >> AMD64. And here is what happens when I start QEMU: > >> Nothing. No output, no CPU activity. > >> I know that this is not a whole lot of information, but I will provide > >> any further information that is requested. > >> Thanks in advance! > >> > >> Rudi Lippert (Herzogenaurach, Germany) > >> > >> _______________________________________________ > >> Qemu-devel mailing list > >> Qemu-devel@nongnu.org > >> http://lists.nongnu.org/mailman/listinfo/qemu-devel > >> > > > > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel > ^ permalink raw reply [flat|nested] 17+ messages in thread
* [Qemu-devel] Re: Re: Nothing happens 2005-05-18 21:57 ` Struan Bartlett @ 2005-05-19 9:23 ` Rudi Lippert 2005-05-19 23:30 ` Struan Bartlett 2005-05-20 8:12 ` Oliver Gerlich 0 siblings, 2 replies; 17+ messages in thread From: Rudi Lippert @ 2005-05-19 9:23 UTC (permalink / raw) To: qemu-devel [-- Attachment #1: Type: text/plain, Size: 1860 bytes --] well, nothing really means nothing. the guest window does not come up, and the console window does not show anything, even with -monitor stdio. the thread just goes to sleep. strace may be interesting, and 5kb are not too much, i think, so here it comes. thanks for now, Rudi Struan Bartlett wrote: > How do you mean 'nothing'? Can you be more precise? > > Does it display the network interface configuration? open the guest > window? Or really is does it just hang immediately? With the '-monitor > stdio' option does it give you a monitor prompt? > > Have you tried running qemu with: > > strace qemu <your normal options> 2>/tmp/qemu.log > > On Wed, 18 May 2005, Rudi Lippert wrote: > >> My OS: >> GNU/Linux (Gentoo) >> QEMU Version: >> 0.7.0, compiled using the standard ebuild; no kqemu or qvm86 >> I'd include the exact build options, but they're rather lengthy. >> >> I've experienced the same problem with 0.6.1 and CVS somewhere in between >> 0.6.1 and 0.7.0. >> >> Cheers, >> Rudi >> >> Hetz Ben Hamo wrote: >> >> > How about starting with trivial details such as: >> > >> > * Which host OS do you use? >> > * Which QEMU version? >> > * binaries downloaded or did you compile it? >> > >> > Thanks, >> > Hetz >> > >> > On 5/18/05, Rudi Lippert <Rudi@lyrikpage.de> wrote: >> >> Hi! >> >> I keep wondering why QEMU does not do anything when I start it. >> >> First of all: yes, I know how to use QEMU. When I use it on my other >> >> PC, it works like a charm. >> >> The major difference between the two systems is, that this one is an >> >> AMD64. And here is what happens when I start QEMU: >> >> Nothing. No output, no CPU activity. >> >> I know that this is not a whole lot of information, but I will provide >> >> any further information that is requested. >> >> Thanks in advance! >> >> >> >> Rudi Lippert (Herzogenaurach, Germany) >> >> [-- Attachment #2: qemu.log --] [-- Type: text/plain, Size: 5363 bytes --] execve("./run", ["./run", "-monitor", "stdio"], [/* 57 vars */]) = 0 uname({sys="Linux", node="rudi", ...}) = 0 brk(0) = 0x5ba000 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2a9556b000 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 3 fstat(3, {st_mode=S_IFREG|0644, st_size=100748, ...}) = 0 mmap(NULL, 100748, PROT_READ, MAP_PRIVATE, 3, 0) = 0x2a9556c000 close(3) = 0 open("/lib/libdl.so.2", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340\17\0"..., 640) = 640 lseek(3, 624, SEEK_SET) = 624 read(3, "\4\0\0\0\20\0\0\0\1\0\0\0GNU\0\0\0\0\0\2\0\0\0\4\0\0\0"..., 32) = 32 fstat(3, {st_mode=S_IFREG|0755, st_size=11480, ...}) = 0 mmap(NULL, 1056984, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x2a9566c000 mprotect(0x2a9566e000, 1048792, PROT_NONE) = 0 mmap(0x2a9576c000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0) = 0x2a9576c000 close(3) = 0 open("/lib/libc.so.6", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\316"..., 640) = 640 lseek(3, 624, SEEK_SET) = 624 read(3, "\4\0\0\0\20\0\0\0\1\0\0\0GNU\0\0\0\0\0\2\0\0\0\4\0\0\0"..., 32) = 32 fstat(3, {st_mode=S_IFREG|0755, st_size=1270528, ...}) = 0 mmap(NULL, 2250248, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x2a9576f000 mprotect(0x2a9588b000, 1086984, PROT_NONE) = 0 mmap(0x2a9596f000, 135168, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x100000) = 0x2a9596f000 mmap(0x2a95990000, 17928, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x2a95990000 close(3) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2a95995000 mprotect(0x2a9598a000, 12288, PROT_READ) = 0 munmap(0x2a9556c000, 100748) = 0 open("/dev/urandom", O_RDONLY) = 3 read(3, "\211\377\260-\276\3508\247", 8) = 8 close(3) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [RTMIN], 8) = 0 open("/dev/tty", O_RDWR|O_NONBLOCK) = 3 close(3) = 0 brk(0) = 0x5ba000 brk(0x5db000) = 0x5db000 getuid() = 1000 getgid() = 100 geteuid() = 1000 getegid() = 100 rt_sigprocmask(SIG_BLOCK, NULL, [RTMIN], 8) = 0 open("/etc/mtab", O_RDONLY) = 3 fstat(3, {st_mode=S_IFREG|0644, st_size=694, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2a9556c000 read(3, "/dev/hdc3 / ext3 rw,noatime 0 0\n"..., 4096) = 694 close(3) = 0 munmap(0x2a9556c000, 4096) = 0 open("/proc/meminfo", O_RDONLY) = 3 fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2a9556c000 read(3, "MemTotal: 1026832 kB\nMemFre"..., 1024) = 600 close(3) = 0 munmap(0x2a9556c000, 4096) = 0 rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0 rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0 rt_sigaction(SIGINT, {SIG_DFL}, {SIG_DFL}, 8) = 0 rt_sigaction(SIGINT, {SIG_DFL}, {SIG_DFL}, 8) = 0 rt_sigaction(SIGQUIT, {SIG_DFL}, {SIG_DFL}, 8) = 0 rt_sigaction(SIGQUIT, {SIG_DFL}, {SIG_DFL}, 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [RTMIN], 8) = 0 rt_sigaction(SIGQUIT, {SIG_IGN}, {SIG_DFL}, 8) = 0 uname({sys="Linux", node="rudi", ...}) = 0 stat("/vms/w2k", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat(".", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 getpid() = 11960 getppid() = 11959 getpgrp() = 11959 rt_sigaction(SIGCHLD, {0x431290, [], SA_RESTORER, 0x2a9579eba0}, {SIG_DFL}, 8) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [RTMIN], 8) = 0 open("./run", O_RDONLY) = 3 ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, 0x7fbfffefe0) = -1 ENOTTY (Inappropriate ioctl for device) lseek(3, 0, SEEK_CUR) = 0 read(3, "#!/bin/bash\n/usr/local/bin/qemu "..., 80) = 76 lseek(3, 0, SEEK_SET) = 0 getrlimit(RLIMIT_NOFILE, {rlim_cur=1024, rlim_max=1024}) = 0 dup2(3, 255) = 255 close(3) = 0 fcntl(255, F_SETFD, FD_CLOEXEC) = 0 fcntl(255, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE) fstat(255, {st_mode=S_IFREG|0755, st_size=76, ...}) = 0 lseek(255, 0, SEEK_CUR) = 0 rt_sigprocmask(SIG_BLOCK, NULL, [RTMIN], 8) = 0 read(255, "#!/bin/bash\n/usr/local/bin/qemu "..., 76) = 76 rt_sigprocmask(SIG_BLOCK, NULL, [RTMIN], 8) = 0 rt_sigprocmask(SIG_BLOCK, [INT CHLD], [RTMIN], 8) = 0 fork() = 11961 rt_sigprocmask(SIG_SETMASK, [RTMIN], NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, [CHLD], [RTMIN], 8) = 0 rt_sigprocmask(SIG_SETMASK, [RTMIN], NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, [CHLD], [RTMIN], 8) = 0 rt_sigaction(SIGINT, {0x4300d0, [], SA_RESTORER, 0x2a9579eba0}, {SIG_DFL}, 8) = 0 wait4(-1, <unfinished ...> ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [Qemu-devel] Re: Re: Nothing happens 2005-05-19 9:23 ` [Qemu-devel] " Rudi Lippert @ 2005-05-19 23:30 ` Struan Bartlett 2005-05-20 8:12 ` Oliver Gerlich 1 sibling, 0 replies; 17+ messages in thread From: Struan Bartlett @ 2005-05-19 23:30 UTC (permalink / raw) To: qemu-devel [-- Attachment #1: Type: text/plain, Size: 10896 bytes --] I'm at a bit of a loss to explain this. My strace output is quite different. I'm running the 2005-05-18 snapshot of qemu 0.7.0. I think it's time to start inserting fprintf(stderr, "OK1\n"); statements into your code, recompiling, to trace the error origin (or use gdb). In detail... Yours: $ grep ^open /tmp/qemu.log open("/etc/ld.so.cache", O_RDONLY) = 3 open("/lib/libdl.so.2", O_RDONLY) = 3 open("/lib/libc.so.6", O_RDONLY) = 3 open("/dev/urandom", O_RDONLY) = 3 open("/dev/tty", O_RDWR|O_NONBLOCK) = 3 open("/etc/mtab", O_RDONLY) = 3 open("/proc/meminfo", O_RDONLY) = 3 open("./run", O_RDONLY) = 3 Mine: $ grep ^open /tmp/q.log open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 3 open("/lib/tls/libm.so.6", O_RDONLY) = 3 open("/usr/lib/libz.so.1", O_RDONLY) = 3 open("/usr/lib/libSDL-1.2.so.0", O_RDONLY) = 3 open("/lib/tls/libpthread.so.0", O_RDONLY) = 3 open("/lib/tls/libutil.so.1", O_RDONLY) = 3 open("/lib/tls/libc.so.6", O_RDONLY) = 3 open("/usr/X11R6/lib/libX11.so.6", O_RDONLY) = 3 open("/usr/X11R6/lib/libXext.so.6", O_RDONLY) = 3 open("/usr/lib/libasound.so.2", O_RDONLY) = 3 open("/lib/tls/libdl.so.2", O_RDONLY) = 3 open("/dev/net/tun", O_RDWR|O_LARGEFILE) = 3 open("/dev/shm/qemuybaeub", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0600) = 4 open("/dev/shm/qemuybaeub", O_RDWR|O_CREAT|O_TRUNC|O_LARGEFILE, 0600) = 5 open("c.img", O_RDONLY|O_LARGEFILE) = 6 open("c.img", O_RDWR|O_LARGEFILE) = 6 open("/dev/kqemu", O_RDWR|O_LARGEFILE) = 7 open("/home/struan/.Xauthority", O_RDONLY) = 9 open("/home/struan/.Xauthority", O_RDONLY) = 9 open("/home/struan/.Xauthority", O_RDONLY) = 10 open("/etc/ld.so.cache", O_RDONLY) = 10 open("/usr/lib/libXcursor.so.1", O_RDONLY) = 10 open("/usr/lib/libXrender.so.1", O_RDONLY) = 10 open("/usr/X11R6/lib/X11/locale/locale.alias", O_RDONLY) = 10 open("/usr/X11R6/lib/X11/locale/locale.dir", O_RDONLY) = 10 open("/usr/X11R6/lib/X11/locale/C/XI18N_OBJS", O_RDONLY) = 10 open("/usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2", O_RDONLY) = 10 open("/usr/X11R6/lib/X11/locale/locale.alias", O_RDONLY) = 10 open("/usr/X11R6/lib/X11/locale/locale.dir", O_RDONLY) = 10 open("/usr/X11R6/lib/X11/locale/C/XLC_LOCALE", O_RDONLY) = 10 open("/home/struan/.Xdefaults-xebedee", O_RDONLY) = -1 ENOENT (No such file or directory) open("/proc/stat", O_RDONLY) = 10 open("/usr/local/share/qemu/bios.bin", O_RDONLY|O_LARGEFILE) = 10 open("/usr/local/share/qemu/bios.bin", O_RDONLY|O_LARGEFILE) = 10 open("/usr/local/share/qemu/vgabios-cirrus.bin", O_RDONLY|O_LARGEFILE) = 10 open("/etc/localtime", O_RDONLY) = 10 Rudi Lippert wrote: >well, nothing really means nothing. the guest window does not come up, and >the console window does not show anything, even with -monitor stdio. the >thread just goes to sleep. >strace may be interesting, and 5kb are not too much, i think, so here it >comes. >thanks for now, > >Rudi > > >Struan Bartlett wrote: > > > >>How do you mean 'nothing'? Can you be more precise? >> >>Does it display the network interface configuration? open the guest >>window? Or really is does it just hang immediately? With the '-monitor >>stdio' option does it give you a monitor prompt? >> >>Have you tried running qemu with: >> >>strace qemu <your normal options> 2>/tmp/qemu.log >> >>On Wed, 18 May 2005, Rudi Lippert wrote: >> >> >> >>>My OS: >>>GNU/Linux (Gentoo) >>>QEMU Version: >>>0.7.0, compiled using the standard ebuild; no kqemu or qvm86 >>>I'd include the exact build options, but they're rather lengthy. >>> >>>I've experienced the same problem with 0.6.1 and CVS somewhere in between >>>0.6.1 and 0.7.0. >>> >>>Cheers, >>>Rudi >>> >>>Hetz Ben Hamo wrote: >>> >>> >>> >>>>How about starting with trivial details such as: >>>> >>>>* Which host OS do you use? >>>>* Which QEMU version? >>>>* binaries downloaded or did you compile it? >>>> >>>>Thanks, >>>>Hetz >>>> >>>>On 5/18/05, Rudi Lippert <Rudi@lyrikpage.de> wrote: >>>> >>>> >>>>>Hi! >>>>>I keep wondering why QEMU does not do anything when I start it. >>>>>First of all: yes, I know how to use QEMU. When I use it on my other >>>>>PC, it works like a charm. >>>>>The major difference between the two systems is, that this one is an >>>>>AMD64. And here is what happens when I start QEMU: >>>>>Nothing. No output, no CPU activity. >>>>>I know that this is not a whole lot of information, but I will provide >>>>>any further information that is requested. >>>>>Thanks in advance! >>>>> >>>>>Rudi Lippert (Herzogenaurach, Germany) >>>>> >>>>> >>>>> >>>>>------------------------------------------------------------------------ >>>>> >>>>>execve("./run", ["./run", "-monitor", "stdio"], [/* 57 vars */]) = 0 >>>>>uname({sys="Linux", node="rudi", ...}) = 0 >>>>>brk(0) = 0x5ba000 >>>>>mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2a9556b000 >>>>>access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) >>>>>open("/etc/ld.so.cache", O_RDONLY) = 3 >>>>>fstat(3, {st_mode=S_IFREG|0644, st_size=100748, ...}) = 0 >>>>>mmap(NULL, 100748, PROT_READ, MAP_PRIVATE, 3, 0) = 0x2a9556c000 >>>>>close(3) = 0 >>>>>open("/lib/libdl.so.2", O_RDONLY) = 3 >>>>>read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340\17\0"..., 640) = 640 >>>>>lseek(3, 624, SEEK_SET) = 624 >>>>>read(3, "\4\0\0\0\20\0\0\0\1\0\0\0GNU\0\0\0\0\0\2\0\0\0\4\0\0\0"..., 32) = 32 >>>>>fstat(3, {st_mode=S_IFREG|0755, st_size=11480, ...}) = 0 >>>>>mmap(NULL, 1056984, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x2a9566c000 >>>>>mprotect(0x2a9566e000, 1048792, PROT_NONE) = 0 >>>>>mmap(0x2a9576c000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0) = 0x2a9576c000 >>>>>close(3) = 0 >>>>>open("/lib/libc.so.6", O_RDONLY) = 3 >>>>>read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\316"..., 640) = 640 >>>>>lseek(3, 624, SEEK_SET) = 624 >>>>>read(3, "\4\0\0\0\20\0\0\0\1\0\0\0GNU\0\0\0\0\0\2\0\0\0\4\0\0\0"..., 32) = 32 >>>>>fstat(3, {st_mode=S_IFREG|0755, st_size=1270528, ...}) = 0 >>>>>mmap(NULL, 2250248, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x2a9576f000 >>>>>mprotect(0x2a9588b000, 1086984, PROT_NONE) = 0 >>>>>mmap(0x2a9596f000, 135168, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x100000) = 0x2a9596f000 >>>>>mmap(0x2a95990000, 17928, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x2a95990000 >>>>>close(3) = 0 >>>>>mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2a95995000 >>>>>mprotect(0x2a9598a000, 12288, PROT_READ) = 0 >>>>>munmap(0x2a9556c000, 100748) = 0 >>>>>open("/dev/urandom", O_RDONLY) = 3 >>>>>read(3, "\211\377\260-\276\3508\247", 8) = 8 >>>>>close(3) = 0 >>>>>rt_sigprocmask(SIG_BLOCK, NULL, [RTMIN], 8) = 0 >>>>>open("/dev/tty", O_RDWR|O_NONBLOCK) = 3 >>>>>close(3) = 0 >>>>>brk(0) = 0x5ba000 >>>>>brk(0x5db000) = 0x5db000 >>>>>getuid() = 1000 >>>>>getgid() = 100 >>>>>geteuid() = 1000 >>>>>getegid() = 100 >>>>>rt_sigprocmask(SIG_BLOCK, NULL, [RTMIN], 8) = 0 >>>>>open("/etc/mtab", O_RDONLY) = 3 >>>>>fstat(3, {st_mode=S_IFREG|0644, st_size=694, ...}) = 0 >>>>>mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2a9556c000 >>>>>read(3, "/dev/hdc3 / ext3 rw,noatime 0 0\n"..., 4096) = 694 >>>>>close(3) = 0 >>>>>munmap(0x2a9556c000, 4096) = 0 >>>>>open("/proc/meminfo", O_RDONLY) = 3 >>>>>fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0 >>>>>mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2a9556c000 >>>>>read(3, "MemTotal: 1026832 kB\nMemFre"..., 1024) = 600 >>>>>close(3) = 0 >>>>>munmap(0x2a9556c000, 4096) = 0 >>>>>rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0 >>>>>rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0 >>>>>rt_sigaction(SIGINT, {SIG_DFL}, {SIG_DFL}, 8) = 0 >>>>>rt_sigaction(SIGINT, {SIG_DFL}, {SIG_DFL}, 8) = 0 >>>>>rt_sigaction(SIGQUIT, {SIG_DFL}, {SIG_DFL}, 8) = 0 >>>>>rt_sigaction(SIGQUIT, {SIG_DFL}, {SIG_DFL}, 8) = 0 >>>>>rt_sigprocmask(SIG_BLOCK, NULL, [RTMIN], 8) = 0 >>>>>rt_sigaction(SIGQUIT, {SIG_IGN}, {SIG_DFL}, 8) = 0 >>>>>uname({sys="Linux", node="rudi", ...}) = 0 >>>>>stat("/vms/w2k", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 >>>>>stat(".", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 >>>>>getpid() = 11960 >>>>>getppid() = 11959 >>>>>getpgrp() = 11959 >>>>>rt_sigaction(SIGCHLD, {0x431290, [], SA_RESTORER, 0x2a9579eba0}, {SIG_DFL}, 8) = 0 >>>>>rt_sigprocmask(SIG_BLOCK, NULL, [RTMIN], 8) = 0 >>>>>open("./run", O_RDONLY) = 3 >>>>>ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, 0x7fbfffefe0) = -1 ENOTTY (Inappropriate ioctl for device) >>>>>lseek(3, 0, SEEK_CUR) = 0 >>>>>read(3, "#!/bin/bash\n/usr/local/bin/qemu "..., 80) = 76 >>>>>lseek(3, 0, SEEK_SET) = 0 >>>>>getrlimit(RLIMIT_NOFILE, {rlim_cur=1024, rlim_max=1024}) = 0 >>>>>dup2(3, 255) = 255 >>>>>close(3) = 0 >>>>>fcntl(255, F_SETFD, FD_CLOEXEC) = 0 >>>>>fcntl(255, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE) >>>>>fstat(255, {st_mode=S_IFREG|0755, st_size=76, ...}) = 0 >>>>>lseek(255, 0, SEEK_CUR) = 0 >>>>>rt_sigprocmask(SIG_BLOCK, NULL, [RTMIN], 8) = 0 >>>>>read(255, "#!/bin/bash\n/usr/local/bin/qemu "..., 76) = 76 >>>>>rt_sigprocmask(SIG_BLOCK, NULL, [RTMIN], 8) = 0 >>>>>rt_sigprocmask(SIG_BLOCK, [INT CHLD], [RTMIN], 8) = 0 >>>>>fork() = 11961 >>>>>rt_sigprocmask(SIG_SETMASK, [RTMIN], NULL, 8) = 0 >>>>>rt_sigprocmask(SIG_BLOCK, [CHLD], [RTMIN], 8) = 0 >>>>>rt_sigprocmask(SIG_SETMASK, [RTMIN], NULL, 8) = 0 >>>>>rt_sigprocmask(SIG_BLOCK, [CHLD], [RTMIN], 8) = 0 >>>>>rt_sigaction(SIGINT, {0x4300d0, [], SA_RESTORER, 0x2a9579eba0}, {SIG_DFL}, 8) = 0 >>>>>wait4(-1, <unfinished ...> >>>>> >>>>> >>>>>------------------------------------------------------------------------ >>>>> >>>>>_______________________________________________ >>>>>Qemu-devel mailing list >>>>>Qemu-devel@nongnu.org >>>>>http://lists.nongnu.org/mailman/listinfo/qemu-devel >>>>> >>>>> [-- Attachment #2: Type: text/html, Size: 11240 bytes --] ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [Qemu-devel] Re: Re: Nothing happens 2005-05-19 9:23 ` [Qemu-devel] " Rudi Lippert 2005-05-19 23:30 ` Struan Bartlett @ 2005-05-20 8:12 ` Oliver Gerlich 1 sibling, 0 replies; 17+ messages in thread From: Oliver Gerlich @ 2005-05-20 8:12 UTC (permalink / raw) To: qemu-devel Rudi Lippert wrote: > well, nothing really means nothing. the guest window does not come up, and > the console window does not show anything, even with -monitor stdio. the > thread just goes to sleep. > strace may be interesting, and 5kb are not too much, i think, so here it > comes. > thanks for now, > > Rudi > > [...] Do you have the SDL devel packages installed? Usually people have this problem when they compiled Qemu without SDL... Could you compare what SDL packages are installed on the two computers? ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [Qemu-devel] Nothing happens 2005-05-18 19:17 [Qemu-devel] Nothing happens Rudi Lippert 2005-05-18 20:55 ` Hetz Ben Hamo @ 2005-05-21 12:07 ` Per-Erik Kristensson 2005-05-21 16:26 ` Damien Mascord 1 sibling, 1 reply; 17+ messages in thread From: Per-Erik Kristensson @ 2005-05-21 12:07 UTC (permalink / raw) To: qemu-devel ----- Original Message ----- From: "Rudi Lippert" <Rudi@LYRIKpage.de> > Hi! > I keep wondering why QEMU does not do anything when I start it. > First of all: yes, I know how to use QEMU. When I use it on my other PC, it > works like a charm. I had similar problems when I run qemu on NT4 for a while ago. Using "-nics 0" make the system start. The sad thing is that qemu by default (at least never versions) doesn't write any error messages or output when it's started on Windows. I did report this for a while ago by didn't have any response. http://lists.gnu.org/archive/html/qemu-devel/2005-05/msg00006.html PEK ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [Qemu-devel] Nothing happens 2005-05-21 12:07 ` [Qemu-devel] " Per-Erik Kristensson @ 2005-05-21 16:26 ` Damien Mascord 2005-05-21 21:59 ` Jernej Simončič 0 siblings, 1 reply; 17+ messages in thread From: Damien Mascord @ 2005-05-21 16:26 UTC (permalink / raw) To: qemu-devel Per-Erik Kristensson wrote: >----- Original Message ----- >From: "Rudi Lippert" <Rudi@LYRIKpage.de> > > >>Hi! >>I keep wondering why QEMU does not do anything when I start it. >>First of all: yes, I know how to use QEMU. When I use it on my other PC, >> >> >it > > >>works like a charm. >> >> > >I had similar problems when I run qemu on NT4 for a while ago. Using "-nics >0" make the system start. The sad thing is that qemu by default (at least >never versions) doesn't write any error messages or output when it's started >on Windows. I did report this for a while ago by didn't have any response. > >http://lists.gnu.org/archive/html/qemu-devel/2005-05/msg00006.html > >PEK > > PEK, The no-console-on-Windows can be resolved by linking extra libraries, as per http://lists.gnu.org/archive/html/qemu-devel/2005-04/msg00422.html Damien ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [Qemu-devel] Nothing happens 2005-05-21 16:26 ` Damien Mascord @ 2005-05-21 21:59 ` Jernej Simončič 0 siblings, 0 replies; 17+ messages in thread From: Jernej Simončič @ 2005-05-21 21:59 UTC (permalink / raw) To: Damien Mascord on [qemu-devel] On Saturday, May 21, 2005, 18:26:25, Damien Mascord wrote: > The no-console-on-Windows can be resolved by linking extra libraries, as > per http://lists.gnu.org/archive/html/qemu-devel/2005-04/msg00422.html Actually, no additional libs are needed, just the -mconsole compile-time option. Another option is to edit the compiled executable, I posted a small program that does that a while ago: <http://lists.gnu.org/archive/html/qemu-devel/2005-04/msg00437.html> -- < Jernej Simoncic ><><><><>< http://deepthought.ena.si/ > Logic is a systematic method of coming to the wrong conclusion with confidence. -- Manley's Maxim ^ permalink raw reply [flat|nested] 17+ messages in thread
* [Qemu-devel] Booting Linux in Windows XP @ 2005-06-16 13:12 Aaron Feng 2005-06-16 14:29 ` [Qemu-devel] re: Nothing happens Josef Moffett 0 siblings, 1 reply; 17+ messages in thread From: Aaron Feng @ 2005-06-16 13:12 UTC (permalink / raw) To: qemu-devel Yesterday I tried QEMU for the first time, I downloaded the 0.70 Windows installer package, and everything installed just fine. I also downloaded Mandrake 10 image from freeoszoo.org, but I'm having trouble to get Mandrake to boot. Here is the command I used: qemu.exe -L "path_to_my_mandrake_image" Nothing happened, I just get the prompt back without any errors. Is there any way for me to get a more informative error messages when I'm trying to boot? Thanx in advance.... Aaron Feng ^ permalink raw reply [flat|nested] 17+ messages in thread
* [Qemu-devel] re: Nothing happens 2005-06-16 13:12 [Qemu-devel] Booting Linux in Windows XP Aaron Feng @ 2005-06-16 14:29 ` Josef Moffett 2005-06-16 16:36 ` Paul Brook 2005-06-16 21:25 ` Henrik Nordstrom 0 siblings, 2 replies; 17+ messages in thread From: Josef Moffett @ 2005-06-16 14:29 UTC (permalink / raw) To: qemu-devel I have already sent this, but just before I was confirmed on the list, so I don't think it went through. If it did, please forgive me for a double post - and if you can let me have a ref to any replies it may have received. I have just joined the mail list after coming up with a problem similar to one I googled here and perhaps to which I can add a bit more information. Unfortunatly, I can only add a little more prescision to the problem rather than any answers, but perhaps Rudi Lippert can verify if this is happening to him too. I have a problem after compiling qemu with SDL-devel and KQemu support. The problem seems similar to what has been posted and replied to in the following messages http://www.mail-archive.com/qemu-devel@nongnu.org/msg00540.html but I did find the following with the -monitor stdio; that when I did a screen dump qemu was running and dumping valid (linux, win 98 and winxp) screen images. I only had no access to these - in other words the emulator was working fine, both with and without kqemu, but there was no console or visual output with which to manipulate the emulated virtual machine. (ie no visual and no keyboard/mouse access to the (hidden) console.) here is my configure output using: qemu-0.7.0-i386.tar.gz and : kqemu-0.6.2-1.tar.gz downloaded on Sat 11/06/2005 around 22:oo ---------------- joe@anvard:~/qemu-0.7.0> ./configure Install prefix /usr/local BIOS directory /usr/local/share/qemu binary directory /usr/local/bin Manual directory /usr/local/share/man ELF interp prefix /usr/gnemul/qemu-%M Source path /home/joe/qemu-0.7.0 C compiler gcc make make host CPU i386 host big endian no target list i386-user arm-user armeb-user sparc-user ppc-user i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu gprof enabled no static build no SDL support yes SDL static link no mingw32 support no Adlib support no FMOD support no kqemu support yes KQEMU Linux module configuration: kernel sources /lib/modules/2.6.8-24.16-default/build kbuild type 2.6 ----------------- I am running under Suse 9.2 and the precompiled binaries work right "out of the box" (even the network stuff which some people seem to be having trouble with) but are just a tad too slow for what I wanted to use qemu for so I wanted to try with kqemu built in. I first just tried without the SDL-devel libs, but that was the same, and the above mentioned thread suggested that SDL may be a cause (although I suspect we may be talking of different problems). The thing is, once the virtual machine achieves a state of "completion" (ie windows gets to the login promt, or linux gets to the bash prompt - same problem there by the way) the cpu cycles disappear as the virtual machine is not doing any work at all. So perhaps the problem is the same? Any help would be appreciated... ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [Qemu-devel] re: Nothing happens 2005-06-16 14:29 ` [Qemu-devel] re: Nothing happens Josef Moffett @ 2005-06-16 16:36 ` Paul Brook 2005-06-16 18:15 ` Thayne Harbaugh 2005-06-16 21:25 ` Henrik Nordstrom 1 sibling, 1 reply; 17+ messages in thread From: Paul Brook @ 2005-06-16 16:36 UTC (permalink / raw) To: qemu-devel; +Cc: Josef Moffett > I first just tried without the SDL-devel libs, but that was the same, > and the above mentioned thread suggested that SDL may be a cause > (although I suspect we may be talking of different problems). Did you actually do a clean build after installing sdl-devel? You need to either delete your build directory or do "make clean" before rebuilding. Otherwise qemu will reuse the old (output disabled) object files. > The thing > is, once the virtual machine achieves a state of "completion" (ie > windows gets to the login promt, or linux gets to the bash prompt - same > problem there by the way) the cpu cycles disappear as the virtual > machine is not doing any work at all. That's normal. When the guest suspends the CPU (via the HLT instruction) there's no need to qemu to do anything, so it doesn't. Real CPUs do the same thing. Paul ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [Qemu-devel] re: Nothing happens 2005-06-16 16:36 ` Paul Brook @ 2005-06-16 18:15 ` Thayne Harbaugh 2005-06-17 7:18 ` Josef Moffett 0 siblings, 1 reply; 17+ messages in thread From: Thayne Harbaugh @ 2005-06-16 18:15 UTC (permalink / raw) To: qemu-devel On Thu, 2005-06-16 at 17:36 +0100, Paul Brook wrote: > > I first just tried without the SDL-devel libs, but that was the same, > > and the above mentioned thread suggested that SDL may be a cause > > (although I suspect we may be talking of different problems). > > Did you actually do a clean build after installing sdl-devel? You need to > either delete your build directory or do "make clean" before rebuilding. > Otherwise qemu will reuse the old (output disabled) object files. Don't forget that configure needs to be re-run so that SDL can be re-detected. ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [Qemu-devel] re: Nothing happens 2005-06-16 18:15 ` Thayne Harbaugh @ 2005-06-17 7:18 ` Josef Moffett 0 siblings, 0 replies; 17+ messages in thread From: Josef Moffett @ 2005-06-17 7:18 UTC (permalink / raw) To: qemu-devel Thayne Harbaugh wrote: >>Did you actually do a clean build after installing sdl-devel? You need to >>either delete your build directory or do "make clean" before rebuilding. >>Otherwise qemu will reuse the old (output disabled) object files. >> >> > >Don't forget that configure needs to be re-run so that SDL can be >re-detected. > > > > >_______________________________________________ >Qemu-devel mailing list >Qemu-devel@nongnu.org >http://lists.nongnu.org/mailman/listinfo/qemu-devel > > Oh dear, what a silly bunt. I threw the make clean out of the window, so of course it didn't work. I cringe with shame! ;-) Sorry to have wasted your time on something that mind bendingly simple! Cheers Joe ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [Qemu-devel] re: Nothing happens 2005-06-16 14:29 ` [Qemu-devel] re: Nothing happens Josef Moffett 2005-06-16 16:36 ` Paul Brook @ 2005-06-16 21:25 ` Henrik Nordstrom 2005-06-16 21:47 ` Paul Brook 1 sibling, 1 reply; 17+ messages in thread From: Henrik Nordstrom @ 2005-06-16 21:25 UTC (permalink / raw) To: qemu-devel On Thu, 16 Jun 2005, Josef Moffett wrote: > but I did find the following with the -monitor stdio; that when I did a > screen dump qemu was running and dumping valid (linux, win 98 and winxp) > screen images. I only had no access to these - in other words the emulator > was working fine, both with and without kqemu, but there was no console or > visual output with which to manipulate the emulated virtual machine. (ie no > visual and no keyboard/mouse access to the (hidden) console.) Sounds very much like the SDL driver didn't get compiled for whatever reason, or you are using the -nographic qemu command line flag do disable graphic output.. > I first just tried without the SDL-devel libs, but that was the same If you don't have SDL development libs then only "dumb" (hidden) graphics mode is available. Try make clean ./configure make In your configure output I notice you didn't have static versions of the SDL libraries available. This will limit the availability of the SDL support somewhat. Use the following to verify which modes have SDL support after you ran configure: grep CONFIG_SDL */config.h You should at least see CONFIG_SDL for i386-softmmu. Regards Henrik ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [Qemu-devel] re: Nothing happens 2005-06-16 21:25 ` Henrik Nordstrom @ 2005-06-16 21:47 ` Paul Brook 2005-06-17 7:08 ` Josef Moffett 0 siblings, 1 reply; 17+ messages in thread From: Paul Brook @ 2005-06-16 21:47 UTC (permalink / raw) To: qemu-devel > In your configure output I notice you didn't have static versions of the > SDL libraries available. This will limit the availability of the SDL > support somewhat. In most cases it doesn't make any difference. Static SDL is only needed if you're building qemu-fast or you're building everything as static libraries, neither of which are the default. Paul ^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [Qemu-devel] re: Nothing happens 2005-06-16 21:47 ` Paul Brook @ 2005-06-17 7:08 ` Josef Moffett 0 siblings, 0 replies; 17+ messages in thread From: Josef Moffett @ 2005-06-17 7:08 UTC (permalink / raw) To: qemu-devel Paul Brook wrote: >>In your configure output I notice you didn't have static versions of the >>SDL libraries available. This will limit the availability of the SDL >>support somewhat. >> >> > >In most cases it doesn't make any difference. Static SDL is only needed if >you're building qemu-fast or you're building everything as static libraries, >neither of which are the default. > >Paul > > >_______________________________________________ >Qemu-devel mailing list >Qemu-devel@nongnu.org >http://lists.nongnu.org/mailman/listinfo/qemu-devel > > Okay - a flood of replies. I am going to try the make clean, etc again. I seem to remember doing it, but can't be 100% sure so better try that. I did do the ./configure though because that gave me the option for SDL or no SDL. Thanks for all the replies, I'll report back on that as soon as I've tried it - ie in about 10mins ;-) Cheers Joe ^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2005-06-17 7:19 UTC | newest] Thread overview: 17+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2005-05-18 19:17 [Qemu-devel] Nothing happens Rudi Lippert 2005-05-18 20:55 ` Hetz Ben Hamo 2005-05-18 21:32 ` [Qemu-devel] " Rudi Lippert 2005-05-18 21:57 ` Struan Bartlett 2005-05-19 9:23 ` [Qemu-devel] " Rudi Lippert 2005-05-19 23:30 ` Struan Bartlett 2005-05-20 8:12 ` Oliver Gerlich 2005-05-21 12:07 ` [Qemu-devel] " Per-Erik Kristensson 2005-05-21 16:26 ` Damien Mascord 2005-05-21 21:59 ` Jernej Simončič -- strict thread matches above, loose matches on Subject: below -- 2005-06-16 13:12 [Qemu-devel] Booting Linux in Windows XP Aaron Feng 2005-06-16 14:29 ` [Qemu-devel] re: Nothing happens Josef Moffett 2005-06-16 16:36 ` Paul Brook 2005-06-16 18:15 ` Thayne Harbaugh 2005-06-17 7:18 ` Josef Moffett 2005-06-16 21:25 ` Henrik Nordstrom 2005-06-16 21:47 ` Paul Brook 2005-06-17 7:08 ` Josef Moffett
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).