[PATCH 1/1] include/qemu: Provide a C++ compatible version of typeof_strip_qual

2024-06-24 Thread Felix Wu
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

[PATCH 1/2] qom: Rename Object::class into Object::klass

2024-06-24 Thread Felix Wu
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-system.c | 2

[PATCH 2/2] include/qom: Rename typename into type_name

2024-06-24 Thread Felix Wu
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

Re: udp guestfwd

2024-03-13 Thread Felix Wu
/-/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'm int

[PATCH 0/1] smbios_build_type_8_table should use T8_BASE.

2024-01-11 Thread Felix Wu
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

[PATCH 1/1] SMBIOS type 8 should use T8_BASE.

2024-01-11 Thread Felix Wu
--- 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)

Re: Tips for local testing guestfwd

2023-09-06 Thread Felix Wu
ch. 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/qemu/-/issues/1835. Any feedback will be appreciated, thanks! Felix [1].

Re: Tips for local testing guestfwd

2023-08-23 Thread Felix Wu
, 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

Re: Tips for local testing guestfwd

2023-08-17 Thread Felix Wu
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 Samuel Thibault

Re: Tips for local testing guestfwd

2023-07-18 Thread Felix Wu
put 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? Thanks in advance, F

Tips for local testing guestfwd

2023-06-26 Thread Felix Wu
I need it in the invocation. Thanks in advance! Felix [1]. https://gitlab.freedesktop.org/slirp/libslirp/-/issues/67

Re: [PATCH] gtk: Add show_tabs=on|off command line option.

2022-07-12 Thread Felix Queißner
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: &

[PATCH v2] gtk: Add show_tabs=on|off command line option.

2022-07-12 Thread Felix xq Queißner
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

[PATCH] gtk: Add show_tabs=on|off command line option.

2022-06-27 Thread Felix xq Queißner
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.

Re: [Qemu-devel] [PATCH] gtk: Add show_tabs=on|off command line option.

2022-06-23 Thread Felix Queißner
it work. - Felix

Re: [Qemu-devel] [PATCH] gtk: Add show_tabs=on|off command line option.

2022-06-23 Thread Felix Queißner
ve 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

[Bug 1897568] Re: Strange keyboard behaviour in Vim editor

2021-06-27 Thread 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

[Bug 1860914] Re: QEMU prepends pathnames to command lines of Multiboot kernels and modules, contrary to the specification

2020-06-14 Thread felix
** 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

[Bug 1878915] Re: util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed.

2020-05-22 Thread felix
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

[Bug 1878915] Re: util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed.

2020-05-17 Thread felix
** 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

