On Tue, Oct 30, 2012 at 9:48 PM, Wen Congyang wrote:
> At 10/31/2012 09:12 AM, Marcelo Tosatti Wrote:
>> It has been asked earlier why a simple virtio device is not usable
>> for this (with no response IIRC).
>
> 1. We can't use virtio device when the kernel is booting.
So the issue here is the s
On 08/29/2012 07:18 AM, Wen Congyang wrote:
> We can know the guest is panicked when the guest runs on xen.
> But we do not have such feature on kvm.
>
> Another purpose of this feature is: management app(for example:
> libvirt) can do auto dump when the guest is panicked. If management
> app does
On 08/30/2012 04:03 AM, Wen Congyang wrote:
> At 08/29/2012 07:56 PM, Sasha Levin Wrote:
>> On 08/29/2012 07:18 AM, Wen Congyang wrote:
>>> diff --git a/Documentation/virtual/kvm/pv_event.txt
>>> b/Documentation/virtual/kvm/pv_event.txt
>>> new file mo
On Fri, 2012-01-06 at 07:37 +, Zhang, Yang Z wrote:
> Please refer the patch zero for the description.
Each patch should have description about what it does in the changelog,
otherwise you're going to lose important information about the change.
Furthermore, cover letters don't get merged at
Hi,
On Mon, 2011-05-30 at 13:09 +0800, Zhi Yong Wu wrote:
> Hello, all,
>
> I have prepared to work on a feature called "Disk I/O limits" for
> qemu-kvm projeect.
> This feature will enable the user to cap disk I/O amount performed by a
> VM.It is important for some storage resources to
On Thu, 2011-06-02 at 14:29 +0800, Zhi Yong Wu wrote:
> On Thu, Jun 02, 2011 at 09:17:06AM +0300, Sasha Levin wrote:
> >Date: Thu, 02 Jun 2011 09:17:06 +0300
> >From: Sasha Levin
> >To: Zhi Yong Wu
> >Cc: qemu-devel@nongnu.org, k...@vger.kernel.org, kw...@redhat.com,
On Fri, 2011-08-12 at 09:55 +0800, Jason Wang wrote:
> From: Krishna Kumar
>
> Implement mq virtio-net driver.
>
> Though struct virtio_net_config changes, it works with the old
> qemu since the last element is not accessed unless qemu sets
> VIRTIO_NET_F_MULTIQUEUE.
>
> Signed-off-by: Krishna
[I've sent this patch couple of months ago and noticed it
didn't make it's way in - so I'm sending it again]
It is possible to create CPU-less NUMA nodes, node amount shouldn't be
limited by amount of CPUs.
Tested-by: Michael Roth
Signed-off-by: Sasha Levin
---
On Tue, Jul 19, 2011 at 11:51 PM, Anthony Liguori wrote:
> On 07/19/2011 11:10 AM, Avi Kivity wrote:
>>
>> On 07/19/2011 07:05 PM, Avi Kivity wrote:
>>>
>>> On 07/19/2011 05:50 PM, Anthony Liguori wrote:
>>
>> There's bits I don't like about the interface
>
> Which bits are th
On Tue, 2011-07-19 at 21:53 -0500, Anthony Liguori wrote:
> QEMU does use it and it's quite important. Coalesced MMIO is really
> about write caching MMIO exits. It only works with devices that have
> registers where writing has no side effects. Moreover, it only really
> works well when ther
On Mon, 2011-07-25 at 11:32 +0200, Alexander Graf wrote:
> On 25.07.2011, at 10:51, Avi Kivity wrote:
>
> > qemu_malloc() is type-unsafe as it returns a void pointer. Introduce
> > QEMU_NEW() (and QEMU_NEWZ()), which return the correct type.
>
> What does this buy you over
>
> type *x = qemu_ma
On Mon, Nov 7, 2011 at 12:23 PM, Gerd Hoffmann wrote:
> Hi,
>
>> It's not just about code, it's as much about culture and development process.
>
> Indeed. The BSDs have both kernel and the base system in a single
> repository. There are probably good reasons for (and against) it.
>
> In Linux w
Hi Anthony,
Thank you for your comments!
On Mon, 2011-11-07 at 11:37 -0600, Anthony Liguori wrote:
> On 11/06/2011 02:40 PM, Sasha Levin wrote:
> > Hi all,
> >
> > I'm planning on doing a small fork of the KVM tool to turn it into a
> > 'Secure KVM'
On Tue, Nov 8, 2011 at 4:52 PM, Christoph Hellwig wrote:
> On Tue, Nov 08, 2011 at 04:41:40PM +0200, Avi Kivity wrote:
>> On 11/06/2011 03:35 AM, Alexander Graf wrote:
>> > To quickly get going, just execute the following as user:
>> >
>> > $ ./Documentation/run-qemu.sh -r / -a init=/bin/bash
On Wed, 2011-11-09 at 20:00 +0200, Avi Kivity wrote:
> On 11/09/2011 07:56 PM, Anthony Liguori wrote:
> > On 11/09/2011 07:44 AM, Avi Kivity wrote:
> >> The fact that a host cpu supports a feature doesn't mean that QEMU
> >> and KVM
> >> will also support it, yet -cpuid host brings host features wh
Hi,
Currently when we run the guest we treat it as a black box, we're not
quite sure what it's going to start and whether it supports the same
features we expect it to support when running it from the host.
This forces us to start the guest with the safest defaults possible, for
example: '-drive
On Thu, 2011-08-25 at 08:32 +0100, Richard W.M. Jones wrote:
> On Thu, Aug 25, 2011 at 08:33:04AM +0300, Avi Kivity wrote:
> > On 08/25/2011 08:21 AM, Sasha Levin wrote:
> > >Hi,
> > >
> > >Currently when we run the guest we treat it as a black box, we'
Hello,
I am looking to implement an ivshmem device for KVM tools, the purpose
is to provide same functionality as QEMU and interoperability with QEMU.
Going through the spec (I found here:
https://gitorious.org/nahanni/guest-code/blobs/master/device_spec.txt )
and the code in QEMU I have gathered
On Thu, 2011-08-25 at 17:00 +0300, Avi Kivity wrote:
> On 08/25/2011 04:29 PM, Sasha Levin wrote:
> > 2. The spec describes DOORBELL as an array of DWORDs, when one guest
> > wants to poke a different guest it would write something into the offset
> > of the other guest
On Thu, 2011-08-25 at 17:40 +0300, Avi Kivity wrote:
> On 08/25/2011 05:39 PM, Sasha Levin wrote:
> > On Thu, 2011-08-25 at 17:00 +0300, Avi Kivity wrote:
> > > On 08/25/2011 04:29 PM, Sasha Levin wrote:
> > > > 2. The spec describes DOORBELL as an a
On Thu, 2011-08-25 at 16:48 -0500, Anthony Liguori wrote:
> On 08/25/2011 12:21 AM, Sasha Levin wrote:
> > Hi,
> >
> > Currently when we run the guest we treat it as a black box, we're not
> > quite sure what it's going to start and whether it supports the same
On Thu, 2011-08-25 at 16:25 +, Decker, Schorschi wrote:
> I would ask two things be done in the design if it goes forward, 1)
> have an explicit way to disable this feature, where the hypervisor
> cannot interact with the guest OS directly in any way if disablement
> is selected.
I doubt that
On Fri, 2011-08-26 at 09:04 +0100, Richard W.M. Jones wrote:
> On Fri, Aug 26, 2011 at 09:22:45AM +0300, Sasha Levin wrote:
> > On Thu, 2011-08-25 at 16:25 +, Decker, Schorschi wrote:
> > > 2) implement the feature as an agent in the guest OS where the
> > > hypervis
On Thu, 2011-08-25 at 16:29 +0300, Sasha Levin wrote:
> Hello,
>
> I am looking to implement an ivshmem device for KVM tools, the purpose
> is to provide same functionality as QEMU and interoperability with QEMU.
[snip]
> 1. File handles and guest IDs are passed between the
On Thu, 2011-09-01 at 16:09 +1000, David Gibson wrote:
> The virtio code already has memory barrier wmb() macros in the code.
> However they are was defined as no-ops. The comment claims that real
> barriers are not necessary because the code does not run concurrent.
> However, with kvm and io-thr
On Thu, 2011-09-01 at 10:37 +0300, Sasha Levin wrote:
> On Thu, 2011-09-01 at 16:09 +1000, David Gibson wrote:
> > The virtio code already has memory barrier wmb() macros in the code.
> > However they are was defined as no-ops. The comment claims that real
> > barriers are
c:170: failed to allocate
18446744073709529965 bytes"
This patch handles the case where the magic sig wasn't located in the
provided kernel, and loading it as multiboot failed as well.
Cc: Anthony Liguori
Signed-off-by: Sasha Levin
---
hw/pc.c |8 +++-
1 files changed, 7 insertions(+), 1
Ping?
On Sat, 2011-09-03 at 22:35 +0300, Sasha Levin wrote:
> When providing QEMU with a bad '-kernel' parameter, such as a file which
> is not really a kernel, QEMU will attempt to allocate a huge amount of
> memory and fail either with "Failed to allocate memory: Cannot
On Mon, Nov 5, 2012 at 8:58 PM, Hu Tao wrote:
> But in the case of panic notification, more dependency means more
> chances of failure of panic notification. Say, if we use a virtio device
> to do panic notification, then we will fail if: virtio itself has
> problems, virtio for some reason can't
On 02/28/2013 04:22 AM, Cornelia Huck wrote:
> Currently, eventfd introduces module_init/module_exit functions
> to initialize/cleanup the irqfd workqueue. This only works, however,
> if no other module_init/module_exit functions are built into the
> same module.
>
> Let's just move the initializa
This allows the user to add custom parameters to the up or down
scripts.
Cc: Anthony Liguori
Signed-off-by: Sasha Levin
---
net.c |8
net/tap.c | 37 ++---
2 files changed, 38 insertions(+), 7 deletions(-)
diff --git a/net.c b/net.c
index
On Thu, 2011-09-29 at 17:20 +0200, Jan Kiszka wrote:
> On 2011-09-29 16:40, Thomas Jung wrote:
> > On 2011-09-29 16:11 jan kiszka wrote
> >> What kind of parameters would you want to pass? Something that tells VMs
> >> apart (which can be solved without these extensions) or more?
> >>
> >> Jan
> >
This allows the user to add custom parameters to the up or down
scripts.
Extra parameters are useful in more complex networking scenarios
where we would like to configure network devices when starting
or stopping the guest.
Cc: Anthony Liguori
Signed-off-by: Sasha Levin
---
net.c |8
On Fri, 2011-10-14 at 17:51 +0800, Lai Jiangshan wrote:
> Currently, NMI interrupt is blindly sent to all the vCPUs when NMI
> button event happens. This doesn't properly emulate real hardware on
> which NMI button event triggers LINT1. Because of this, NMI is sent to
> the processor even when LINT
On Thu, 2011-11-17 at 16:36 +0200, Avi Kivity wrote:
> On 11/14/2011 05:56 AM, zanghongy...@huawei.com wrote:
> > From: Hongyong Zang
> >
> > Ivshmem(nahanni) is a mechanism for sharing host memory with VMs running on
> > the same host. Currently, guest notifies qemu by reading or writing ivshmem
On 07/21/2012 09:12 AM, Wen Congyang wrote:
> +#define KVM_PV_PORT (0x505UL)
> +
> #ifdef __KERNEL__
> #include
>
> @@ -221,6 +223,11 @@ static inline void kvm_disable_steal_time(void)
> }
> #endif
>
> +static inline unsigned int kvm_arch_pv_features(void)
> +{
> + return inl(KVM_PV_P
On 07/21/2012 10:44 AM, Wen Congyang wrote:
> We can know the guest is panicked when the guest runs on xen.
> But we do not have such feature on kvm.
>
> Another purpose of this feature is: management app(for example:
> libvirt) can do auto dump when the guest is panicked. If management
> app does
On 07/22/2012 09:14 PM, Anthony Liguori wrote:
> Sasha Levin writes:
>
>> On 07/21/2012 10:44 AM, Wen Congyang wrote:
>>> We can know the guest is panicked when the guest runs on xen.
>>> But we do not have such feature on kvm.
>>>
>>> Anothe
On 07/22/2012 09:22 PM, Anthony Liguori wrote:
> Sasha Levin writes:
>
>> On 07/21/2012 09:12 AM, Wen Congyang wrote:
>>> +#define KVM_PV_PORT(0x505UL)
>>> +
>>> #ifdef __KERNEL__
>>> #include
>>>
>>> @
On 07/22/2012 10:19 PM, Sasha Levin wrote:
> On 07/22/2012 09:22 PM, Anthony Liguori wrote:
>> Sasha Levin writes:
>>
>>> On 07/21/2012 09:12 AM, Wen Congyang wrote:
>>>> +#define KVM_PV_PORT (0x505UL)
>>>> +
>>>> #ifdef __KERN
On 07/23/2012 12:29 AM, Anthony Liguori wrote:
> Sasha Levin writes:
>
>> On 07/22/2012 10:19 PM, Sasha Levin wrote:
>>> On 07/22/2012 09:22 PM, Anthony Liguori wrote:
>>>> Sasha Levin writes:
>>>>
>>>>> On 07/21/2012 09:12 AM,
On 07/23/2012 12:36 AM, Anthony Liguori wrote:
> Sasha Levin writes:
>
>> On 07/22/2012 09:14 PM, Anthony Liguori wrote:
>>> Sasha Levin writes:
>>>
>>>> On 07/21/2012 10:44 AM, Wen Congyang wrote:
>>>>> We can know the guest is panicked
It is possible to create CPU-less NUMA nodes, node amount shouldn't be
limited by amount of CPUs.
Signed-off-by: Sasha Levin
---
vl.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/vl.c b/vl.c
index 8bcf2ae..8cc1aa8 100644
--- a/vl.c
+++ b/vl.c
@@ -3002,8 +3
On Wed, 2011-03-30 at 14:28 -0500, Anthony Liguori wrote:
> On 03/30/2011 02:14 PM, Sasha Levin wrote:
> > It is possible to create CPU-less NUMA nodes, node amount shouldn't be
> > limited by amount of CPUs.
>
> But does this actually work in the code today and does
Hi
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.6.5, v5.5.18, v5.4.33, v4.19.116,
v4.14.176, v4.9.219, v4.4.219.
v5.6.5: Build O
Hi
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.6.5, v5.5.18, v5.4.33, v4.19.116,
v4.14.176, v4.9.219, v4.4.219.
v5.6.5: Build O
Hi
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.6.10, v5.4.38, v4.19.120, v4.14.178,
v4.9.221, v4.4.221.
v5.6.10: Build OK!
v5.4
47 matches
Mail list logo
