> On Mar 28, 2022, at 1:16 PM, Andy Lutomirski wrote:
>
> On Thu, Mar 10, 2022 at 6:09 AM Chao Peng wrote:
>>
>> This is the v5 of this series which tries to implement the fd-based KVM
>> guest private memory. The patches are based on latest kvm/queue branch
>> commit:
>>
>> d5089416b7fb KVM:
> On Feb 2, 2022, at 1:23 AM, Steven Price wrote:
>
> Hi Jun,
>
> On 02/02/2022 02:28, Nakajima, Jun wrote:
>>
>>> On Jan 28, 2022, at 8:47 AM, Steven Price wrote:
>>>
>>> On 18/01/2022 13:21, Chao Peng wrote:
>>>> This is t
> On Jan 28, 2022, at 8:47 AM, Steven Price wrote:
>
> On 18/01/2022 13:21, Chao Peng wrote:
>> This is the v4 of this series which try to implement the fd-based KVM
>> guest private memory. The patches are based on latest kvm/queue branch
>> commit:
>>
>> fea31d169094 KVM: x86/pmu: Fix availa
Hi Michael,
Looks like the discussions tapered off, but do you have a plan to
implement this if people are eventually fine with it? We want to
extend this to support multiple VMs.
On Mon, Aug 31, 2015 at 11:35 AM, Nakajima, Jun wrote:
> On Mon, Aug 31, 2015 at 7:11 AM, Michael S. Tsirkin wr
BTW, can you please take a look at the following URL to see my
understanding is correct? Our engineers are saying that they are not
really sure if they understood your proposal (especially around
IOMMU), and I drew a figure, adding notes...
https://wiki.opnfv.org/vm2vm_mst
Thanks,
--
Jun
Intel O
On Tue, Sep 1, 2015 at 9:28 AM, Jan Kiszka wrote:
> On 2015-09-01 18:02, Michael S. Tsirkin wrote:
...
>> You don't need to be able to map all guest memory if you know
>> guest won't try to allow device access to all of it.
>> It's a question of how good is the bus address allocator.
>
> But those
My previous email has been bounced by virtio-...@lists.oasis-open.org.
I tried to subscribed it, but to no avail...
On Tue, Sep 1, 2015 at 1:17 AM, Michael S. Tsirkin wrote:
> On Mon, Aug 31, 2015 at 11:35:55AM -0700, Nakajima, Jun wrote:
>> On Mon, Aug 31, 2015 at 7:11 AM, Michael S
On Mon, Aug 31, 2015 at 7:11 AM, Michael S. Tsirkin wrote:
> Hello!
> During the KVM forum, we discussed supporting virtio on top
> of ivshmem. I have considered it, and came up with an alternative
> that has several advantages over that - please see below.
> Comments welcome.
Hi Michael,
I like
Avi Kivity wrote on Mon, 20 Sep 2010 at 09:50:55:
> On 09/20/2010 06:44 PM, Chris Wright wrote:
>> Please send in any agenda items you are interested in covering.
>>
> nested vmx: the resurrection. Nice to see it progressing again, but
> there's still a lot of ground to cover. Perhaps we can
andrzej zaborowski wrote:
> Hi,
>
> On 02/05/07, Nakajima, Jun <[EMAIL PROTECTED]> wrote:
>> Now I realized that I needed to use 32-bit Linux to build the
>> bios.bin (i.e. BIOS-bochs-latest) in bochs. As long as I used x86-64
>> Linux to build bios.bin, the res
Now I realized that I needed to use 32-bit Linux to build the bios.bin
(i.e. BIOS-bochs-latest) in bochs. As long as I used x86-64 Linux to
build bios.bin, the resulting binary had a problem, as I reported
previously.
With this very simple patch, I was able to install and run 32-bit Vista
on KVM (
Paul Brook wrote:
> On Monday 30 April 2007, Nakajima, Jun wrote:
>> We found a way to get 32-bit Vista up on KVM by fixing bios.bin. And
>> I think it should be helpful to qemu as well. However, I'm not sure
>> if the binary file has been created simply by applying
We found a way to get 32-bit Vista up on KVM by fixing bios.bin. And I
think it should be helpful to qemu as well. However, I'm not sure if the
binary file has been created simply by applying bios.diff to the latest
bochs CVS tree (actually I doubt it). Can somebody provide a recipe for
creating bi
13 matches
Mail list logo
