Hello¸
new bee wrote:
...
when I boot the new kernel, there is the message :
IP-Config: No network device available
Looking up port of RPC 13/2 on 192.168.15.1 http://192.168.15.1
and the kernel cannot mount the root fs.but the kernel has the network
device driver.
What is the reason?
We currently don't check the return value in the init function where the
new timer is created but do check it wherever it is used which is backwards
and wasteful.
You would prefer that qemu just segfaults rather than die gracefully?
I think qemu should die before it returns from qemu_malloc.
On 1/3/08, Paul Brook [EMAIL PROTECTED] wrote:
On Wednesday 02 January 2008, Blue Swirl wrote:
On 1/2/08, Paul Brook [EMAIL PROTECTED] wrote:
Also the opaque parameter may need to be different for each function,
it just didn't matter for the unassigned memory case.
Do you really
Blue Swirl wrote:
On 1/3/08, Paul Brook [EMAIL PROTECTED] wrote:
On Wednesday 02 January 2008, Blue Swirl wrote:
On 1/2/08, Paul Brook [EMAIL PROTECTED] wrote:
Also the opaque parameter may need to be different for each function,
it just didn't matter for the unassigned memory case.
Do you
On 1/3/08, Fabrice Bellard [EMAIL PROTECTED] wrote:
Blue Swirl wrote:
On 1/3/08, Paul Brook [EMAIL PROTECTED] wrote:
On Wednesday 02 January 2008, Blue Swirl wrote:
On 1/2/08, Paul Brook [EMAIL PROTECTED] wrote:
Also the opaque parameter may need to be different for each function,
it
* Filip Navara [EMAIL PROTECTED] [2007-12-11 15:29]:
Hi Ryan others,
now I have been holding a SMBIOS patch on my hard disk for way to long it
seems. I used a different approach from yours, so I decided to publish it
for review or further ideas. What I did was to modify the bochs bios to
As I said earlier, the only correct way to handle memory accesses is to
be able to consider a memory range and its associated I/O callbacks as
an object which can be installed _and_ removed. It implies that there is
a priority system close to what you described. It is essential to
hi!
has anyone ever used some real performance monitoring tools (like papiex,
perfex, pfmon, etc.) on qemu? i'm running a debian linux and would like to
time some applications inside qemu and have tried the perfmon2 kernel-patch
(http://perfmon2.sourceforge.net/) for testing.
sadly, it does
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer ths 08/01/03 21:26:24
Modified files:
target-mips: helper.c
Log message:
Fix exception debug output.
CVSWeb URLs:
On Thursday 03 January 2008 22:29:06 Paul Brook wrote:
... Ok, to cut a long question short: Is there any hardware support im
qemu for doing monitoring (that goes deeper than using time) and has
anyone ever tested something that could work?
Probably your application wants the performance
... Ok, to cut a long question short: Is there any hardware support im qemu
for doing monitoring (that goes deeper than using time) and has anyone
ever tested something that could work?
Probably your application wants the performance counters. Qemu doesn't emulate
those.
Besides which, qemu
Does anyone have an idea on how I can measure performance in qemu to a
somewhat accurate level? I have modified qemu (the memory handling) and the
linux kernel and want to find out the penalty this introduced... does
anyone have any comments / ideas on this?
Short answer is you probably
On Thursday 03 January 2008 23:07:07 you wrote:
Does anyone have an idea on how I can measure performance in qemu to a
somewhat accurate level? I have modified qemu (the memory handling) and
the linux kernel and want to find out the penalty this introduced... does
anyone have any comments
Le lundi 24 décembre 2007 à 15:34 +0100, andrzej zaborowski a écrit :
[...]
-#define BLK_READ_BLOCK(a, len) sd_blk_read(sd-bdrv, sd-data, a, len)
-#define BLK_WRITE_BLOCK(a, len)sd_blk_write(sd-bdrv, sd-data, a,
len)
I committed the patch but I retained the use of these macros
On Jan 3, 2008 11:11 PM, Clemens Kolbitsch [EMAIL PROTECTED] wrote:
Well, the measuring I had in mind partly concentrats on TLB misses, page
faults, etc. (in addition to the cycle measuring). guess i'll have to
implement something for myself in qemu :-/
There's something not clear here: do
On Thursday 03 January 2008 23:18:58 Paul Brook wrote:
Well, the measuring I had in mind partly concentrats on TLB misses, page
faults, etc. (in addition to the cycle measuring). guess i'll have to
implement something for myself in qemu :-/
Be aware that the TLB qemu uses behaves very
Well, the measuring I had in mind partly concentrats on TLB misses, page
faults, etc. (in addition to the cycle measuring). guess i'll have to
implement something for myself in qemu :-/
Be aware that the TLB qemu uses behaves very differently to a real CPU TLB. If
you want to get TLB miss
QEMU Development Team,
I've been playing with the latest snapshot of the QEMU
stuff (qemu-snapshot-2008-01-03_05.tar.bz2) to play
with the Gumstix Connex machine (the latest stable
version 0.9.0 doesn't seem to have the Gumstix connex
machine).
I noticed that this architecture supports only one
Hi,
On 04/01/2008, John W [EMAIL PROTECTED] wrote:
3. gpio line 37, I took a stab in the dark.
With this change, eth0 seemed to continue to work
perfectly.
As for Eth1:
1. The Linux Kernel seemed to ALSO recognize eth1.
(example: ifconfig eth1 seemed to work fine)
2. Sending packets
Hello All,
Has anyone had success installing (and runnning) Vista 64 bit on QEMU. I
tried it and landed into a variety of windows blue screen errors. The EFI
BIOS also does not seem to be working with the QEMU version in CVS.
Thanks for the help.
Regards,
Anup
20 matches
Mail list logo
