** Changed in: qemu
Status: Incomplete => New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1860575
Title:
qemu64 CPU model is incorrect
Status in QEMU:
New
Bug description:
At the
I finally understand where the problem is.
Qemu's user-mode emulation maps guest threads to native ones by spawning a new
native one
and running a forked copy of the CPUX86State in parallel with the main thread.
This works fine for pretty much every architecture but i386 where the GDT/LDT
Public bug reported:
Given the following C program, qemu-i386 will surely and certainly segfault
when executing it.
The problem is only noticeable if the program is statically linked to musl's
libc and, as written
in the title, it only manifests when targeting i386.
Removing the pthread calls
The new code in Qemu is correct, the real problem is that the code [1] is
trying to negotiate an invalid working voltage with CMD41.
The SD specification marks the first 15 bits as reserved (except for the 7th,
that's the dual-voltage flag) meaning that compliant cards will timeout as well.
If
Sorry to bother you, I would like to ask a question.I want to use qemu to
monitor the information of the target thread reading and writing memory. I
see that qemu supports the tcg plugin, but I just find the following code
in plugin-gen.c .Do I just need to add a record function in it? How do I
The error message is a rather cryptic "LLVM ERROR: 64-bit code requested on a
subtarget
that doesn't support it!" as it knows Athlon CPUs don't support the AMD64 ISA.
I will relay the tip to the people managing the VMs, I guess this problem went
unnoticed
for so long because there are not many
Public bug reported:
At the moment the "qemu64" CPU is defined as follows:
```
.vendor = CPUID_VENDOR_AMD,
.family = 6,
.model = 6,
.stepping = 3,
```
According to Wikipedia [1] this means the CPU is defined as part of the
K7 family while the AMD64 ISA was only
** Also affects: archlinux
Importance: Undecided
Status: New
** No longer affects: archlinux
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1541643
Title:
IA32_FEATURE_CONTROL MSR unset
Hi Andrea,
On 09/11/2015 10:47 AM, Michael Kerrisk (man-pages) wrote:
> On 05/14/2015 07:30 PM, Andrea Arcangeli wrote:
>> Add documentation.
>
> Hi Andrea,
>
> I do not recall... Did you write a man page also for this new system call?
No response to my last mail, so I'll
On 05/14/2015 07:30 PM, Andrea Arcangeli wrote:
> Add documentation.
Hi Andrea,
I do not recall... Did you write a man page also for this new system call?
Thanks,
Michael
> Signed-off-by: Andrea Arcangeli <aarca...@redhat.com>
> ---
> Documentation/vm/use
in userland by talking to the kernel using the userfaultfd
protocol.
Is there someting like a man page for this new syscall?
Thanks,
Michael
poll() can be used to know when there are new pending userfaults to be
read (POLLIN).
Signed-off-by: Andrea Arcangeli aarca...@redhat.com
---
fs
sensitive apps, which might want to select which areas are dumped.
Since we have
MADV_DODUMP
MADV_DONTDUMP
MADV_NODUMP
heading for userspace in 3.4, would you be willing to write patches
for the madvise(2) man page to describe these flags?
See http://www.kernel.org/doc/man-pages/download.html
)
... but it is a new information to write inside win documentation
because if i use qemu-0.9.0 windows stable build
\\ is not mandatory...
Looks like result of patch posted by Cd-MaN 30.12.2007 12:01 EEST
Sergey Bychkow
ICQ: 21014758
FTN: 2:450/118.55
Description:
When using base images (ie difference disks), the path of the backing image is
interpreted correctly as being relative to the path of the difference image
(which is very nice). However, at creation time, the path is copied verbatim
from the command line, which can lead to
W00t, my first patch got applied :) Thank you.
Here goes version 0.3 of my packet capture patch. I rewritten it to be a custom
VLANClient which implements the capturing part in its fd_read proceudre, rather
than adding additional properties to the VLAN structure. Monitor support is
also
Hello all,
First of all I want to apologize for this mail and hope that I won't wast to
much of your valuable time hacking on Qemu ;-). My goal is to implement a
tracing system in Qemu, which would suspend the emulation at certain points
(determined by linear addresses), dump some information
Here goes v0.2 for my patch :-)
Changes
- now the option is a separate command line switch:
-net capture,vlan=2,file=test.pcap
- it is also available from the monitor
- added some more constants / defines to avoid repeating portions of the code
The use case I need it for is for honeypot-like systems. Ie. the system starts
from a snapshot and accesses links / runs executables while observing the
behaviour. For this use case it is the best if it is setable from the command
line.
This patch allows to capture the traffic flowing through a particular vlan in a
tcpdump compatible pcap file.
The patch is identical to the one created some time back, however it was
updated to apply to HEAD.
Usage: -net nic,pcap=capture_file.pcap
This patch allows to capture the traffic flowing through a particular
vlan in a tcpdump compatible pcap file.
The patch is identical to the one created some time back, however it
was updated to apply to HEAD.
Usage: -net nic,pcap=capture_file.pcap
I like the idea but I think it would
The attached patch modifies the parser function for the mac addresses (ie. -net
nic,macaddr=XX) in the following ways:
- the accepted separators now include -, because on Windows it is common to
write a MAC addresses separated by dashes (ie. 54-32-00-12-34-56)
- it supports specifying the
Le mercredi 28 novembre 2007 à 14:24 +, Samuel Thibault a écrit :
Hi,
Laurent Vivier, le Wed 28 Nov 2007 15:02:50 +0100, a écrit :
+ret = posix_memalign((void**)buf, 0x200, 512);
For making this more easily portable, maybe it should be a new
qemu_memalign() function? Also, the
Hello all.
Attached you find an updated version of my patch to dump the traffic on a given
interface to a tcpdump file. The changes are:
-moved from f* functions (fopen, fwrite) to the more basic functions (open,
write, etc) because this seems to be the norm in the source code
-fixed some
Hello all.
Attached is an other patch (against the CVS) to allow for more flexible mac
address parsing from the command line. Specifically it allows:
-using the '-' as separator (as Windows uses it)
-using no separator at all (just 12 hexadecimal characters in a row) - again
Windows uses this
You're absolutely right. Attached a corrected version.
- Original Message
From: Blue Swirl [EMAIL PROTECTED]
To: qemu-devel@nongnu.org
Sent: Sunday, 1 July, 2007 9:08:00 PM
Subject: Re: [Qemu-devel] [PATCH] Dump traffic to pcap file - update
On 7/1/07, Balazs Attila-Mihaly (Cd-MaN
per interface per virtual
computer), I welcome any suggestion where the code should be put.
Best regards,
Cd-MaN
___
New Yahoo! Mail is the ultimate force in competitive emailing. Find out more
that this improves readibility of the code, since
having both 1 and the constant HAS_ARG present implies that they have different
meaning (0 doesn't need to be replaced with any symbolic name imho, since it is
usually associated with nothing anyways).
Best regards,
Cd-MaN
I must prefix this with the fact that IANAL, but as I understand it, you must
release the source code only if you distribute that modified system (with GPL
v2). That is, if you use this system internally in you company, you don't have
to provide your modifications. But if you, for example,
Hello all.
First of all I want to congratulate everybody on this list for the wonderful
job s/he is doing. Qemu is the best Open Source emulator out there (and it is
fast ;-) ). I'm using Qemu to build an automated malicious code analysis system
and as such I would like to make some
29 matches
Mail list logo
