On 01.03.2017 20:23, Viktor Mihajlovski wrote:
> On 01.03.2017 19:44, Daniel P. Berrange wrote:
> [...]
> replying on the list, a bit lengthy
>>
>> Ok, my guest has 4 disks
>>
>> - sda - virtio-scsi, over virtio-pci transport
>> - sdb - virtio-scsi, over virtio-mmio transport
>> - vda - virtio-s
On 01.03.2017 19:44, Daniel P. Berrange wrote:
[...]
replying on the list, a bit lengthy
>
> Ok, my guest has 4 disks
>
> - sda - virtio-scsi, over virtio-pci transport
> - sdb - virtio-scsi, over virtio-mmio transport
> - vda - virtio-scsi, over virtio-pci transport
> - vdb - virtio-scsi, ov
On Wed, Mar 01, 2017 at 07:28:46PM +0100, Viktor Mihajlovski wrote:
> On 01.03.2017 16:58, Daniel P. Berrange wrote:
> > given a basic Fedora 25 guest, with a virtio-mmio disk added as per the
> > guide above...
> >
> > looking at device
> > '/devices/platform/a003e00.virtio_mmio/virtio3/block/
On 01.03.2017 16:58, Daniel P. Berrange wrote:
> On Wed, Mar 01, 2017 at 04:02:53PM +0100, Viktor Mihajlovski wrote:
>> On 01.03.2017 04:30, Zbigniew Jędrzejewski-Szmek wrote:
>>> On Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote:
One could argue about back-level compatibi
On Wed, Mar 01, 2017 at 03:58:12PM +, Daniel P. Berrange wrote:
> On Wed, Mar 01, 2017 at 04:02:53PM +0100, Viktor Mihajlovski wrote:
> > If wanted, I can take a stab at virtio-mmio, but would need the output
> > of udevadm -a /dev/vda from a virtio-mmio system.
>
> Presumably you mean 'udevad
On Wed, Mar 01, 2017 at 04:02:53PM +0100, Viktor Mihajlovski wrote:
> On 01.03.2017 04:30, Zbigniew Jędrzejewski-Szmek wrote:
> > On Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote:
> >> One could argue about back-level compatibility, but virtio by-path
> >> naming has chang
On 01.03.2017 04:30, Zbigniew Jędrzejewski-Szmek wrote:
> On Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote:
>> One could argue about back-level compatibility, but virtio by-path
>> naming has changed multiple times. We have seen virtio-pci-virtio
>> (not predictable),
On Wed, Mar 01, 2017 at 06:51:17AM +0300, Andrei Borzenkov wrote:
> 01.03.2017 06:43, Zbigniew Jędrzejewski-Szmek пишет:
> >
> > We could keep an informal list of people who care about specific areas.
>
> MAINTAINERS file as part of systemd sources?
Heh, I really didn't want to mention this ;)
I
On Tue, Feb 28, 2017 at 08:39:07PM +0100, Lennart Poettering wrote:
> On Tue, 28.02.17 19:28, Daniel P. Berrange (berra...@redhat.com) wrote:
> > The problem with splitting these rules out into a separate project
> > is that there's no other existing place that they would live. The
> > "virtio peop
01.03.2017 06:43, Zbigniew Jędrzejewski-Szmek пишет:
>
> We could keep an informal list of people who care about specific areas.
MAINTAINERS file as part of systemd sources?
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lis
On Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote:
> One could argue about back-level compatibility, but virtio by-path
> naming has changed multiple times. We have seen virtio-pci-virtio
> (not predictable), pci- and virtio-pci- already. It
> might be a good ti
On Tue, 28.02.17 19:28, Daniel P. Berrange (berra...@redhat.com) wrote:
> > Even better would be if the kernel would do the naming on its own, and
> > maybe just provide us with a sysattr on the relevant devices that we
> > can read to determine the path from, so that we don#t have to maintain
> >
On Mon, Feb 20, 2017 at 04:14:32PM +0100, Lennart Poettering wrote:
> On Mon, 20.02.17 15:34, Viktor Mihajlovski (mihaj...@linux.vnet.ibm.com)
> wrote:
>
> > But then, I find this naming scheme somewhat weird.
> > A virtio disk shows up as a regular PCI function on the PCI
> > bus side by side wi
On 27.02.2017 12:22, Michal Sekletar wrote:
> On Fri, Feb 24, 2017 at 10:56 AM, Viktor Mihajlovski
> wrote:
>> On 20.02.2017 17:00, Cornelia Huck wrote:
>>> On Mon, 20 Feb 2017 15:34:49 +0100
>>> Viktor Mihajlovski wrote:
>>>
Hi,
with systemd > v229 all virtio block devices will re
On Fri, Feb 24, 2017 at 10:56 AM, Viktor Mihajlovski
wrote:
> On 20.02.2017 17:00, Cornelia Huck wrote:
>> On Mon, 20 Feb 2017 15:34:49 +0100
>> Viktor Mihajlovski wrote:
>>
>>> Hi,
>>>
>>> with systemd > v229 all virtio block devices will receive persistent
>>> device names in the format /dev/di
On 20.02.2017 17:00, Cornelia Huck wrote:
> On Mon, 20 Feb 2017 15:34:49 +0100
> Viktor Mihajlovski wrote:
>
>> Hi,
>>
>> with systemd > v229 all virtio block devices will receive persistent
>> device names in the format /dev/disk-by/virtio-pci-, the
>> last component being the udev built-in path
On Mon, 20.02.17 15:34, Viktor Mihajlovski (mihaj...@linux.vnet.ibm.com) wrote:
> But then, I find this naming scheme somewhat weird.
> A virtio disk shows up as a regular PCI function on the PCI
> bus side by side with other (non-virtio) devices. The naming otoh
> suggests that virtio-pci is a su
Hi,
with systemd > v229 all virtio block devices will receive persistent
device names in the format /dev/disk-by/virtio-pci-, the
last component being the udev built-in path_id.
This naming introduces some issues.
First and obvious, there are virtio implementations not based
on PCI, like virtio-
18 matches
Mail list logo