From: Avi Kivity a...@redhat.com
* commit 'upstream/master':
Use qemu_irq for system_powerdown
Sparc32: use qemu_irq for system_powerdown
Sparc32: move sparc32_dma init to sun4m.c
Sparc32: remove VRAM and NVRAM sizes from hwdef
Sparc32: remove IRQ numbers from hwdef
Sparc32: move
From: Avi Kivity a...@redhat.com
Needed by KVM.
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/arch/x86/mm/highmem_32.c b/arch/x86/mm/highmem_32.c
index 2112ed5..572f47c 100644
--- a/arch/x86/mm/highmem_32.c
+++ b/arch/x86/mm/highmem_32.c
@@ -104,6 +104,7 @@ EXPORT_SYMBOL(kunmap);
Hi Daniel!
Aug 4 17:38:39 ss03 kernel: [4.750023] bnx2 :03:00.0: firmware:
requesting bnx2/bnx2-mips-06-4.6.16.fw
Aug 4 17:38:39 ss03 kernel: [4.751070] bnx2: Can't load firmware file
bnx2/bnx2-mips-06-4.6.16.fw
Aug 4 17:38:39 ss03 kernel: [4.751141] bnx2 :03:00.0: PCI
On Sunday, August 09, 2009 7:47 PM Avi Kivity wrote:
On 08/09/2009 02:32 PM, Avi Kivity wrote:
I see that the guest is in stopped state after migration, issuing the
cont command in the monitor unhalts it.
Anthony, was this a planned change, or is it a regression?
Okay, looks like a
Bugs item #2834538, was opened at 2009-08-09 20:23
Message generated for change (Comment added) made by thekozmo
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2834538group_id=180599
Please note that this message will contain a full copy of the comment
On Sun, 2009-08-09 at 12:58 +0300, Avi Kivity wrote:
On 08/07/2009 03:31 PM, Chris Lalancette wrote:
Avi,
Trying to use libvirt with development snapshots of qemu-kvm is a bit
problematic. The trouble is that for all development snapshots, the value
that
gets placed into this
Released versions of qemu-kvm now have a KVM_VERSION of either
qemu-kvm-x.y.z or qemu-kvm-devel-XX. However, when building from git,
KVM_VERSION is kvm-devel.
Defaulting to qemu-kvm-devel makes more sense.
With newer versions of qemu-kvm, libvirt actually ignores the kvm
snapshot number (i.e.
On 08/10/2009 12:19 PM, Mark McLoughlin wrote:
This is problematic in two ways. One is that I am basically guaranteed
to forget to edit the file (which is why the release scripts generate
the name based on the tag).
Anthony manages to remember to update VERSION :-)
I'm not
On 08/10/2009 12:39 PM, Mark McLoughlin wrote:
Released versions of qemu-kvm now have a KVM_VERSION of either
qemu-kvm-x.y.z or qemu-kvm-devel-XX. However, when building from git,
KVM_VERSION is kvm-devel.
Defaulting to qemu-kvm-devel makes more sense.
With newer versions of qemu-kvm, libvirt
On 08/10/09 08:55, Amit Shah wrote:
Bad example. Quite a lot of modern devices drivers are using dynamic
major/minor numbers because they have proven to be such a pain in the
butt. That's why we have more sophisticated mechanisms like udev for
userspace to make use of.
Let me explain how we
On Mon, 2009-08-10 at 12:46 +0300, Avi Kivity wrote:
On 08/10/2009 12:19 PM, Mark McLoughlin wrote:
Or we could drop this kvm snapshot numbering system and just use qemu
VERSION numbering - i.e. qemu-kvm-devel-88 could have been published as
qemu-kvm-0.10.50
Yeah. You still
On 08/10/2009 12:52 PM, Mark McLoughlin wrote:
On Mon, 2009-08-10 at 12:46 +0300, Avi Kivity wrote:
On 08/10/2009 12:19 PM, Mark McLoughlin wrote:
Or we could drop this kvm snapshot numbering system and just use qemu
VERSION numbering - i.e. qemu-kvm-devel-88 could have been
Bugs item #2834538, was opened at 2009-08-09 20:23
Message generated for change (Comment added) made by thekozmo
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2834538group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #2829519, was opened at 2009-07-30 12:13
Message generated for change (Comment added) made by avik
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2829519group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #2827947, was opened at 2009-07-27 20:16
Message generated for change (Comment added) made by avik
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2827947group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #2793994, was opened at 2009-05-19 20:52
Message generated for change (Comment added) made by avik
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2793994group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #2725669, was opened at 2009-04-01 23:44
Message generated for change (Comment added) made by avik
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2725669group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #2490866, was opened at 2009-01-06 23:10
Message generated for change (Comment added) made by avik
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2490866group_id=180599
Please note that this message will contain a full copy of the comment
On 08/10/2009 03:13 PM, Gene Horodecki wrote:
Avi Kivity wrote:
On 08/08/2009 03:56 AM, Gene Horodecki wrote:
Hi there, I currently have about five guests set up with KVM, one of
them being windows XP. I am having trouble with the windows XP
one. It will works for a bit and then the process
Bugs item #2099075, was opened at 2008-09-07 22:22
Message generated for change (Comment added) made by avik
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2099075group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #1941302, was opened at 2008-04-13 14:21
Message generated for change (Comment added) made by avik
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1941302group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #1984384, was opened at 2008-06-04 14:49
Message generated for change (Comment added) made by avik
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1984384group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #1906189, was opened at 2008-03-03 13:33
Message generated for change (Comment added) made by avik
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1906189group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #2024740, was opened at 2008-07-22 17:36
Message generated for change (Comment added) made by avik
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2024740group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #1831632, was opened at 2007-11-14 10:46
Message generated for change (Comment added) made by avik
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1831632group_id=180599
Please note that this message will contain a full copy of the comment
Bugs item #1929279, was opened at 2008-03-30 14:21
Message generated for change (Settings changed) made by avik
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1929279group_id=180599
Please note that this message will contain a full copy of the comment
kvm_para.h contains userspace interface and so
should be exported.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
Avi, this fixes a bug (in build system) that has been there since
2.6.26. Since userspace already uses this header, I think it would be
nice to have the fix in 2.6.31.
kvm_para.h contains userspace interface and so
should be exported.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
Changes since v1:
Added asm/kvm_para.h which was also missing
Avi, this fixes a bug (in build system) that has been there since
2.6.26. Since userspace already uses this
Gerd Hoffmann wrote:
There are some other problems with usb too: It's not transparent to
users. Any hotplug event could alert users and that's not desired. It's
a system-only thing and should also remain that way.
I think virtio-serial is the better way to handle vmchannel. Unlike
usb
As sourceforge keeps changing the way it organizes its
download pages, a slightly better way to sort out the
latest KVM release tag was devised: Look in all regexp
matches of what looks like a release tag, and return the
largest integer, which will be therefore the latest
release tag. This way we
On 08/10/09 15:02, Anthony Liguori wrote:
I think you're missing my fundamental point. Don't use the kernel as the
guest interface.
Introduce a userspace daemon that exposes a domain socket. Then we can
have a proper protocol that uses reverse fqdns for identification.
We need nothing but
Gerd Hoffmann wrote:
On 08/10/09 15:02, Anthony Liguori wrote:
I think you're missing my fundamental point. Don't use the kernel as the
guest interface.
Introduce a userspace daemon that exposes a domain socket. Then we can
have a proper protocol that uses reverse fqdns for identification.
Gerd Hoffmann wrote:
On 08/10/09 15:02, Anthony Liguori wrote:
I think you're missing my fundamental point. Don't use the kernel as the
guest interface.
Introduce a userspace daemon that exposes a domain socket. Then we can
have a proper protocol that uses reverse fqdns for identification.
On Monday, 10 August 2009 08:40:48 +0200,
Bernhard Held wrote:
Hi Daniel!
Hi Bernhard!
Aug 4 17:38:39 ss03 kernel: [4.750023] bnx2 :03:00.0: firmware:
requesting bnx2/bnx2-mips-06-4.6.16.fw
Aug 4 17:38:39 ss03 kernel: [4.751070] bnx2: Can't load firmware file
On 08/10/09 16:20, Anthony Liguori wrote:
Gerd Hoffmann wrote:
Do we really want design a daemon and a protocol for such a simple thing?
Yes, because we also need (c) the ability to write cross platform
software that targets vmchannel.
So having a library interface is going to be extremely
Anthony Liguori wrote:
Gregory Haskins wrote:
We add a new virtio transport for accessing backends located on vbus.
This
complements the existing transports for virtio-pci, virtio-s390, and
virtio-lguest that already exist.
Signed-off-by: Gregory Haskins ghask...@novell.com
Very
On 08/10/09 16:27, Anthony Liguori wrote:
I think my fundamental argument boils down to two points. 1) we should
not require new guest drivers unless we absolutely have to
Allow guest drivers is fine though I guess?
2) we should
always do things in userspace unless we absolutely have to do
Hi Daniel!
I've set in the kernel config:
CONFIG_FIRMWARE_IN_KERNEL=y
And what happened? Are you sure you recompiled and booted the new kernel with
CONFIG_FIRMWARE_IN_KERNEL=y?
Although I don't see the asked file in initramfs. The file with full
path is
-- Forwarded message --
From: K R I S K kernelb...@gmail.com
Date: Sun, Aug 9, 2009 at 8:36 AM
Subject: virDomainCreateLinux() failed QEMU quit during console
startup bind() failed
To: kvm@vger.kernel.org
Hi,
Please help me with the creation of new Virtual m/c on Ubuntu 8.04.3
Gerd Hoffmann wrote:
Ok, lets rip out the in-kernel ioapic code then. It can (and has
been) done in userspace.
The justification is performance although that's not really true anymore
post TPR optimization.
But FWIW, I opposed both the in-kernel apic and the in-kernel pit when
they were
Hi all,
I post here because I experiment a lot of problem to activate windows
2003 server se on kvm guest. I use the latest version of kvm (88). I've
tested with 2 different emulated nic (realtek 8139 and intel pro 1000)
and with the intel one, impossible to go to windows update website which
Descriptor table can be placed on two non-contiguous pages.
It is better to read descriptor by linear address.
Signed-off-by: Mikhail Ershov mike.ers...@gmail.com
---
arch/x86/kvm/x86.c | 10 ++
1 files changed, 2 insertions(+), 8 deletions(-)
diff --git a/arch/x86/kvm/x86.c
Anthony Liguori wrote:
There is nothing sane about vmchannel. It's just an attempt to bypass
QEMU which is going to introduce all sorts of complexities wrt
migration, guest compatibility, etc.
However, as I've mentioned repeatedly, the reason I won't merge
virtio-serial is that it
This implements vhost: a kernel-level backend for virtio,
The main motivation for this work is to reduce virtualization
overhead for virtio by removing system calls on data path,
without guest changes. For virtio-net, this removes up to
4 system calls per packet: vm exit for kick, reentry for
vhost net module wants to do copy to/from user from a kernel thread,
which needs switch_mm (like what fs/aio has).
export cpu_tlbstate to make this possible
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
arch/x86/mm/tlb.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff
What it is: vhost net is a character device that can be used to reduce
the number of system calls involved in virtio networking.
Existing virtio net code is used in the guest without modification.
There's similarity with vringfd, with some differences and reduced scope
- uses eventfd for
This adds support for vhost-net virtio kernel backend.
This is RFC, but works without issues for me.
Still needs to be split up, tested and benchmarked properly,
but posting it here in case people want to test drive
the kernel bits I posted.
Michael S. Tsirkin (3):
qemu-kvm: move virtio-pci.o
virtio-pci depends, and will always depend, on pci.c
so it makes sense to keep it in the same makefile,
(unlike the rest of virtio files which should eventually
be moved out to Makefile.hw).
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
Makefile.hw |2 +-
Makefile.target |2
devices should have the final say over which virtio features they
support. E.g. indirect entries may or may not make sense in the context
of virtio-console. Move the common bits from virtio-pci to an inline
function and let each device call it.
No functional changes.
Signed-off-by: Michael S.
This adds support for vhost-net virtio kernel backend.
To enable (assuming device eth2):
1. enable promisc mode or program guest mac in device eth2
2. disable tso, gso, lro on the card
3. add vhost=eth0 to -net flag
4. run with CAP_NET_ADMIN priviledge (e.g. root)
This patch is RFC, but works
On Monday 10 August 2009, Michael S. Tsirkin wrote:
What it is: vhost net is a character device that can be used to reduce
the number of system calls involved in virtio networking.
Existing virtio net code is used in the guest without modification.
Very nice, I loved reading it. It's getting
Whild reading virtio code, I found some memory leak in removing
virtio_net.
In virtnet_remove, only skb has been freed not the pages in skb
frags. Here is the patch to fix this, please review it.
Signed-off-by: Shirley Ma x...@us.ibm.com
diff --git a/drivers/net/virtio_net.c
On Mon, Aug 10, 2009 at 09:51:18PM +0200, Arnd Bergmann wrote:
On Monday 10 August 2009, Michael S. Tsirkin wrote:
What it is: vhost net is a character device that can be used to reduce
the number of system calls involved in virtio networking.
Existing virtio net code is used in the guest
Bugs item #2793994, was opened at 2009-05-19 19:52
Message generated for change (Comment added) made by benb
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2793994group_id=180599
Please note that this message will contain a full copy of the comment
Michael S. Tsirkin wrote:
This adds support for vhost-net virtio kernel backend.
This is RFC, but works without issues for me.
Still needs to be split up, tested and benchmarked properly,
but posting it here in case people want to test drive
the kernel bits I posted.
Any rough idea on
Hi,
Please help me with the creation of new Virtual m/c on Ubuntu 8.04.3
over KVM on top of 2.6.24-24-generic
Kernel. This is a Dell m/c.
I am using Fedora 8 ISO image as the virtual OS.
Following is the error:
Unable to complete install 'class 'libvirt.libvirtError'
virDomainCreateLinux()
On 08/10/2009 11:53 AM, Michael S. Tsirkin wrote:
vhost net module wants to do copy to/from user from a kernel thread,
which needs switch_mm (like what fs/aio has).
export cpu_tlbstate to make this possible
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
arch/x86/mm/tlb.c |1 +
On Monday 10 August 2009 20:10:44 Michael S. Tsirkin wrote:
On Mon, Aug 10, 2009 at 09:51:18PM +0200, Arnd Bergmann wrote:
what is the difference between vhost_net_reset_owner(n)
and vhost_net_set_socket(n, -1)?
set socket to -1 will only stop the device.
reset owner will let another
On 08/10/2009 03:06 PM, Michael S. Tsirkin wrote:
Wouldn't it be a *lot* better to move use_mm() from fs/aio.c into common
code, and export that instead?
That's easy too. What would a good place for it be?
Somewhere in mm/, presumably. When in doubt, make it a new file...
On Mon, Aug 10, 2009 at 02:56:46PM -0700, H. Peter Anvin wrote:
On 08/10/2009 11:53 AM, Michael S. Tsirkin wrote:
vhost net module wants to do copy to/from user from a kernel thread,
which needs switch_mm (like what fs/aio has).
export cpu_tlbstate to make this possible
Signed-off-by:
On Mon, 10 Aug 2009 07:17:54 pm Gerd Hoffmann wrote:
On 08/10/09 08:55, Amit Shah wrote:
Bad example. Quite a lot of modern devices drivers are using dynamic
major/minor numbers because they have proven to be such a pain in the
butt. That's why we have more sophisticated mechanisms like
Rusty Russell wrote:
On Mon, 10 Aug 2009 07:17:54 pm Gerd Hoffmann wrote:
On 08/10/09 08:55, Amit Shah wrote:
Bad example. Quite a lot of modern devices drivers are using dynamic
major/minor numbers because they have proven to be such a pain in the
butt. That's why we have more
According to 16.2.5 in the SDM, eflags.vm in the tss is consulted before loading
and new segments. If eflags.vm == 1, then the segments are treated as 16-bit
segments.
This fixes an invalid vmentry failure in a custom OS that was happening after
a task switch into vm8086 mode. Since the
Bugs item #2835276, was opened at 2009-08-10 21:38
Message generated for change (Tracker Item Submitted) made by agriffis
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2835276group_id=180599
Please note that this message will contain a full copy of the
64 matches
Mail list logo
