Since there hasn't been any response to this ticket anymore, I assume
the problem has been solved by other means on that machine - or by a
newer version of QEMU. So I'm closing this ticket now - if you still got
problems, please feel free to open it again.
** Changed in: qemu
Status: Incomp
Since there hasn't been any response to the question in comment #1, and
version 0.13 is very outdated nowadays, I'm closing this ticket now. If
you've still got USB problems with the very latest version of QEMU,
please feel free to re-open this ticket again, or open a new ticket
instead.
** Change
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1184616
Title:
undefined reference to `trace_qemu_anon_ram_alloc'
Status in QEMU:
Invalid
Bug de
Looking at http://lists.gnu.org/archive/html/qemu-
devel/2013-05/msg02268.html it seems this has been fixed with commits
8db165b36ef893ac69af045 and 3cb8c205e36531a07dff1d84 ==> setting status
to "Fix released"
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notif
I assume this had been fixed by this commit here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=1405b6290fa2143e02dce -
so I'm closing this ticket now. If you still hit the problem with the
latest version of QEMU, please feel free to open this ticket again.
** Changed in: qemu
Status: New
** 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/786440
Title:
qcow2 double free
Status in QEMU:
Incomplete
Bug description:
version 0.14.1 w
fw_cfg_write() support has been removed since QEMU 2.4, so I think we
can treat this as fixed now:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=023e3148567ac898c725813
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
OK, according to the last comments, the bug has been fixed somewhere
with the last kernel or QEMU releases, so I'm closing this ticket now.
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is sub
Right, this problem should be fixed with Spice, so I'm closing this
ticket now.
** Changed in: qemu
Status: Confirmed => 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/498039
Titl
To be able to include your patch, you've got to send it to the qemu-
devel mailing list, with a proper Signed-off-by line. Please see http
://qemu-project.org/Contribute/SubmitAPatch#Submitting_your_Patches for
details.
--
You received this bug notification because you are a member of qemu-
devel
Thanks for reporting the issue, patch has now been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=04bb79d1f519ae190a
** 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 QEM
Thanks for reporting this bug! Looks like this has already been fixed by this
commit here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=1d5b128cbeeab638f772e
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-
This problem has been fixed here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=7b4b0b5795e934a9b7efb
** 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.
https://bugs.launchpad.net/
FWIW, u-boot was apparently fixed here:
http://git.denx.de/?p=u-boot.git;a=commitdiff;h=2c13ba2f63a67664ab5
** 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.
https://bugs.launc
roms/u-boot is not under control of the QEMU project - you should report such
bugs to the u-boot project instead. Anyway, looks like the problem has been
fixed there:
http://git.denx.de/?p=u-boot.git;a=commitdiff;h=cc87d18a6ec74180784a6b
** Changed in: qemu
Status: New => Fix Released
--
Not sure whether this is really a bug or working as intended - but
apparently, the server IP address from the guest point of view (before
the NAT) has to be in the same subnet as the guest itself. So everything
should work fine if you use something like this in your first example:
-netdev
'user,i
Hi Timothy, sounds like this is a KVM (i.e. kernel) problem which might
not directly be related to QEMU. So you likely should report this bug in
the kernel bug tracker of your distro instead. Anyway, I've got some
questions:
1) Can you always reproduce this problem after a while, or does it occur
Fix has been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=a41c457881b5463b18901a849
** 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.
https://bugs.launchpad.net/b
That log does not look very helpful. Could you please provide more
details like command line options and the exact output of QEMU if your
problem still persists with the latest version of QEMU? Thanks!
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification bec
I think that firmware prompt is not really useful. Anyway, according to
https://virtuallyfun.superglobalmegacorp.com/2014/02/19/alpha-linux-on-
qemu/ you currently have to specify the (uncompressed) vmlinux kernel
with the "-kernel" option of QEMU. Then you should be able to start
Linux with qemu-s
The pci_add command has been remove since QEMU 2.3.0 ... so I'm closing
this bug now - sorry that nobody picked this up in 2013! If you still
can reproduce this problem with device_add, please feel free to open
this ticket again.
** Changed in: qemu
Status: New => Invalid
--
You received
The "pci_add" command has been removed since QEMU 2.3.0, so I guess we
can close this bug ... if you still can reproduce the problem with the
latest version, please feel free to open this ticket again.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification becaus
As mentioned in previous comments already, this issue should be solved
by commit a795ef8dcb8cbadffc996c4, so setting the 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
Snapshotting for XHCI has been implemented after QEMU 1.5.0:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=37352df30fbc38d1de464db8
... i.e. this should be working since QEMU 1.6.0. So I'm setting the status to
"Fix Released" - if you still have problems with the latest version of QEMU,
please f
Patch has been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=66518bf668f09eaab14c174
==> 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.
https://bug
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1257334
Title:
diffuse handling of image creation from another path
Status in QEMU:
Invalid
Bug d
I think this has likely been fixed by this commit here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=dec3fc9657e0682637de4d
... so setting the status to "Fix Released" now. If the problem still persists,
please feel free to open this ticket again.
** Changed in: qemu
Status: In Progress
Does this problem still occur with the latest version of QEMU (currently
it's 2.7.0)? If so, can you please post the exact assertion message, and
if possible a stack trace (taken with gdb)? Thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscrib
libcacard has been removed from the QEMU sources and is an external
project now, so this problem should not exist anymore with the latest
version of QEMU. If it still persists, please feel free to re-open this
ticket.
** Changed in: qemu
Status: New => Invalid
--
You received this bug not
Do you know what the DECAR SPR contains at that point in time? I guess
it's 0 ... but what does that mean here? Should the decrementer be
stopped?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1624896
** Tags added: ppc
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1624896
Title:
[PPC] SegFault due to Stack Overflow in E500
Status in QEMU:
New
Bug description:
I am getting a Segmentatio
Fix has been picked up into the repository now:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=344aa283b89bec2af9761
** 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.
https:
Closing according to comment #2.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1596009
Title:
config/build problem due to libncursesw on Xenial
S
The fix mentioned in comment #4 has been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=7e4e88656c1e6192e9e47
==> Setting status to "Fix released".
** Changed in: qemu
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of qemu
** Changed in: qemu
Status: Confirmed => 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/1589923
Title:
https websockets not working in 2.5 or 2.6
Status in QEMU:
Fix Released
Alll revisions are available in the git repository, so please simply do:
git clone git://git.qemu-project.org/qemu.git
cd qemu
git checkout 4fd811a6bd0b8f24f4761fc281454494c336d310
./configure ...
make -j4
And then check whether it is working or not.
Once you're done, switch to the other rev
The patch mentioned in comment #5 has been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=a4d1f142542935b90d2e
** 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.
http
Hi Luigi,
70f87e0f0aa04f764dabaeb3ed71ff195748076a is a merge commit ... that should not
have shown up as a result from bisecting.
Anyway, since it is pointing to a ui merge ... could you please:
1) check whether it is still working fine with the first patch of that ui
series, i.e.:
git chec
The referenced website is no longer available, thus setting this ticket
to INVALID. Please feel free to re-open it if the information is
available somewhere else and you can reproduce it with the latest
version of QEMU.
** Changed in: qemu
Status: New => Invalid
--
You received this bug n
Current QEMU 2.7 does not segfault here anymore, and the "thesecurity"
problem is also not available in the sources anymore ==> I think this
can be closed nowadays.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
deve
Looks like the ISO from comment #4 (thanks for attaching that one!)
shows the correct behavior with up to date QEMU 2.7. Also, the affected
softfloat code has been completely reworked in between (e.g. with commit
cf67c6bad56d43e6d60), so I assume this has been fixed sometimes in the
past years.
**
The following commit contains the patch that has been suggested in comment #1:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=33aa30cafcce053b83
... so this issue should be fixed in recent versions of QEMU.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notificat
Nigel, looking at https://www.freebsd.org/platforms/ppc.html it seems
like FreeBSD does not support the pseries machines yet, only some
flavours of PowerMac machines. So you should either use the "qemu-
system-ppc" binary (without the "64" suffix), or you've got to specify
one of the Mac machines,
Hi, is this still a problem with the latest version of QEMU? If yes,
please submit your keymap as a patch to the qemu-devel mailing list (see
http://qemu-project.org/Contribute/SubmitAPatch for details). Thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, whi
Closing according to comment #3
** 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.
https://bugs.launchpad.net/bugs/965327
Title:
virtio-pci: can't reserve io 0x-0x001f
Statu
Looks like this has been finally fixed by this commit here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=7f81dbb9a0e89b53
** 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.
https:
QEMU Wiki does not use e-mail addresses, so this is not a bug
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/789652
Title:
Cannot confirm email add
Closing bug according to comment #2
** 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.
https://bugs.launchpad.net/bugs/722311
Title:
Segmentation fault if started without -enable
Should be fixed according to the comments from blueswirl ==> setting
status to "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.
https://bugs.launchpad.net/bugs/8308
Seems like this problem has been fixed here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=249cdb420a3b68cf6
... so we can close this bug ticket now.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
Fixes should be part of QEMU v2.7.0, e.g.:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=014628a705bdaf31c09915
... so setting the status to "Fix Released" now.
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qem
Fix has been included in QEMU v2.7.0:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=bc35d51077b33e68a0
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1589923
Title:
https websockets not working in
Fix has been included in QEMU v2.7.0 --> changing status to Fix
Released.
** 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/1594239
Title
Fix has been included in QEMU v2.7.0:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=4d3fc4fdc6857e33346e
** 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.
https://bugs.launchpad.n
Fix has been included in QEMU v2.7.0:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=ea697449884d83b83fefb
** 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.
https://bugs.launchpad.
** 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/1589564
Title:
qemu/hw/scsi/scsi-disk.c:2741: possible missing break ?
Status in QEMU
** 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/1581796
Title:
console-gl.c:96:surface_gl_create_texture:code should not be reached
S
Patch has been included in QEMU v2.7.0:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=e0dadc1e9ef1f35208e5d2a
** 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.
https://bugs.launc
** 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/1577841
Title:
target-mips/helper.c:542: bad sizeof ?
Status in QEMU:
Fix Released
Fix has been included in QEMU v2.7.0:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=1f8b56e7cebc71d80a
** 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.lau
Closing this bug since the hardware is not available anymore (according
to comment #11).
** Changed in: qemu
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/241119
I think this is not a bug, but you are using the command line parameters
in a wrong way. When you use "-net user,hostfwd=tcp:127.0.0.1:1122-:22"
you are creating a *new*, second host network device which is not
connected to the guest NIC device that you specified. Please try to
avoid mixing "-net"
Please report this problem in the bug tracker of your Linux distribution
instead.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1348106
Title:
kvm
Looking at comment #1, it sounds like this has been fixed, so let's
close this ticket now.
** 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/
Patch had been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=8656954aedbd9995e68e
... so closing this ticket 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.
Patch had been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=fe3e7f2dc05225cdd2ba
... so I'm closing this ticket 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 QE
Patch had been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=cfeda5f4b8710b6ba14
So I think we can now mark this ticket as "Fix released".
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, whic
Marking this ticket as "Invalid" according to comment #2.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1192344
Title:
qemu crashes on unaligned e
Moving this to likewise-open according to comment #1.
** Project changed: qemu => likewise-open (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/873460
Title:
Likewise no sound
Status in li
Marking this ticket as "Fix released" according to comment #6.
** 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.
https://bugs.launchpad.net/bugs/1205156
Title:
Errors while comp
** Tags added: ppc
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1087411
Title:
pseries machine breaks in instalation of SLES11_SP2
Status in QEMU:
New
Bug description:
QEMU version: 1.0, 1.1
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1062201
Title:
qemu core dumped by kvm-spice
Status in QEMU:
Invalid
Status in qemu-kvm-spice pack
According to comment #3, this has been fixed, so let's change the bug
status accordingly.
** 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.
https://bugs.launchpad.net/bugs/581353
Commit c4c0e236beabb9de5ff mentioned in comment #5 has been included
long ago, so setting this ticket to "Fix released" now.
** 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
Commit ad1be89948f88e8 has been included long ago, so let's set this
ticket 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.
https://bugs.launchpad.net/bugs
The fix mentioned in comment #1 has been included long ago (commit ID
6d1acda8f16d1f2d0b05cf), so marking this ticket as "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 subscribe
** Project changed: qemu => qemu-kvm (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/939437
Title:
spice is not supported by this qemu build.(ubuntu 12.04)
Status in qemu-kvm package in Ubu
There is no QEMU version 11.x or 12.x, so I assume this ticket is rather
meant for the Ubuntu QEMU package
** Project changed: qemu => qemu-kvm (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/
Looks like this the key has been added by this commit here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=33aa30cafcce053b83
So I think we can close this bug ticket now.
** Changed in: qemu
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member o
Thanks for the update ... since it is working with the current version
of QEMU, I assume this problem has been fixed sometimes during the past
years, thus we can close this ticket now.
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you
** 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.
https://bugs.launchpad.net/bugs/1613133
Title:
SLIRP code regression fails to build on OpenBSD
Status in QEMU:
Fix Committed
Patch suggested here: http://patchwork.ozlabs.org/patch/659132/
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1613133
Title:
SLIRP code regression fails to build on OpenBSD
Status in QEMU:
New
Looks like Serge's fix has been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=efc8243d00ab4cf4fa05a9b
... so let's close this bug now.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
Peter's fix had been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=967c0da73a7b0da186baba6
... so I think we can close this bug ticket now.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, whi
As far as I can see, this should have been fixed in upstream QEMU by this
commit here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=8cb6bfb54e91b1a31a
... so closing this issue now.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a
According to Stefan, this problem has been fixed by this commit:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=cc4662f9642995c78
... so let's close this bug ticket now.
** Changed in: qemu
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of
Since there is no udev file in upstream QEMU, I guess this bug was meant
for the qemu Ubuntu package instead?
** 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/8
Based on comment #30, it sounds like the original problem of this bug
has been fixed, and since the remaining apic-related problem is tracked
in ticket #1395217 already, I think we can close this bug now (if you
don't agree, feel free to open this ticket again).
** Changed in: qemu
Status:
I can not reproduce this issue using -curses with the latest version of
qemu, so I guess this has been fixed somewhen during the last years ...
if nobody else can reproduce it, I think we should close this bug.
--
You received this bug notification because you are a member of qemu-
devel-ml, whic
Confirmed, this is indeed broken. I sent a patch with a fix to the mailing list:
https://marc.info/?i=1470900060-25821-1-git-send-email-thuth%40redhat.com
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which i
Looks like this issue has been fixed by this commit here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=4efeabbbe8441cc327052304
... so I think it should be OK to close this now.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a membe
A check for multicast MAC addresses has been introduced by this commit here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=d60b20cf2ae6644b051
So I think we can close this ticket now.
** Changed in: qemu
Status: Confirmed => Fix Released
--
You received this bug notification because you
If git bisect says something about "XX revisions left to test after this" then
you're not done yet, you have to continue the git bisecting process until it is
finished.
And if you need the sdl2 patch additionally, you have to apply it manually
after each step if necessary. I'm sorry, it's quite
Please send your patch to the qemu-devel (and qemu-block) mailing list.
See http://qemu-project.org/Contribute/SubmitAPatch for details on how
to submit a patch. Thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.lau
You initially have to specify a commit that is known to fail, and one that is
known to work, so in this case it's likely:
git bisect start master v2.6.0
It then checks out a revision inbetween. Compile it with "make" and run the
built QEMU to check whether it is working or not.
If it is not work
Can you use "git bisect" to determine the exact commit that causes this
problem to appear?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1603636
Title:
Guest has not initialized the display yet on
According to comment #8 the fixes have been included in the upstream
QEMU repository, so setting the status to "Fix released" now.
** Changed in: qemu
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed
Has this bug been fixed by this commit here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=1645b8eee558ffe2389
?
If so, I think we could now close this bug ticket...
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launch
Patch has been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=63ba17d39f1a8d262b31e
... so I think it's OK to close this bug now.
** Changed in: qemu
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which
Patch has been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=8689907266b649b757c220
... so I think it should be OK to close this bug ticket now.
** Changed in: qemu
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of qemu-
1 - 100 of 206 matches
Mail list logo
