Hi Dan...!
How are you doing?
Okay, just a few notes:
* Sorry for sending this rather badly written patch, I have loads of
other stuff at the moment. I hope that it serves as a ground for
further development, though.
I appreciate your work here, congratulations!
regards,
Mulyadi
Hi Jason...
> This patch adds the functionality to the gdb-stub to single step with
> the IRQs and timers disabled. It greatly improves gdb's ability to
> perform run control while running a linux kernel and stepping off of
> breakpoints or stepping into certain types of functions. I have also
>
Hi Jason..
> The patch is completely arch independent and should work with any of
> the targets that use the gdb-stub.
Just want to report that I gave it a try and it works great.
However, I am just courious, what happen if I use stepbit=0x6? That
means: IRQ off, timer off, but single step disa
Hi Steve...
> Hi -
>
> I'm having a bit of trouble getting gdb to do what I was hoping it
> would with qemu. Following the instructions in the docs:
>
> #1) I launch qemu with -S -s flags ( since I want to trace the
> bootloader code )
> It says: Waiting gdb connection on port 1234 - which is corr
Hi Fabrice
> Log message:
> multiple snapshot support
Could you kindly explain how does it work? And, is the concept similar
to VMWare's incremental snapshot?
regards,
Mulyadi
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.no
Hi..
> Hello everybody
>
> Today I boot my FC2 disk image along with 2.6.17-mm6 kernel using
> this command line:
> qemu -hda ./fc2.img -m 64 -net none -kernel
> /mnt/linux/linux-2.6.17-mm6-HZ1000/arch/i386/boot/bzImage -no-kqemu
> -append root=/dev/hda1
Following up my own post, I revealed that
Hi David...
> I started playing with nspluginwrapper -- and finally got annoyed with
> the fact that not even /bin/echo from current i386 userspace will run in
> qemu-i386 any more. So I had a go at implementing set_thread_area, futex
> and set_tid_address.
A small request, if you are willing to
Hi Salvador...
> The patch available from http://qemu-forum.ipi.fi/viewtopic.php?t=2718 adds
> a new utility, qemu-nbds, that implements a NBD server (see
> http://nbd.sf.net) for QEMU images.
>
> Using this utility it is posible to mount images in any format supported by
> QEMU.
Good work IMHO !
Hi...
> If anyone could point me the Source Code Portian which handles this part it
> would be really helpful for me to learn about the Images and Guest Os to
> Hos Os IO mechanisms...
I think what you need to check is the block-*.c files e.g block-cow.c,
block-qcow.c etc. raw block driver is in
Hi Phil
If I start qemu like this (from an interactive shell (tcsh))
qemu -m 256 -localtime -net nic -net tap -nographic trixbox.img \
&! /tmp/qemulog &
I never did this before, but maybe you need to take a look on -serial
option. Maybe you can use it to redirect the serial output onto
Hello Fabrice and all
I noticed small typo in kqemu-tech.html. In "Future Development"
section, it is said that:
Support for the Linux 2.4.20 paravirtualization interface
But I believe it should be:
Support for the Linux 2.6.20 paravirtualization interface
regards,
Mulyadi
___
Hi
Hi all,
I'm doing use qemu 0.8.2. I have just create my instance and all run
perfectly.
But, it's possible to assign a CPU(x) each individual instance? I have a
multicore platform.
IMHO yes, google for Linux CPU affinity.
regards,
Mulyadi
Hi
I'm doing use qemu 0.8.2. I have just create my instance and all run
perfectly.
But, it's possible to assign a CPU(x) each individual instance? I have a
multicore platform.
IMHO yes, google for Linux CPU affinity
regards,
Mulyadi
___
Qe
Hello Paul...
> > CCD : Compiled Code Destination (?)
>
> Condition Code Source.
Or Condition Code Destination?
> These 3 are used to implement lazy flag evaluation. Most x86
> instructions set the condition code flags, but only a relatively
> small subset of instructions actually use these flag
Dear Hetz ...
> I think it will be a good idea if you put the Howto that you've sent
> to here - inside the QEMU forums in the HOWTOs section. That way, you
> could always edit your text in the forum and it's the most accessible
> way for everyone.
Ahhh, yes, sorry...I forgot about the Qemu forum
hello everyone
Here is a small patch to be applied for qemu 0.7.0. The patch adds a
functionality to automatically generate cscope tag file. It assumes
that cscope has been installed properly and is included on PATH
regards
Mulyadi
--- Makefile.orig 2005-04-28 03:52:05.0 +0700
+++ Make
Dear Eric
> I have been stymied by the networking of qemu and I really want to
> try and solve my problems and hopefully document them so the solution
> is useful to others.
i read it at a glance and I think it is well written. Very useful for
newbie and also helpful as cheat sheet for Qemu
Hello everybody
Yesterday I tried to install Fedora Core 2 guest using qemu 0.7.1 (no
kqemu) on top of FC 2 host. Both guest and host are running 2.6.5-1.358
(the default kernel of FC2). I experienced slower boot speed and slower
keyboard typing (the delay between a key a pressed and the actual
Hello Hetz, Ozan...
> Add: clock=pit
> to the fedora core GRUB kernel boot parameters .
I have tried itstill feel slower than RH 9I've tried
HPET=disable too with no luck. I'll try to investigate this issue
deeper but still welcome everyone's ideas
To Ozan: i use -m 256. do I need
On Tuesday 02 August 2005 13:26, Mulyadi Santosa wrote:
> I have tried itstill feel slower than RH 9I've tried
> HPET=disable too with no luck. I'll try to investigate this issue
> deeper but still welcome everyone's ideas
Following up my own earlier posting toda
Hello Andreas!
> Introduction part:
> --
> I'm doing a performance tuning effort all over the place in
> frequently-used Linux programs:
> I'm trying to mark as many data areas as possible const (and static)
> in various programs (at those places where it's actually feasible,
> that is).
Hello...
> It simply
> replaces the virtual timer mechanism based on CPU tick count (which
> is totally messed up in a SpeedStep setting) with calls to the
> realtime clock. It should work even when emulation is stopped
> intermittently, I hope, since the built in "virtual clock stop"
> mechanism
Hello Sven...
> rdtsc gives you the cpu's clock count, which, if CPU frequency
> changes, or your code is run on different processors (multiprocessor
> machine), cannot be assumed to be related to real time anymore.
> Resolutionwise, the real time clock may be inferior, of course, as
> Jim mention
hello
> ah, so what are my options here? Can I compile qemu with an explicit
> -lpthread flag, or will I have to recomplile glibc? It seems that
> having two glibc libraries on my system is rather messy...
try to use LD_ASSUME_KERNEL, so your command becomes
LD_ASSUME_KERNEL=2.4.9 ./qemu-i386 /bi
Hello...
> I worked with pbrook on #qemu to debug this issue. The problem turns
> out to be that qemu's do_fork function on PowerPC zeroes out r7-r31
> in the new CPU state structure after a clone, which it should not do,
Joshat least it proves (to me) that the parameters passed to the
clon
Hello everybody
> GetNetworkParams failed. ret = 0032
> Could not get DNS address
try to look at my attached simple patch (in bzip2 format). This patch
simply fake "127.0.0.1" as DNS entry in non user-mode network stack. To
enable it, run "qemu" using "-fake-dns" parameter.
Thi
Hello
> I will try it when I am able to compile, or maybe there is another
> solution, not needing compilation ?
In Linux, I simply add this line to /etc/resolv.conf:
nameserver 127.0.0.1
In Windows, I don't know the equal file configuration for storing DNS
server configuration, but you can
Hello
> 1. How do I build my own .img file to boot?
Simply use qemu-img to create one. There are many file types you can
use, raw, cow,qcow and etc.
After that, simply start qemu with this new blank image together with
your favourite distro ISO image (pass the path and the filename to
-cdrom)
Hello...
> I'm trying to build/install kqemu on Redhat 9 running a 2.6.5 kernel.
> Grabbed latest sources (0.7.2) for qemu and kqemu. Build doesn't
> appear to generate the .ko module.
You're missing the kqemu package itself. Grab it from Qemu website and
put it inside the Qemu directory (resul
Dear Fabrice...
> I just commited the code to emulate SMP targets. As an example, I
> added support for x86 PCs with up to 8 CPUs (option -smp).
Gooshhh, finally you made itthanks a lot! I don't need 8 CPUs
anyway, 2 is fine for me, but heysurplus is always welcome :)
Testing is on the
Dear Dr Bos..
First, congratulations for the Argos release. Looks interesting for
me..I'll give it a try ASAP.
> We have extended QEMU to enable it to detect remote attempts to
> compromise the emulated guest operating system. Using dynamic taint
> analysis Argos tracks network data throughout t
Hello Andre...
> I'm running into problems using qemu to debug a kernel module. My
> host and virtual machine are both x86 running Fedora Core 4. After
> insmoding the module in the virtual machine, starting gdbserver,
> running gdb on the host with the module sections loaded at the right
> place,
Hello Andre
> breakpoint was hit. I finally tracked down the problem to
> exec.c:breakpoint_invalidate. The problem is that
> breakpoint_invalidate, which is supposed to invalidate the
> translation block for the address you want to break at, was
> actualling invalidating the translation block
Hello Andre...
> Not a problem. I only started using qemu a month ago, so it took me a
> while to get oriented in the code and understand what was going on. I
> must say that I've been really impressed with qemu so far.
There was an interesting case I had found recently. In Linux kernel for
i386
Hi Andre...
> The problem that you are running into here is that sys_uname has been
> replaced by sys_newuname in kernel/sys.c. When I put a breakpoint in
> this function, everything works correctly when I run uname in the
> virtual machine.
yes, you're right. sys_newuname is the system call hand
Hi...
On Saturday 28 January 2006 19:26, Blue Swirl wrote:
> Hi,
>
> Qemu's system emulators could be modified to output information about
> the code areas which have been executed by the virtual CPU. The
> output could then be used in standard test coverage tools. The
> benefit would be the abili
Dear Fabrice
> Log message:
> support for builtin profiler
Does this mean, qemu will have native profiling support just like
oprofile does? In other word, we can easily access cpu perfomance
counter such as TLB miss, unaligned cache access and so on?
regards
Mulyadi
Dear Jim...
> Ok, I managed to fix my VDE issues and get this to work on eth0.
> Working sources for vde-inject and vde_pcap_inject attached.
I haven't tested, so I will just give "untested" comment :) Great work
Jim, finally you can work on it and release the code to the public
My first note:
Hi...
I re-posted the patch by Andre Pech in Qemu forum. The URL is
http://qemu.dad-answers.com/viewtopic.php?p=2809#2809
The patch is written to tackle missed breakpoint that sometimes happen.
refer to the related Qemu forum's entry or the original Andre Pech's
posting on December 24, 2005 in
Hi...
On Sunday 19 February 2006 22:39, Paul Brook wrote:
> This patch is not sufficient.
>
> There seems to be some inconsistency whether cpu_get_phys_page_debug
> returns the physical address or the base address of the page.
Hm, I am not so sure either. Anyway, using cscope to find out which
f
Hi..
> So I modify
> QEMU's source code to disable interrupts in single step mode,and now
> I can use "step" or "next" command in gdb to single step
> functions.
very interesting! Please post your patch on qemu-devel and preferably on
qemu.dad-answers.com too. Personally, I'd be glad to review
Hi...
> As my interest in Qemu, Xen and other virtualization technologies is
> quite high, and a lot of stuff is happening in this area, Ingo
> Wichmann from the Linuxhotel in Essen, Germany and myself teamed up
> to organize a workshop about this topic.
very interesting! Sadly, I live too far fr
Hi Fausto
> I have this problem during linking qemu under Ubuntu 5.10
> (linux-ppc). The system is up to date, and I'm using the gcc-3.4 as
> you can see.
Personally, I suggest to put your hint on the Qemu forum
(qemu.dad-answers.com). That way, it will be archieved and people will
easily sear
Hi Julian...
> Using qemu from cvs simulating x86-softmmu (no kqemu) on x86,
> booting SuSE 9.1 and getting to the xdm (kdm?) graphical login
> screen, requires making about 1088000 translations, and the
> translation cache is flushed 17 times. Booting is not too bad,
> but once user-mode starts
Hi Paul...
> CVSROOT: /sources/qemu
> Module name: qemu
> Branch:
> Changes by: Paul Brook <[EMAIL PROTECTED]> 06/04/08 17:14:56
>
> Modified files:
> . : exec.c
>
> Log message:
> Fix breakpoint TLB invalidation.
Does this fix do the same thing like Andre pech's
Hi...
> Attached is a patch to add the case for interrupting the gdbstub and
> sending the correct signal to gdb.
Excellent. I haven't tested by myself, but could you test your patch
together with Andre Pech's patch that I put in
http://qemu.dad-answers.com/viewtopic.php?p=2809#2809?
BTW, Pau
Hi!
> QEMU version 0.8.1 is available at
> http://bellard.org/qemu/download.html.
Great! Thanks for the hard work of Qemu community!
BTW, any decision about the async I/O patch? Will you merge it or does
it need more tests?
regards,
Mulyadi
___
Qe
GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> Thank you.
> Chan Kim
>
>
>
>
>
> ___
> Kernelnewbies mailing list
> kernelnewb...@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
201 - 248 of 248 matches
Mail list logo
