search for: virtio3

...processes via > GFP_KERNEL allocation requests. Although fill_balloon() was printing > a lot of noises due to __GFP_NORETRY, the system made forward progress > in the form of kernel panic triggered by no more OOM killable processes. > > ---------- > [ 88.270838] virtio_balloon virtio3: Out of puff! Can't get 1 pages > [ 88.503496] virtio_balloon virtio3: Out of puff! Can't get 1 pages > [ 88.730058] virtio_balloon virtio3: Out of puff! Can't get 1 pages > [ 88.937971] Out of memory: Kill process 669 (dhclient) score 54 or sacrifice child > [ 89.00...

...else killing all OOM killable processes via GFP_KERNEL allocation requests. Although fill_balloon() was printing a lot of noises due to __GFP_NORETRY, the system made forward progress in the form of kernel panic triggered by no more OOM killable processes. ---------- [ 88.270838] virtio_balloon virtio3: Out of puff! Can't get 1 pages [ 88.503496] virtio_balloon virtio3: Out of puff! Can't get 1 pages [ 88.730058] virtio_balloon virtio3: Out of puff! Can't get 1 pages [ 88.937971] Out of memory: Kill process 669 (dhclient) score 54 or sacrifice child [ 89.007322] virtio_balloon...

...else killing all OOM killable processes via GFP_KERNEL allocation requests. Although fill_balloon() was printing a lot of noises due to __GFP_NORETRY, the system made forward progress in the form of kernel panic triggered by no more OOM killable processes. ---------- [ 88.270838] virtio_balloon virtio3: Out of puff! Can't get 1 pages [ 88.503496] virtio_balloon virtio3: Out of puff! Can't get 1 pages [ 88.730058] virtio_balloon virtio3: Out of puff! Can't get 1 pages [ 88.937971] Out of memory: Kill process 669 (dhclient) score 54 or sacrifice child [ 89.007322] virtio_balloon...

