qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: C Anthony Risinger <anthony@xtfx.me>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] VirtIO 9p mount_tag (bogus?) limit of 32 bytes
Date: Thu, 23 Feb 2012 23:38:18 +0530	[thread overview]
Message-ID: <87d395zalp.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAGAVQTERjnjvXSNgwX1rbVBmwbr9MtJeJGRxD3_Z8S8petA6pQ@mail.gmail.com>

On Tue, 21 Feb 2012 21:58:39 -0600, C Anthony Risinger <anthony@xtfx.me> wrote:
> On Sat, Feb 18, 2012 at 11:38 AM, Aneesh Kumar K.V
> <aneesh.kumar@linux.vnet.ibm.com> wrote:
> > On Thu, 16 Feb 2012 06:20:21 -0600, C Anthony Risinger <anthony@xtfx.me> wrote:
> >> a) mapped FS security policy (xattrs) causes `ldconfig` to abort()?
> >> root or normal user ...
> >>
> >> somehow `ldconfig` gets a duplicate inode while constructing the
> >> cache, even though it already de-duped (confirmed via gdb and grep --
> >> only a single abort() in the source)
> >>

I will try to reproduce this to get more info.


> >> b) unable to run `locale-gen` on *any* virtfs configuration? (strace)
> >>
> >> [...]
> >> mmap(NULL, 536870912, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> >> 0x7fb3aac63000
> >> mmap(0x7fb3aac63000, 103860, PROT_READ|PROT_WRITE,
> >> MAP_SHARED|MAP_FIXED, 3, 0) = -1 EINVAL (Invalid argument)
> >> cannot map archive header: Invalid argument
> >>

For writable mmap to work you need to mount with -o cache=loose. Did
you try local-gen with that mount option ?


> >> c) package files containing device nodes fail (maybe this is expected
> >> ...); specifically `/lib/udev/devices/loop0`
> >>
> >

Does this mean mknod fails for you. Or is something else in package
manager causing the failure ? 


> > Is this with 9p2000.L ?. What is the guest kernel version ?
> 
> (not sure if list will accept this ... too much traffic! had to remove myself)
> 
> yes this is with 9p2000.L, both host and guests run kernel 3.2.5.  i'm
> happy to provide/try additional information/tests if useful.
> 

One quick thing you could do is to try latest linus kernel as the guest
kernel. 

> ... is there really no chance of upping the max path?  seems like
> config space will be a big constraint, forever :-(
> 
> and i'm very much willing to do additional testing for the other
> issues as well (i had to revert to qemu-as-root to get passthru
> working 100% on rootfs ... ldconfig is kind of critical :-).  are
> these known issues?
> 

I don't have much suggestion on what could be going wrong there. I will
try to reproduce the ldconfig issue here.

-aneesh

  reply	other threads:[~2012-02-23 18:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 12:20 [Qemu-devel] VirtIO 9p mount_tag (bogus?) limit of 32 bytes C Anthony Risinger
2012-02-16 20:54 ` Paul Brook
2012-02-18 17:38 ` Aneesh Kumar K.V
2012-02-22  3:58   ` C Anthony Risinger
2012-02-23 18:08     ` Aneesh Kumar K.V [this message]
2012-03-07 16:29     ` M. Mohan Kumar
  -- strict thread matches above, loose matches on Subject: below --
2011-09-22 17:42 Daniel P. Berrange
2011-09-28 11:52 ` Harsh Bora
2011-09-28 15:18   ` Daniel P. Berrange
2011-09-29 15:22     ` Aneesh Kumar K.V
2011-09-29 15:45       ` Daniel P. Berrange

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d395zalp.fsf@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=anthony@xtfx.me \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).