On 13.12.2016 14:52, Gerd Hoffmann wrote:
> On Di, 2016-12-13 at 13:44 +0100, Thomas Huth wrote:
>> When passing through a USB storage device to a pseries guest, it
>> is currently not possible to automatically boot from the device
>> if the "bootindex" property has
On 06.12.2016 23:42, Oscar A wrote:
> Hello dear all,
>
> I just started to get interested in operative systems, booting, and
> virtual machines, and found this project, which is very nice. I have
> a question. For instance, take the Hanoi´s towers image of yesterday.
>
> I want to boot my
Fix has been committed:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=e6e2784cacd4cfec149
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Fix has been committed:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=a813fe73621e1221a09
** Changed in: qemu
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
t-device path properly that
SLOF can automatically boot from the device.
Buglink: https://bugzilla.redhat.com/show_bug.cgi?id=1354177
Signed-off-by: Thomas Huth <th...@redhat.com>
---
v2: Improved the comment in spapr.c as requested by David
hw/ppc/spapr.c | 13 +
hw/usb/
On 14.12.2016 10:36, Gerd Hoffmann wrote:
> Hi,
>
in the /chosen/qemu,boot-list property. SLOF, however, probes the
USB device, recognizes that it is a storage device and thus changes
its name to "storage", and additionally adds a child node for the
SCSI LUN, so the correct
On 16.12.2016 20:13, Richard Henderson wrote:
> This is a linux-user only port, emulating a 32-bit only version of a
> pa-2.0 cpu. This is good enough to do well with both the gcc and glibc
> testsuites. Helge Deller has provided invaluable assistance testing
> with a more complete debian
Released with version 2.8
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/808737
Title:
No option to load additional binary files
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1596160
Title:
SIGSEGV in memory_region_access_valid on Sabre Lite board
Status in
e default behaviour of the "none" machine is not changed, i.e.
no CPU and no RAM is instantiated by default. You've explicitely got to
specify the CPU model with "-cpu" and the amount of RAM with "-m" to get
these new features.
Signed-off-by: Thomas Huth <th...@redhat.com>
--
Which QEMU version did you use? Can you still reproduce this with the
latest release?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1256432
Which QEMU version did you use here? Can you still reproduce this
problem with the latest version of QEMU (currently 2.8)?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On 11.01.2017 18:12, Eric Blake wrote:
> On 01/11/2017 10:41 AM, dcb wrote:
>> so I think the compiler warning is for the i * 2 lhs of the ?.
>
> Yes - the compiler is complaining that 'i * 2' can only be non-zero if
> 'i' was non-zero (given that the code occurs in a loop for i between 0
> and
Fix has been committed:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=97efe4f961dcf5a0126
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Released with version 2.8
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1611979
Title:
GTK+ interface, backspace is broken in the
Fix has been committed here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=6ab3fc32ea640026726b
... and been released with QEMU version 2.8
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
Released with version 2.8
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1464611
Title:
4 * redundant conditions
Status in QEMU:
Released with version 2.8
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1631625
Title:
target-mips/dsp_helper.c: two possible bad
FWIW, the crash should be fixed by this commit here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=7bacfd7f7289192c83330
(but we still need to fix the gtk side, too, to only send as much characters at
once as the receiving side can take)
--
You received this bug notification because you are a
Released with version 2.8.
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1631773
Title:
hw/dma/pl080.c:354: possible typo ?
On 12.01.2017 21:18, Laurent Vivier wrote:
> Address Register indirect With postincrement:
>
> When using the stack pointer (A7) with byte size data, the register
> is incremented by two.
>
> Address Register indirect With predecrement:
>
> When using the stack pointer (A7) with byte size data,
Better late than never ;-)
** Changed in: qemu
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/622367
Title:
No BIOS MPFP structure with smp=92 and more
ve any CPUs by default, but these HMP commands did
not check for a valid CPU pointer yet. Add such checks now, so we get
an error message about the missing CPU instead.
Signed-off-by: Thomas Huth <th...@redhat.com>
---
v2:
- Added more checks to cover "nmi" and "memsave", too
This should have been fixed by this commit here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=5d6768e3b8908a60f0
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On 12.01.2017 09:10, Markus Armbruster wrote:
> Thomas Huth <th...@redhat.com> writes:
>
>> When running certain HMP commands ("info registers", "info cpustats"
>> or dumping virtual memory) with the "none" machine, QEMU crashes
>&g
ve any CPUs by default, but these HMP commands did
not check for a valid CPU pointer yet. Add such checks now, so we get
an error message about the missing CPU instead.
Reviewed-by: Dr. David Alan Gilbert <dgilb...@redhat.com>
Signed-off-by: Thomas Huth <th...@redhat.com>
---
v3:
- Use
On 12.01.2017 13:19, Dr. David Alan Gilbert wrote:
> * Thomas Huth (th...@redhat.com) wrote:
>> When running certain HMP commands ("info registers", "info cpustats",
>> "nmi", "memsave" or dumping virtual memory) with the "none"
Moving this to the Ubuntu-qemu bug tracker since you're apparently using
Ubuntu's QEMU, not the upstream QEMU.
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Triaging old bug tickets ... can you still reproduce this problem with
the latest version of QEMU (currently version 2.8)?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
** Changed in: qemu
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/917645
Title:
[Feature request] ia64-softmmu wanted
Status in HelenOS branches:
Confirmed
Triaging old bug tickets ... can you still reproduce this problem with
the latest version of QEMU (currently version 2.8)?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
According to comment #6 this has been fixed in version 1.0 ... is there
still something left to do here?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On 13.01.2017 08:59, Markus Armbruster wrote:
> Thomas Huth <th...@redhat.com> writes:
>
>> On 12.01.2017 17:22, Markus Armbruster wrote:
>>> Thomas Huth <th...@redhat.com> writes:
>>>
>>>> When running certain HMP commands ("info re
machine does not have any CPUs by default, but these HMP commands
did not check for a valid CPU pointer yet. Add such checks now, so we get
an error message about the missing CPU instead.
Signed-off-by: Thomas Huth <th...@redhat.com>
---
v4:
- Added some more target-specifc checks (for "inf
& opsize == OS_BYTE &&
> +m68k_feature(s->env, M68K_FEATURE_M68000)) {
> +tcg_gen_subi_i32(tmp, reg, 2);
> +} else {
> + tcg_gen_addi_i32(tmp, reg, opsize_bytes(opsize));
> +}
> delay_set_areg(s, reg0, tmp, true);
> }
> return result;
>
Reviewed-by: Thomas Huth <h...@tuxfamily.org>
On 13.01.2017 13:23, Mark Cave-Ayland wrote:
> On 12/01/17 12:57, Hervé Poussineau wrote:
>
>> Le 11/01/2017 à 17:58, Artyom Tarasenko a écrit :
>>> Hi Hervé,
>>>
>>> nice work!
>>>
>>> On Thu, Dec 29, 2016 at 11:12 PM, Hervé Poussineau
>>> wrote:
Hi,
This
On 10.01.2017 01:39, David Gibson wrote:
> On Mon, Jan 09, 2017 at 01:57:24PM +0100, Thomas Huth wrote:
>> Running "qemu-system-ppc64 -M pseries -cpu POWER9" currently does not work
>> yet and results in this error message:
>>
>> qemu-system-ppc64: Una
On 10.01.2017 04:32, Michael S. Tsirkin wrote:
> On Thu, Nov 10, 2016 at 11:11:43AM +0100, Thomas Huth wrote:
>> There are only very old and orphaned stable branches listed
>> in the MAINTAINERS file - so this section is pretty useless
>> nowadays. Let's remove it.
>>
&g
Released with version 2.8
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1414293
Title:
target-lm32/translate.c:336: bad ? :
Released with version 2.8
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1625295
Title:
qemu-arm dies with libarmmem inside
Thanks for verifying!
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/696834
Title:
FP exception reporting not working on NetBSD host
Patch has been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=e9d9ee234f852026d58
... and been released with QEMU version 2.8
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
Released with version 2.8
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1619438
Title:
GTK+ UI, delete key deletes to the left in
QEMU 0.12 is quite outdated nowadays ... can you still reproduce this
issue with the latest version of QEMU (currently version 2.8)?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
On 12.01.2017 17:22, Markus Armbruster wrote:
> Thomas Huth <th...@redhat.com> writes:
>
>> When running certain HMP commands ("info registers", "info cpustats",
>> "nmi", "memsave" or dumping virtual memory) with the "none"
ds did not check for
a valid CPU pointer yet. Add such a check now and print a message
about the missing CPU instead.
Signed-off-by: Thomas Huth <th...@redhat.com>
---
monitor.c | 29 +
1 file changed, 25 insertions(+), 4 deletions(-)
diff --git a/monit
QEMU 0.12 is completely outdated nowadays ... can you still reproduce
this problem with the latest version of QEMU?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Peter's patch had been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=1669add752d9f2928
==> Fix released
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On 30.11.2016 17:44, Yongbok Kim wrote:
> Fixed issues in the MIPSDSP64 instructions dextp and dextpdp.
> Shifting can go out of 32 bit range.
>
> https://bugs.launchpad.net/qemu/+bug/1631625
>
> Reported-by: Thomas Huth <th...@redhat.com>
> Reported-by: Jia Liu <
On 02.12.2016 23:59, Programmingkid wrote:
> I thought we could use a Hosts page to sort all the host documentation we
> have. It is located here: http://wiki.qemu.org/Hosts
Since it's documentation, shouldn't this rather go to
/Documentation/Hosts instead of /Hosts ?
Thomas
So can we close this bug now, or is there still something left to do
here?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/902413
Title:
If I've got comment 27 right, the issue has also been fixed upstream, so
I'm setting the status now to "Fix released". If there's still something
left to do here, feel free to change it again.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because
Looks like this had been fixed here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=ba2b22888c43f
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Can you still reproduce this issue with the latest version of QEMU / the
latest version of gtk?
** Changed in: qemu
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Can you still reproduce this problem with the latest version of QEMU? If
so, could you please send a refreshed patch to the qemu-devel mailing
list? We do not pick up patches from the bug tracker. Thanks!
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification
Can you still reproduce this problem with the latest version of QEMU? If
so, could you please refresh your patch and send it to the qemu-devel
mailing list? (we do not accept patches from the bug tracker)
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1645287
Title:
Option "split" does not available for kernel_irqchip flag in qemu-
system-x86_64
Status in
this rather just as unnecessary code churn instead?
(Note: This patch series does also not contain all targets yet,
I first would like to get some feedback before continuing this work)
Thomas Huth (11):
Makefile: Allow CPU targets to reside in target/ folder, too
tilegx: Move CPU files
Signed-off-by: Thomas Huth <th...@redhat.com>
---
MAINTAINERS | 4 ++--
include/hw/mips/cpudevs.h | 2 +-
{target-mips => target/mips}/Makefile.objs| 0
{target-mips => target/mips}/TODO | 0
{target-mips => t
Signed-off-by: Thomas Huth <th...@redhat.com>
---
MAINTAINERS | 8
Makefile.objs | 2 +-
{target-s390x => target/s390x}/Makefile.objs | 2 +-
{target-s390x => target/s390x}/arch_dump.c
On 30.11.2016 02:01, Tom Rini wrote:
> Hey all,
>
> I'm trying to make use of the r2d platform for U-Boot testing via QEMU.
> After applying a series[1] I can use the kernel.org sh4 toolchain to get
> a u-boot.bin that runs, mostly. I say mostly as first of all I have to
> pass "-monitor null
Signed-off-by: Thomas Huth <th...@redhat.com>
---
MAINTAINERS | 2 +-
Makefile.objs | 2 +-
{target-sparc => target/sparc}/Makefile.objs | 0
{target-sparc => target/sparc}/TODO | 0
{target-sparc => targ
On 30.11.2016 09:02, Aurelien Jarno wrote:
> On 2016-11-30 08:33, Thomas Huth wrote:
>> On 30.11.2016 02:01, Tom Rini wrote:
>>> Hey all,
>>>
>>> I'm trying to make use of the r2d platform for U-Boot testing via QEMU.
>>> After applying a series[1]
Signed-off-by: Thomas Huth <th...@redhat.com>
---
MAINTAINERS| 2 +-
include/hw/m68k/mcf.h | 2 +-
{target-m68k => target/m68k}/Makefile.objs | 0
{target-m68k => target/m68k}/cpu-qom.h | 0
{target-m68k => target/m68k}/cp
To be able to compile the CPU targets from within a subfolder
of the target/ folder, we've got to adapt the Makefile.target
a little bit first.
Signed-off-by: Thomas Huth <th...@redhat.com>
---
Makefile.target | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff
Signed-off-by: Thomas Huth <th...@redhat.com>
---
MAINTAINERS | 2 +-
hw/alpha/alpha_sys.h | 2 +-
{target-alpha => target/alpha}/Makefile.objs | 0
{target-alpha => target/alpha}/STATUS| 0
{target-alpha => target/a
Signed-off-by: Thomas Huth <th...@redhat.com>
---
MAINTAINERS| 4 ++--
Makefile.objs | 2 +-
hw/arm/strongarm.h | 2 +-
hw/arm/virt-acpi-build.c | 2 +-
include/hw/arm
Signed-off-by: Thomas Huth <th...@redhat.com>
---
MAINTAINERS | 4 ++--
Makefile.objs| 2 +-
hw/i386/acpi-build.c | 2 +-
hw/i386/kvm/apic.c
Signed-off-by: Thomas Huth <th...@redhat.com>
---
MAINTAINERS | 2 +-
{target-microblaze => target/microblaze}/Makefile.objs | 0
{target-microblaze => target/microblaze}/cpu-qom.h | 0
{target-microblaze => target/mi
Signed-off-by: Thomas Huth <th...@redhat.com>
---
MAINTAINERS | 4 ++--
Makefile.objs | 2 +-
hw/ppc/fdt.c| 2 +-
hw/ppc/pnv.c| 2
Signed-off-by: Thomas Huth <th...@redhat.com>
---
{target-tilegx => target/tilegx}/Makefile.objs | 0
{target-tilegx => target/tilegx}/cpu.c | 0
{target-tilegx => target/tilegx}/cpu.h | 0
{target-tilegx => target/tilegx}/helper.c| 0
{target-tileg
On 30.11.2016 11:10, Laurent Vivier wrote:
> Le 30/11/2016 à 10:47, Thomas Huth a écrit :
>> We've currently got 18 architectures in QEMU, and thus 18 target-xxx
>> folders in the root folder of the QEMU source tree. More architectures
>> (e.g. RISC-V, AVR) are likely to be i
).
And yes, we still need more disk images to complete the run this year -
if you are interested in contributing, please have a look at my original
mail below.
Enjoy,
Thomas
On 17.09.2016 15:05, Thomas Huth wrote:
>
> Hi all!
>
> This year, we are celebrating the 10th anniversa
On 01.12.2016 08:24, Stefan Hajnoczi wrote:
> I recently upgraded to Fedora 25 which runs Wayland by default.
>
> The GTK UI is now sending unknown keycodes to the guests. Although
> alphanumeric keys work, the cursor keys are broken.
>
> There is X11-specific code for keycode mapping in
Triaging old bug tickets ... QEMU 1.5 is quite old already - can you
still reproduce the crash with the latest version of QEMU?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Triaging old bug tickets ... is this still an issue with the latest
version of QEMU or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Looks like Petar's patch from comment #6 has been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=4d66261f71f2efa31e1052e
==> Fix released
** Changed in: qemu
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml,
Can you still reproduce this problem with the latest version of QEMU?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1248469
Title:
qemu 1.6.1
Which version of QEMU are you using?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1646610
Title:
"Assertion `!r->req.sg' failed." during live migration with VirtIO
Status in QEMU:
New
Bug
because the MCF NIC has never been adapted to
the currently expected QEMU device behavior. Thus let's QOMify the
NIC now to get rid of the warning message.
Signed-off-by: Thomas Huth <h...@tuxfamily.org>
---
hw/m68k/mcf5208.c | 20 ++
On 02.01.2017 11:54, Laurent Vivier wrote:
> Le 27/12/2016 à 14:58, Thomas Huth a écrit :
>> Am Tue, 27 Dec 2016 12:52:30 +0100
>> schrieb Laurent Vivier <laur...@vivier.eu>:
>>
>>> Le 20/12/2016 à 15:32, Thomas Huth a écrit :
>>>> You can
** Changed in: qemu
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/925405
Title:
VNC server does not work with Mac Screen Sharing
Status in QEMU:
Confirmed
Hi,
On 07.01.2017 16:23, Hervé Poussineau wrote:
> Machine supports both Open Hack'Ware and OpenBIOS.
> Open Hack'Ware is the default because OpenBIOS is currently unable to boot
> PReP boot partitions or PReP kernels.
>
> Signed-off-by: Hervé Poussineau
> ---
>
Triaging old bug tickets ... can you still reproduce this issue with the
latest version of QEMU (currently version 2.8)?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Triaging old bug tickets ... can you still reproduce this issue with the
latest version of QEMU (currently version 2.8)?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Since it has been fixed in Precise ... I assume this has also been fixed
in upstream QEMU? Or is there still anything left to do here?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
because the MCF NIC has never been adapted to
the currently expected QEMU device behavior. Thus let's QOMify the
NIC now to get rid of the warning message.
Signed-off-by: Thomas Huth <h...@tuxfamily.org>
---
v2:
- Add the mcf_fec.h header file for the shared #defines
- Use qemu_check_nic
Can you reproduce this problem with the latest version of QEMU from http
://qemu-project.org/Download ?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Since nobody replied here within the last years: I think you should
rather report problems with XEN / Proxmox to the XEN or Proxmox
bugtracker instead.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
Oh, I meant "comment from Alex", not "comment to Alex", sorry!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/884401
Title:
PCI Passthrough for Digium TCE400P Codec Card Not working
Status in
According to the comment to Alex, this should have been fixed in newer
versions, so setting status to "Fix Released" now.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
AFAIK a lot of issues reported by coverity have been addressed in the
recent versions of QEMU ... is there still anything left here that needs
special attention?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
On 06.01.2017 10:58, Thomas Huth wrote:
> When running qemu-system-m68k with the "-net" parameter (for example
> simply "-net nic -net user"), there is currently a confusing warning
> message saying:
>
> Warning: requested NIC (anonymous, model mcf_fec
Can you still reproduce this problem with the latest version of QEMU
from http://qemu-project.org/Download and recent host and guest Linux
kernels?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
ggable CPU there, too.
Signed-off-by: Thomas Huth <th...@redhat.com>
---
hw/ppc/spapr_cpu_core.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/hw/ppc/spapr_cpu_core.c b/hw/ppc/spapr_cpu_core.c
index 9dddaeb..71253f9 100644
--- a/hw/ppc/spapr_cpu_core.c
+++ b/hw/ppc/spapr_cpu_core.c
@@ -360,6
Triaging old bug tickets... QEMU 0.14 is completely outdated nowadays.
Can you still reproduce this behavior with the latest version of QEMU?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
QEMU 2.0 is not maintained by the QEMU project anymore. Can you please
try again with the latest release of QEMU (v2.8)? ... otherwise you
should report this to the bug tracker of your distro instead.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification
On 03.01.2017 18:11, Sean Bruno wrote:
>
>
> On 01/03/17 09:18, Sean Bruno wrote:
>>
>> I'm pondering where to start with getting FreeBSD's bsd-user code into
>> shape so it could actually be reviewed and accepted now that its sort of
>> working again (signal handling fixed finally).
>>
>> I
On 07.01.2017 16:23, Hervé Poussineau wrote:
> Hi,
>
> This patchset adds the emulation of the IBM RS/6000 7020 (40p). The real
> machine is
> able to run AIX (up to 4.3.3), Windows NT (up to 4.0 SP1), the beta of OS/2
> PowerPC,
> Solaris, Linux, NetBSD/PReP ...
>
> I've tested current
None of the ColdFire boards that we currently support has a PCI or
USB bus (and AFAIK the upcoming q800 machine does not support PCI
and USB either), so we do not need these settings the config file.
Signed-off-by: Thomas Huth <h...@tuxfamily.org>
---
default-configs/m68k-softmmu.mak | 2
1601 - 1700 of 17805 matches
Mail list logo