On Sat, Oct 14, 2017 at 01:41:14AM +0900, Tetsuo Handa wrote: > Michael S. Tsirkin wrote: > > On Tue, Oct 10, 2017 at 07:47:37PM +0900, Tetsuo Handa wrote: > > > In leak_balloon(), mutex_lock(&vb->balloon_lock) is called in order to > > > serialize against fill_balloon(). But in fill_balloon(), > > > alloc_page(GFP_HIGHUSER[_MOVABLE] | __GFP_NOMEMALLOC |

On Sat, Oct 14, 2017 at 01:41:14AM +0900, Tetsuo Handa wrote: > Michael S. Tsirkin wrote: > > On Tue, Oct 10, 2017 at 07:47:37PM +0900, Tetsuo Handa wrote: > > > In leak_balloon(), mutex_lock(&vb->balloon_lock) is called in order to > > > serialize against fill_balloon(). But in fill_balloon(), > > > alloc_page(GFP_HIGHUSER[_MOVABLE] | __GFP_NOMEMALLOC |

...x260 [virtio_balloon] [ 19.541626] process_one_work+0x149/0x360 [ 19.542417] worker_thread+0x4d/0x3c0 [ 19.543186] kthread+0x109/0x140 [ 19.543930] ? rescuer_thread+0x380/0x380 [ 19.544716] ? kthread_park+0x60/0x60 [ 19.545426] ret_from_fork+0x25/0x30 [ 19.546141] virtio_balloon virtio3: Out of puff! Can't get 1 pages [ 19.547903] virtio_balloon virtio3: Released 256 pages. Remains 1984834 pages. [ 19.659660] virtio_balloon virtio3: Released 256 pages. Remains 1984578 pages. [ 21.891392] virtio_balloon virtio3: Released 256 pages. Remains 1984322 pages. [ 21.894719] vi...

...x260 [virtio_balloon] [ 19.541626] process_one_work+0x149/0x360 [ 19.542417] worker_thread+0x4d/0x3c0 [ 19.543186] kthread+0x109/0x140 [ 19.543930] ? rescuer_thread+0x380/0x380 [ 19.544716] ? kthread_park+0x60/0x60 [ 19.545426] ret_from_fork+0x25/0x30 [ 19.546141] virtio_balloon virtio3: Out of puff! Can't get 1 pages [ 19.547903] virtio_balloon virtio3: Released 256 pages. Remains 1984834 pages. [ 19.659660] virtio_balloon virtio3: Released 256 pages. Remains 1984578 pages. [ 21.891392] virtio_balloon virtio3: Released 256 pages. Remains 1984322 pages. [ 21.894719] vi...

...41626] process_one_work+0x149/0x360 > [ 19.542417] worker_thread+0x4d/0x3c0 > [ 19.543186] kthread+0x109/0x140 > [ 19.543930] ? rescuer_thread+0x380/0x380 > [ 19.544716] ? kthread_park+0x60/0x60 > [ 19.545426] ret_from_fork+0x25/0x30 > [ 19.546141] virtio_balloon virtio3: Out of puff! Can't get 1 pages > [ 19.547903] virtio_balloon virtio3: Released 256 pages. Remains 1984834 pages. > [ 19.659660] virtio_balloon virtio3: Released 256 pages. Remains 1984578 pages. > [ 21.891392] virtio_balloon virtio3: Released 256 pages. Remains 1984322 pages. &g...

...output > of udevadm -a /dev/vda from a virtio-mmio system. Presumably you mean 'udevadm info -a /dev/vda' ? That reports the following, 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/vda': KERNEL=="vda" SUBSYSTEM=="block" DRIVER=="" ATTR{alignment_offset}=="0" ATTR{badblocks}=="" ATTR{cache_type}=="write back" ATTR{capability}=="50" ATTR{discard_alignment}=="0&qu...

...output > of udevadm -a /dev/vda from a virtio-mmio system. Presumably you mean 'udevadm info -a /dev/vda' ? That reports the following, 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/vda': KERNEL=="vda" SUBSYSTEM=="block" DRIVER=="" ATTR{alignment_offset}=="0" ATTR{badblocks}=="" ATTR{cache_type}=="write back" ATTR{capability}=="50" ATTR{discard_alignment}=="0&qu...

...ably you mean 'udevadm info -a /dev/vda' ? That reports the following, yes, I always have to type the command twice :-( > 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/vda': > KERNEL=="vda" > SUBSYSTEM=="block" > DRIVER=="" > ATTR{alignment_offset}=="0" > ATTR{badblocks}=="" > ATTR{cache_type}=="write back" > ATTR{capability}=="50" >...

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<n> > >>>> (not predictable), pci-<busid> and virtio-pci-<busid> already. It > >>>> might be a good time now

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<n> > >>>> (not predictable), pci-<busid> and virtio-pci-<busid> already. It > >>>> might be a good time now

...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/vda': > > KERNEL=="vda" > > SUBSYSTEM=="block" > > DRIVER=="" > > ATTR{alignment_offset}=="0" > > ATTR{badblocks}=="" > > ATTR{cache_type}=="write back" > > AT...

...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/vda': > > KERNEL=="vda" > > SUBSYSTEM=="block" > > DRIVER=="" > > ATTR{alignment_offset}=="0" > > ATTR{badblocks}=="" > > ATTR{cache_type}=="write back" > > AT...

...e seen errors like this in syslog: 9pnet: Installing 9P2000 support virtio-pci 0000:00:08.0: irq 42 for MSI/MSI-X virtio-pci 0000:00:08.0: irq 43 for MSI/MSI-X virtio-pci 0000:00:08.0: irq 42 for MSI/MSI-X virtio-pci 0000:00:08.0: irq 43 for MSI/MSI-X 9pnet_virtio: probe of virtio3 failed with error -2 FS-Cache: Loaded 9p: Installing v9fs 9p2000 file system support FS-Cache: Netfs '9p' registered for caching 9pnet_virtio: no channels available and `mount` complains that the source (tag) doesn't exist when trying to mount the filesystem share again...

...l_thread_starter+0x6/0xc > [<0000000000aeab34>] kernel_thread_starter+0x0/0xc > > [..] > > virtio_ccw 0.0.0301: no vq > ---[ end trace d35815958c12cad3 ]--- > virtio_ccw 0.0.0300: no vq > virtio_blk: probe of virtio1 failed with error -12 > virtio_blk: probe of virtio3 failed with error -12 > > Means virtio devices broken. > > Should I > s/we have a problem if a virtio-ccw device/virtio-ccw devices do not work if the device/ > ? Much better :) (That is, this happens if we switch on the feature bit in the hypervisor, right?) > > >...

...267.178006] bus: 'pci': driver_probe_device: matched device 0000:00:07.0 with driver virtio-pci [ 267.179849] bus: 'pci': really_probe: probing driver virtio-pci with device 0000:00:07.0 [ 267.396589] virtio-pci 0000:00:07.0: setting latency timer to 64 [ 267.402664] device: 'virtio3': device_add [ 267.409606] bus: 'virtio': add device virtio3 [ 267.435679] driver: '0000:00:07.0': driver_bound: bound to device 'virtio-pci' [ 267.441713] bus: 'pci': really_probe: bound device 0000:00:07.0 to driver virtio-pci [ 267.449350] bus: 'pci...

...267.178006] bus: 'pci': driver_probe_device: matched device 0000:00:07.0 with driver virtio-pci [ 267.179849] bus: 'pci': really_probe: probing driver virtio-pci with device 0000:00:07.0 [ 267.396589] virtio-pci 0000:00:07.0: setting latency timer to 64 [ 267.402664] device: 'virtio3': device_add [ 267.409606] bus: 'virtio': add device virtio3 [ 267.435679] driver: '0000:00:07.0': driver_bound: bound to device 'virtio-pci' [ 267.441713] bus: 'pci': really_probe: bound device 0000:00:07.0 to driver virtio-pci [ 267.449350] bus: 'pci...