Hi,
>> Well, we also want to clean up the registers, so how about:
>>
>> BAR0: legacy, as is. If you access this, don't use the others.
Ok.
>> BAR1: new format virtio-pci layout. If you use this, don't use BAR0.
>> BAR2: virtio-cfg. If you use this, don't use BAR0.
Why use two bars for thi
The Buildbot has detected a new failure on builder next-ia64 while building kvm.
Full details are available at:
http://buildbot.b1-systems.de/kvm/builders/next-ia64/builds/673
Buildbot URL: http://buildbot.b1-systems.de/kvm/
Buildslave for this Build: b1_kvm_1
Build Reason: The Nightly schedule
Paolo Bonzini writes:
> Il 05/10/2012 07:43, Rusty Russell ha scritto:
>> That's good. But virtio_blk's scsi command is insoluble AFAICT. As I
>> said to Anthony, the best rules are "always" and "never", so I'd really
>> rather not have to grandfather that in.
>
> It is, but we can add a rule th
Another thing should be concerned:
when I attach another disk after a disk attached but cannot found in guest,
the TWO disks all appear in guest!
Oct 9 10:45:24 debian kernel: [61068.049509] pci :00:11.0: [1af4:1001]
type 0 class 0x000100
Oct 9 10:45:24 debian kernel: [61068.049715] pci 000
The Buildbot has detected a new failure on builder ia64 while building kvm.
Full details are available at:
http://buildbot.b1-systems.de/kvm/builders/ia64/builds/688
Buildbot URL: http://buildbot.b1-systems.de/kvm/
Buildslave for this Build: b1_kvm_1
Build Reason: The Nightly scheduler named 'n
Hi all,
I got a issue when attach disk to a qemu-kvm guest(kernel version: Linux debian
3.2.0-3-amd64 #1 SMP Thu Jun 28 09:07:26 UTC 2012 x86_64 GNU/Linux)
The steps are:
1. using libvirt API start a guest
2. 'ping' the IP address of the guest once each time
3. when 'ping' return OK, I attach a IS
Anthony Liguori writes:
> We'll never remove legacy so we shouldn't plan on it. There are
> literally hundreds of thousands of VMs out there with the current virtio
> drivers installed in them. We'll be supporting them for a very, very
> long time :-)
You will be supporting this for qemu on x86
Rusty Russell writes:
> Anthony Liguori writes:
>> Gerd Hoffmann writes:
>>
>>> Hi,
>>>
> So we could have for virtio something like this:
>
> Capabilities: [??] virtio-regs:
> legacy: BAR=0 offset=0
> virtio-pci: BAR=1 offset=1000
>
Hi,
Actually, I know that disabling EPT would work. But thank U anyway.
What I interesting in is why would it fail when EPT is enable.
Thank U for answering.
2012/10/9 Marcelo Tosatti :
> On Mon, Oct 08, 2012 at 04:15:57PM +0800, R wrote:
>> Hi,
>>
>> I am a student. And my teacher told me to mo
Change existing kernel error message to include return value from
iommu_attach_device() when it fails. This will help debug device
assignment failures more effectively.
Signed-off-by: Shuah Khan
---
virt/kvm/iommu.c |6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/virt
Anthony Liguori writes:
> Gerd Hoffmann writes:
>
>> Hi,
>>
So we could have for virtio something like this:
Capabilities: [??] virtio-regs:
legacy: BAR=0 offset=0
virtio-pci: BAR=1 offset=1000
virtio-cfg: BAR
On 09/30/2012 04:59 AM, Fengguang Wu wrote:
On Sun, Sep 30, 2012 at 01:32:46PM +0200, Avi Kivity wrote:
On 09/30/2012 01:23 PM, Fengguang Wu wrote:
On Sun, Sep 30, 2012 at 01:10:55PM +0200, Avi Kivity wrote:
On 09/28/2012 05:35 AM, Paul E. McKenney wrote:
On Thu, Sep 27, 2012 at 12:40:44PM +0
On Mon, Oct 8, 2012 at 6:04 AM, Dave Martin wrote:
> On Fri, Oct 05, 2012 at 10:00:25AM +0100, Russell King - ARM Linux wrote:
>> On Mon, Oct 01, 2012 at 01:53:26PM +0100, Dave Martin wrote:
>> > A good starting point would be load/store emulation as this seems to be a
>> > common theme, and we wo
On 10/08/2012 04:01:11 PM, Alexander Graf wrote:
On 08.10.2012, at 22:45, Scott Wood wrote:
> On 10/07/2012 08:30:06 AM, Alexander Graf wrote:
>> On 07.10.2012, at 15:26, Avi Kivity wrote:
>> > The downside of this generic approach is that it prepares
suprises down
>> > the road. The alterna
On 08.10.2012, at 22:45, Scott Wood wrote:
> On 10/07/2012 08:30:06 AM, Alexander Graf wrote:
>> On 07.10.2012, at 15:26, Avi Kivity wrote:
>> > The downside of this generic approach is that it prepares suprises down
>> > the road. The alternative approach, of adding a new KVM_EXIT_RESET,
>> > a
Gerd Hoffmann writes:
> Hi,
>
>>> So we could have for virtio something like this:
>>>
>>> Capabilities: [??] virtio-regs:
>>> legacy: BAR=0 offset=0
>>> virtio-pci: BAR=1 offset=1000
>>> virtio-cfg: BAR=1 offset=1800
>>
>> This would be
On 08.10.2012, at 22:50, Scott Wood wrote:
> On 10/07/2012 08:58:02 AM, Alexander Graf wrote:
>> diff --git a/arch/powerpc/kvm/bookehv_interrupts.S
>> b/arch/powerpc/kvm/bookehv_interrupts.S
>> index 099fe82..4421293 100644
>> --- a/arch/powerpc/kvm/bookehv_interrupts.S
>> +++ b/arch/powerpc/kvm
On 10/07/2012 08:58:02 AM, Alexander Graf wrote:
diff --git a/arch/powerpc/kvm/bookehv_interrupts.S
b/arch/powerpc/kvm/bookehv_interrupts.S
index 099fe82..4421293 100644
--- a/arch/powerpc/kvm/bookehv_interrupts.S
+++ b/arch/powerpc/kvm/bookehv_interrupts.S
@@ -23,7 +23,6 @@
#include
#includ
On 10/07/2012 08:30:06 AM, Alexander Graf wrote:
On 07.10.2012, at 15:26, Avi Kivity wrote:
> The downside of this generic approach is that it prepares suprises
down
> the road. The alternative approach, of adding a new KVM_EXIT_RESET,
> avoids this minefield, but requires ABI changes every
On Thu, Oct 04, 2012 at 01:04:56PM +0930, Rusty Russell wrote:
> Anthony Liguori writes:
> > Rusty Russell writes:
> >
> >> "Michael S. Tsirkin" writes:
> >>
> >>> Thinking about Sasha's patches, we can reduce ring usage
> >>> for virtio net small packets dramatically if we put
> >>> virtio net
Hi,
>> So we could have for virtio something like this:
>>
>> Capabilities: [??] virtio-regs:
>> legacy: BAR=0 offset=0
>> virtio-pci: BAR=1 offset=1000
>> virtio-cfg: BAR=1 offset=1800
>
> This would be a vendor specific PCI capability so
Yes, that is in the host, but in the guest I always see "steal time"
=0. I checked through /proc/stat, mpstat, top, vmstat.
Not sure, why the steal time information is not getting propagated to
the guest.
Thanks,
Abhishek
On Mon, Oct 8, 2012 at 3:02 PM, Marcelo Tosatti wrote:
> On Mon, Oct 08,
On Mon, Oct 08, 2012 at 02:47:59PM -0500, Abhishek Gupta wrote:
> I think this flag is enabled since I see that there is some information
>
> cat /proc/schedstat
This is in the host? Then, yes, the host has schedstat enabled.
Definition of steal time: the amount of time in which this vCPU did no
I think this flag is enabled since I see that there is some information
cat /proc/schedstat
version 15
timestamp 4332448322
cpu0 12 0 65142011 32031105 32750248 22717261 2447620065997 58787405876 32964108
domain0 ,,,,,,,0005
3254935 3249
Thanks for the answer. I am more of an application user. Is there a
quick way to check this flag and enable it if its disabled?
Abhishek
On Mon, Oct 8, 2012 at 2:39 PM, Marcelo Tosatti wrote:
> On Mon, Oct 08, 2012 at 02:55:25AM -0500, Abhishek Gupta wrote:
>> Hi,
>>
>> I am trying to get the st
On Wed, Oct 03, 2012 at 04:14:17PM +0930, Rusty Russell wrote:
> "Michael S. Tsirkin" writes:
>
> > Thinking about Sasha's patches, we can reduce ring usage
> > for virtio net small packets dramatically if we put
> > virtio net header inline with the data.
> > This can be done for free in case gu
On Mon, Oct 08, 2012 at 02:55:25AM -0500, Abhishek Gupta wrote:
> Hi,
>
> I am trying to get the steal time with 2 VMs (each with 1 Vcpu) pinned
> to same core.
>
> While finding documentation on this, I came across your patches and
> posts related to the implementation of this feature, so I thou
On Fri, Oct 05, 2012 at 06:22:58AM -0600, David Torres wrote:
> Hi all,
>
> My name is David Torres, I am from Costa Rica. See this is the problem I have
> with the KVM instalation:
>
> 2012-10-03 20:28:17.395+: 25793: warning : qemuCapsInit:856 : Failed to
> get host power management capab
On Mon, Oct 08, 2012 at 04:15:57PM +0800, R wrote:
> Hi,
>
> I am a student. And my teacher told me to monitor every process in guest.
> So, I try to intercept every Cr3 access. However, if kvm is loaded
> with EPT enable, Acesses to Cr3 would not cause VM-exit.
Disable EPT by loading kvm-intel
On Wed, Sep 19, 2012 at 05:44:46PM +, Auld, Will wrote:
> >From 9982bb73460b05c1328068aae047b14b2294e2da Mon Sep 17 00:00:00 2001
> From: Will Auld
> Date: Wed, 12 Sep 2012 18:10:56 -0700
> Subject: [PATCH] Enabling IA32_TSC_ADJUST for guest VM
>
> CPUID.7.0.EBX[1]=1 indicates IA32_TSC_ADJUS
On Thu, Sep 20, 2012 at 07:43:08AM +0200, Jan Kiszka wrote:
> From: Jan Kiszka
>
> There are no external callers of this function as there is no concept of
> resetting a vcpu from generic code.
>
> Signed-off-by: Jan Kiszka
Applied, thanks.
--
To unsubscribe from this list: send the line "uns
On Thu, Sep 20, 2012 at 07:43:17AM +0200, Jan Kiszka wrote:
> From: Jan Kiszka
>
> No users outside of kvm/x86.c.
>
> Signed-off-by: Jan Kiszka
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordo
Gerd Hoffmann writes:
> Hi,
>
>> But I think we could solve this in a different way. I think we could
>> just move the virtio configuration space to BAR1 by using a transport
>> feature bit.
>
> Why hard-code stuff?
>
> I think it makes alot of sense to have a capability simliar to msi-x
> whi
Hi,
> But I think we could solve this in a different way. I think we could
> just move the virtio configuration space to BAR1 by using a transport
> feature bit.
Why hard-code stuff?
I think it makes alot of sense to have a capability simliar to msi-x
which simply specifies bar and offset of
Hi!
I have connected my kvm guest using a macvtap interface and configured a
macvlan interface in bridge mode on the host to allow host to guest
communication.
If using virtio_net in the guest, host to guest transfer works fine. But
in guest to host direction large tcp segments do not arrive at t
On 08.10.2012, at 16:03, Andreas Färber wrote:
> Am 05.10.2012 04:24, schrieb Alexander Graf:
>>
>> On 05.10.2012, at 04:17, Anthony Liguori wrote:
>>
>>> Alexander Graf writes:
>>>
On 03.10.2012, at 22:26, Peter Maydell wrote:
> On 3 October 2012 21:01, Blue Swirl wrote:
Am 05.10.2012 04:24, schrieb Alexander Graf:
>
> On 05.10.2012, at 04:17, Anthony Liguori wrote:
>
>> Alexander Graf writes:
>>
>>> On 03.10.2012, at 22:26, Peter Maydell wrote:
>>>
On 3 October 2012 21:01, Blue Swirl wrote:
> On Mon, Oct 1, 2012 at 4:20 PM, Anthony Liguori
> wro
Rusty Russell writes:
> (Topic updated, cc's trimmed).
>
> Anthony Liguori writes:
>> Rusty Russell writes:
>>> 4) The only significant change to the spec is that we use PCI
>>>capabilities, so we can have infinite feature bits.
>>>(see
>>> http://lists.linuxfoundation.org/pipermail/vi
On 08.10.2012, at 15:06, Caraman Mihai Claudiu-B02008 wrote:
>> -Original Message-
>> From: Alexander Graf [mailto:ag...@suse.de]
>> Sent: Monday, October 08, 2012 1:11 PM
>> To: Caraman Mihai Claudiu-B02008
>> Cc: kvm-...@vger.kernel.org; kvm@vger.kernel.org; linuxppc-
>> d...@lists.ozla
> -Original Message-
> From: Alexander Graf [mailto:ag...@suse.de]
> Sent: Monday, October 08, 2012 1:11 PM
> To: Caraman Mihai Claudiu-B02008
> Cc: kvm-...@vger.kernel.org; kvm@vger.kernel.org; linuxppc-
> d...@lists.ozlabs.org; qemu-...@nongnu.org
> Subject: Re: [Qemu-ppc] [RFC PATCH 05/1
On (Sun) 30 Sep 2012 [21:50:07], Amos Kong wrote:
> - Original Message -
> > On Thu, Sep 20, 2012 at 09:46:41AM -0300, Marcelo Tosatti wrote:
> > > On Thu, Sep 20, 2012 at 01:55:20PM +0530, Amit Shah wrote:
> > > > Commit f349c12c0434e29c79ecde89029320c4002f7253 added the guest
> > > > stop
On (Sun) 30 Sep 2012 [20:05:16], Marcelo Tosatti wrote:
> On Thu, Sep 20, 2012 at 09:46:41AM -0300, Marcelo Tosatti wrote:
> > On Thu, Sep 20, 2012 at 01:55:20PM +0530, Amit Shah wrote:
> > > Commit f349c12c0434e29c79ecde89029320c4002f7253 added the guest stop
> > > notification, but it did it in a
On 05.07.2012, at 13:14, Caraman Mihai Claudiu-B02008 wrote:
>
>
>> -Original Message-
>> From: Alexander Graf [mailto:ag...@suse.de]
>> Sent: Wednesday, July 04, 2012 4:50 PM
>> To: Caraman Mihai Claudiu-B02008
>> Cc: kvm-...@vger.kernel.org; kvm@vger.kernel.org; linuxppc-
>> d...@list
On Fri, Oct 05, 2012 at 10:00:25AM +0100, Russell King - ARM Linux wrote:
> On Mon, Oct 01, 2012 at 01:53:26PM +0100, Dave Martin wrote:
> > A good starting point would be load/store emulation as this seems to be a
> > common theme, and we would need a credible deployment for any new
> > framework
Hi,
I am trying to get the steal time with 2 VMs (each with 1 Vcpu) pinned
to same core.
While finding documentation on this, I came across your patches and
posts related to the implementation of this feature, so I thought it
would be best to ask you.
I run the same application on these 2 VMs si
45 matches
Mail list logo