From: Roman Kiryanov
to use the QEMU headers with a C++ compiler.
Signed-off-by: Felix Wu
Signed-off-by: Roman Kiryanov
---
include/qemu/atomic.h | 8
include/qemu/atomic.hpp | 38 ++
2 files changed, 46 insertions(+)
create mode 100644
From: Roman Kiryanov
'class' is a C++ keyword and it prevents from
using the QEMU headers with a C++ compiler.
Google-Bug-Id: 331190993
Change-Id: I9ab7d2d77edef654a9c7b7cb9cd01795a6ed65a2
Signed-off-by: Felix Wu
Signed-off-by: Roman Kiryanov
---
hw/core/qdev-properties-sys
From: Roman Kiryanov
`typename` is a C++ keyword and it prevents from
using the QEMU headers with a C++ compiler.
Google-Bug-Id: 331190993
Change-Id: Iff313ca5ec157a1a3826b4f5665073534d961a26
Signed-off-by: Felix Wu
Signed-off-by: Roman Kiryanov
---
hw/core/bus.c | 8 +--
include
/-/issues/1835
If you want to use IPv6, let me know and I can create pull requests in
libslirp so you can try it.
Thanks, Felix
On Fri, Dec 8, 2023 at 9:33 AM Patrick Venture wrote:
>
> On Fri, Oct 27, 2023 at 11:44 PM Louai Al-Khanji
> wrote:
>
>> Hi,
>>
>> I'
It should use T8_BASE instead of T0_BASE.
Felix Wu (1):
SMBIOS type 8 should use T8_BASE.
hw/smbios/smbios.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
2.43.0.275.g3460e3d667-goog
---
hw/smbios/smbios.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/hw/smbios/smbios.c b/hw/smbios/smbios.c
index 2a90601ac5..7dda84b284 100644
--- a/hw/smbios/smbios.c
+++ b/hw/smbios/smbios.c
@@ -591,6 +591,7 @@ bool smbios_skip_table(uint8_t type, bool required_table)
lso, 132480-129600 = 2880 vs 2076, the read byte doesn't match.
Either I need to go with the way in question 1, b.c. steps, or I don't need
to delete the socket, but the sopreprbuf wasn't proper to be used there and
I need to correct it.
Also updated https://gitlab.com/qemu-project/
, 0==disconnected.
```
And after that, the state of `SocketChardev` remained disconnected, and
when the 2nd request came in, the `tcp_chr_write` dropped it directly.
Maybe this state machine should be reset after every connection? Not sure.
On Thu, Aug 17, 2023 at 11:58 AM Felix Wu wrote:
> Hi
I am using a simple http server for this test, and just noticed this bug
also exists in IPv4 guestfwd. I've documented it in
https://gitlab.com/qemu-project/qemu/-/issues/1835.
Just want to check if anyone has seen the same issue before.
Thanks! Felix
On Thu, Jul 20, 2023 at 7:54 AM Samue
tcp_input tcp_output
QEMU > slirp --> host
< <--
tcp_output tcp_input
2. I don't see port 6655 in the above process. How does slirp know 6655 is
the port that needs to be visited on the host side?
e? I think I need it in
the invocation.
Thanks in advance! Felix
[1]. https://gitlab.freedesktop.org/slirp/libslirp/-/issues/67
Heya!
On 27.06.22 18:44, Felix xq Queißner wrote:
The patch adds "show_tabs" command line option for GTK ui similar to
"grab_on_hover". This option allows tabbed view mode to not have to be enabled by hand at
each start of the VM.
On 30.06.22 16:09, Hanna Reitz wrote:
&
The patch adds "show_tabs" command line option for GTK ui similar to
"grab_on_hover". This option allows tabbed view mode to not have to be
enabled by hand at each start of the VM.
Signed-off-by: Felix "xq" Queißner
---
qapi/ui.json| 7 ++-
qemu-o
The patch adds "show_tabs" command line option for GTK ui similar to
"grab_on_hover". This option allows tabbed view mode to not have to be enabled
by hand at each start of the VM.
Signed-off-by: Felix "xq" Queißner
---
qapi/ui.json| 5 -
qemu-options.
ke it work.
- Felix
'd love to see that patch land in QEMU one day.
I discovered that patch by searching for "start qemu with tabs visible"
and found this link:
https://patchwork.ozlabs.org/project/qemu-devel/patch/56d0203f.5060...@gmail.com/
Regards
- Felix
Can someone explain why the patch keeps the incorrect behaviour as the
default? It’s silly.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1897568
Title:
Strange keyboard behaviour in Vim editor
St
** Patch added: "cmdline.patch"
https://bugs.launchpad.net/qemu/+bug/1860914/+attachment/5383658/+files/cmdline.patch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1860914
Title:
QEMU prepends
Confirming that I can no longer reproduce the bug with the latest master
(ae3aa5da96f4ccf0c2a28851449d92db9fcfad71). I have not bisected the bug,
though; at the moment I am not quite able to afford the time.
--
You received this bug notification because you are a member of qemu-
devel-ml, which i
** Description changed:
qemu 5.0.0, liburing1 0.6-3, Linux 5.6.0-1-686-pae (Debian)
Stack trace:
- Stack trace of thread 31002:
- #0 0xb7faf1cd __kernel_vsyscall (linux-gate.so.1 +
0x11cd)
- #1 0xb6c618e2 __libc_signal_re
Public bug reported:
qemu 5.0.0, liburing1 0.6-3, Linux 5.6.0-1-686-pae (Debian)
Stack trace:
Stack trace of thread 31002:
#0 0xb7faf1cd __kernel_vsyscall (linux-gate.so.1 +
0x11cd)
#1 0xb6c618e2 __libc_signal_restore_set (libc.s
Public bug reported:
When QEMU is launched with the -kernel option to boot a Multiboot image,
the command line passed in the -append option is additionally prefixed
the pathname of the kernel image and a space. Likewise, module command
lines passed in the -initrd option are passed with the module
Never mind, 0ec7e6779fc830e5b4e6a448d75317fafcf69477 fixed this.
This can be closed.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1827871
Title:
Race condition when rebooting with the TCG backend
Public bug reported:
Reporting this as present in QEMU 3.1.0, although I don't see any commit
in current git master (a6ae23831b05a11880b40f7d58e332c45a6b04f7) that
would suggest this issue is fixed.
$ uname -a
Linux boole 4.19.0-4-686-pae #1 SMP Debian 4.19.28-2 (2019-03-15) i686
GNU/Lin
** Patch added: "disas.patch"
https://bugs.launchpad.net/qemu/+bug/1774830/+attachment/5261663/+files/disas.patch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1774830
Title:
qemu monitor disas
Hi stefan:
Thank you very much for your reply. Yes, I want to reduce impact of
resources among virtual machines including I/O resources, vCPU and etc. I
can use CPU pin feature to pin vCPU to dedicated host's physical CPU and
use I/O throttling feature to limit IOPS and bandwidth of VM's disks.
Hi Peter Maydell:
Got it, thank you very much!
2017-12-02 19:52 GMT+08:00 Peter Maydell :
> On 2 December 2017 at 07:41, FelixYao wrote:
> > hi Paolo Bonzini:
> >
> > Those codes seem useless, Could it be removed?
> >
> > Signed-off-by: FelixYao
> > ---
> > vl.c | 4
> > 1 file changed,
I believe commits f82d92bb028a1d674bab4ccc7e6cde6c04956230 and
6817efea3a0d1bf87be815970cdb014c5a64b628 have fixed this particular bug;
although I've since noticed the vvfat driver remains quite fragile,
especially FAT32 and writing support. I've got some patches for it of my
own, which I might sub
where this should be fixed.
-- Felix
Peter Maydell wrote:
> On 30 September 2016 at 16:39, Felix Janda wrote:
> > The F_EXLCK and F_SHLCK fcntl lock constants are obsolete synonyms for
> > F_WRLCK and F_RDLCK.
>
> This seems unlikely, since on for instance Alpha F_EXLCK is
> 16, F_SHLCK is 32, F_RDLCK i
Peter Maydell wrote:
> On 30 September 2016 at 16:41, Felix Janda wrote:
> > This fixes a compilation error with the musl c library.
> > ---
> > I don't really understand the purpose of the hack, which was
> > introduced in
> >
> >
Peter Maydell wrote:
> On 30 September 2016 at 16:39, Felix Janda wrote:
> > The F_EXLCK and F_SHLCK fcntl lock constants are obsolete synonyms for
> > F_WRLCK and F_RDLCK.
>
> This seems unlikely, since on for instance Alpha F_EXLCK is
> 16, F_SHLCK is 32, F_RDLCK i
This removes the last usage of in the code base.
Signed-off-by: Felix Janda
---
linux-user/syscall.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 3d1f694..4bfb671 100644
--- a/linux-user/syscall.c
+++ b/linux-user
This fixes a compilation error with the musl c library.
---
I don't really understand the purpose of the hack, which was
introduced in
http://git.qemu.org/?p=qemu.git;a=commit;h=624f7979058b84cbf81c76d45f302ce757b213ca
but musl does not have a separate thread library (it is included in
libc.so),
The F_EXLCK and F_SHLCK fcntl lock constants are obsolete synonyms for
F_WRLCK and F_RDLCK. Include to fix compilation with
the musl c library, which does not expose these constants.
Signed-off-by: Felix Janda
---
linux-user/syscall.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/linux
integer type promotions. Since glibc-2.4
is now a decade old, we can remove this workaround.
Signed-off-by: Felix Janda
---
linux-user/mmap.c | 14 --
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/linux-user/mmap.c b/linux-user/mmap.c
index c4371d9..ffd099d 100644
Peter Maydell wrote:
> On 17 September 2016 at 18:20, Felix Janda wrote:
> > Signed-off-by: Felix Janda
> > ---
> > linux-user/mmap.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/linux-user/mmap.c b/linux-user/m
Riku Voipio wrote:
> Hi,
>
> On Sat, Sep 17, 2016 at 09:20:14PM -0400, Felix Janda wrote:
> > Signed-off-by: Felix Janda
>
> Have you run the mremap tests of ltp with this on your host/guest
> combo?
I have just run the tests. My host is arm and my guest is aarch64.
W
Signed-off-by: Felix Janda
---
linux-user/mmap.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/linux-user/mmap.c b/linux-user/mmap.c
index c4371d9..4882816 100644
--- a/linux-user/mmap.c
+++ b/linux-user/mmap.c
@@ -682,7 +682,7 @@ abi_long target_mremap(abi_ulong
The original issue turned out to be trivial. The dot and dot-dot entries
need to be the two very first entries in a non-root directory table;
however, readdir() does not guarantee that "." and ".." will be the
first items returned. When I patched read_directory() to generate "."
and ".." entries fi
I noticed another bug in vvfat disk image generation. Applying the patch
I attached earlier made testing easier. I'm less sure what the actual
problem is.
Steps to reproduce (you'll need to have cpio, md5sum and GNU GRUB 2.x
installed):
0. Apply the patch and build qemu-img.
1. Create a directory
** Patch added: "Patch to fix the qemu-img issue (does NOT resolve the whole
bug)"
https://bugs.launchpad.net/qemu/+bug/1599539/+attachment/4707063/+files/make_vvfat_work_with_qemu-img.patch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed
Public bug reported:
The vvfat driver sometimes generates entries about which file system
checking utilities generate complaints.
For example, dosfsck will complain that the volume label entry has non-
zero size. ScanDisk from Windows 9x complains about invalid dot (".")
and dot-dot ("..") entrie
> I could actually see the use of non-raw over NBD. We support nested
> protocols (where you can use qcow2->qcow2->file), that is, where a file
> contains a qcow2 file whose contents are themselves a qcow2 image.
> (Perhaps useful in nested guests, where the outer qcow2 layer serves a
> disk to an
I compiled the latest git snapshot (tag: v2.6.0-rc4, calling itself
2.5.94; with GTK frontend) and could only half-reproduce the bug; keys
do not longer "jam", but arrow keys are still captured twice. I woudn't
make much of that difference; this bug seems very timing-sensitive. It
could be that the
Public bug reported:
QEMU 2.5.0, SeaBIOS 1.9.1; I've been noticing this bug for quite a
while, though.
Steps to reproduce:
# Create a VM image, install DOS in it (doesn't matter which) and launch it.
# Launch a "bare DOS" DPMI host (not an operating system) in it; I tested with
CWSDPMI and HDPM
if i try to compile with target-list=i386-linux-user it is working so
the problem must the target i386-softmmu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1545024
Title:
compiling on armv7 crashe
i have tried gcc4.9 and gcc4.8. both creating this error
im using debian 8(jessie) and the host is a odroid-xu4
(http://www.hardkernel.com/main/products/prdt_info.php?g_code=G143452239825&tab_idx=2)
spice and spice-platform are build from the last stable the other
dependecies are from the debian
Public bug reported:
If i try to compile qemu on armv7 cpu i get this error:
LINK qemu-nbd
CCqemu-img.o
LINK qemu-img
LINK qemu-io
LINK qemu-bridge-helper
CCqmp-marshal.o
CChw/display/qxl.o
{standard input}: Assembler messages:
{standard input}:1704: Error: bad instr
Regressed in commit f29783f72ea77dfbd7ea0c993d62d253d4c4e023.
I've just run into this in a similar circumstance: trying to reverse-
engineer a driver for a phone to which I can only connect via Bluetooth.
No problem, I can just have it pretend to be a USB device. Except that I
can't, because the d
Public bug reported:
Running
qemu -drive file.driver=vvfat,file.dir=.
displays
WARNING: Image format was not specified for 'json:{"dir": ".", "driver":
"vvfat"}' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write
operations on block 0 will
ping (forgot to CC to maintainer before)
http://patchwork.ozlabs.org/patch/417154/
The resource argument is translated from host to target for
[gs]etprlimit but not for prlimit64. Fix this.
Signed-off-by: Felix Janda
---
linux-user/syscall.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index aaac6a2..5658b66
Public bug reported:
Suppose you have a single filesystem image. It would be nice if QEMU
could generate a virtual partition table for it and make it available to
the guest as a partitioned disk. Otherwise you have to use workarounds
like this:
wiki.archlinux.org/index.php/QEMU#Simulate_virtual_di
It turns out that expr does not support ^ (at least according to the man
page). :-)
Still, you could do expr -$flag + 1 to do the same thing.
Is the ruckus just about this one place where $(( )) is used or are
there other non-Bourne-shell constructs?
--
You received this bug notification becaus
I actually have bash installed as /bin/sh and /bin/bash.
But I also have heirloom sh installed, which installs itself as /sbin/sh, and
that happened to be first in my $PATH.
Since the makefiles use "sh script" to run the scripts, that called the
heirloom sh.
http://heirloom.sourceforge.net/sh.ht
Public bug reported:
hxtool (part of the early build process) is a bash script. Running it
with /bin/sh yields a syntax error on line 10:
10 STEXI*|ETEXI*|SQMP*|EQMP*) flag=$(($flag^1))
$(( expr )) is a bash extension, not part of /bin/sh.
Note that replacing the sh in the first l
2134828 ioctl
704023 timerfd_settime
689105 poll
83122 futex
803 writev
476 rt_sigprocmask
287 recvmsg
178 brk
Signed-off-by: Felix Geyer
---
qemu-seccomp.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/qemu-seccomp.c b/qemu-seccomp.c
inde
On 28.01.2014 14:00, Eduardo Otubo wrote:
> On 01/26/2014 10:21 AM, Felix Geyer wrote:
>> libusb calls timerfd_create() and timerfd_settime() when it's built with
>> timerfd support.
>>
>> Command to reproduce:
>>
>> qemu -sandbox on -monitor stdio -d
quot;qemu-system-x86" sig=31 syscall=286
compat=0 ip=0x7f03513a06da code=0x0
Signed-off-by: Felix Geyer
---
qemu-seccomp.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/qemu-seccomp.c b/qemu-seccomp.c
index caa926e..2705468 100644
--- a/
internal representation is irrelevant here.
http://c-faq.com/null/
Felix
at if someone (also with a current qemu) could have a
look, as I did not even manage to get a core file...
Thanks
Felix
Thank you all for your responses.
It appears that it would be wise to continue to maintain Sun hardware.
On 12 June 2011 22:51, Blue Swirl wrote:
> On Wed, Jun 8, 2011 at 2:19 PM, Stefan Hajnoczi wrote:
>> On Wed, Jun 8, 2011 at 11:08 AM, Felix Oxley wrote:
>>> I have a an (a
Hello,
I have a an (almost) EOL factory planning system running on Solaris
Sparc which I would like to move to intel (and preferably virtualise)
in order to avoid having to maintain the Sun system and backup system.
The text based cobol application runs on this system: SunOS gplan 5.9
Generic_1185
Liguori <[EMAIL PROTECTED]> wrote:
Evan Felix wrote:
> Folks here is a patch i've made for qemu that adds a memory based
> block device, it utilizes memory on the Host side to emulate a block
> device.
>
I often use -hda /dev/null for -kernel/-append.
If you really want
the code to
allocate the memory used twice, even though it only gets used the
second time.
- using qemu_mallocz seems to pre-allocate all the memory used, which
is fine, but my early code with calloc only allocated what blocks were
actually used. Does this bother people.
Evan Felix
diff -urNp -
66 matches
Mail list logo
