Bisected merrily away, and this is where it definitively begins to fail
. . . To verify, I checked out both commits, and confirmed change in
function at this point. I attempted a revoke of this commit on my clone
to test, but too many merge errors to make that a simple task, so that
was not done.
This does not appear to be run-time selectable (or I have not found the
option yet . . . ) so not quire sure how to verify if backing this out
will resolve the issue in later versions.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Additional test (I just don't know when to go to bed . . . *sigh* . . .
).
In a checkout of the 2.1.2 code base, and based on the above failing
commit as per bisect, I removed the change in the commit for
target-i386/cpu.c of the line:
[FEAT_1_ECX] = CPUID_EXT_X1APIC,
as added by the errant
Broadwell - Fails, Host won't support it:
warning: host doesn't support requested feature: CPUID.01H:ECX.fma [bit 12]
warning: host doesn't support requested feature: CPUID.01H:ECX.movbe [bit 22]
warning: host doesn't support requested feature: CPUID.07H:EBX.fsgsbase [bit 0]
warning: host doesn't
(Wow . . . that last was incredibly redundant . . . staying up most of
the night working on this has apparently left me a bit stupid this
morning/afternoon . . . sorry!)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Note that this Illumos image is certified/runs cleanly on Intel hardware
from the last 5 years when natively on it. I doubt that it is a kernel
problem with Illumos with regard to the actual CPU architecture. Older
releases that are OpenSolaris based also see the problem.
Generally speaking, I
Much appreciated! Please let me know if there is anything else I can do
to help this bug progress . . . .
- Tim
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1395217
Title:
Networking in qemu
Paolo - I should have some time to do that this week, as well as bone up
on git (it's been a bit . . .)
And thanks for the quick reply!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1395217
Title:
** Attachment added: Wireshark pcap format packet dump of 2.1.2 failing to
come up successfully
https://bugs.launchpad.net/qemu/+bug/1395217/+attachment/4265387/+files/WS_pcap_2.1.2
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
Host platform is Slackware 14.1, x86_64 . . . cc 4.8.2, kernel 3.10.17
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1395217
Title:
Networking in qemu 2.0.0 and beyond is not compatible with Open
Note that the host system, network config, etc. are identical, qemu is
built with an identical config, and started with the same command - the
*ONLY* variable is the qemu version. This is utilizing the bridge-
helper binary, but as noted earlier, using virt-manager whether allowing
it to define
Public bug reported:
The networking code in qemu in versions 2.0.0 and beyond is non-
functional with Solaris/Illumos 5.11 images.
Building 1.7.1, 2.0.0, 2.0.2, 2.1.2,and 2.2.0rc1with the following
standard Slackware config:
# From Slackware build tree . . .
./configure \
--prefix=/usr \
Folks -
I have been having a problem getting a usable qemu-2.0.0 (or 1.7.1, or
current GIT for that matter) build under slackware 14.1. For some
reason, the inter-thread communication hangs when built on this OS
distro, and display hangs in virt-manager as well as the gtk display in
qemu,
13 matches
Mail list logo
