#17
I have the same situtaion
when I use cpu line as "-cpu qemu64,-x2apic" the network still doesn't work.
maybe there is another way to remove x2apic,but I don't get it.
for the arp ,as you say ,there is not MAC.
Have you solve the problem ?
host: ubuntu 14.04
qemu img:openindiana 5.11
I fixed this by adding the configuration in the xml configuration file:
SandyBridge
See also attachement
(https://bugzilla.redhat.com/attachment.cgi?id=1072357) of bug
https://bugzilla.redhat.com/show_bug.cgi?id=1262093.
Note that I tested with Solaris 10, not openindiana 5.11
On
See the following bug report for a working Solaris 10 KVM guest configuration:
https://bugzilla.redhat.com/show_bug.cgi?id=1262093
** Bug watch added: Red Hat Bugzilla #1262093
https://bugzilla.redhat.com/show_bug.cgi?id=1262093
--
You received this bug notification because you are a member
See also bug #638955
--
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
Solaris (Illumos) 5.11
Status in QEMU:
New
Hello to all, I confirm this bug in qemu.
12 different Linux versions/distributions and 1 Windows 7 VM are running fine
without any networking issue.
Solaris 5.11 Version 11.2 can be installed (text version) and is running but
network is broken.
DHCPOFFER will not be received by Solaris 5.11
FWIW there's some other hits on this:
Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=1040500
Openstack mailing list:
http://lists.openstack.org/pipermail/openstack-dev/2014-December/053478.html
** Bug watch added: Red Hat Bugzilla #1040500
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
Tim Dawson tadaw...@tpcsvc.com writes:
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] =
It is runtime selectable using -cpu ...,-x2apic (as indicated by
Markus on qemu-devel).
First thing we need to find out is if it fails on the newest CPU model
that can be run in enforce mode.
So, assuming you are running on an Intel host CPU, it would be
interesting to test those CPU models in
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
So, if it breaks even with -cpu SandyBridge and -cpu host, it is likely
to be a KVM or QEMU bug. Thanks for the testing!
--
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
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:
Can you try bisecting between 1.7 and 2.0 with git?
--
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
Solaris (Illumos)
** 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
21 matches
Mail list logo
