Michael, this bug cannot be solved with a reconfiguration, it's actually
a TCG emulation bug. There is an experimental patch on the QEMU mailing
list you should have a look at
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bu
Hi Peter,
sure, that's fine too :). I just meant "great that it will be picked up in
a future version" :)
Thanks!
-Clemens
On Sat, Apr 19, 2014 at 3:50 PM, Peter Maydell wrote:
> On 19 April 2014 23:41, Clemens Kolbitsch wrote:
> > Thanks guys, awesome feedback and g
ps://lists.gnu.org/archive/html/qemu-devel/2014-04/msg01455.html
>
> thanks
> -- PMM
>
--
Clemens Kolbitsch
Security Researcher
kolbit...@lastline.com
Mobile +1 (206) 356-7745
Land +1 (805) 456-7076
Lastline, Inc.
6950 Hollister Avenue, Suite 101
Goleta, CA 93117
www.lastline.com
set_cc_op(s, ((s->cc_op - CC_OP_MULB) & 3) + CC_OP_SARB);
> +break;
> +default:
> +/* Otherwise, generate EFLAGS and replace the C bit. */
> +gen_compute_eflags(s);
> +tcg_gen_deposit_tl(cpu_cc_src, cpu_cc_src, cpu_tmp4,
> +
o 0? I see that most flag-computations set undefined flags
to 0 - is this just a convention or really a requirement?
Thanks guys!
-Clemens
On Wed, Apr 9, 2014 at 10:33 AM, Clemens Kolbitsch
wrote:
> Hi guys,
>
> I have to revive a rather old thread [1,2]. A quick summary of the issue:
&
per-instruction-set-reference-manual-325383.pdf
--
Clemens Kolbitsch
Security Researcher
kolbit...@lastline.com
Mobile +1 (206) 356-7745
Land +1 (805) 456-7076
Lastline, Inc.
6950 Hollister Avenue, Suite 101
Goleta, CA 93117
www.lastline.com
I was thinking about
detecting this very specific case and marking the TB for re-translation
only after the TB is exited, but this is not very clean and also somewhat
prone to errors.
Thanks!
-Clemens
--
Clemens Kolbitsch
Security Researcher
kolbit...@lastline.com
Mobile +1 (206) 356-7745
La
On Sun, May 26, 2013 at 7:54 AM, Andreas Färber wrote:
> Hi,
>
> Am 24.05.2013 23:44, schrieb Paolo Bonzini:
>> Il 24/05/2013 23:39, Clemens Kolbitsch ha scritto:
>>> we recently had an issue with running a program using FPU instructions
>>> to obtain the curr
rather old, you have
probably come across it before - if there was a reason for not
including it in QEMU (I checked in git:master and it's not applied).
If there isn't, maybe it'd be worth re-considering :)
thanks!
-Clemens
--
Clemens Kolbitsch
Security Researcher
kolbit...@lastline
On Thu, Oct 18, 2012 at 10:24 AM, Jan Kiszka wrote:
> On 2012-10-18 08:29, Paolo Bonzini wrote:
>> Il 17/10/2012 20:37, Jan Kiszka ha scritto:
>>> On 2012-10-17 18:44, Paolo Bonzini wrote:
>>>> Il 17/10/2012 18:37, Clemens Kolbitsch ha scritto:
>>>>&
rning
different results, are there obvious problems even trying to go down
that road?
Would love to hear some thoughts on this - don't hesitate to tell me
"that's stupid and impossible because XYZ" (assuming you also fill in
the blanks ;) )
Thanks!
Clemens
--
Clemens Kolbitsch
S
Hi Rolando,
thanks for this detailed report. Since you mention that Windows7 runs
fine for you, you gotten me really curious. Could you please post
the exact command line you are using (e.g., what additional hardware you
are emulating, etc.), the build version, the host system, etc.
I'm pretty su
We have been discussing this issue on the QEMU mailing list. It is of
CPU definition, but none of the current configurations allow QEMU to
boot Windows7 64bit WITHOUT KVM. The issue behind it is that the TCG
(code generator) might not fully support all CPU bits required by Win7.
There is a patch t
which is as follows:
>
> 00 -- Break on instruction execution only.
> 01 -- Break on data writes only.
> 10 -- Undefined.
> 11 -- Break on data reads or writes but not instruction fetches.
>
> On Mon, Sep 17, 2012 at 2:54 PM, Clemens Kolbitsch
> wrote:
>> On Mon, Sep 17,
On Mon, Sep 17, 2012 at 11:19 AM, Aurelien Jarno wrote:
> On Mon, Sep 17, 2012 at 10:27:35AM -0700, Clemens Kolbitsch wrote:
>> On Mon, Sep 10, 2012 at 10:31 AM, Aurelien Jarno
>> wrote:
>> > On Mon, Sep 10, 2012 at 06:23:43PM +0200, Stefan Weil wrote:
>> >>
On Mon, Sep 10, 2012 at 10:31 AM, Aurelien Jarno wrote:
> On Mon, Sep 10, 2012 at 06:23:43PM +0200, Stefan Weil wrote:
>> Am 10.09.2012 08:19, schrieb Clemens Kolbitsch:
>> >On Sat, Sep 8, 2012 at 11:22 AM, Clemens Kolbitsch
>> > wrote:
>> >>On Fri, Sep
> On 2012-09-12 15:54, Anthony Liguori wrote:
>>
>> Hi,
>>
>> We've been running into a lot of problems lately with Windows guests and
>> I think they all ultimately could be addressed by revisiting the missed
>> tick catchup algorithms that we use. Mike and I spent a while talking
>> about it yes
On Mon, Sep 10, 2012 at 9:23 AM, Stefan Weil wrote:
> Am 10.09.2012 08:19, schrieb Clemens Kolbitsch:
>
> On Sat, Sep 8, 2012 at 11:22 AM, Clemens Kolbitsch
> wrote:
>
> On Fri, Sep 7, 2012 at 9:26 PM, Stefan Weil wrote:
>
> Am 08.09.2012 02:48, schrieb Clemens Kolbi
On Sat, Sep 8, 2012 at 11:22 AM, Clemens Kolbitsch
wrote:
> On Fri, Sep 7, 2012 at 9:26 PM, Stefan Weil wrote:
>> Am 08.09.2012 02:48, schrieb Clemens Kolbitsch:
>>>
>>> Hi guys,
>>>
>>> I need to run Win7 64bit in Qemu without KVM support. I found a
On Fri, Sep 7, 2012 at 9:26 PM, Stefan Weil wrote:
> Am 08.09.2012 02:48, schrieb Clemens Kolbitsch:
>>
>> Hi guys,
>>
>> I need to run Win7 64bit in Qemu without KVM support. I found a few
>> messages concerning the "unsupported architecture"
Hi guys,
I need to run Win7 64bit in Qemu without KVM support. I found a few
messages concerning the "unsupported architecture" problem (Windows
shows a BSOD with "STOP 0x005D ..." on boot), for example
http://lists.gnu.org/archive/html/qemu-devel/2011-03/msg01623.html
or
http://permalink.gma
> On 03/18/11 21:39, Clemens Kolbitsch wrote:
> > Hi list,
> >
> > strange situation: When I create a snapshot using Qemu 0.14.0 stable,
> > everything works smoothly and resuming the CPU takes about 1-2 seconds.
> > If I don't use the snapshot file for some
Hi list,
strange situation: When I create a snapshot using Qemu 0.14.0 stable,
everything works smoothly and resuming the CPU takes about 1-2 seconds. If I
don't use the snapshot file for some time, the time it takes to resume grows
by 2-3 seconds per day. At the moment, I'm looking at a snapsh
Guys,
I need a Qemu-internals expert to help me out here:
I'm trying to monitor execution of certain (user-land) TBs in a i386-softmmu
system. For this, the cpu-main loop has been patched:
Before jumping into a TB's generated code, I first check its guest-virtual
start address whether it matc
On Tuesday 15 December 2009 08:54:04 pm Avi Kivity wrote:
> On 12/15/2009 08:48 PM, Clemens Kolbitsch wrote:
> > Hi list,
> >
> > I'm experiencing a strange emulation bug with the op-code below. The
> > instruction raises a segfault in the application (running
Hi list,
I'm experiencing a strange emulation bug with the op-code below. The
instruction raises a segfault in the application (running on the guest),
however, if I enable KVM to run the exact same application, no segfault is
raised.
0x0080023b: 8b 04 65 11 22 33 44mov regEAX, [0x443
Patch #8:
CRC32 helper code. Sorry if there is already some global function that could
be used for this purpose. Simply took the code from Wireshark (license and
header documentation unchanged obviously).
diff -Naur qemu/hw/atheros_wlan_crc32.c qemu-altered/hw/atheros_wlan_crc32.c
--- qemu/hw/at
+++ qemu-altered/hw/atheros_wlan_packet.c 2008-03-01 12:33:11.0
+0100
@@ -0,0 +1,481 @@
+/**
+ * QEMU WLAN access point emulation
+ *
+ * Copyright (c) 2008 Clemens Kolbitsch
+ *
+ * Permission is hereby granted, free of charge, to any person obtaining a copy
+ * of this software and
/atheros_wlan_io.c 2008-03-01 12:33:11.0 +0100
@@ -0,0 +1,1188 @@
+/**
+ * QEMU WLAN device emulation
+ *
+ * Copyright (c) 2008 Clemens Kolbitsch
+ *
+ * Permission is hereby granted, free of charge, to any person obtaining a copy
+ * of this software and associated documentation files (the "Sof
/atheros_wlan_ap.c
--- qemu/hw/atheros_wlan_ap.c 1970-01-01 01:00:00.0 +0100
+++ qemu-altered/hw/atheros_wlan_ap.c 2008-03-01 12:33:11.0 +0100
@@ -0,0 +1,771 @@
+/**
+ * QEMU WLAN access point emulation
+ *
+ * Copyright (c) 2008 Clemens Kolbitsch
+ *
+ * Permission is hereby granted
:11.0 +0100
@@ -0,0 +1,345 @@
+/**
+ * QEMU WLAN device emulation
+ *
+ * Copyright (c) 2008 Clemens Kolbitsch
+ *
+ * Permission is hereby granted, free of charge, to any person obtaining a
copy
+ * of this software and associated documentation files (the "Software"), to
deal
emulation
+ *
+ * Copyright (c) 2008 Clemens Kolbitsch
+ *
+ * Permission is hereby granted, free of charge, to any person obtaining a
copy
+ * of this software and associated documentation files (the "Software"), to
deal
+ * in the Software without restriction, including without limi
Patch #1:
Necessary changes to Qemu itself... Makefile and hw/pci.c to include the
device:
diff -Naur qemu/hw/pci.c qemu-altered/hw/pci.c
--- qemu/hw/pci.c 2008-02-03 03:20:18.0 +0100
+++ qemu-altered/hw/pci.c 2008-03-01 12:59:50.0 +0100
@@ -636,6 +636,8 @@
Hello!
Since I cannot guarantee that the code will be on my server forever, I'll post
the CVS-patch here once more. Furthermore, I'll split it into smaller
sections and put it inline, so the chance of getting it reviewed are a little
bigger ;-)
Also, here are some comments I posted mistakenly i
On Friday 29 February 2008 19:22:53 Sylvain Petreolle wrote:
> Look at pci.c.rej.
> Because of the lines of the recent e1000 pci card inclusion,
> patch refuses to apply it.
>
> Its just a matter of resynch...
Now I got it ;-)
This one (http://stud4.tuwien.ac.at/~e0126605/qemu_atheros/atheros_wla
On Friday 29 February 2008 19:22:53 Sylvain Petreolle wrote:
> Look at pci.c.rej.
> Because of the lines of the recent e1000 pci card inclusion,
> patch refuses to apply it.
>
> Its just a matter of resynch...
ok thanks.
will take a look at it!
On Friday 29 February 2008 01:20:10 [EMAIL PROTECTED] wrote:
> The emulation works beautifully on windows Xp Pro SP2 guest and official
> Atheros drivers, no installation problems at all.
>
> Nice job !
>
> > Some infos about the patch:
> > - 2 lines added to pci.c
>
> you have to take recent e100
On Thursday 28 February 2008 15:12:20 [EMAIL PROTECTED] wrote:
> Atheros Wireless Device Emulation
Hm... seems attachments don't go too well.
Since it is a 9.500 LOC patch, I put here for download:
http://stud4.tuwien.ac.at/~e0126605/qemu_atheros/atheros_wlan.patch
Cheers
On Friday 04 January 2008 09:49:22 Rob Landley wrote:
> On Thursday 03 January 2008 15:38:02 Clemens Kolbitsch wrote:
> > Does anyone have an idea on how I can measure performance in qemu to a
> > somewhat accurate level?
>
> hwclock --show > time1
> tar xvjf linux
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 ve
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 co
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 perf
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 n
are you passing an initrd to qemu?
i call qemu like this:
qemu \
-hda image \
-boot c \
-net user \
-net nic,vlan=0,model=rtl8139 \
-initrd initrd \
-append "root=/dev/hda1" \
-kernel kernel \
-no-kqemu
whereas kernel is a link to t
On Friday 19 October 2007 09:13:40 [EMAIL PROTECTED] wrote:
> Then I try this command:
> qemu -m 32 hda rootfs.img kernel linux-2.6.18.1/arch/i386/boot/bzImage
> -append “root=/dev/hda \clock=pit”
>
> and I get the error...
>
> I tried to pass init=/sbin/init or init=/bin/init but it doesn't help..
hi everyone!
I have a question concerning how i386 execution is continued after a page
fault has occured...
What I have understood so far:
In the executing TB the TLB is checked and if the address is not found
__ld (e.g. __ldl_user)
is called. this calls
lb_fill
(if it rea
On Thursday 04 October 2007 15:05:22 Thiemo Seufer wrote:
> Clemens Kolbitsch wrote:
> > hi everyone!
> > if i want to increase the size of my TLB (for emulating an i386
> > processor), is it enough to simply increase CPU_TLB_BITS (e.g. by one)??
>
> IIRC CPU_TLB_B
hi everyone!
if i want to increase the size of my TLB (for emulating an i386 processor), is
it enough to simply increase CPU_TLB_BITS (e.g. by one)??
Or are there any side effects to that I should be aware of?
Thanks!
On Wednesday 03 October 2007 16:16:55 [EMAIL PROTECTED] wrote:
> Hi,
>
> On 03/10/2007, Clemens Kolbitsch <[EMAIL PROTECTED]> wrote:
> > hi!
> > i know... i have been told not to use them, but i just HAVE TO for the
> > moment :-(
> >
> > i need to
On Wednesday 03 October 2007 13:04:33 you wrote:
> hi!
> i know... i have been told not to use them, but i just HAVE TO for the
> moment :-(
>
> i need to run a second thread inside my hardware module which is not a
> problem as long as i don't use the qcow2 image format. when i switch to
> qcow2,
hi!
i know... i have been told not to use them, but i just HAVE TO for the
moment :-(
i need to run a second thread inside my hardware module which is not a problem
as long as i don't use the qcow2 image format. when i switch to qcow2, qemu's
main thread hangs because the second thread is waiti
> > The only difference I see (that really matters) is how the bytes are
> > copied to the result-pointer (i.e. using movzbl vs. movsbl)... but that's
> > it.
>
> It is a cast. The generic C version for the other architectures makes
> this more obvious.
>
> > If there is some deeper reason behind
hi everyone!
i have a (maybe rather tricky) question:
why do you define 2 different inline load-functions in softmmu_header:
static inline int glue(glue(lds, SUFFIX), MEMSUFFIX)(target_ulong ptr)
vs.
static inline RES_TYPE glue(glue(ld, USUFFIX), MEMSUFFIX)(target_ulong ptr)
??
Obviously this
> Clemens Kolbitsch wrote:
> > hi everyone!
> > i have a strange problem (at least to me it seems strange :-) ):
> >
> > i have implemented a pci device (Network IC) and it works just fine when
> > using a standard image. however i now want to support snapshottin
hi everyone!
i have a strange problem (at least to me it seems strange :-) ):
i have implemented a pci device (Network IC) and it works just fine when using
a standard image. however i now want to support snapshotting...
i started to convert my image into the qcow2 format and suddenly my code d
On Thursday 27 September 2007 17:27:32 Daniel Jacobowitz wrote:
> On Thu, Sep 27, 2007 at 05:02:46PM +0200, Clemens Kolbitsch wrote:
> > but will kernel mode always use the TLB[0] for address translation (even
> > for addresses at e.g. 0x0800) and user mode TLB[1] (even for e.g.
On Thursday 27 September 2007 16:01:08 [EMAIL PROTECTED] wrote:
> > does the MEMSUFFIX macro ("kernel" / "user") mean that the memory is
> > access by code running in ring0/ring3 or does this tell about the memory
> > region being access (mem < or > TASK_SIZE / 0xc000)?
>
> The former.
ok :-)
hi guys!
just a short question:
in softmmu_header.h, for example in function
glue(glue(ld, USUFFIX), MEMSUFFIX)(target_ulong ptr)
which boils down to be included in (e.g.)
op_ldl_kernel_T0_A0
or
op_ldub_user_T0_A0
or
...
does the MEMSUFFIX macro ("kernel" / "user") mean that the memory is acc
On Tuesday 25 September 2007 12:04:17 Clemens Kolbitsch wrote:
> hi!
> i've been trying around for quite some time now trying to start qemu
> without the graphic screen... can someone tell me exactly what I'm supposed
> to do??
>
> i want to redirect the output of my
hi!
i've been trying around for quite some time now trying to start qemu without
the graphic screen... can someone tell me exactly what I'm supposed to do??
i want to redirect the output of my i386 debian linux to my host-console (also
a i386 debian) to fully see the output of a kernel panic (se
On Monday 24 September 2007 18:11:04 andrzej zaborowski wrote:
> On 24/09/2007, Johannes Schindelin <[EMAIL PROTECTED]> wrote:
> > On Mon, 24 Sep 2007, Clemens Kolbitsch wrote:
> > > when the kernel crashes, it displayes the message, however as it is way
> > >
hi!
i'm having a problem that could have a very easy answer:
my i386 linx system crashes due to a module error and i have to find out where
it crashes exactly i have the module source code.
when the kernel crashes, it displayes the message, however as it is way much
more information that ca
On Thursday 20 September 2007 18:34:22 Thiemo Seufer wrote:
> Clemens Kolbitsch wrote:
> > On Thursday 20 September 2007 16:08:51 Thiemo Seufer wrote:
> > > Clemens Kolbitsch wrote:
> > > > Hi guys!
> > > > Short question: I'm having a speech at Blac
On Thursday 20 September 2007 16:08:51 Thiemo Seufer wrote:
> Clemens Kolbitsch wrote:
> > Hi guys!
> > Short question: I'm having a speech at BlackHat Japan in Oktober about
> > something I made with qemu. Basically it is a new hardware type (so it is
> > j
Hi guys!
Short question: I'm having a speech at BlackHat Japan in Oktober about
something I made with qemu. Basically it is a new hardware type (so it is
just an additional file in the hw-subdirectory) --- it's the wireless device
I have been asking questions for a couple of months ago in case s
hi!
finally found out why it did not work ... the problem was kqemu after all.
after compiling qemu with kqemu-support disabled, the address
translation/access worked as expected :-)
is there a good documentation/technical paper online that could help me
understand how address handling is done u
hi!
ah... i'm going crazy... could someone help me please:
i'm still (as previously posted on irc) trying to catch when the guest OS (or
a program running in it) accesses a certain virtual address (e.g. reads from
it).
my guest code is something like:
...
unsigned long *p = (unsigned long*
> Hi Clemens,
>
> if you enable "log asm_in,op,op_opt,asm_out" you will see the
> intermediate code used during translation.
>
> The opcodes are generated from the macros you already found in
> softmmu_header.h by target-i386/ops_mem.h included from target-i386/op.c
>
> Hope this helps,
> Eddie
found the functions in target-xxx/ops_mem.h
the macros confused my grepping, but how much more self-speaking can a
filename be *gg* ??
oh well... i found it :-)
i think to have found it in translate.c:
/* sign does not matter, except for lidt/lgdt call (TODO: fix it) */
static GenOpFunc *gen_op_ld_T0_A0[3 * 4] = {
gen_op_ldub_raw_T0_A0,
gen_op_lduw_raw_T0_A0,
gen_op_ldl_raw_T0_A0,
X86_64_ONLY(gen_op_ldq_raw_T0_A0),
#ifndef CONFIG_USER_ONL
hi!
i tried asking this in the irc but got no answer, hope someone can help me
here :-)
i'm working on memory-protection for my mather's thesis and have to dig into
qemu memory management... could someone help me here please? i have the
following problem:
i'm trying to understand the dynamic
> Am 24.07.2007 um 15:32 schrieb Clemens Kolbitsch:
> > i'm emulating i386 (what else when using windows *g*) [...]
> >
> > just in case someone knows :-)
>
> As far as I recall, in chronological order: alpha, ia64, amd64. ;-)
ok.. ok ... my fault ;-)
o low
> for KDE.
>
> Try first 192, 256, and then 512 if you can afford it.
>
> On 7/24/07, Clemens Kolbitsch <[EMAIL PROTECTED]> wrote:
> > hi!
> > i've got a questions... just out of curiosity: when emulating windows xp,
> > i get quite good speeds.
hi!
i've got a questions... just out of curiosity: when emulating windows xp, i
get quite good speeds. however, when running linux, i can only work with it
when turning off kde... it is WAY too slow.
is there a known reason for that / does anyone know what i could be doing
wrong?
i'm emulating
academic thing than a programmer's job :-)
greets!
Clemens Kolbitsch wrote:
hi everyone!
i have a strange problem:
i use the following code on my linux 2.6.20 (kubuntu debian, i386) to
dynamically get the location of the system-call table (as can also be
found in /proc/kallsyms --> &qu
hi everyone!
i have a strange problem:
i use the following code on my linux 2.6.20 (kubuntu debian, i386) to
dynamically get the location of the system-call table (as can also be
found in /proc/kallsyms --> "sys_call_table") as it is quite interesting
for new exploits ( :-) )
on a real cpu
Paul Brook wrote:
On Thursday 14 June 2007, Clemens Kolbitsch wrote:
hi!
i'm looking for a way to monitor the eip register. is there a simple way
to do this? i know that that produces tons of data...
even better would be to know where i could intercept the main-loop
(exec_cpu ??) to
hi!
i'm looking for a way to monitor the eip register. is there a simple way
to do this? i know that that produces tons of data...
even better would be to know where i could intercept the main-loop
(exec_cpu ??) to check for a certain eip value...
could someone assist me doing that?
thanks!
Hi!
I'd like to detect if the client OS crashes... right now, only for
linux, but windows systems will become interesting for me as well in the
future...
Is there an easy way of detecting if a BSOD or a kernel oops happened??
Maybe that'd be possible by checking if the IP is inside a certain
hi everyone!
i'm programming a pci-device that includes some threads &
socket-connections (that allow remote debugging of my device).
however, i want to cleanly shutdown all threads and sockets when qemu
exits... is there an easy way of getting informed of a qemu shutdown?
(something similar t
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Qemu-devel digest..."
Today's Topics:
1. qemu vl.c (Paul Brook)
2. QEMU/PCI shutdown event
Johannes Schindelin wrote:
Hi,
On Tue, 29 May 2007, Clemens Kolbitsch wrote:
Clemens Kolbitsch wrote:
my virtual device inside qemu (a pci device) is listening for
socket-(tcp)-connections.
however, accept() always fails (code works fine if not executed inside
the qemu-process
Clemens Kolbitsch wrote:
hi!
my virtual device inside qemu (a pci device) is listening for
socket-(tcp)-connections.
however, accept() always fails (code works fine if not executed inside
the qemu-process)... now i'm wondering if qemu interferes somehow...
is that possible?
frust
hi!
my virtual device inside qemu (a pci device) is listening for
socket-(tcp)-connections.
however, accept() always fails (code works fine if not executed inside
the qemu-process)... now i'm wondering if qemu interferes somehow...
is that possible?
frustrated *gg*
hi!
sorry that I'm posting for such a dumb thing, but I'm going crazy
Up until now, I had a single file added to the qemu/hw folder. after adding
VL_OBJS += myfile.o
everything compiled without problems.
but now my project grew too large and i wanted to split everything into
multiple head
hi everyone!
i'm programming a pci-device that includes some threads &
socket-connections (that allow remote debugging of my device).
however, i want to cleanly shutdown all threads and sockets when qemu
exits... is there an easy way of getting informed of a qemu shutdown?
(something similar t
hi everyone!
i'm programming a pci-device that includes some threads &
socket-connections (that allow remote debugging of my device).
however, i want to cleanly shutdown all threads and sockets when qemu
exits... is there an easy way of getting informed of a qemu shutdown?
(something similar
Hi everyone!
Could someone please point out some links to a good documentation and/or
tutorial on how to write hardware devices for qemu?
I have been reading through the parallel & ne2k code and - although it
is not that hard - just do not get all the information necessary it seems.
are ther
If you need a wireless PCI device, I can provide code for
TNETW1130 (ACX111). Get it from
http://svn.berlios.de/svnroot/repos/ar7-firmware/qemu/trunk/hw/tnetw1130.c
It works partially with an emulated Linux 2.6.20:
the PCI card is recognized, and it loads firmware.
Stefan
hi!
did you ever
If you need a wireless PCI device, I can provide code for
TNETW1130 (ACX111). Get it from
http://svn.berlios.de/svnroot/repos/ar7-firmware/qemu/trunk/hw/tnetw1130.c
It works partially with an emulated Linux 2.6.20:
the PCI card is recognized, and it loads firmware.
wow!! it'll take a good l
Paul Brook wrote:
I want to create a "fake"/virtual pci device that only exists in the vm.
so basically it boils down to adding a new (wireless) device that is not
connected to anything and that i can write data to/read data from the
device driver runnnig inside of qemu.
Qemu already has m
Hi everyone!
I've read some posts in the qemu-mailinglist archives about the idea of
a pci-proxy (allowing the client-os to access the host-os-pci devices)
and the problems related to that.
now, I want to make something similar and wonder if there is already
some source code that does all tha
92 matches
Mail list logo
