On Tue, May 18, 2010 at 03:22:36PM +0200, Kevin Wolf wrote:
I think it's stuck here in an endless loop:
while (laiocb-ret == -EINPROGRESS)
qemu_laio_completion_cb(laiocb-ctx);
Can you verify this by single-stepping one or two loop iterations? ret
and errno after the read call
On Wed, 12 May 2010 04:57:22 am Avi Kivity wrote:
On 05/07/2010 06:23 AM, Rusty Russell wrote:
On Thu, 6 May 2010 07:30:00 pm Avi Kivity wrote:
On 05/05/2010 11:58 PM, Michael S. Tsirkin wrote:
+ /* We publish the last-seen used index at the end of the available ring.
+ *
Am 19.05.2010 09:29, schrieb Christoph Hellwig:
On Tue, May 18, 2010 at 03:22:36PM +0200, Kevin Wolf wrote:
I think it's stuck here in an endless loop:
while (laiocb-ret == -EINPROGRESS)
qemu_laio_completion_cb(laiocb-ctx);
Can you verify this by single-stepping one or two loop
On 05/19/2010 10:39 AM, Rusty Russell wrote:
I think we're talking about the last 2 entries of the avail ring. That means
the worst case is 1 false bounce every time around the ring.
It's low, but why introduce an inefficiency when you can avoid doing it
for the same effort?
I think
On 05/18/2010 10:22 PM, Stefan Hajnoczi wrote:
On Tue, May 18, 2010 at 6:18 PM, Avi Kivitya...@redhat.com wrote:
The block multiwrite code pretends to be able to merge overlapping requests,
but doesn't do so in fact. This leads to I/O errors (for example on mkfs
of a large virtio disk).
Kevin Wolf wrote:
Am 19.05.2010 09:29, schrieb Christoph Hellwig:
On Tue, May 18, 2010 at 03:22:36PM +0200, Kevin Wolf wrote:
I think it's stuck here in an endless loop:
while (laiocb-ret == -EINPROGRESS)
qemu_laio_completion_cb(laiocb-ctx);
Can you verify this by
On Tue, May 18, 2010 at 08:52:36AM -0500, Anthony Liguori wrote:
This should be filed in launchpad as a qemu bug and it should be tested
against the latest git. This bug sounds like we're using an int to
represent sector offset somewhere but there's not enough info in the bug
report to
Hi, Michael
Thanks for your patch.
We plan add netdev parameter support in make_qemu_command. Since you are
working on this part. Could you add netdev support in your patch? hopeful
netdev can be default supported in make_qemu_command if qemu support it. Thanks
very much!
I think the point
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
target-i386/cpuid.c | 32
1 files changed, 32 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpuid.c b/target-i386/cpuid.c
index eebf038..21e94f3 100644
--- a/target-i386/cpuid.c
+++
From: Dexuan Cui dexuan@intel.com
Enable XSAVE/XRSTORE for guest.
Change from V1:
1. Use FPU API.
2. Fix CPUID issue.
3. Save/restore all possible guest xstate fields when switching. Because we
don't know which fields guest has already touched.
Signed-off-by: Dexuan Cui
This is a multi-part message in MIME format.
Hi,
I have a server dual xeon quad core with gentoo and qemu:
app-emulation/qemu-kvm-0.12.3-r1 USE=aio gnutls ncurses sasl vde -alsa
-bluetooth -curl -esd -fdt -hardened -kvm-trace -pulseaudio -qemu-ifup -sdl
-static
There is a lot of vm running with
Linus, please pull from
git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/2.6.35
to receive the KVM updates for the 2.6.35 merge window. Highlights
include a ppc64 port, timekeeping improvements, a lot of emulator work,
and perf integration.
Shortlog/diffstat below. Messy due to
On Tue, May 18, 2010 at 08:38:22PM +0300, Avi Kivity wrote:
Yes. Why would Linux post overlapping requests? makes
0x sense.
There may be a guest bug in here too. Christoph?
Overlapping writes are entirely fine from the guest POV, although they
should be rather unusual. We
On Wed, May 19, 2010 at 9:09 AM, Avi Kivity a...@redhat.com wrote:
On 05/18/2010 10:22 PM, Stefan Hajnoczi wrote:
What cache= mode are you running?
writeback.
In the cache=writeback case the virtio-blk guest driver does:
blk_queue_ordered(q, QUEUE_ORDERED_DRAIN_FLUSH, ...)
Stefan
--
To
On 05/19/2010 11:57 AM, Christoph Hellwig wrote:
On Tue, May 18, 2010 at 08:38:22PM +0300, Avi Kivity wrote:
Yes. Why would Linux post overlapping requests? makes
0x sense.
There may be a guest bug in here too. Christoph?
Overlapping writes are entirely fine from the guest
On 05/19/2010 12:01 PM, Stefan Hajnoczi wrote:
On Wed, May 19, 2010 at 9:09 AM, Avi Kivitya...@redhat.com wrote:
On 05/18/2010 10:22 PM, Stefan Hajnoczi wrote:
What cache= mode are you running?
writeback.
In the cache=writeback case the virtio-blk guest driver does:
This checker serves as the post_command to find the panic information
in the file which contains the content of guest serial console.
Changes from v2:
- Put all things into __main__
- Fix some typos
Signed-off-by: Jason Wang jasow...@redhat.com
---
client/tests/kvm/scripts/check_serial.py |
-kernel option is useful for both unattended installation and the
unittest in /kvm/user/test.
Signed-off-by: Jason Wang jasow...@redhat.com
---
client/tests/kvm/kvm_vm.py | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/client/tests/kvm/kvm_vm.py
When we do the unattended installation in tap mode, we should use
vm.get_address() instead of the 'localhost' in order the connect to
the finish program running in the guest.
Signed-off-by: Jason Wang jasow...@redhat.com
---
client/tests/kvm/tests/unattended_install.py | 25
This patch could let the unattended installation to be done through
the following method:
- cdrom: the original method which does the installation from cdrom
- url: installing the linux guest from http or ftp, tree url was specified
through url
- nfs: installing the linux guest from nfs. the
On Sun, May 16, 2010 at 7:52 PM, Avi Kivity a...@redhat.com wrote:
On 05/15/2010 04:19 AM, Teck Choon Giam wrote:
Hi,
Anyone encountered the same issue as me about system_powerdown no
longer working since upgraded to qemu-kvm 0.12.4?
Compared with what version?
--
error compiling
On Wed, May 19, 2010 at 10:06 AM, Avi Kivity a...@redhat.com wrote:
In the cache=writeback case the virtio-blk guest driver does:
blk_queue_ordered(q, QUEUE_ORDERED_DRAIN_FLUSH, ...)
I don't follow. What's the implication?
I was wondering whether the queue is incorrectly set to a mode
On Wed, May 19, 2010 at 10:23:44AM +0100, Stefan Hajnoczi wrote:
On Wed, May 19, 2010 at 10:06 AM, Avi Kivity a...@redhat.com wrote:
In the cache=writeback case the virtio-blk guest driver does:
blk_queue_ordered(q, QUEUE_ORDERED_DRAIN_FLUSH, ...)
I don't follow. ?What's the
Jan Kiszka schrieb:
...
--enable-io-thread?
If you had it disabled, it would also answer my question if -smp works
without problems without that feature.
Jan
Hi,
i have a dumb question: what is the --enable-io-thread? Is this a
kvm-switch?
My kvm 0.12.4 don't accept this switch. I'm know
We have lists for healthcare, business finance, consumers and professionals.
Lots of different lists from various optin sources.
Just send me an email here for additional info: successto...@gmx.com
to stop receiving future correspondence from us please email remfi...@gmx.com
--
To
On Wed, May 19, 2010 at 2:04 AM, Aurelien Jarno aurel...@aurel32.net wrote:
The idea is nice, but would it be possible to hold this on a week-end,
I personally won't be able to attend such thing on a day week.
Or maybe holding that on two days: friday and saturday so that people
can
On Mon, May 17, 2010 at 08:43:33AM -0400, Joerg Roedel wrote:
these two patches implement the workaround for AMD Erratum 383 into KVM.
This is necessary to prevent the host to crash if a guest triggers the
erratum.
For details on the erratum please see page 96 of
On 05/18/2010 08:45 PM, Jamie Lokier wrote:
Natalia Portillo wrote:
Hi,
- We'll try to migrate as many confirmable bugs from the Source Forge tracker
to Launchpad.
I think that part of the bug day should also include retesting OSes that appear
in OS Support List as having
Anthony Liguori wrote:
[]
For the Bug Day, anything is interesting IMHO. My main interest is to
get as many people involved in testing and bug fixing as possible. If
folks are interested in testing specific things like unusual or older
OSes, I'm happy to see it!
Well, interesting or not,
On 05/19/2010 08:19 AM, Michael Tokarev wrote:
Anthony Liguori wrote:
[]
For the Bug Day, anything is interesting IMHO. My main interest is to
get as many people involved in testing and bug fixing as possible. If
folks are interested in testing specific things like unusual or older
OSes,
On 05/19/2010 12:04 AM, Aurelien Jarno wrote:
On Tue, May 18, 2010 at 05:38:27PM -0500, Anthony Liguori wrote:
Hi,
In an effort to improve the 0.13 release quality, I'd like to host a
Bug Day on June 1st, 2010. I've setup a quick wiki page with some
more info
Hi,
There have been reports of several legacy OSes being unable to install
or boot in the newer qemu while working in the older one. They're
probably not in the OS Support List though. Are they effectively
uninteresting for the purpose of the 0.13 release?
For the Bug Day, anything
Hi,
There are a couple of.
The majority of them are because SeaBIOS not behaving like real hardware
should and must do.
If you know any OS that's not in the OS Support List and is broken please
commit.
If something is broken, please file a bug against it. The OS Support List is
a
On Tue, 18 May 2010 17:38:27 -0500
Anthony Liguori aligu...@linux.vnet.ibm.com wrote:
Hi,
In an effort to improve the 0.13 release quality, I'd like to host a Bug
Day on June 1st, 2010. I've setup a quick wiki page with some more info
(http://wiki.qemu.org/BugDay/June2010).
Tuesday is
Michael Tokarev wrote:
Anthony Liguori wrote:
[]
For the Bug Day, anything is interesting IMHO. My main interest is to
get as many people involved in testing and bug fixing as possible. If
folks are interested in testing specific things like unusual or older
OSes, I'm happy to see it!
On 05/19/2010 03:03 PM, Joerg Roedel wrote:
On Mon, May 17, 2010 at 08:43:33AM -0400, Joerg Roedel wrote:
these two patches implement the workaround for AMD Erratum 383 into KVM.
This is necessary to prevent the host to crash if a guest triggers the
erratum.
For details on the erratum
On 05/18/2010 08:47 PM, Avi Kivity wrote:
On 05/18/2010 05:21 AM, Michael S. Tsirkin wrote:
With PUBLISH_USED_IDX, guest tells us which used entries
it has consumed. This can be used to reduce the number
of interrupts: after we write a used entry, if the guest has not yet
consumed the previous
On 05/17/2010 12:37 PM, Avi Kivity wrote:
On 05/17/2010 12:08 PM, Sheng Yang wrote:
Change from v1:
Use unlazy_fpu() to handle host FPU, avoiding save/restore of host
FPU states.
Looks good, will wait a bit for more reviews and apply.
Now applied. Thanks.
--
Do not meddle in the
On 05/15/2010 01:51 PM, Xiao Guangrong wrote:
Split kvm_sync_page() into kvm_sync_page() and kvm_sync_page_transient()
to clarify the code address Avi's suggestion
kvm_sync_page_transient() function only update shadow page but not mark
it sync and not write protect sp-gfn. it will be used by
On 05/19/2010 12:57 PM, Udo Lembke wrote:
Jan Kiszka schrieb:
...
--enable-io-thread?
If you had it disabled, it would also answer my question if -smp works
without problems without that feature.
Jan
Hi,
i have a dumb question: what is the --enable-io-thread? Is this a
kvm-switch?
It's a
On 05/19/2010 12:23 PM, Teck Choon Giam wrote:
On Sun, May 16, 2010 at 7:52 PM, Avi Kivitya...@redhat.com wrote:
On 05/15/2010 04:19 AM, Teck Choon Giam wrote:
Hi,
Anyone encountered the same issue as me about system_powerdown no
longer working since upgraded to qemu-kvm 0.12.4?
On 05/19/2010 11:33 AM, Riccardo wrote:
This is a multi-part message in MIME format.
Hi,
I have a server dual xeon quad core with gentoo and qemu:
app-emulation/qemu-kvm-0.12.3-r1 USE=aio gnutls ncurses sasl vde -alsa
-bluetooth -curl -esd -fdt -hardened -kvm-trace -pulseaudio -qemu-ifup -sdl
On 05/19/2010 11:34 AM, Sheng Yang wrote:
From: Dexuan Cuidexuan@intel.com
Enable XSAVE/XRSTORE for guest.
Change from V1:
1. Use FPU API.
2. Fix CPUID issue.
3. Save/restore all possible guest xstate fields when switching. Because we
don't know which fields guest has already touched.
On 05/19/2010 11:34 AM, Sheng Yang wrote:
Signed-off-by: Sheng Yangsh...@linux.intel.com
---
target-i386/cpuid.c | 32
Can send to Anthony directly, while tcg doesn't support xsave/ymm, all
the code here is generic.
1 files changed, 32
On 05/19/2010 09:52 AM, Luiz Capitulino wrote:
On Tue, 18 May 2010 17:38:27 -0500
Anthony Liguorialigu...@linux.vnet.ibm.com wrote:
Hi,
In an effort to improve the 0.13 release quality, I'd like to host a Bug
Day on June 1st, 2010. I've setup a quick wiki page with some more info
On 05/18/2010 05:29 PM, Chris Wright wrote:
sourceforge bug tracker...
- sucks
- unclear if there's active triage
- anthony prefers the launchpad instance
Kernel bugs can go to bugzilla.kernel.org. Of course it isn't always
clear if a bug is a kernel or qemu bug. Recommend we ask users
On 05/18/2010 04:19 AM, Michael S. Tsirkin wrote:
With PUBLISH_USED_IDX, guest tells us which used entries
it has consumed. This can be used to reduce the number
of interrupts: after we write a used entry, if the guest has not yet
consumed the previous entry, or if the guest has already consumed
On 05/19/2010 04:46 PM, Harald Dunkel wrote:
Hi folks,
Please post kvm issues to the kvm mailing list.
I am trying to run Solaris 10u8 as a guest in kvm (kernel
2.6.33.2). Problem: The virtual network devices don't work
with this Solaris version.
e1000 and pcnet work just by chance, as
Am 19.05.2010 um 18:25 schrieb Avi Kivity a...@redhat.com:
On 05/19/2010 11:33 AM, Riccardo wrote:
This is a multi-part message in MIME format.
Hi,
I have a server dual xeon quad core with gentoo and qemu:
app-emulation/qemu-kvm-0.12.3-r1 USE=aio gnutls ncurses sasl vde -
alsa
-bluetooth
When libvirt launches a guest it first chowns the relevenat
/sys/bus/pci/.../config file for an assigned device then drops privileges.
This causes an issue for device assignment because despite being file
owner, the sysfs config space file checks for CAP_SYS_ADMIN before
allowing access to device
On Wed, 2010-05-19 at 12:00 -0700, Chris Wright wrote:
When libvirt launches a guest it first chowns the relevenat
/sys/bus/pci/.../config file for an assigned device then drops privileges.
This causes an issue for device assignment because despite being file
owner, the sysfs config space
On 05/19/2010 02:00 PM, Chris Wright wrote:
When libvirt launches a guest it first chowns the relevenat
/sys/bus/pci/.../config file for an assigned device then drops privileges.
This causes an issue for device assignment because despite being file
owner, the sysfs config space file checks for
Hi,
this patch is a block driver for the distributed file system Ceph
(http://ceph.newdream.net/). Ceph was included in the Linux v2.6.34
kernel. However, this driver uses librados (which is part of the Ceph
server) for direct access to the Ceph object store and is running entirely
in userspace.
The attached patch is a block driver for the distributed file system
Ceph (http://ceph.newdream.net/). This driver uses librados (which
is part of the Ceph server) for direct access to the Ceph object
store and is running entirely in userspace. Therefore it is
called rbd - rados block device.
To
19.05.2010 21:09, Avi Kivity wrote:
On 05/19/2010 04:46 PM, Harald Dunkel wrote:
I am trying to run Solaris 10u8 as a guest in kvm (kernel
2.6.33.2). Problem: The virtual network devices don't work
with this Solaris version.
e1000 and pcnet work just by chance, as it seems. I can ping
the
On 05/19/2010 03:20 AM, Christoph Hellwig wrote:
On Tue, May 18, 2010 at 08:52:36AM -0500, Anthony Liguori wrote:
This should be filed in launchpad as a qemu bug and it should be tested
against the latest git. This bug sounds like we're using an int to
represent sector offset somewhere but
Avi Kivity schrieb:
On 05/19/2010 12:57 PM, Udo Lembke wrote:
Jan Kiszka schrieb:
...
--enable-io-thread?
If you had it disabled, it would also answer my question if -smp works
without problems without that feature.
Jan
Hi,
i have a dumb question: what is the --enable-io-thread? Is this a
* Anthony Liguori (anth...@codemonkey.ws) wrote:
An fd as a qdev property seems like a bad idea to me.
What is your concern?
I'm not sure I have a better suggestion though.
Anything else requires inventing some new commandline options and monitor
comnmands (-pcidevice anyone? ;-). I'm not
The vmexit handler returns KVM_EXIT_UNKNOWN since there is no handler
for vmentry failures. This intercepts vmentry failures and returns
KVM_FAIL_ENTRY to userspace instead.
Signed-off-by: Mohammed Gamal m.gamal...@gmail.com
---
arch/x86/kvm/vmx.c |7 +++
1 files changed, 7
This patch address bug report in https://bugs.launchpad.net/qemu/+bug/530077.
Failed vmentries were handled with handle_unhandled() which prints a rather
unfriendly message to the user. This patch separates handling vmentry failures
from unknown exit reasons and prints a friendly message to the
On 05/19/2010 04:10 PM, Chris Wright wrote:
* Anthony Liguori (anth...@codemonkey.ws) wrote:
An fd as a qdev property seems like a bad idea to me.
What is your concern?
qdev properties are supposed to represent device tunables. A file
descriptor is not a tunable.
It's like
On 05/19/2010 04:16 PM, Mohammed Gamal wrote:
This patch address bug report in https://bugs.launchpad.net/qemu/+bug/530077.
Failed vmentries were handled with handle_unhandled() which prints a rather
unfriendly message to the user. This patch separates handling vmentry failures
from unknown
* Anthony Liguori (anth...@codemonkey.ws) wrote:
On 05/19/2010 04:10 PM, Chris Wright wrote:
* Anthony Liguori (anth...@codemonkey.ws) wrote:
An fd as a qdev property seems like a bad idea to me.
What is your concern?
qdev properties are supposed to represent device tunables. A file
On 05/19/2010 04:59 PM, Chris Wright wrote:
I'm not sure I have a better suggestion though.
Anything else requires inventing some new commandline options and monitor
comnmands (-pcidevice anyone? ;-). I'm not sure the benefit, esp with
hopes of moving to uio.
Yeah, I think
From: Jan Kiszka jan.kis...@siemens.com
Guest debugging under KVM is currently broken once io-threads are
enabled. Easily fixable by switching the fake on_vcpu to the real
run_on_cpu implementation.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
kvm-all.c | 12 +---
1 files
On 05/19/2010 05:29 PM, Andre Przywara wrote:
Michael Tokarev wrote:
...
Also, thanks to Andre Przywara, whole winNT thing works but it requires
-cpu qemu64,level=1 (or level=2 or =3), -- _not_ with default CPU. This
is also testing, but it's not obvious what to do witht the result...
Can't
On Wed, May 19, 2010 at 08:04:51PM +0300, Avi Kivity wrote:
On 05/18/2010 04:19 AM, Michael S. Tsirkin wrote:
With PUBLISH_USED_IDX, guest tells us which used entries
it has consumed. This can be used to reduce the number
of interrupts: after we write a used entry, if the guest has not yet
On Wed, May 19, 2010 at 11:06:42AM +0300, Avi Kivity wrote:
On 05/19/2010 10:39 AM, Rusty Russell wrote:
I think we're talking about the last 2 entries of the avail ring. That means
the worst case is 1 false bounce every time around the ring.
It's low, but why introduce an inefficiency when
* Mohammed Gamal m.gamal...@gmail.com [2010-05-19 16:17]:
This patch address bug report in https://bugs.launchpad.net/qemu/+bug/530077.
Failed vmentries were handled with handle_unhandled() which prints a rather
unfriendly message to the user. This patch separates handling vmentry failures
On Thu, May 20, 2010 at 4:28 AM, Ryan Harper ry...@us.ibm.com wrote:
* Mohammed Gamal m.gamal...@gmail.com [2010-05-19 16:17]:
This patch address bug report in
https://bugs.launchpad.net/qemu/+bug/530077.
Failed vmentries were handled with handle_unhandled() which prints a rather
Hello,
I'm trying to track down a bug I'm observing in a branched version of
kvm I'm using for research. I'm hoping someone might be able to point
me int to the right direction as I haven't had any luck with it on my
own. Here are the details:
I have made some changes to kvm that enable
This patch address bug report in https://bugs.launchpad.net/qemu/+bug/530077.
Failed vmentries were handled with handle_unhandled() which prints a rather
unfriendly message to the user. This patch separates handling vmentry failures
from unknown exit reasons and prints a friendly message to the
Hi folks,
Autotest 0.12.0 is almost ready, due to be released in a few days
http://autotest.kernel.org/milestone/0.12.0
I rolled out some pre-release tarballs that can be found on
http://test.kernel.org/releases/0.12.0-rc1/
If you want to test it to see what it looks like, be my guest and
On Thu, 20 May 2010 07:57:18 am Michael S. Tsirkin wrote:
On Wed, May 19, 2010 at 08:04:51PM +0300, Avi Kivity wrote:
On 05/18/2010 04:19 AM, Michael S. Tsirkin wrote:
With PUBLISH_USED_IDX, guest tells us which used entries
it has consumed. This can be used to reduce the number
of
On Wed, 19 May 2010 05:36:42 pm Avi Kivity wrote:
Note that this is a exclusive-shared-exclusive bounce only, too.
A bounce is a bounce.
I tried to measure this to show that you were wrong, but I was only able
to show that you're right. How annoying. Test code below.
Virtio is
On Thu, 20 May 2010 02:31:50 pm Rusty Russell wrote:
On Wed, 19 May 2010 05:36:42 pm Avi Kivity wrote:
Note that this is a exclusive-shared-exclusive bounce only, too.
A bounce is a bounce.
I tried to measure this to show that you were wrong, but I was only able
to show that
This patch enables protocol drivers to use their create options which
are not supported by the format. For example, protcol drivers can use
a backing_file option with raw format.
Signed-off-by: MORITA Kazutaka morita.kazut...@lab.ntt.co.jp
---
block.c |7 +++
block.h |1
Hi, Folks:
Could you provide pointer to the kvm device passthrough howto/FAQ?
I have two questions:
1. my host os, the Linux doesn't have the native device driver for some home
grown pci devices, the driver is in the guest os, does device passthrough work
in this case? Assuming I have VT-d.
20.05.2010 02:30, Anthony Liguori wrote:
On 05/19/2010 05:29 PM, Andre Przywara wrote:
Michael Tokarev wrote:
...
Also, thanks to Andre Przywara, whole winNT thing works but it requires
-cpu qemu64,level=1 (or level=2 or =3), -- _not_ with default CPU. This
[]
It'd be nice if we had more
On 05/18/2010 10:34 AM, Jean Delvare wrote:
kvmppc_e500_exit() is a module_exit function, so it should be tagged
with __exit, not __init. The incorrect annotation was added by commit
2986b8c72c272ea58edd37903b042c6da985627d.
Applied, thanks.
--
Do not meddle in the internals of kernels,
80 matches
Mail list logo