[Bug 1878915] [NEW] util/fdmon-io_uring.c:95: get_sqe: Assertion `ret > 1' failed.

2020-05-15 Thread felix
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

[Bug 1860914] [NEW] QEMU prepends pathnames to command lines of Multiboot kernels and modules, contrary to the specification

2020-01-26 Thread felix
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

[Qemu-devel] [Bug 1827871] Re: Race condition when rebooting with the TCG backend

2019-05-06 Thread felix
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

[Qemu-devel] [Bug 1827871] [NEW] Race condition when rebooting with the TCG backend

2019-05-06 Thread felix
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

[Qemu-devel] [Bug 1774830] Re: qemu monitor disassembled memory dump produces incorrect output

2019-05-05 Thread felix
** 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

Re: [Qemu-devel] [PATCH 1/1] util/thread-pool: add parameter to limit maximum threads in thread pool

2018-07-30 Thread felix yao
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

Re: [Qemu-devel] [PATCH 1/1] main loop: remove useless code

2017-12-03 Thread felix yao
Hi Peter Maydell: Got it, thank you very much! 2017-12-02 19:52 GMT+08:00 Peter Maydell <peter.mayd...@linaro.org>: > On 2 December 2017 at 07:41, FelixYao <felix@gmail.com> wrote: > > hi Paolo Bonzini: > > > > Those codes seem useless, Could it be removed

[Qemu-devel] [Bug 1599539] Re: 2.6.0: vvfat driver generates bad FAT entries

2017-08-19 Thread felix
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

Re: [Qemu-devel] Fix build break during configuration on musl-libc based system

2017-02-16 Thread Felix Janda
where this should be fixed. -- Felix

Re: [Qemu-devel] [PATCH] linux-user: include for F_EXLCK and F_SHLCK

2016-10-01 Thread Felix Janda
Peter Maydell wrote: > On 30 September 2016 at 16:39, Felix Janda <felix.ja...@posteo.de> 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 > 1

Re: [Qemu-devel] [PATCH RFC] linux-user: peform __SIGRTMIN hack only when __SIGRTMIN is defined

2016-09-30 Thread Felix Janda
Peter Maydell wrote: > On 30 September 2016 at 16:41, Felix Janda <felix.ja...@posteo.de> 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 > > > &g

Re: [Qemu-devel] [PATCH] linux-user: include for F_EXLCK and F_SHLCK

2016-09-30 Thread Felix Janda
Peter Maydell wrote: > On 30 September 2016 at 16:39, Felix Janda <felix.ja...@posteo.de> 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 > 1

[Qemu-devel] [PATCH] linux-user: include instead of

2016-09-30 Thread Felix Janda
This removes the last usage of in the code base. Signed-off-by: Felix Janda <felix.ja...@posteo.de> --- 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/sys

[Qemu-devel] [PATCH RFC] linux-user: peform __SIGRTMIN hack only when __SIGRTMIN is defined

2016-09-30 Thread Felix Janda
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),

[Qemu-devel] [PATCH] linux-user: include for F_EXLCK and F_SHLCK

2016-09-30 Thread Felix Janda
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 <felix.ja...@posteo.de> --- linux-user/syscall.c | 1 + 1 file changed, 1 ins

[Qemu-devel] [PATCH] linux-user: use libc wrapper instead of direct mremap syscall

2016-09-30 Thread Felix Janda
integer type promotions. Since glibc-2.4 is now a decade old, we can remove this workaround. Signed-off-by: Felix Janda <felix.ja...@posteo.de> --- linux-user/mmap.c | 14 -- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/linux-user/mmap.c b/linux-user/mmap.c

Re: [Qemu-devel] [PATCH] linux-user: fix mremap for 64bit targets on 32bit hosts

2016-09-28 Thread Felix Janda
Peter Maydell wrote: > On 17 September 2016 at 18:20, Felix Janda <felix.ja...@posteo.de> wrote: > > Signed-off-by: Felix Janda <felix.ja...@posteo.de> > > --- > > linux-user/mmap.c | 4 ++-- > > 1 file changed, 2 insertions(+), 2 deletions(-) > > &g

Re: [Qemu-devel] [PATCH] linux-user: fix mremap for 64bit targets on 32bit hosts

2016-09-22 Thread Felix Janda
Riku Voipio wrote: > Hi, > > On Sat, Sep 17, 2016 at 09:20:14PM -0400, Felix Janda wrote: > > Signed-off-by: Felix Janda <felix.ja...@posteo.de> > > Have you run the mremap tests of ltp with this on your host/guest > combo? I have just run the tests. My host

[Qemu-devel] [PATCH] linux-user: fix mremap for 64bit targets on 32bit hosts

2016-09-17 Thread Felix Janda
Signed-off-by: Felix Janda <felix.ja...@posteo.de> --- 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 @@ ab

[Qemu-devel] [Bug 1599539] Re: 2.6.0: vvfat driver generates bad FAT entries

2016-08-10 Thread felix
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

[Qemu-devel] [Bug 1599539] Re: 2.6.0: vvfat driver generates bad FAT entries

2016-07-25 Thread felix
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

[Qemu-devel] [Bug 1599539] Re: 2.6.0: vvfat driver generates bad FAT entries

2016-07-25 Thread felix
** 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

[Qemu-devel] [Bug 1599539] [NEW] 2.6.0: vvfat driver generates bad FAT entries

2016-07-06 Thread felix
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 ("..")

[Qemu-devel] [Bug 1474263] Re: "Image format was not specified" warning should be suppressed for the vvfat (and probably nbd) driver

2016-07-05 Thread felix
> 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

[Qemu-devel] [Bug 1574246] Re: Drunken keyboard in go32v2 programs

2016-05-04 Thread felix
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

[Qemu-devel] [Bug 1574246] [NEW] Drunken keyboard in go32v2 programs

2016-04-24 Thread felix
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

[Qemu-devel] [Bug 1545024] [NEW] compiling on armv7 crashes compile qlx.o

2016-02-12 Thread Klaftenegger Felix
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

[Qemu-devel] [Bug 1545024] Re: compiling on armv7 crashes compile qlx.o

2016-02-12 Thread Klaftenegger Felix
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

[Qemu-devel] [Bug 1545024] Re: compiling on armv7 crashes compile qlx.o

2016-02-12 Thread Klaftenegger Felix
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_idx=2) spice and spice-platform are build from the last stable the other dependecies are from the debian

[Qemu-devel] [Bug 1180924] Re: fails to handle a usb serial port with a specific vendorid

2015-10-18 Thread felix
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

[Qemu-devel] [Bug 1474263] [NEW] Image format was not specified warning should be suppressed for the vvfat (and probably nbd) driver

2015-07-14 Thread felix
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 be

Re: [Qemu-devel] linux-user: translate resource also for prlimit64

2014-12-11 Thread Felix Janda
ping (forgot to CC to maintainer before) http://patchwork.ozlabs.org/patch/417154/

[Qemu-devel] [PATCH] linux-user: translate resource also for prlimit64

2014-12-02 Thread Felix Janda
The resource argument is translated from host to target for [gs]etprlimit but not for prlimit64. Fix this. Signed-off-by: Felix Janda felix.ja...@posteo.de --- linux-user/syscall.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/linux-user/syscall.c b/linux-user/syscall.c

[Qemu-devel] [Bug 1378407] [NEW] [feature request] Partition table wrapper for single-filesystem images

2014-10-07 Thread felix
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:

[Qemu-devel] [Bug 1347555] Re: qemu build failure, hxtool is a bash script, not a /bin/sh script

2014-07-24 Thread Felix von Leitner
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

[Qemu-devel] [Bug 1347555] [NEW] qemu build failure, hxtool is a bash script, not a /bin/sh script

2014-07-23 Thread Felix von Leitner
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

[Qemu-devel] [Bug 1347555] Re: qemu build failure, hxtool is a bash script, not a /bin/sh script

2014-07-23 Thread Felix von Leitner
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.

[Qemu-devel] [PATCH v2] seccomp: add timerfd_create and timerfd_settime to the whitelist

2014-01-30 Thread Felix Geyer
689105 poll 83122 futex 803 writev 476 rt_sigprocmask 287 recvmsg 178 brk Signed-off-by: Felix Geyer de...@fobos.de --- qemu-seccomp.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/qemu-seccomp.c b/qemu-seccomp.c index caa926e..b00922c

Re: [Qemu-devel] [PATCH] seccomp: add timerfd_create and timerfd_settime to the whitelist

2014-01-28 Thread Felix Geyer
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 -device piix3-usb-uhci,id=usb -device usb-host,hostbus

[Qemu-devel] [PATCH] seccomp: add timerfd_create and timerfd_settime to the whitelist

2014-01-26 Thread Felix Geyer
syscall=286 compat=0 ip=0x7f03513a06da code=0x0 Signed-off-by: Felix Geyer de...@fobos.de --- 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/qemu-seccomp.c +++ b

Re: [Qemu-devel] [PATCH] ppc: virtex_ml507: QEMU_OPTION_dtb support for this machine.

2013-08-14 Thread Felix Deichmann
representation is irrelevant here. http://c-faq.com/null/ Felix

[Qemu-devel] qemu-ppc (prep) crashes with NetBSD guest

2013-08-13 Thread Felix Deichmann
did not even manage to get a core file... Thanks Felix

Re: [Qemu-devel] QEMU suitable for mission critical applications?

2011-06-13 Thread Felix Oxley
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 blauwir...@gmail.com wrote: On Wed, Jun 8, 2011 at 2:19 PM, Stefan Hajnoczi stefa...@gmail.com wrote: On Wed, Jun 8, 2011 at 11:08 AM, Felix Oxley fe

[Qemu-devel] QEMU suitable for mission critical applications?

2011-06-08 Thread Felix Oxley
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

[Qemu-devel] [PATCH] Memory Based Block Device

2007-07-25 Thread Evan Felix
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 -x '*~' -x '*html' -x

[Qemu-devel] Re: [kvm-devel] [PATCH] Memory Based Block Device

2007-07-25 Thread Evan Felix
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 to implement a proper solution