Hans de Bruin wrote:
Avi Kivity wrote:
Oliver Rath wrote:
Hi List,
maybe i missed some announcements, but
git clone git://git.kernel.org/pub/scm/virt/kvm/kvm-userspace.git
givs no response:
kvm-userspace # git clone
git://git.kernel.org/pub/scm/virt/kvm/kvm-userspace.git
Initialized
The related MSRs are emulated. MCE capability is exported via
extension KVM_CAP_MCE and ioctl KVM_X86_GET_MCE_CAP_SUPPORTED. A new
vcpu ioctl command KVM_X86_SETUP_MCE is used to setup MCE emulation
such as the mcg_cap. MCE is injected via vcpu ioctl command
KVM_X86_SET_MCE. Extended
- MCE features are initialized when VCPU is intialized according to CPUID.
- A monitor command mce is added to inject a MCE.
- A new interrupt mask: CPU_INTERRUPT_MCE is added to inject the MCE.
Signed-off-by: Huang Ying ying.hu...@intel.com
---
cpu-all.h |4 ++
cpu-exec.c
KVM ioctls are used to initialize MCE simulation and inject MCE. The
real MCE simulation is implemented in Linux kernel.
ChangeLog:
v3:
- Re-based on qemu/tcg MCE support patch
v2:
- Use new kernel MCE capability exportion interface.
Signed-off-by: Huang Ying ying.hu...@intel.com
---
Anthony Liguori schrieb:
Sorry this explanation is long winded, but this is a messy situation.
In Linux, there isn't a very consistent policy about userspace kernel
header inclusion. On a typical Linux system, you're likely to find
kernel headers in three places.
glibc headers
On Sun, 2009-05-03 at 22:28 -0700, Nicholas A. Bellinger wrote:
On Mon, 2009-05-04 at 10:09 +0800, Sheng Yang wrote:
Greetings Sheng,
So, I have been trying the latest kvm-85 release on a v2.6.30-rc3
checkout from linux-2.6.git on a CentOS 5u3 x86_64 install on Intel
IOH-5520
Avi Kivity a...@redhat.com wrote:
Hi
diff --git a/kvm-all.c b/kvm-all.c
index 36659a9..1642a2a 100644
--- a/kvm-all.c
+++ b/kvm-all.c
@@ -64,6 +64,30 @@ struct KVMState
static KVMState *kvm_state;
+int kvm_check_extension(int extension)
+{
+int ret;
+
+ret =
On Mon, May 04, 2009 at 09:40:03AM +0300, Avi Kivity wrote:
Hans de Bruin wrote:
Avi Kivity wrote:
kvm-userspace.git has been retired; it's now playing golf in
git://git.kernel.org/pub/scm/virt/kvm/retired/kvm-userspace.git. Use
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git instead.
Anthony Liguori wrote:
Sorry this explanation is long winded, but this is a messy situation.
In Linux, there isn't a very consistent policy about userspace kernel
header inclusion. On a typical Linux system, you're likely to find
kernel headers in three places.
glibc headers
Carlo Marcelo Arenas Belon wrote:
On Mon, May 04, 2009 at 09:40:03AM +0300, Avi Kivity wrote:
Hans de Bruin wrote:
Avi Kivity wrote:
kvm-userspace.git has been retired; it's now playing golf in
git://git.kernel.org/pub/scm/virt/kvm/retired/kvm-userspace.git. Use
Avi Kivity wrote:
Carlo Marcelo Arenas Belon wrote:
On Mon, May 04, 2009 at 09:40:03AM +0300, Avi Kivity wrote:
Hans de Bruin wrote:
Avi Kivity wrote:
kvm-userspace.git has been retired; it's now playing golf in
git://git.kernel.org/pub/scm/virt/kvm/retired/kvm-userspace.git.
Jes Sorensen wrote:
Zhang, Xiantao wrote:
Jes Sorensen wrote:
I still can't see the difference with the patch in Avi's tree except
nvram stuff. And I believe the global variable you mentioned should
be only used for nvram. So I propose an incremental patch for that. :)
Hi,
Here is an
Bugs item #2786468, was opened at 2009-05-04 10:18
Message generated for change (Tracker Item Submitted) made by kubrick_fr
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2786468group_id=180599
Please note that this message will contain a full copy of the
On Monday 04 May 2009 12:36:04 Nicholas A. Bellinger wrote:
On Mon, 2009-05-04 at 10:09 +0800, Sheng Yang wrote:
On Monday 04 May 2009 08:53:07 Nicholas A. Bellinger wrote:
On Sat, 2009-05-02 at 18:22 +0800, Sheng Yang wrote:
On Thu, Apr 30, 2009 at 01:22:54PM -0700, Nicholas A.
On Mon, May 04, 2009 at 08:51:21AM +0200, Stefan Weil wrote:
Anthony Liguori schrieb:
Sorry this explanation is long winded, but this is a messy situation.
In Linux, there isn't a very consistent policy about userspace kernel
header inclusion. On a typical Linux system, you're likely to
Sheng Yang wrote:
Disable interrupt at interrupt handler and enable it when guest ack is for
the level triggered interrupt, to prevent reinjected interrupt. MSI/MSI-X don't
need it.
One possible problem is multiply same vector interrupt injected between irq
handler and scheduled work handler
Glauber Costa wrote:
Appearently nobody turned this on in a while...
setting apic_debug to something compilable, generates
some errors. This patch fixes it.
Applied, thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
--
To unsubscribe from this
On Monday 04 May 2009 16:25:55 Avi Kivity wrote:
Sheng Yang wrote:
Disable interrupt at interrupt handler and enable it when guest ack is
for the level triggered interrupt, to prevent reinjected interrupt.
MSI/MSI-X don't need it.
One possible problem is multiply same vector interrupt
Glauber Costa wrote:
As soon as we call kvm_init_vcpu(), we start the vcpu thread.
However, there is still things that has to be done, as soon
as the new CPUState is created. Examples include initializing the
apic, halting the cpu, etc.
Without this patch, it is possible that the cpu may want
On Mon, May 04, 2009 at 11:14:58AM +0300, Avi Kivity wrote:
Avi Kivity wrote:
Carlo Marcelo Arenas Belon wrote:
On Mon, May 04, 2009 at 09:40:03AM +0300, Avi Kivity wrote:
Hans de Bruin wrote:
Avi Kivity wrote:
kvm-userspace.git has been retired; it's now playing golf in
Glauber Costa wrote:
KVM will 24-shift bits in addr 0x20 (APIC_ID) before actually
using it. We currently load phys_id as s-id. After shifted
by 24 bits, it will result in a meaningless value. We should really
be doing s-id 24, which, after shifted, will lead to the correct
value.
This is for
Sheng Yang wrote:
On Monday 04 May 2009 16:25:55 Avi Kivity wrote:
Sheng Yang wrote:
Disable interrupt at interrupt handler and enable it when guest ack is
for the level triggered interrupt, to prevent reinjected interrupt.
MSI/MSI-X don't need it.
One possible problem is multiply
On Monday 04 May 2009 16:34:00 Avi Kivity wrote:
Sheng Yang wrote:
On Monday 04 May 2009 16:25:55 Avi Kivity wrote:
Sheng Yang wrote:
Disable interrupt at interrupt handler and enable it when guest ack is
for the level triggered interrupt, to prevent reinjected interrupt.
MSI/MSI-X
Jes Sorensen wrote:
Avi Kivity wrote:
Currently, use TARGET_I386 to comment out the mapping machanism
for other archs, but mapping machanism should be useful for other archs
to maintain guest's memory mapping.
Hollis, does this work for you?
If now, you can add a new define KVM_WANT_MAPPING
Jes Sorensen wrote:
Zhang, Xiantao wrote:
Hi, Jes
There should be no issue here. You may refer to
qemu-kvm/kvm/kernel/arch/x86/include/asm/kvm.h, and it also includes
this stuff. I remebered this stuff was used to solve the issues when
uses kernel header files in userspace and the
Anthony Liguori wrote:
Sorry this explanation is long winded, but this is a messy situation.
In Linux, there isn't a very consistent policy about userspace kernel
header inclusion. On a typical Linux system, you're likely to find
kernel headers in three places.
glibc headers
Michael S. Tsirkin wrote:
So what I see is transports providing something like:
struct virtio_interrupt_mapping {
int virtqueue;
int interrupt;
};
map_vqs_to_interrupt(dev, struct virtio_interrupt_mapping *, int nvirtqueues);
unmap_vqs(dev);
Isn't that the same
Avi Kivity wrote:
Jes Sorensen wrote:
+int destroy_region_works = 0;
Global name, prefix with kvm_. Does it actually need to be global?
Gone, now local to qemu-kvm-x86.c. I moved the initializer into
kvm_arch_create_context() instead.
The header depends on target_phys_addr_t, so it must
Andre Przywara wrote:
AMDs VMCB does not have an explicit unusable segment descriptor field,
so we emulate it by using not present. This has to be setup before
the fixups, because this field is used there.
Applied both, thanks.
--
Do not meddle in the internals of kernels, for they are
On Monday 04 May 2009 17:11:59 Nicholas A. Bellinger wrote:
On Mon, 2009-05-04 at 16:20 +0800, Sheng Yang wrote:
On Monday 04 May 2009 12:36:04 Nicholas A. Bellinger wrote:
On Mon, 2009-05-04 at 10:09 +0800, Sheng Yang wrote:
On Monday 04 May 2009 08:53:07 Nicholas A. Bellinger wrote:
Avi Kivity wrote:
Avi Kivity wrote:
This is the one implementing the KVM_WANT_MAPPING change.
There is in fact a call to drop_mapping() outside any #ifdef (in
kvm_cpu_register_physical_memory()). I'm confused... maybe we should
make this code unconditional.
Hi Avi,
I don't follow this -
Michael S. Tsirkin wrote:
kvm-common.h:25:7: warning: __ia64__ is not defined
Went in by another route.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to
Michael S. Tsirkin wrote:
make 'clean' target propage into libkvm if it's enabled
Applied, thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to
Michael S. Tsirkin wrote:
libkvm-x86.c:55: warning: no previous prototype for ‘kvm_create_pit’
Applied, thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message
Avi Kivity wrote:
Jes Sorensen wrote:
Avi Kivity wrote:
Hollis, does this work for you?
If now, you can add a new define KVM_WANT_MAPPING or something, and
define it for I386 and IA64.
Hi,
This is the one implementing the KVM_WANT_MAPPING change.
Cheers,
Jes
There is in fact a call
Michael S. Tsirkin wrote:
CONFIG_KVM_TRACE in kernel conflicts with the definition
in external module. external-module-compat-comm.h tried
to work around this, but this didn't work as some
code still does #include linux/autoconf.h
directly.
Solve this differently by
On Mon, 2009-05-04 at 17:49 +0800, Sheng Yang wrote:
On Monday 04 May 2009 17:11:59 Nicholas A. Bellinger wrote:
On Mon, 2009-05-04 at 16:20 +0800, Sheng Yang wrote:
On Monday 04 May 2009 12:36:04 Nicholas A. Bellinger wrote:
On Mon, 2009-05-04 at 10:09 +0800, Sheng Yang wrote:
On
On Mon, 27 Apr 2009 10:01:53 pm Michael S. Tsirkin wrote:
This adds 2 new optional virtio operations: request_vqs/free_vqs. They will be
used for MSI support, because MSI needs to know the total number of vectors
upfront.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
Hi Michael,
On Mon, May 04, 2009 at 09:02:20PM +0930, Rusty Russell wrote:
On Mon, 27 Apr 2009 10:01:53 pm Michael S. Tsirkin wrote:
This adds 2 new optional virtio operations: request_vqs/free_vqs. They will
be
used for MSI support, because MSI needs to know the total number of vectors
upfront.
On Sunday 03 May 2009, Anthony Liguori wrote:
A classic example is linux/compiler.h and the broken usbdevice_fs.h
header that depends on it. There are still distributions today that
QEMU doesn't compile on because of this.
Can you clarify this? I can't find any version of usbdevice_fs.h that
Jan Kiszka wrote:
The stats entry request_nmi is no longer used as the related user space
interface was dropped. So clean it up.
Applied, thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
--
To unsubscribe from this list: send the line
On Monday 04 May 2009, Mark McLoughlin wrote:
Right, but if you e.g. try to build a newer qemu-kvm on F10, you
currently need newer kvm kernel headers - IMHO, we should use #ifdef to
allow newer qemu-kvm build with older kvm headers.
I think the kvm and virtio headers should just be shipped
Stefan Weil wrote:
Anthony Liguori schrieb:
For Debian systems, those headers are installed by package linux-libc-dev.
There are also packages for cross compilation in emdebian
(linux-libc-dev-mips-cross, linux-libc-dev-powerpc-cross, ...).
Yes, those headers did not always match the
Arnd Bergmann wrote:
On Monday 04 May 2009, Mark McLoughlin wrote:
Right, but if you e.g. try to build a newer qemu-kvm on F10, you
currently need newer kvm kernel headers - IMHO, we should use #ifdef to
allow newer qemu-kvm build with older kvm headers.
I think the kvm and virtio
Avi Kivity wrote:
At least on Fedora, kernel-headers is. It is installed in
/usr/include/linux and is synced (sorta) to the installed kernel.
It's not the case with Ubuntu.
Carrying a subset of kernel headers is a bit too much, IMO.
Carrying virtio, kvm, and if_tun would be sufficient
Anthony Liguori wrote:
I don't see the need to copy all the core headers. These should have
been working for ages, and hardly ever see changes that are relevant
to kvm.
If we want to use virtio_*.h instead of duplicating the copies as we
are now, then we need all of the core headers
On Mon, May 04, 2009 at 08:13:16AM -0500, Anthony Liguori wrote:
The fact is, linux-libc-dev is *not* meant for applications to use as
the official kernel ABI. We shouldn't depend on it.
Umm, it is. That's exactly the reason what it is for. Note that the
name of the package varies depending
On Mon, May 04, 2009 at 04:38:12PM +0300, Avi Kivity wrote:
qemu provides virtio, it doesn't consume it. We can merge the virtio
headers and remove the linuxisms.
Yeah. virtio is a one the (virtual) wire protocol, not a kernel ABI in
the tradition sense. qemu should have it's own defintion.
Hello everyone,
I like to resubmit patch to add support for remote migration in
kvm-autotest, based on Michael Goldish's suggestions.
To use this patch the following seven parameters should be added to the
existing migration test
remote_dst = yes
hostip = localhost ip or name
On Mon, May 04, 2009 at 11:30:58AM +0300, Avi Kivity wrote:
Glauber Costa wrote:
As soon as we call kvm_init_vcpu(), we start the vcpu thread.
However, there is still things that has to be done, as soon
as the new CPUState is created. Examples include initializing the
apic, halting the cpu,
On Mon, May 04, 2009 at 08:13:16AM -0500, Anthony Liguori wrote:
We can not just rely on everyone who uses QEMU to use the latest version
of Debian...
The fact is, linux-libc-dev is *not* meant for applications to use as
the official kernel ABI. We shouldn't depend on it.
Actually I
On Mon, May 04, 2009 at 05:33:26PM +0300, Avi Kivity wrote:
Glauber Costa wrote:
I'd like to avoid vcpu ioctls from more than one thread, in case we
ever move to a syscall implementation.
Although I don't see exactly what's your point in here.
We're just adding a serialization points
Hey,
I am comparing Xen and KVM to see which one is suitable for me usage.
From the FAQ:
http://www.linux-kvm.org/page/FAQ#What_is_the_difference_between_kvm_and_Xen.3F
It said:
kvm does not support paravirtualization for cpu but may support
paravirtualization for device drivers to
On Mon, May 4, 2009 at 9:49 AM, howard chen howac...@gmail.com wrote:
On Mon, May 4, 2009 at 10:44 PM, Pasi Kärkkäinen pa...@iki.fi wrote:
On Mon, May 04, 2009 at 10:40:00PM +0800, howard chen wrote:
Yes, paravirtualization is good. If running KVM, use paravirtualized network
and disk/block
Anthony Liguori wrote:
Thinking again about it, this is not really necessary.
In general a distro provides kernel headers matched to the running
kernel. For example F10 provides
kernel-headers-2.6.27.21-170.2.56.fc10.x86_64 to go along with
kernel-2.6.27.21-170.2.56.fc10.x86_64. So a user
On Mon, May 4, 2009 at 10:44 PM, Pasi Kärkkäinen pa...@iki.fi wrote:
On Mon, May 04, 2009 at 10:40:00PM +0800, howard chen wrote:
Yes, paravirtualization is good. If running KVM, use paravirtualized network
and disk/block drivers for better performance.
So does it mean generally Xen is more
On Mon, May 04, 2009 at 08:15:58AM -0500, Anthony Liguori wrote:
Edgar E. Iglesias wrote:
I don't feel very strongly about it but my gut feeling tells me we
shouldn't be doing this.
We have to. It's not just KVM, it's virtio, tun/tap, and as we add more
things to the Linux kernel to
I think this is a known problem in qemu mentioned here on qemu-devel
http://article.gmane.org/gmane.comp.emulators.qemu/42321
Ok, it is fixed in the latest qemu git code.
- Dietmar
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to
On Mon, May 4, 2009 at 11:49 AM, howard chen howac...@gmail.com wrote:
On Mon, May 4, 2009 at 10:44 PM, Pasi Kärkkäinen pa...@iki.fi wrote:
On Mon, May 04, 2009 at 10:40:00PM +0800, howard chen wrote:
Yes, paravirtualization is good. If running KVM, use paravirtualized network
and disk/block
Arnd Bergmann wrote:
On Sunday 03 May 2009, Anthony Liguori wrote:
A classic example is linux/compiler.h and the broken usbdevice_fs.h
header that depends on it. There are still distributions today that
QEMU doesn't compile on because of this.
Can you clarify this? I can't find any
Glauber Costa wrote:
On Mon, May 04, 2009 at 05:33:26PM +0300, Avi Kivity wrote:
Glauber Costa wrote:
I'd like to avoid vcpu ioctls from more than one thread, in case we
ever move to a syscall implementation.
Although I don't see exactly what's your point in here.
We're
Mark McLoughlin wrote:
On Mon, 2009-05-04 at 12:08 +0300, Avi Kivity wrote:
In general a distro provides kernel headers matched to the running
kernel. For example F10 provides
kernel-headers-2.6.27.21-170.2.56.fc10.x86_64 to go along with
kernel-2.6.27.21-170.2.56.fc10.x86_64. So a user
On Mon, 2009-05-04 at 16:48 +0300, Avi Kivity wrote:
Cristi Magherusan wrote:
Hello,
Which is the maximum size supported for a custom BIOS image(eg.
coreboot-based)? I tried some 256K coreboot BIOS images and seemed to
work fine, but it blowed up with a 3MB image (which by the way
Edgar E. Iglesias wrote:
I don't feel very strongly about it but my gut feeling tells me we
shouldn't be doing this.
We have to. It's not just KVM, it's virtio, tun/tap, and as we add more
things to the Linux kernel to support QEMU, it'll just grow larger.
This is how applications are
Cristi Magherusan wrote:
Hello,
Which is the maximum size supported for a custom BIOS image(eg.
coreboot-based)? I tried some 256K coreboot BIOS images and seemed to
work fine, but it blowed up with a 3MB image (which by the way works on
qemu just fine).
256K is the maximum with kvm. It
Glauber Costa wrote:
I'd like to avoid vcpu ioctls from more than one thread, in case we ever
move to a syscall implementation.
Although I don't see exactly what's your point in here.
We're just adding a serialization points through pthreads function, not doing
any ioctl from
the
Anthony Liguori wrote:
Stefan Weil wrote:
Anthony Liguori schrieb:
For Debian systems, those headers are installed by package
linux-libc-dev.
There are also packages for cross compilation in emdebian
(linux-libc-dev-mips-cross, linux-libc-dev-powerpc-cross, ...).
Yes, those headers did not
Avi Kivity wrote:
Anthony Liguori wrote:
Comments?
Thinking again about it, this is not really necessary.
In general a distro provides kernel headers matched to the running
kernel. For example F10 provides
kernel-headers-2.6.27.21-170.2.56.fc10.x86_64 to go along with
On Mon, May 04, 2009 at 10:40:00PM +0800, howard chen wrote:
Hey,
I am comparing Xen and KVM to see which one is suitable for me usage.
From the FAQ:
http://www.linux-kvm.org/page/FAQ#What_is_the_difference_between_kvm_and_Xen.3F
It said:
kvm does not support paravirtualization
Avi Kivity wrote:
random kernel tree
Developers, in particular, like to point things at their random
kernel trees. In general though, relying on a full kernel source
tree being available isn't a good idea. Kernel headers change
dramatically across versions too so it's very likely that we
- paravirtualized drivers widely available both for Linux and Windows
(Xen's drivers on windows can be hard and/or expensive to get)
Well, Xen has GPL PV drivers for windows (at least for networking)
which KVM doesn't have. There is a promise
but no date attached to it.
If a set of drivers
Hello Jan,
thank you very much for processing my request.
I [1]patched the KVM sources from Lenny and created a new Debian packet.
When I boot the VM from the Lenny CD, there is no audible signal tone.
It does not make a difference whether I start the KVM with or without
the option
Hi,
I've rewritten the x86(-64) instruction decoder with instruction
attribute table and a generator according to Peter's comments.
Currently, an opcode map file (x86-opcode-map.txt) is based on opcode
maps in Intel(R) Software Developers Manual Vol.2: Appendix.A, and it
contains below two types
When i moved to the latest qemu-kvm git tree from kvm-85, i noticed that
networking stopped working between the host and the guest.
It started working when i put the device in promiscuos mode by running
tcpdump in background on the guest.
After browsing through the recent patches, i found that
On Mon, 2009-05-04 at 09:39 +0800, Zhang, Xiantao wrote:
Could you explain why this patch breaks the powerpc build?
qemu_sync_icache has the definition for non-ai64 case, so shoudn't
break any arch-specific build.
cutils.o: In function `qemu_iovec_from_buffer':
On Mon, 2009-05-04 at 09:50 -0700, Sridhar Samudrala wrote:
When i moved to the latest qemu-kvm git tree from kvm-85, i noticed that
networking stopped working between the host and the guest.
It started working when i put the device in promiscuos mode by running
tcpdump in background on the
(Applies to kvm.git:7da2e3ba, plus you will also need Davide Libenzi's
eventfd_file_create() patch, which you can find here:
http://www.mail-archive.com/kvm@vger.kernel.org/msg13923.html
You can find my complete tree with kvm.git, Davide's patch, and this series
here:
We will re-use eventfd for implmenting irqfd later in the series, and the
irqfd users will potentially live in modules.
Signed-off-by: Gregory Haskins ghask...@novell.com
---
fs/eventfd.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/fs/eventfd.c b/fs/eventfd.c
KVM provides a complete virtual system environment for guests, including
support for injecting interrupts modeled after the real exception/interrupt
facilities present on the native platform (such as the IDT on x86).
Virtual interrupts can come from a variety of sources (emulated devices,
(Applies to kvm.git:7da2e3ba, plus you will also need Davide Libenzi's
eventfd_file_create() patch, which you can find here:
http://www.mail-archive.com/kvm@vger.kernel.org/msg13923.html
You can find my complete tree with kvm.git, Davide's patch, and this series
here:
KVM provides a complete virtual system environment for guests, including
support for injecting interrupts modeled after the real exception/interrupt
facilities present on the native platform (such as the IDT on x86).
Virtual interrupts can come from a variety of sources (emulated devices,
We will re-use eventfd for implmenting irqfd later in the series, and the
irqfd users will potentially live in modules.
Signed-off-by: Gregory Haskins ghask...@novell.com
---
fs/eventfd.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/fs/eventfd.c b/fs/eventfd.c
Gregory Haskins wrote:
(Applies to kvm.git:7da2e3ba, plus you will also need Davide Libenzi's
eventfd_file_create() patch, which you can find here:
[ snip ]
Sorry about the double post of v4. The first time through I
fat-fingered Al's and LKML's addresses so they were munged together. I
Gregory Haskins wrote:
(Applies to kvm.git:7da2e3ba, plus you will also need Davide Libenzi's
eventfd_file_create() patch, which you can find here:
[snip]
I should also add that v4 is build-tested only. I am in the middle of
refactoring virtual-bus, which is my only current test-harness
Hi Avi,
Avi Kivity wrote:
Erik Rull wrote:
The file system is the guest's business. Instead of '-hda /dev/hda2', try
-drive file=/dev/hda2,cache=none
great!
cache=off worked - none caused an error.
The Timing problem is still present but the XP system is now much more
interactive during
Hi Avi,
Avi Kivity wrote:
Erik Rull wrote:
The file system is the guest's business. Instead of '-hda /dev/hda2', try
-drive file=/dev/hda2,cache=none
great!
cache=off worked - none caused an error.
The Timing problem is still present but the XP system is now much more
interactive during
Thanks for the new patch. I'll comment on it later because I want to take some
more time to review it.
The login prompt problem is my fault -- please see my comment below.
- yogi anant...@linux.vnet.ibm.com wrote:
Hello everyone,
I like to resubmit patch to add support for remote
Simon Bienlein wrote:
Hello Jan,
thank you very much for processing my request.
I [1]patched the KVM sources from Lenny and created a new Debian packet.
Did you patch both kernel and user space? Note that my kernel patch was
against the kernel git repository, not against the external modules
Samuel Thibault wrote:
Jan Kiszka, le Mon 04 May 2009 22:29:39 +0200, a écrit :
When I boot the VM from the Lenny CD, there is no audible signal tone.
Hmm, I successfully tested with '-soundbw pcspk' + my patches or
-no-kvm-pit. There is probably a different, unrelated issue with your setup.
Avi Kivity wrote:
Jan Kiszka wrote:
I'm getting closer to a working qemu-kvm, but there are still a few
messy parts. The magic dance goes like this:
cd qemu-kvm/kvm
ln -s .. qemu(or apply patch below)
./configure -whatever
make
Still, this is unintuitive. As both top-level
These patches resolve the irq0-inti2 override issue, and get the hpet working
on kvm.
Override and HPET changes are sent as a series because HPET depends on the
override. Win2k8 expects the HPET interrupt on inti2, regardless of whether
an override exists in the BIOS. And the HPET spec states
Signed-off-by: Beth Kon e...@us.ibm.com
diff --git a/hw/fw_cfg.c b/hw/fw_cfg.c
index e1b19d7..bb74f38 100644
--- a/hw/fw_cfg.c
+++ b/hw/fw_cfg.c
@@ -279,6 +279,7 @@ void *fw_cfg_init(uint32_t ctl_port, uint32_t data_port,
fw_cfg_add_bytes(s, FW_CFG_UUID, qemu_uuid, 16);
Signed-off-by: Beth Kon e...@us.ibm.com
diff --git a/kvm/bios/acpi-dsdt.dsl b/kvm/bios/acpi-dsdt.dsl
index c756fed..0e142be 100755
--- a/kvm/bios/acpi-dsdt.dsl
+++ b/kvm/bios/acpi-dsdt.dsl
@@ -308,7 +308,6 @@ DefinitionBlock (
})
}
#ifdef BX_QEMU
-#ifdef HPET_WORKS_IN_KVM
Signed-off-by: Beth Kon e...@us.ibm.com
diff --git a/hw/hpet.c b/hw/hpet.c
index c7945ec..47c9f89 100644
--- a/hw/hpet.c
+++ b/hw/hpet.c
@@ -30,6 +30,7 @@
#include console.h
#include qemu-timer.h
#include hpet_emul.h
+#include qemu-kvm.h
//#define HPET_DEBUG
#ifdef HPET_DEBUG
@@ -48,6
Jan Kiszka, le Mon 04 May 2009 22:29:39 +0200, a écrit :
When I boot the VM from the Lenny CD, there is no audible signal tone.
Hmm, I successfully tested with '-soundbw pcspk' + my patches or
-no-kvm-pit. There is probably a different, unrelated issue with your setup.
Remember that the
On Sat, 2009-05-02 at 10:52 +0300, Avi Kivity wrote:
Hollis Blanchard wrote:
In that case it's sufficient to have the build system use the upstream
kvm integration (CONFIG_KVM) rather than the qemu-kvm integration
(USE_KVM).
OK, I give up... how is this supposed to work? Nobody
On Mon, 2009-05-04 at 11:25 +0200, Jes Sorensen wrote:
Avi Kivity wrote:
Jes Sorensen wrote:
+int destroy_region_works = 0;
Global name, prefix with kvm_. Does it actually need to be global?
Gone, now local to qemu-kvm-x86.c. I moved the initializer into
kvm_arch_create_context()
On Mon, May 04, 2009 at 01:57:45PM -0400, Gregory Haskins wrote:
@@ -56,6 +57,7 @@ int eventfd_signal(struct file *file, int n)
return n;
}
+EXPORT_SYMBOL_GPL(eventfd_signal);
perhaps, but...
@@ -197,6 +199,7 @@ struct file *eventfd_fget(int fd)
return file;
}
Justin,
On Sun, May 03, 2009 at 11:40:47AM -0700, Justin Dossey wrote:
Hi all,
I have a pretty straightforward setup.
Hypervisor:
dual xeon e5205 running Gentoo Linux
kernel 2.6.27 with virtio devices enabled
kvm 84
libvirt 0.5.1
Guest:
32-bit, virtio for nic and disk, qcow2.
Hi,
The VF also works in the host if the VF driver is programed properly.
So it would be easier to develop the VF driver in the host and then
verify the VF driver in the guest.
BTW, I didn't see the SR-IOV is enabled in your dmesg, did you select
the CONFIG_PCI_IOV in the kernel .config?
1 - 100 of 108 matches
Mail list logo
