Hi Anthony,
I found a bug in the last code: send_command() failed to copy back the
result into extboot_cmd structure. This patch fixes it.
I succesfully tested this version with guest Win2K (fully updated,
scsi boot) and Linux 2.6.25-rc8 (virtio).
Let me know if you can boot Windows with this ve
> That's it. If anyone can attest to this procedures and report, it would
> be greatly appreciated.
I did try to do so But I do get an "disk read error".
kvm is invoked via
qemu-system-x86_64 \
-m 768 \
-drive file=Vista.img,if=scsi,bus=0,index=0,media=disk,boot=on \
Discover new ways to grow your man device http://www.bugehaej.com/
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code
Anthony Liguori wrote:
>>
>> What about aio completions? The only race-free way to handle both
>> posix aio completion and fd readiness is signals AFAIK.
>
> We poll aio completion after the select don't we? Worst case scenario
> we miss a signal and wait to poll after the next select event. T
David S. Ahern wrote:
> I have been looking at RHEL3 based guests lately, and to say the least the
> performance is horrible. Rather than write a long tome on what I've done and
> observed, I'd like to find out if anyone has some insights or known problem
> areas running 2.4 guests. The short of it
Hi All,
This is today's KVM test result against kvm.git
8d3a833dc9d42f0967e57717f89c518375d6a417 and kvm-userspace.git
bae043c2ddf35ed1965f062131394afa75e45b17.
Three Old Issues:
1. Booting four guests likely fails
https://sourceforge.net/track
Avi Kivity wrote:
> if select() doesn't enable signals (like you can do with pselect) you
> may sit for a long time in select() until the timer expires.
Hm. Does the guest timer affect host userspace in all configurations? The
original trigger for my SIGIO patch was that opening a VNC connection
Anders wrote:
> Avi Kivity wrote:
>
>
>> if select() doesn't enable signals (like you can do with pselect) you
>> may sit for a long time in select() until the timer expires.
>>
>
> Hm. Does the guest timer affect host userspace in all configurations? The
> original trigger for my SIGIO pat
Enrico Weigelt wrote:
> Hi folks,
>
> I'm using dozens of VE's / jails to separate applications
> (even complete webapps w/ their own httpd) for easier maintenance
> and better security. But this tends to consume a lot of memory,
> since code sharing (.so's) cannot take effect here (each jail/VE
>
Avi Kivity wrote:
> Enrico Weigelt wrote:
>> Hi folks,
>>
>> I'm using dozens of VE's / jails to separate applications
>> (even complete webapps w/ their own httpd) for easier maintenance
>> and better security. But this tends to consume a lot of memory,
>> since code sharing (.so's) cannot take ef
From: Ben-Ami Yassour <[EMAIL PROTECTED]>
Signed-off-by: Ben-Ami Yassour <[EMAIL PROTECTED]>
Signed-off-by: Muli Ben-Yehuda <[EMAIL PROTECTED]>
---
libkvm/libkvm.c | 24
qemu/hw/pci-passthrough.c | 89 +++--
qemu/hw/pci-passthroug
From: Ben-Ami Yassour <[EMAIL PROTECTED]>
Signed-off-by: Ben-Ami Yassour <[EMAIL PROTECTED]>
Signed-off-by: Muli Ben-Yehuda <[EMAIL PROTECTED]>
---
libkvm/libkvm.c | 24
qemu/hw/pci-passthrough.c | 89 +++--
qemu/hw/pci-passthroug
From: Ben-Ami Yassour <[EMAIL PROTECTED]>
Signed-off-by: Ben-Ami Yassour <[EMAIL PROTECTED]>
Signed-off-by: Muli Ben-Yehuda <[EMAIL PROTECTED]>
---
arch/x86/kvm/mmu.c | 59 +--
arch/x86/kvm/paging_tmpl.h | 19 +
include/linux/kvm_hos
This patch for PCI passthrough devices enables a guest to access a device's
memory mapped I/O regions directly, without requiring the host to trap and
emulate every MMIO access.
Updated from last version: we create a memory slot for each MMIO region of the
guest's devices, and then use the /sys/
Hi all,
I am glad to announce the first beta release of 'Proxmox Virtual
Environment' - an open source virtualization platform for the
enterprise.
The main features are:
- All code is GPL
- OpenVZ and KVM support
- bare metal installer (debian etch 64)
- Backup/r
From: Ben-Ami Yassour <[EMAIL PROTECTED]>
Signed-off-by: Ben-Ami Yassour <[EMAIL PROTECTED]>
Signed-off-by: Muli Ben-Yehuda <[EMAIL PROTECTED]>
---
arch/x86/kvm/mmu.c | 59 +--
arch/x86/kvm/paging_tmpl.h | 19 +
include/linux/kvm_hos
Avi Kivity wrote:
> Anthony Liguori wrote:
>>>
>>> What about aio completions? The only race-free way to handle both
>>> posix aio completion and fd readiness is signals AFAIK.
>>
>> We poll aio completion after the select don't we? Worst case
>> scenario we miss a signal and wait to poll after
From: Christian Borntraeger <[EMAIL PROTECTED]>
This patch changes the interrupt defintions for virtio on s390. We now use
the extint number 0x2603, which is used as a host interrupt already by z/VM
for pfault and dasd_diag.
We will use subcode 0x0D to distinguish virtio from dasd and pfault.
Sig
On Wed, Apr 16, 2008 at 1:14 PM, Dietmar Maurer <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I am glad to announce the first beta release of 'Proxmox Virtual
> Environment' - an open source virtualization platform for the
> enterprise.
>
> The main features are:
>
> - All code is GPL
>
Hi Avi,
these two fixes repair two things in kvm-s390:
- #1 makes kvm complile again on s390 after a common code change
- #2 changes our virtio interrupt definitions to the values that will
be reserved for kvm use in s390 architecture
I'd be great if both could make 2.6.26.
so long,
Carsten
From: Christian Borntraeger <[EMAIL PROTECTED]>
Since
commit ded6fb24fb694bcc5f308a02ec504d45fbc8aaa6
Author: Marcelo Tosatti <[EMAIL PROTECTED]>
Date: Fri Apr 11 13:24:45 2008 -0300
KVM: add ioctls to save/store mpstate
kvm does not compile on s390.
This patch provides ioctl stubs for s
Nguyen Anh Quynh wrote:
> Hi Anthony,
>
> I found a bug in the last code: send_command() failed to copy back the
> result into extboot_cmd structure. This patch fixes it.
>
> I succesfully tested this version with guest Win2K (fully updated,
> scsi boot) and Linux 2.6.25-rc8 (virtio).
>
> Let me kn
Anthony Liguori wrote:
> There is a 5th option. Do away with the use of posix aio. We get
> absolutely no benefit from it because it's limited to a single thread.
> Fabrice has reverted a patch to change that in the past.
How about using linux aio for it? It seems much better, because it
does
Today's new kvm architecture is ia64, aka Itanium 2. Like s390, it is
only provided in the git tree, not in the tarball. Windows and Linux
guests are supported.
On good old x86, we have a the new kvmtrace performance monitoring
framework together with a sizable number of bug fixes.
Changes f
With the usage of the V_TPR field this comment is now obsolet.
Signed-off-by: Joerg Roedel <[EMAIL PROTECTED]>
---
arch/x86/kvm/svm.c |7 ---
1 files changed, 0 insertions(+), 7 deletions(-)
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index 61bb2cb..d643605 100644
--- a/arch/x86
If the CR8 write intercept is disabled the V_TPR field of the VMCB needs to be
synced with the TPR field in the local apic.
Signed-off-by: Joerg Roedel <[EMAIL PROTECTED]>
---
arch/x86/kvm/svm.c | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kvm/svm.
This patch series implements optimizations to the CR8 intercept handling in
SVM. With these patches applied CR8 reads are not intercepted anymore. The
writes to CR8 are only intercepted if the TPR masks interrupts. This
significantly reduces the number of total CR8 intercepts when running Windows
6
This patch disables the intercept of CR8 writes if the TPR is not masking
interrupts. This reduces the total number CR8 intercepts to below 1 percent of
what we have without this patch using Windows 64 bit guests.
Signed-off-by: Joerg Roedel <[EMAIL PROTECTED]>
---
arch/x86/kvm/svm.c | 31 +
There is not selective cr0 intercept bug. The code in the comment sets the
CR0.PG bit. But KVM sets the CR4.PG bit for SVM always to implement the paged
real mode. So the 'mov %eax,%cr0' instruction does not change the CR0.PG bit.
Selective CR0 intercepts only occur when a bit is actually changed.
Anthony Liguori wrote:
> A couple general comments.
>
> I'd feel a lot more comfortable with the int13 handler returning an
> int and the asm stub code uses that result to determine how to set
> CF. You set CF deep within the function stack and there's no
> guarantee that GCC isn't going to sto
This patch exports the kvm_lapic_set_tpr() function from the lapic code to
modules. It is required in the kvm-amd module to optimize CR8 intercepts.
Signed-off-by: Joerg Roedel <[EMAIL PROTECTED]>
---
arch/x86/kvm/lapic.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/ar
This patch adds syncing of the lapic.tpr field to the V_TPR field of the VMCB.
With this change we can safely remove the CR8 read intercept.
Signed-off-by: Joerg Roedel <[EMAIL PROTECTED]>
---
arch/x86/kvm/svm.c | 18 --
1 files changed, 16 insertions(+), 2 deletions(-)
diff --
By the way Marcelo, it would be polite to provide these stubs yourself to
avoid breaking the build on other architectures.
It looks like IA64 is still broken because of this.
--
Hollis Blanchard
IBM Linux Technology Center
On Wednesday 16 April 2008 09:06:34 Carsten Otte wrote:
> From: Christi
Host software:
Linux 2.6.24.4
KVM 65 (I am using the kernel modules from this release).
X11 7.2 from Xorg
SDL 1.2.13
GCC 4.1.1
Glibc 2.4
Host hardware:
Asus P5B Deluxe (P965 chipset based) motherboard
4 GB RAM
Intel E6700 CPU
Guest software:
Slackware 12.0 installed from CD-ROM.
Command used to
I don't think this lock mechanism is completely working. I have
gotten a few failures trying to dereference 0x100100 which appears to
be LIST_POISON1.
Thanks,
Robin
-
This SF.net email is sponsored by the 2008 JavaOne(SM) C
A couple general comments.
I'd feel a lot more comfortable with the int13 handler returning an int
and the asm stub code uses that result to determine how to set CF. You
set CF deep within the function stack and there's no guarantee that GCC
isn't going to stomp on it.
I also don't think we w
It makes no sense for the clock initialization to be
hanging around in setup_32.c when we have a generic kvm guest
initialization function available. So, we move kvmclock_init()
inside such a function, leading to a cleaner code.
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
arch/x86/kernel
Glauber Costa wrote:
> It makes no sense for the clock initialization to be
> hanging around in setup_32.c when we have a generic kvm guest
> initialization function available. So, we move kvmclock_init()
> inside such a function, leading to a cleaner code.
>
> Signed-off-by: Glauber Costa <[EMAIL
On Wed, Apr 16, 2008 at 11:21:05AM -0500, Hollis Blanchard wrote:
> By the way Marcelo, it would be polite to provide these stubs yourself to
> avoid breaking the build on other architectures.
Indeed, should have been more careful.
> It looks like IA64 is still broken because of this.
Now I'm n
From: Ryan Harper <[EMAIL PROTECTED]>
Rather than faking up some geometry, allow the backend to push the disk
geometry via virtio pci config option. Keep the old geo code around for
compatibility.
Signed-off-by: Ryan Harper <[EMAIL PROTECTED]>
Reviewed-by: Anthony Liguori <[EMAIL PROTECTED]>
di
From: Ryan Harper <[EMAIL PROTECTED]>
Rather than faking up some geometry, allow the backend to push the disk
geometry via virtio pci config option. Keep the old geo code around for
compatibility.
Signed-off-by: Ryan Harper <[EMAIL PROTECTED]>
Reviewed-by: Anthony Liguori <[EMAIL PROTECTED]>
di
On Wed, Apr 16, 2008 at 11:35:38AM -0700, Christoph Lameter wrote:
> On Wed, 16 Apr 2008, Robin Holt wrote:
>
> > I don't think this lock mechanism is completely working. I have
> > gotten a few failures trying to dereference 0x100100 which appears to
> > be LIST_POISON1.
>
> How does xpmem unre
On Wed, 16 Apr 2008, Robin Holt wrote:
> I don't think this lock mechanism is completely working. I have
> gotten a few failures trying to dereference 0x100100 which appears to
> be LIST_POISON1.
How does xpmem unregistering of notifiers work?
---
On Wed, 16 Apr 2008, Robin Holt wrote:
> On Wed, Apr 16, 2008 at 11:35:38AM -0700, Christoph Lameter wrote:
> > On Wed, 16 Apr 2008, Robin Holt wrote:
> >
> > > I don't think this lock mechanism is completely working. I have
> > > gotten a few failures trying to dereference 0x100100 which appear
On 4/16/08, Anthony Liguori <[EMAIL PROTECTED]> wrote:
> This patch introduces a DMA API and plumbs support through the DMA layer. We
> use a mostly opaque structure, IOVector to represent a scatter/gather list of
> physical memory. Associated with each IOVector is a read/write function and
>
--- Alex Davis <[EMAIL PROTECTED]> wrote:
> Host software:
> Linux 2.6.24.4
> KVM 65 (I am using the kernel modules from this release).
> X11 7.2 from Xorg
> SDL 1.2.13
> GCC 4.1.1
> Glibc 2.4
>
> Host hardware:
> Asus P5B Deluxe (P965 chipset based) motherboard
> 4 GB RAM
> Intel E6700 CPU
>
>
Blue Swirl wrote:
> On 4/16/08, Anthony Liguori <[EMAIL PROTECTED]> wrote:
>
>> This patch introduces a DMA API and plumbs support through the DMA layer. We
>> use a mostly opaque structure, IOVector to represent a scatter/gather list
>> of
>> physical memory. Associated with each IOVector
kvm_pv_mmu_op should not take mmap_sem. All gfn_to_page() callers down
in the MMU processing will take it if necessary, so as it is it can
deadlock.
Apparently a leftover from the days before slots_lock.
Signed-off-by: Marcelo Tosatti <[EMAIL PROTECTED]>
diff --git a/arch/x86/kvm/mmu.c b/arch/
On Thursday 17 April 2008 04:56:37 Ryan Harper wrote:
> From: Ryan Harper <[EMAIL PROTECTED]>
>
> Rather than faking up some geometry, allow the backend to push the disk
> geometry via virtio pci config option. Keep the old geo code around for
> compatibility.
Hi Ryan,
Looks good! Some brief
Rusty Russell wrote:
> On Thursday 17 April 2008 04:56:37 Ryan Harper wrote:
>
>> From: Ryan Harper <[EMAIL PROTECTED]>
>>
>> Rather than faking up some geometry, allow the backend to push the disk
>> geometry via virtio pci config option. Keep the old geo code around for
>> compatibility.
>>
This isn't fully cooked yet, but pretty close. The basic idea is to
make the aio usage in block-raw go to a set of function pointers and
allow multiple simultaneous AIO implementations.
I converted the posix-aio support to this, and also introduced a "unix"
aio which just uses O_NONBLOCK and
On Wednesday 16 April 2008 16:32:30 Anthony Liguori wrote:
> > diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c
> > --- a/drivers/block/virtio_blk.c
> > +++ b/drivers/block/virtio_blk.c
> > @@ -157,10 +157,25 @@ static int virtblk_ioctl(struct inode *i
> > /* We provide getgeo
Hi Marcelo,
> virtio-blk is doing synchronous IO which blocks the guest CPU.
>
> This is especially bad for write intensive loads where the guest
> will hang in the host write throttling logic.
>
> In the meantime please try the following patch:
>
> http://www.mail-archive.com/kvm-devel@lists.sour
On Thu, Apr 17, 2008 at 01:05:50AM +0200, Gerd von Egidy wrote:
> Hi Marcelo,
>
> > virtio-blk is doing synchronous IO which blocks the guest CPU.
> >
> > This is especially bad for write intensive loads where the guest
> > will hang in the host write throttling logic.
> >
> > In the meantime plea
On Wed, Apr 16, 2008 at 04:36:42PM -0500, Anthony Liguori wrote:
> This isn't fully cooked yet, but pretty close. The basic idea is to
> make the aio usage in block-raw go to a set of function pointers and
> allow multiple simultaneous AIO implementations.
The AIO API looks great. Looking forwa
Hi,
I've got some qemu crashes while trying to passthrough an ide device
to a kvm guest. After some investigation, it turned out that
register_ioport_{read/write} will abort on errors instead of returning
a meaningful error.
However, even if we do return an error, the asynchronous nature of pci
From: Glauber Costa <[EMAIL PROTECTED]>
map which io registers where already sucessfuly registered
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
qemu/hw/pci.c |5 +++--
qemu/hw/pci.h |3 +++
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/qemu/hw/pci.c b/qemu/hw/pci
From: Glauber Costa <[EMAIL PROTECTED]>
Currently, any error in register_ioports make qemu
abort through hw_error(). But there are situations
in which those errors are not fatal. Just return
< 0 instead
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
qemu/vl.c | 12 +++-
1 files c
From: Glauber Costa <[EMAIL PROTECTED]>
In situations like pci-passthrough, the ioport registering can
fail, because another device is already present and in charge for
an io address. The current state would crash qemu, but we can propagate
the errors up to the pci layer, avoiding it.
Signed-off-
On Thu, Apr 17, 2008 at 12:02 AM, Anthony Liguori <[EMAIL PROTECTED]> wrote:
> A couple general comments.
>
> I'd feel a lot more comfortable with the int13 handler returning an int and
> the asm stub code uses that result to determine how to set CF. You set CF
> deep within the function stack an
This patch replaces the current assembly code of Extboot option rom
with new C code. Patch is against kvm-66.
This version returns an error code in case int 13 handler cannot
handle a requested function.
Signed-off-by: Nguyen Anh Quynh <[EMAIL PROTECTED]>
# diffstat extboot3.diff
b/extboot/Mak
Bugs item #1944629, was opened at 2008-04-17 13:44
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1944629&group_id=180599
Please note that this message will contain a full copy
Hi All,
This is today's KVM test result against kvm.git
eeff99b6f7e47630356cf2aee2e58d1b3e1af931 and kvm-userspace.git
cd6ac0431e01c01c7870aadfafc6ddaf09a8fb95.
One New Issue
1.Can't boot smp guests on ia32e host
https://sourceforge.net/tracker/
Nguyen Anh Quynh wrote:
> This patch replaces the current assembly code of Extboot option rom
> with new C code. Patch is against kvm-66.
>
> This version returns an error code in case int 13 handler cannot
> handle a requested function.
>
> Signed-off-by: Nguyen Anh Quynh <[EMAIL PROTECTED]>
>
> + .globl linux_boot
> +linux_boot:
> + cli
> + cld
> + mov $0x9000, %ax
> + mov %ax, %ds
> + mov %ax, %es
> + mov %ax, %fs
> + mov %ax, %gs
> + mov %ax, %ss
> + mov $0x8ffe, %sp
> + ljmp $0x9000 + 0x20, $0
The hard use of segment 9000 is really highly
65 matches
Mail list logo
