From: Avi Kivity a...@redhat.com
* commit '59f2689d9082f2f631253c810f73cd22290144a9':
Added readonly flag to -drive command
qcow2: Allow qcow2 disk images with size zero
(x86/Sparc/PPC)-user: fix cpu_copy
IDE: Fix reset handling
user: move CPU reset call to main.c for x86/PPC/Sparc
From: Avi Kivity a...@redhat.com
* commit '4f5e19e6c570459cd524b29b24374f03860f5149':
pci_host.h: move functions in pci_host.h into .c file.
Conflicts:
hw/piix_pci.c
Signed-off-by: Avi Kivity a...@redhat.com
--
To unsubscribe from this list: send the line unsubscribe kvm-commits in
From: Avi Kivity a...@redhat.com
* commit '1945120112e93aa96af6d6004b36599f783ac563':
Update SeaBIOS to latest
Add test suite for json marshalling
Provide marshalling mechanism for json
QDict: Introduce qdict_iter()
Add a unit test for JSON support
Add a QObject JSON wrapper
Add a
From: Avi Kivity a...@redhat.com
* commit 'fb23162885f7fd8cf7334bed22c25ac32c7d8b9d':
pci: initialize pci config headers depending it pci header type.
pci: teach pci_default_config_write() ROM bar for normal/bridge device .
Changed include order in hw/device-assignment.c.
Signed-off-by: Avi
From: Avi Kivity a...@redhat.com
* commit '715a664ac4ca3b9e44ffbc0ca41ecd91fbe96656':
QemuOpts: command line switches for the config file.
QemuOpts: parse config from file.
QemuOpts: dump config.
QemuOpts: add find_list()
Documentation: Add options to image format descriptions
From: Avi Kivity a...@redhat.com
* commit '260c0cd3d985e51b15870ff47e17b7b930efbda1':
pci: use range helper functions.
pci: add helper functions to check ranges overlap.
pci: pcie host and mmcfg support.
vmstate: introduce VMSTATE_BUFFER_UNSAFE_INFO.
pci_host: change the signature of
From: Avi Kivity a...@redhat.com
* commit 'cfc6d90a98ec420998ef2009e359ea04456735ff':
Add linuxboot to BLOBS
Conflicts:
Makefile
Signed-off-by: Avi Kivity a...@redhat.com
--
To unsubscribe from this list: send the line unsubscribe kvm-commits in
the body of a message to
From: Avi Kivity a...@redhat.com
* commit 'dd4239d6574ca41c94fc0d0f77ddc728510ffc57':
Allow build of linuxboot.S with old assemblers
Avoid segfault on net_tap_init() failure
tap-bsd: handle ifname on FreeBSD hosts
Fix tap breakage on BSD hosts (no IFF_VNET_HDR)
Fix OpenBSD build of
From: Avi Kivity a...@redhat.com
The generic pci reset introduced by c0b1905b28580 breaks Windows XP suspend.
Disable it.
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/hw/pci.c b/hw/pci.c
index f4fdc1e..ca7dd73 100644
--- a/hw/pci.c
+++ b/hw/pci.c
@@ -109,9 +109,12 @@ static int
From: Avi Kivity a...@redhat.com
init/reset was left out.
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/qemu-kvm-x86.c b/qemu-kvm-x86.c
index 71a6319..1f0d37a 100644
--- a/qemu-kvm-x86.c
+++ b/qemu-kvm-x86.c
@@ -1291,6 +1291,7 @@ int kvm_arch_init_vcpu(CPUState *cenv)
From: Avi Kivity a...@redhat.com
* commit '3a3fb96d0d9e3331e3beb672108ec18a6d3d8c1c':
configure: Fix spelling in comment and rework the comment
qemu-io: build on all platforms
slirp: fix use-after-free
ARM PBX-A9 board support
ARM Cortex-A9 cpu support
ARM FP16 support
Built network
From: Carsten Otte carst...@de.ibm.com
This patch moves s390 processor status word into the base kvm_run
struct and keeps it up-to date on all userspace exits.
The userspace ABI is broken by this, however there are no applications
in the wild using this. A capability check is provided so users
I've been studying interrupt delivery in KVM myself lately. I hope I
can explain what I've found, but, as I'm pretty new to this, please
take my answer with a grain of salt (as I could be wrong). I would
really appreciate if someone could correct me here if I am wrong or
provide more
Bugs item #2902983, was opened at 2009-11-24 16:17
Message generated for change (Tracker Item Submitted) made by haoxudong
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2902983group_id=180599
Please note that this message will contain a full copy of the
On 24.11.2009, at 09:03, Kurt Kiefer wrote:
I've been studying interrupt delivery in KVM myself lately. I hope I can
explain what I've found, but, as I'm pretty new to this, please take my
answer with a grain of salt (as I could be wrong). I would really appreciate
if someone could
On 11/23/2009 01:06 PM, Johannes Berg wrote:
Commit f691fe1da7e2715137d21ae5a80bec64db4625db is really broken wrt.
the userspace interface for tracing because of the weird
KVM_MMU_PAGE_PRINTK macro.
Can you explain what is wrong with it?
Maybe we should have a unsafe for export flag for
On 11/23/2009 09:00 PM, Glauber Costa wrote:
On Sun, Nov 22, 2009 at 04:42:12PM +0200, Avi Kivity wrote:
A qemu-kvm which merges this commit breaks badly (see qemu-kvm.git next
branch). In the commit log for this commit, you write
you = Glauber Costa
I tested it with qemu
On 11/23/2009 11:07 PM, Glauber Costa wrote:
On Mon, Nov 23, 2009 at 5:00 PM, Glauber Costaglom...@redhat.com wrote:
On Sun, Nov 22, 2009 at 04:42:12PM +0200, Avi Kivity wrote:
A qemu-kvm which merges this commit breaks badly (see qemu-kvm.git next
branch). In the commit log for
On Tue, 2009-11-24 at 11:50 +0200, Avi Kivity wrote:
On 11/23/2009 01:06 PM, Johannes Berg wrote:
Commit f691fe1da7e2715137d21ae5a80bec64db4625db is really broken wrt.
the userspace interface for tracing because of the weird
KVM_MMU_PAGE_PRINTK macro.
Can you explain what is
Commit 6b5bbd04 qdev-ify device assignment forgot to put assigned devices
to devs list. So when IRQ routing changed in pci configure space, calling to
assigned_dev_update_irqs() won't update device guest IRQ, then assigned INTx
devices fail to work.
(OK, I am now aware of the fact that people
On 11/24/2009 12:05 PM, Johannes Berg wrote:
On Tue, 2009-11-24 at 11:50 +0200, Avi Kivity wrote:
On 11/23/2009 01:06 PM, Johannes Berg wrote:
Commit f691fe1da7e2715137d21ae5a80bec64db4625db is really broken wrt.
the userspace interface for tracing because of the weird
On Tue, Nov 24, 2009 at 08:54:23AM +1030, Rusty Russell wrote:
On Tue, 24 Nov 2009 02:37:01 am Shirley Ma wrote:
+ skb = (struct sk_buff *)buf;
This cast is unnecessary, but a comment would be nice:
Without this cast there is a compile warning.
Hi Shirley,
Looks
FYI: Combining that patch with a later fix from Juan fix the issue for
qemu-kvm.
(504c2948)
Also, the patch seems to apply fine ontop of next.
I can send a combined version if you want, or you can combine it yourself
That commit is already merged.
Applying it ontop of
On 11/24/2009 02:16 PM, Glauber Costa wrote:
That commit is already merged.
Applying it ontop of 5d968c942adbc48188dbbcf7d85e69c2e0d7cd8a, which is your
merge commit that includes my patch, make qemu-kvm go from non-working to
working again. So the problem must be something else.
On Tue, 2009-11-24 at 12:34 +0200, Avi Kivity wrote:
Um, C can be easily parsed with a C compiler. I don't think you can
expect it to be a plain format string and argument list.
Actually, it turns out that it cannot be parsed even with a C compiler:
({ const char *ret = p-buffer + p-len;
On 11/15/2009 05:50 PM, Avi Kivity wrote:
Shouldn't you create 13 now?
No, I rather think Glauber's 12 should be downgraded to 11 - unless it
misses the qemu merge windows for 0.12. My extensions definitely target
that release, thus will likely carry 11 in upstream. And we should
really try
On 11/24/2009 04:08 PM, Johannes Berg wrote:
On Tue, 2009-11-24 at 12:34 +0200, Avi Kivity wrote:
Um, C can be easily parsed with a C compiler. I don't think you can
expect it to be a plain format string and argument list.
Actually, it turns out that it cannot be parsed even with a
64bit Intel host system
Fedora host environment
32bit guest built with CPU i686 and no PAE support
This now momentarily flickers up something then reboots back to the BIOS.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
On 11/24/2009 09:50 AM, Alexander Graf wrote:
Currently userspace has no chance to find out which virtual address space we're
in and resolve addresses. While that is a big problem for migration, it's also
unpleasent when debugging, as gdb and the monitor don't work on virtual
addresses.
On 24.11.2009, at 16:02, Avi Kivity wrote:
On 11/24/2009 09:50 AM, Alexander Graf wrote:
Currently userspace has no chance to find out which virtual address space
we're
in and resolve addresses. While that is a big problem for migration, it's
also
unpleasent when debugging, as gdb and
On Tue, 24 Nov 2009, Gleb Natapov wrote:
On Mon, Nov 23, 2009 at 11:30:02AM -0600, Christoph Lameter wrote:
This adds significant overhead for the !PREEMPT case adding lots of code
in critical paths all over the place.
I want to measure it. Can you suggest benchmarks to try?
AIM9 (reaim9)?
On 11/24/2009 05:04 PM, Alexander Graf wrote:
index 92045a9..1240fcb 100644
--- a/include/linux/kvm.h
+++ b/include/linux/kvm.h
@@ -492,6 +492,7 @@ struct kvm_ioeventfd {
#ifdef __KVM_HAVE_VCPU_EVENTS
#define KVM_CAP_VCPU_EVENTS 41
#endif
+#define KVM_CAP_PPC_SEGSTATE 42
42 is
On Tue, Nov 24, 2009 at 08:36:32AM -0600, Anthony Liguori wrote:
Michael S. Tsirkin wrote:
On Tue, Nov 24, 2009 at 08:54:23AM +1030, Rusty Russell wrote:
On Tue, 24 Nov 2009 02:37:01 am Shirley Ma wrote:
+ skb = (struct sk_buff *)buf;
This cast is
On Tue, Nov 24, 2009 at 08:36:32AM -0600, Anthony Liguori wrote:
Michael S. Tsirkin wrote:
On Tue, Nov 24, 2009 at 08:54:23AM +1030, Rusty Russell wrote:
On Tue, 24 Nov 2009 02:37:01 am Shirley Ma wrote:
+ skb = (struct sk_buff *)buf;
This cast is
On 11/24/2009 04:58 PM, Alan Cox wrote:
64bit Intel host system
Fedora host environment
32bit guest built with CPU i686 and no PAE support
This now momentarily flickers up something then reboots back to the BIOS.
Any chance of a bisect to find out where this was introduced?
It's worth
On Sun, Nov 15, 2009 at 04:41:26PM +0100, Jan Kiszka wrote:
Avi Kivity wrote:
On 11/15/2009 05:02 PM, Jan Kiszka wrote:
Where should I add /* next version to use: 13 */, and who will take
care that this comment will also be kept up to date? The CPU vmstate is
already ordered according
On Wed, 25 Nov 2009 01:06:32 am Anthony Liguori wrote:
So does lguest. It's been that way since the beginning. Fixing this
would result in breaking older guests.
Agreed, we can't fix it in the guests, but it's a wart. That's why I
haven't bothered fixing it, but if someone else wants to
This patch adds a test for verifying whether the number of cpus and amount
of memory as seen inside a guest is same as allocated to it on the qemu
command line.
Signed-off-by: Sudhir Kumar sku...@linux.vnet.ibm.com
Index: kvm/tests/verify_resources.py
This patch adds the variants for verify_resources test into the
kvm_tests.cfg.sample file.
Signed-off-by: Sudhir Kumar sku...@linux.vnet.ibm.com
Index: kvm/kvm_tests.cfg.sample
===
--- kvm.orig/kvm_tests.cfg.sample
+++
Harald Dunkel wrote:
Hi folks,
If I migrate a virtual machine (2.6.31.6, amd64) from a host with
AMD cpu to an Intel host, then the guest is terminated on the old
host as expected, but it gets stuck on the new host. Every 60 seconds
it prints a message on the virtual console saying
On 11/24/2009 09:50 AM, Alexander Graf wrote:
Currently userspace has no chance to find out which virtual address space we're
in and resolve addresses. While that is a big problem for migration, it's also
unpleasent when debugging, as gdb and the monitor don't work on virtual
addresses.
On 24.11.2009, at 16:02, Avi Kivity wrote:
On 11/24/2009 09:50 AM, Alexander Graf wrote:
Currently userspace has no chance to find out which virtual address space
we're
in and resolve addresses. While that is a big problem for migration, it's
also
unpleasent when debugging, as gdb and
On 11/24/2009 05:04 PM, Alexander Graf wrote:
index 92045a9..1240fcb 100644
--- a/include/linux/kvm.h
+++ b/include/linux/kvm.h
@@ -492,6 +492,7 @@ struct kvm_ioeventfd {
#ifdef __KVM_HAVE_VCPU_EVENTS
#define KVM_CAP_VCPU_EVENTS 41
#endif
+#define KVM_CAP_PPC_SEGSTATE 42
42 is
43 matches
Mail list logo
