qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] virtio-scsi limits


From: Richard W.M. Jones
Subject: Re: [Qemu-devel] virtio-scsi limits
Date: Tue, 18 Apr 2017 21:28:11 +0100
User-agent: Mutt/1.5.20 (2009-12-10)

On Tue, Apr 18, 2017 at 06:17:03PM +0100, Richard W.M. Jones wrote:
> On Tue, Apr 18, 2017 at 05:30:52PM +0200, Paolo Bonzini wrote:
> > > When I changed libguestfs to use LUNs instead of targets (target=0
> > > unit=i), I got a peculiar bug.  It looks like there is some kind of
> > > race when enumerating the device, where /sys is populated before the
> > > device is actually available.
> > 
> > That's not _too_ surprising because devtmpfs processes creation/deletion
> > requests asynchronously.
> 
> I had a bit of a look into this, and I don't think this can be right.
> At this point we're running inside the initramfs environment, where
> /dev is a rootfs (a special case of either ramfs or tmpfs).
> 
> Would it still be the case that a single process that does mknod
> followed by mount could not see the effect of the mknod?
> 
> The mount error (EINVAL) should indicate an invalid superblock rather
> than a missing inode (if you believe the documentation, so that may be
> wrong).
> 
> The sequence of events (happening in a single init process) is as
> described below:

I see now: this turns out to be a problem in the unpredictable
enumeration order when we use LUNs instead of targets, and nothing to
do with virtio-scsi.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]