etc)? I realize that shared <-> private conversion doesn't strictly
need this, but it seems like it could be useful for logging failures and also
for avoiding a second immediate fault if the type gets converted but doesn't
have the right protection yet.
(Obviously, if this were changed, KVM would need the ability to report that it
doesn't actually know the mode.)
--Andy
(please excuse any formatting disasters. my internet went out as I was
composing this, and i did my best to rescue it.)
On Mon, Sep 19, 2022, at 12:10 PM, Sean Christopherson wrote:
> +Will, Marc and Fuad (apologies if I missed other pKVM folks)
>
> On Mon, Sep 19, 2022, David Hildenbrand wrote:
On Fri, Sep 9, 2022, at 7:32 AM, Kirill A . Shutemov wrote:
> On Thu, Sep 08, 2022 at 09:48:35PM -0700, Andy Lutomirski wrote:
>> On 8/19/22 17:27, Kirill A. Shutemov wrote:
>> > On Thu, Aug 18, 2022 at 08:00:41PM -0700, Hugh Dickins wrote:
>> > > On Thu, 18 Aug 2
On 8/24/22 02:41, Chao Peng wrote:
On Tue, Aug 23, 2022 at 04:05:27PM +, Sean Christopherson wrote:
On Tue, Aug 23, 2022, David Hildenbrand wrote:
On 19.08.22 05:38, Hugh Dickins wrote:
On Fri, 19 Aug 2022, Sean Christopherson wrote:
On Thu, Aug 18, 2022, Kirill A . Shutemov wrote:
On We
On 8/19/22 17:27, Kirill A. Shutemov wrote:
On Thu, Aug 18, 2022 at 08:00:41PM -0700, Hugh Dickins wrote:
On Thu, 18 Aug 2022, Kirill A . Shutemov wrote:
On Wed, Aug 17, 2022 at 10:40:12PM -0700, Hugh Dickins wrote:
If your memory could be swapped, that would be enough of a good reason
to mak
On 8/18/22 06:24, Kirill A . Shutemov wrote:
On Wed, Aug 17, 2022 at 10:40:12PM -0700, Hugh Dickins wrote:
On Wed, 6 Jul 2022, Chao Peng wrote:
This is the v7 of this series which tries to implement the fd-based KVM
guest private memory.
Here at last are my reluctant thoughts on this patchset
On 7/21/22 14:19, Sean Christopherson wrote:
On Thu, Jul 21, 2022, Gupta, Pankaj wrote:
I view it as a performance problem because nothing stops KVM from copying from
userspace into the private fd during the SEV ioctl(). What's missing is the
ability for userspace to directly initialze the
uild its own page cache system for its own file-mapped content but
>> that is unrelated to host page cache.
>
> yes. If guest fills its page cache with file backed memory, this at host
> side(on shmem fd backend) will also fill the host page cache fast. This
> can have an impact on performance of guest VM's if host goes to memory
> pressure situation sooner. Or else we end up utilizing way less System
> RAM.
Is this in any meaningful way different from a regular VM?
--Andy
On Tue, Jun 14, 2022 at 12:09 PM Sean Christopherson wrote:
>
> On Tue, Jun 14, 2022, Andy Lutomirski wrote:
> > On Tue, Jun 14, 2022 at 12:32 AM Chao Peng
> > wrote:
> > >
> > > On Thu, Jun 09, 2022 at 08:29:06PM +, Sean Christopherson wrote:
> >
k, but:
What if shared guest memory could also be file-backed, either in the
same fd or with a second fd covering the shared portion of a memslot?
This would allow changes to the backing store (punching holes, etc) to
be some without mmap_lock or host-userspace TLB flushes? Depending on
what the guest is doing with its shared memory, userspace might need
the memory mapped or it might not.
--Andy
On Mon, Apr 25, 2022 at 1:31 PM Sean Christopherson wrote:
>
> On Mon, Apr 25, 2022, Andy Lutomirski wrote:
> >
> >
> > On Mon, Apr 25, 2022, at 6:40 AM, Chao Peng wrote:
> > > On Sun, Apr 24, 2022 at 09:59:37AM -0700, Andy Lutomirski wrote:
> > >>
On Fri, May 20, 2022, at 11:31 AM, Sean Christopherson wrote:
> But a dedicated KVM ioctl() to add/remove shared ranges would be easy
> to implement
> and wouldn't necessarily even need to interact with the memslots. It
> could be a
> consumer of memslots, e.g. if we wanted to disallow regis
On 5/19/22 08:37, Chao Peng wrote:
Extend the memslot definition to provide guest private memory through a
file descriptor(fd) instead of userspace_addr(hva). Such guest private
memory(fd) may never be mapped into userspace so no userspace_addr(hva)
can be used. Instead add another two new fields
On Mon, Apr 25, 2022, at 6:40 AM, Chao Peng wrote:
> On Sun, Apr 24, 2022 at 09:59:37AM -0700, Andy Lutomirski wrote:
>>
>>
>> 2. Bind the memfile to a VM (or at least to a VM technology). Now it's in
>> the initial state appropriate for that VM.
>>
On Fri, Apr 22, 2022, at 3:56 AM, Chao Peng wrote:
> On Tue, Apr 05, 2022 at 06:03:21PM +, Sean Christopherson wrote:
>> On Tue, Apr 05, 2022, Quentin Perret wrote:
>> > On Monday 04 Apr 2022 at 15:04:17 (-0700), Andy Lutomirski wrote:
> Only when the registe
On Tue, Apr 12, 2022, at 7:36 AM, Jason Gunthorpe wrote:
> On Fri, Apr 08, 2022 at 08:54:02PM +0200, David Hildenbrand wrote:
>
>> RLIMIT_MEMLOCK was the obvious candidate, but as we discovered int he
>> past already with secretmem, it's not 100% that good of a fit (unmovable
>> is worth than mlock
On Thu, Apr 7, 2022, at 9:05 AM, Sean Christopherson wrote:
> On Thu, Mar 10, 2022, Chao Peng wrote:
>> Since page migration / swapping is not supported yet, MFD_INACCESSIBLE
>> memory behave like longterm pinned pages and thus should be accounted to
>> mm->pinned_vm and be restricted by RLIMIT_
On Tue, Apr 5, 2022, at 11:30 AM, Sean Christopherson wrote:
> On Tue, Apr 05, 2022, Andy Lutomirski wrote:
>
>> resume guest
>> *** host -> hypervisor -> guest ***
>> Guest unshares the page.
>> *** guest -> hypervisor ***
>> Hypervisor r
On Tue, Apr 5, 2022, at 3:36 AM, Quentin Perret wrote:
> On Monday 04 Apr 2022 at 15:04:17 (-0700), Andy Lutomirski wrote:
>>
>>
>> On Mon, Apr 4, 2022, at 10:06 AM, Sean Christopherson wrote:
>> > On Mon, Apr 04, 2022, Quentin Perret wrote:
>> >>
On Mon, Apr 4, 2022, at 10:06 AM, Sean Christopherson wrote:
> On Mon, Apr 04, 2022, Quentin Perret wrote:
>> On Friday 01 Apr 2022 at 12:56:50 (-0700), Andy Lutomirski wrote:
>> FWIW, there are a couple of reasons why I'd like to have in-place
>> conversions:
>&g
On Fri, Apr 1, 2022, at 7:59 AM, Quentin Perret wrote:
> On Thursday 31 Mar 2022 at 09:04:56 (-0700), Andy Lutomirski wrote:
> To answer your original question about memory 'conversion', the key
> thing is that the pKVM hypervisor controls the stage-2 page-tables for
>
On Wed, Mar 30, 2022, at 10:58 AM, Sean Christopherson wrote:
> On Wed, Mar 30, 2022, Quentin Perret wrote:
>> On Wednesday 30 Mar 2022 at 09:58:27 (+0100), Steven Price wrote:
>> > On 29/03/2022 18:01, Quentin Perret wrote:
>> > > Is implicit sharing a thing? E.g., if a guest makes a memory access
this series be run and a VM booted without TDX? A feature like
that might help push it forward.
--Andy
On 2/23/22 04:05, Steven Price wrote:
On 23/02/2022 11:49, Chao Peng wrote:
On Thu, Feb 17, 2022 at 11:09:35AM -0800, Andy Lutomirski wrote:
On Thu, Feb 17, 2022, at 5:06 AM, Chao Peng wrote:
On Fri, Feb 11, 2022 at 03:33:35PM -0800, Andy Lutomirski wrote:
On 1/18/22 05:21, Chao Peng wrote
On Thu, Feb 17, 2022, at 5:06 AM, Chao Peng wrote:
> On Fri, Feb 11, 2022 at 03:33:35PM -0800, Andy Lutomirski wrote:
>> On 1/18/22 05:21, Chao Peng wrote:
>> > From: "Kirill A. Shutemov"
>> >
>> > Introduce a new seal F_SEAL_INACCESSIBLE indicatin
On 1/18/22 05:21, Chao Peng wrote:
It maintains a memfile_notifier list in shmem_inode_info structure and
implements memfile_pfn_ops callbacks defined by memfile_notifier. It
then exposes them to memfile_notifier via
shmem_get_memfile_notifier_info.
We use SGP_NOALLOC in shmem_get_lock_pfn since
On 1/18/22 05:21, Chao Peng wrote:
From: "Kirill A. Shutemov"
Introduce a new seal F_SEAL_INACCESSIBLE indicating the content of
the file is inaccessible from userspace through ordinary MMU access
(e.g., read/write/mmap). However, the file content can be accessed
via a different mechanism (e.g.
Turn on pre-defined feature VIRTIO_BLK_F_SIZE_MAX for virtio blk device to
avoid guest DMA request sizes which are too large for hardware spec.
Signed-off-by: Andy Pei
---
hw/block/vhost-user-blk.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/block/vhost-user-blk.c b/hw/block/vhost
Hi Raphael,
Thanks for your reply.
I will fix the grammar mistake in V2.
-Original Message-
From: Raphael Norwitz
Sent: Tuesday, November 30, 2021 5:58 AM
To: Pei, Andy
Cc: qemu-devel@nongnu.org; qemu-bl...@nongnu.org; Liu, Changpeng
; Raphael Norwitz ;
m...@redhat.com; kw
On 11/19/21 05:47, Chao Peng wrote:
From: "Kirill A. Shutemov"
The new seal type provides semantics required for KVM guest private
memory support. A file descriptor with the seal set is going to be used
as source of guest memory in confidential computing environments such as
Intel TDX and AMD S
On 11/19/21 05:47, Chao Peng wrote:
This RFC series try to implement the fd-based KVM guest private memory
proposal described at [1] and an improved 'New Proposal' described at [2].
I generally like this. Thanks!
Turn on pre-defined feature VIRTIO_BLK_F_SIZE_MAX virtio blk device
to avoid guest DMA request size is too large to exceed hardware spec.
Signed-off-by: Andy Pei
---
hw/block/vhost-user-blk.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/block/vhost-user-blk.c b/hw/block/vhost-user
The commit in question is marked for stable:
commit 841c2be09fe4f495fe5224952a419bd8c7e5b455
Author: Maxim Levitsky
Date: Wed Jul 8 14:57:31 2020 +0300
kvm: x86: replace kvm_spec_ctrl_test_value with runtime test on the host
To avoid complex and in some cases incorrect logic
On Sun, Oct 18, 2020 at 8:59 AM Michael S. Tsirkin wrote:
>
> On Sun, Oct 18, 2020 at 08:54:36AM -0700, Andy Lutomirski wrote:
> > On Sun, Oct 18, 2020 at 8:52 AM Michael S. Tsirkin wrote:
> > >
> > > On Sat, Oct 17, 2020 at 03:24:08PM +0200, Jason A. Donenfel
ut it is
> certainly simple to implement ...
Wipe of fork/vmgenid/whatever could end up being much more problematic
than it naively appears -- it could be wiped in the middle of a read.
Either the API needs to handle this cleanly, or we need something more
aggressive like signal-on-fork.
--Andy
On Fri, Oct 16, 2020 at 6:40 PM Jann Horn wrote:
>
> [adding some more people who are interested in RNG stuff: Andy, Jason,
> Theodore, Willy Tarreau, Eric Biggers. also linux-api@, because this
> concerns some pretty fundamental API stuff related to RNG usage]
>
> On Fri, Oct 1
drivers/gpio/Makefile | 1 +
> drivers/gpio/gpio-aggregator.c| 568 ++
> drivers/gpio/gpiolib.c| 22 +-
> drivers/i2c/busses/i2c-i801.c | 6 +-
> drivers/mfd/sm501.c | 24 +-
> include/linux/gpio/machine.h | 17 +-
> 11 files changed, 748 insertions(+), 36 deletions(-)
> create mode 100644 Documentation/admin-guide/gpio/gpio-aggregator.rst
> create mode 100644 drivers/gpio/gpio-aggregator.c
>
> --
> 2.17.1
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
> ge...@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like
> that.
> -- Linus Torvalds
--
With Best Regards,
Andy Shevchenko
On Wed, May 20, 2020 at 3:38 PM Geert Uytterhoeven wrote:
> On Wed, May 20, 2020 at 2:14 PM Andy Shevchenko
> wrote:
> > On Mon, May 11, 2020 at 04:52:51PM +0200, Geert Uytterhoeven wrote:
...
> > Sorry for late reply, recently noticed this nice idea.
> > The comment I
On Wed, May 20, 2020 at 3:40 PM Andy Shevchenko
wrote:
> On Wed, May 20, 2020 at 3:38 PM Geert Uytterhoeven
> wrote:
> > On Wed, May 20, 2020 at 2:14 PM Andy Shevchenko
> > wrote:
> > > On Mon, May 11, 2020 at 04:52:51PM +0200, Geert Uytterhoeven wrote:
>
>
[reg:PxIS] @ 0x10:
0x0002
ahci_mem_write_host ahci(0x7fcc4e19b4a0) write4 [reg:IS] @ 0x8:
0x0001
---
--
Best regards,
Andy Chiu
On 2019/9/10 上午2:13, John Snow wrote:
On 9/9/19 1:18 PM, andychiu via Qemu-devel wrote:
If
> On Dec 28, 2018, at 6:54 PM, Matthew Wilcox wrote:
>
>> On Sat, Dec 29, 2018 at 12:12:27AM +, Peter Maydell wrote:
>> On Fri, 28 Dec 2018 at 23:16, Andreas Dilger wrot
>>> On Dec 28, 2018, at 4:18 AM, Peter Maydell wrote:
The problem is that there is no 32-bit API in some cases
(
[sending again, slightly edited, due to email client issues]
On Thu, Dec 27, 2018 at 9:25 AM Florian Weimer wrote:
>
> We have a bit of an interesting problem with respect to the d_off
> field in struct dirent.
>
> When running a 64-bit kernel on certain file systems, notably ext4,
> this field u
> On Dec 27, 2018, at 10:18 AM, Florian Weimer wrote:
>
> We have a bit of an interesting problem with respect to the d_off
> field in struct dirent.
>
> When running a 64-bit kernel on certain file systems, notably ext4,
> this field uses the full 63 bits even for small directories (strace -
** Changed in: qemu
Assignee: (unassigned) => Andy (andyliuliming)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1790268
Title:
the vhd generated by qemu-img not align with MB again.
Sta
lid
Bug description:
I'm using this version on xenial,
andy@bastion:~/temp$ qemu-img -h
qemu-img version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.31), Copyright (c)
2004-2008 Fabrice Bellard
steps to repro:
dd if=/dev/zero of=/tmp/azure_config_disk_image20180901-22672-16zxelu
bs=1048576
** Description changed:
I'm using this version on xenial,
andy@bastion:~/temp$ qemu-img -h
qemu-img version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.31), Copyright (c)
2004-2008 Fabrice Bellard
steps to repro:
dd if=/dev/zero of=/tmp/azure_config_disk_image20180901-22672-16zxel
:
the vhd generated by qemu-img not align with MB again.
Status in QEMU:
New
Bug description:
I'm using this version on xenial,
andy@bastion:~/temp$ qemu-img -h
qemu-img version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.31), Copyright (c)
2004-2008 Fabrice Bellard
steps to repro:
dd if
and even the format is raw:
andy@bastion:~/temp$ qemu-img info papapa2.vhd
image: papapa2.vhd
file format: raw
virtual size: 24M (25166336 bytes)
disk size: 152K
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https
.
Status in QEMU:
New
Bug description:
I'm using this version on xenial,
andy@bastion:~/temp$ qemu-img -h
qemu-img version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.31), Copyright (c)
2004-2008 Fabrice Bellard
steps to repro:
dd if=/dev/zero of=/tmp/azure_config_disk_image20180901-22672-16
Public bug reported:
I'm using this version on xenial,
andy@bastion:~/temp$ qemu-img -h
qemu-img version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.31), Copyright (c)
2004-2008 Fabrice Bellard
steps to repro:
dd if=/dev/zero of=/tmp/azure_config_disk_image20180901-22672-16zxelu
bs=1048576 cou
I'm using this version on xenial,
andy@bastion:~/temp$ qemu-img -h
qemu-img version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.31), Copyright (c)
2004-2008 Fabrice Bellard
qemu-img convert -f raw -O vpc -o subformat=fixed,force_size
/tmp/azure_config_disk_image20180901-22672-16zxelu papapa
d_devicetable.h from
> linux/platform_device.h")
> Signed-off-by: Arnd Bergmann
> drivers/platform/x86/intel_punit_ipc.c | 1 +
> --- a/drivers/platform/x86/intel_punit_ipc.c
> +++ b/drivers/platform/x86/intel_punit_ipc.c
> @@ -12,6 +12,7 @@
> */
>
> #include
| 444
> +++
Please, split tests to a separate module.
--
With Best Regards,
Andy Shevchenko
On Fri, Feb 16, 2018 at 8:30 PM, Matthew Wilcox wrote:
> On Fri, Feb 16, 2018 at 07:44:50PM +0200, Andy Shevchenko wrote:
>> On Tue, Jan 9, 2018 at 1:10 PM, Wei Wang wrote:
>> > From: Matthew Wilcox
>> >
>> > The eXtensible Bitmap is a sparse bitmap repres
, but target_core_user.ko should contain the access to
/dev/uioX and make sure there is no security risk regarding buggy or malicious
handlers. Otherwise it's a bug that should be fixed. Andy can correct me if I'm
wrong.
Yes... well, TCMU ensures that a bad handler can't scribble to kernel
On Wed, Apr 27, 2016 at 7:54 AM, Michael S. Tsirkin wrote:
> On Wed, Apr 27, 2016 at 07:43:07AM -0700, Andy Lutomirski wrote:
>> On Wed, Apr 27, 2016 at 7:38 AM, Michael S. Tsirkin wrote:
>> > On Wed, Apr 27, 2016 at 07:31:43AM -0700, Andy Lutomirski wrote:
>> >> O
On Wed, Apr 27, 2016 at 7:38 AM, Michael S. Tsirkin wrote:
> On Wed, Apr 27, 2016 at 07:31:43AM -0700, Andy Lutomirski wrote:
>> On Wed, Apr 27, 2016 at 7:23 AM, Joerg Roedel wrote:
>> > On Wed, Apr 27, 2016 at 04:37:04PM +0300, Michael S. Tsirkin wrote:
>> >> One
r as I know, those are the only
problematic platforms.
Is it too late to *disable* QEMU's q35-iommu thingy until it can be
fixed to report correct data in the DMAR tables?
--Andy
Public bug reported:
In TCG mode, the effect of:
xorl %eax, %eax
movl %eax, %gs
is to mark the GS segment unusable and set its base to zero. After
doing this, reading MSR_GS_BASE will return zero and using a GS prefix
in long mode will treat the GS base as zero.
This is correct for Intel CPUs
On Apr 20, 2016 6:14 AM, "Michael S. Tsirkin" wrote:
>
> On Tue, Apr 19, 2016 at 02:07:01PM -0700, Andy Lutomirski wrote:
> > On Tue, Apr 19, 2016 at 1:54 PM, Michael S. Tsirkin wrote:
> > > On Tue, Apr 19, 2016 at 01:27:29PM -0700, Andy Lutomirski wrote:
> &g
On Tue, Apr 19, 2016 at 1:54 PM, Michael S. Tsirkin wrote:
> On Tue, Apr 19, 2016 at 01:27:29PM -0700, Andy Lutomirski wrote:
>> On Tue, Apr 19, 2016 at 1:16 PM, Michael S. Tsirkin wrote:
>> > On Tue, Apr 19, 2016 at 11:01:38AM -0700, Andy Lutomirski wrote:
>> >> On
On Tue, Apr 19, 2016 at 1:16 PM, Michael S. Tsirkin wrote:
> On Tue, Apr 19, 2016 at 11:01:38AM -0700, Andy Lutomirski wrote:
>> On Tue, Apr 19, 2016 at 10:49 AM, Michael S. Tsirkin wrote:
>> > On Tue, Apr 19, 2016 at 12:26:44PM -0400, David Woodhouse wrote:
>> >&g
f whether QEMU is ignoring the IOMMU or not -- I think the
only obstacle is that the PPC and SPARC 1:1 mappings are currectly set
up with an offset. I don't know too much about those platforms, but
presumably the layout could be changed so that 1:1 really was 1:1.
--Andy
On Tue, Apr 19, 2016 at 9:09 AM, Michael S. Tsirkin wrote:
> On Tue, Apr 19, 2016 at 09:02:14AM -0700, Andy Lutomirski wrote:
>> On Tue, Apr 19, 2016 at 3:27 AM, Michael S. Tsirkin wrote:
>> > On Mon, Apr 18, 2016 at 12:24:15PM -0700, Andy Lutomirski wrote:
>> >> On
1 mapping for performance, but to still
handle the case where the guest refuses to do so or where there's more
than one translation layer involved.
But I agree that this part shouldn't delay the other part of your series.
--Andy
On Tue, Apr 19, 2016 at 3:27 AM, Michael S. Tsirkin wrote:
> On Mon, Apr 18, 2016 at 12:24:15PM -0700, Andy Lutomirski wrote:
>> On Mon, Apr 18, 2016 at 11:29 AM, David Woodhouse
>> wrote:
>> > For x86, you *can* enable virtio-behind-IOMMU if your DMAR tables tell
okay to change it in a way that causes some older kernels to OOPS.
--Andy
exposed by the QEMU fw_cfg device.
>
What's the status of "by_name"? There's a single (presumably
incorrect) mention of it in a comment in this patch.
I would prefer if the kernel populated by_name itself rather than
deferring that to udev, since I'd like to use this facility in virtme,
and I'd like to use fw_cfg very early on boot before I even start
udev.
--Andy
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1349277
Title:
AArch64 emulation ignores SPSel=0 when taking (or returning f
> - extended feature bits
> - virtio-ccw new/changed commands
At the risk of some distraction, would it be worth thinking about a
solution to the IOMMU bypassing mess as part of this?
--Andy
n't
> otherwise the in-flight partial copy would be visible to the process,
> breaking the atomicity of the copy), but it would fill in the
> pte/trans_huge_pmd with the same strict behavior that remap_anon_pages
> currently has (in turn it would by design bypass the VM_USERFAULT
>
while the guest is accessing the
disk. See the nbd-server-start command in qapi/block.json.
Stefan
Andy: ping
I hope we didn't scaried you with our monster block backend and it's
associated QMP socket ;)
Hi Benoît,
No, I've gone off to work on a initial proof-of-concept imple
one you are adding to qemu-nbd.
Benoit and I talked a little about QMP on another part of the thread...
I said I didn't think we needed a QMP monitor in qemu-lio-tcmu, but let
me spin up on qemu a little more and I'll be able to speak more
intelligently.
-- Andy
d various times, without much success. See
the many examples of people trying to make the qemu block driver code
into a separate library, and failing.
What's been the sticking point?
Regards -- Andy
Thoughts?
Regards -- Andy
p.s. offline Monday.
e.
Yeah, could be tricky but would be pretty cool if it works. Let me know
how I can help, or with any questions.
Regards -- Andy
This updates x86's kvm_para.h for the feature bit definition and
target-i386/cpu.c for the feature name and default.
Signed-off-by: Andy Lutomirski
---
linux-headers/asm-x86/kvm_para.h | 2 ++
target-i386/cpu.c| 5 +++--
2 files changed, 5 insertions(+), 2 deletions(-)
On 07/02/2014 09:50 AM, Andrea Arcangeli wrote:
> Once an userfaultfd is created MADV_USERFAULT regions talks through
> the userfaultfd protocol with the thread responsible for doing the
> memory externalization of the process.
>
> The protocol starts by userland writing the requested/preferred
>
On 07/02/2014 09:50 AM, Andrea Arcangeli wrote:
> Hello everyone,
>
> There's a large CC list for this RFC because this adds two new
> syscalls (userfaultfd and remap_anon_pages) and
> MADV_USERFAULT/MADV_NOUSERFAULT, so suggestions on changes to the API
> or on a completely different API if someb
On Mon, Apr 14, 2014 at 1:15 AM, Markus Armbruster wrote:
> Peter Crosthwaite writes:
>
>> Hi Andy,
>>
>> On Thu, Apr 10, 2014 at 5:55 AM, Andy Lutomirski wrote:
>>> Currently, -M q35 boots linux quite a bit slower than the default
>>> machine type
On Wed, Apr 9, 2014 at 8:13 PM, Peter Crosthwaite
wrote:
> On Thu, Apr 10, 2014 at 9:57 AM, Andy Lutomirski wrote:
>> On Wed, Apr 9, 2014 at 4:53 PM, Peter Crosthwaite
>> wrote:
>>> Hi Andy,
>>>
>>> On Thu, Apr 10, 2014 at 5:55 AM, Andy Lutomirski
>
On Wed, Apr 9, 2014 at 4:53 PM, Peter Crosthwaite
wrote:
> Hi Andy,
>
> On Thu, Apr 10, 2014 at 5:55 AM, Andy Lutomirski wrote:
>> Currently, -M q35 boots linux quite a bit slower than the default
>> machine type. This seems to be because it takes a few hundred ms to
>
ld it be possible to add something like
-machine default_storage=off to turn off default storage devices?
This could include the AHCI on q35 and the cdrom and such on pc.
There's precedent: -machine usb=off turns off the default USB
controllers, which is great for setups that use xhci.
Thanks,
Andy
On Tue, Apr 1, 2014 at 3:09 PM, Andy Lutomirski wrote:
> Running:
>
> ./virtme-run --installed-kernel
>
> from this virtme commit:
>
> https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git/commit/?id=2b409a086d15b7a878c7d5204b1f44a6564a341f
>
> results in a bun
don't know whether this is a qemu bug or a Linux bug.
I'm seeing this on Fedora's 3.13.7 kernel and on a fairly recent
3.14-rc kernel. For the latter, cirrus is built-in (not a module),
I'm running:
virtme-run --kimg arch/x86/boot/bzImage
and I see more profound corruption.
--Andy
Stefan,
That is what I needed to know. Thanks.
It was somewhat surprising to see how many patches have been backported to the
CentOS6.3 source rpm.
Andy
-Original Message-
From: Stefan Hajnoczi [mailto:stefa...@gmail.com]
Sent: Monday, February 25, 2013 9:41 AM
To: Andy Cress
Cc
would prevent running
qemu-1.1 on the 2.6.32 CentOS 6 kernel?
What would you recommend?
Andy
Thanks for your advices. I have no more problems with VM-size since
deleting snapshot in shutdown-mode. I reduced the overlarge qcow2-images
by converting in qcow2 again (that detects unused sectors and omits
this).
--
You received this bug notification because you are a member of qemu-
devel-ml,
Any solution right now? I have a similar problem like Todor Andreev;
Our daily backup of some virtual machines (qcow2) looks like that:
1. shutdown the VM
2. create a snapshot via: "qemu-img snapshot -c nameofsnapshot..."
3. boot the VM
4. backup the snapshot to another virtual disk via: "qemu-img
, hot dipped
galvanized chain etc!
For more information, we would like to let you know our company web site as
below:http://www.boliwiremesh.com.
Hope to hear good news from you.
Sincerely Yours,
Andy
Sales manager
Boli hardware industrial limited
Tel: 86-0311-87789982
Fax: 86-0311-87769982
On Tue, Sep 27, 2011 at 8:58 AM, Michael S. Tsirkin wrote:
> e1000 spec says CTRL.RST write should have the same effect
> as bus reset, except that is preserves PCI Config.
> Reset device registers and interrupts.
>
> Fix suggested by Andy Gospodarek
> Similar fix proposed
Public bug reported:
I have a Vmware image, so I have files like 'Ubuntu.vmdk', want to
convert to VirtualBox .vdi format using qemu, the first stage of
extracting the image with 'qemu-img convert Ubuntu.vmdk output.bin' just
generates a 512byte file:
{quote}
# Disk DescriptorFile
version=1
CID=3
Andreas,
The program that created the disk image seems confused, but it worked for
creating a VM for FC11.
Windows install seems to run fine, until wanting to boot from the drive it
created.
I don't know what creates the drive image and geometry, but it is broken.
I think this is what I used to
00 00 0C 00 00
00 00 00 02 00 00 00 00 00 00 00 ..|.
# kpartx -d /dev/loop0; losetup -d /dev/loop0
I changed location 0x1a to 0xFF on one or other or both partitions and
it still will not boot in virt-manager.
Cheers,
Andy.
--
Windows XP/2003 doesn't boot
Public bug reported:
I'm working on an app that is very sensitive to round-trip latency
between the guest and host, and qemu/kvm seems to be significantly
slower than it needs to be.
The attached program is a ping/pong over UDP. Call it with a single
argument to start a listener/echo server on t
** Attachment added: "udp-pong.c"
http://launchpadlibrarian.net/50751155/udp-pong.c
--
Slow UDP performance with virtio device
https://bugs.launchpad.net/bugs/597351
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Ne
?
(--fake-super already does almost what you're doing, and if you make
the formats compatible, then rsync could be used to translate. OTOH,
rsyncing a VirtFS-ified filesystem to a remote --fake-super system might
have odd side-effects.)
--Andy
On Wed, 2010-05-12 at 00:09 +0300, Mohammed Gamal wrote:
> On Tue, May 11, 2010 at 11:56 PM, Andy Walls wrote:
> > Running an MS-DOS 6.22 image with qemu-kvm on a RedHat Linux OS, I
> > noticed the guest OS becomes hung and my dmesg gets spammed with
> >
> >set
Ware and on real hardware.
Any ideas on how to make EMM386.EXE and the DOS/$GW extender work in
qemu-kvm?
Regards,
Andy
e.
i looked in many forums, can´t find everything
can you help me ?
by Andy
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
100 matches
Mail list logo
