similar to: Can't build in the virtio console driver on x86_64 when the other virtio drivers are modular

Hi All, Booting my local KVM guest with a build of 3.18-rc1 this morning, it hangs during the normal dracut splash screen When I configured the guest to use a serial console, I got the output below. The guest is a typical KVM guest created with virt-manager, using QXL as the display driver. Nothing fancy about it. I'll try and do a bisect or some other experimentation today, but I thought

Hi All, Booting my local KVM guest with a build of 3.18-rc1 this morning, it hangs during the normal dracut splash screen When I configured the guest to use a serial console, I got the output below. The guest is a typical KVM guest created with virt-manager, using QXL as the display driver. Nothing fancy about it. I'll try and do a bisect or some other experimentation today, but I thought

The following changes since commit b2776bf7149bddd1f4161f14f79520f17fc1d71d: Linux 3.18 (2014-12-07 14:21:05 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus for you to fetch changes up to 803cd18f7b5e6c7ad6bee9571ae8f4450190ab58: virtio_ccw: finalize_features error handling (2014-12-09 16:32:41 +0200) Note: some

The following changes since commit b2776bf7149bddd1f4161f14f79520f17fc1d71d: Linux 3.18 (2014-12-07 14:21:05 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus for you to fetch changes up to 803cd18f7b5e6c7ad6bee9571ae8f4450190ab58: virtio_ccw: finalize_features error handling (2014-12-09 16:32:41 +0200) Note: some

This patchset replace CONFIG_PM with CONFIG_PM_SLEEP for all virtio drivers and virtio pci driver. With patch 1/2, two compile warnings are eliminated for virtio pci driver, and patch 2/2 is a clean up for all virtio drivers as suggested by Amit Shah. Aaron Lu (2): virtio_pci: pm: Use CONFIG_PM_SLEEP instead of CONFIG_PM virtio: pm: use CONFIG_PM_SLEEP instead of CONFIG_PM

This patchset replace CONFIG_PM with CONFIG_PM_SLEEP for all virtio drivers and virtio pci driver. With patch 1/2, two compile warnings are eliminated for virtio pci driver, and patch 2/2 is a clean up for all virtio drivers as suggested by Amit Shah. Aaron Lu (2): virtio_pci: pm: Use CONFIG_PM_SLEEP instead of CONFIG_PM virtio: pm: use CONFIG_PM_SLEEP instead of CONFIG_PM

Hi, I have a fedora21 system that's been running fine under normal network activity, but trying to perform a full backup of the 300GB filesystem is taking forever because the network speed appears to be very slow. Using rsync, the transfer speeds reach a max of like 180kB/s. Using rsync to copy files on the local filesystem is greater than 55MB/s, so I don't think it's a disk

Hello, These patches are an initial attempt at supporting hibernation for virtio drivers. The default configuration of event_index=on doesn't work; i.e. restore from a hibernated image only works if the devices have event_index support turned off. I have not yet dug into this, but is most likely due to some state not being sync'ed. This could be related to the hack that is patch 3.

Hello, These patches are an initial attempt at supporting hibernation for virtio drivers. The default configuration of event_index=on doesn't work; i.e. restore from a hibernated image only works if the devices have event_index support turned off. I have not yet dug into this, but is most likely due to some state not being sync'ed. This could be related to the hack that is patch 3.

Let host know of our state (partial yet) so that the host PCI device is up to where we were when we were suspended. This is still an RFC as this doesn't completely work: an unused device at the time of suspend will work fine after resume, but a device that has seen some activity doesn't behave well after resume. Especially, host->guest communication doesn't go through. This could

Let host know of our state (partial yet) so that the host PCI device is up to where we were when we were suspended. This is still an RFC as this doesn't completely work: an unused device at the time of suspend will work fine after resume, but a device that has seen some activity doesn't behave well after resume. Especially, host->guest communication doesn't go through. This could

From: Rusty Russell <rusty at rustcorp.com.au> Change the u32 to a u64, and make sure to use 1ULL everywhere! Cc: Brian Swetland <swetland at google.com> Cc: Christian Borntraeger <borntraeger at de.ibm.com> [Thomas Huth: fix up virtio-ccw get_features] Signed-off-by: Rusty Russell <rusty at rustcorp.com.au> Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com>

From: Rusty Russell <rusty at rustcorp.com.au> Change the u32 to a u64, and make sure to use 1ULL everywhere! Cc: Brian Swetland <swetland at google.com> Cc: Christian Borntraeger <borntraeger at de.ibm.com> [Thomas Huth: fix up virtio-ccw get_features] Signed-off-by: Rusty Russell <rusty at rustcorp.com.au> Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com>

The virtio_pci_freeze/restore are defined under CONFIG_PM but is used by SET_SYSTEM_SLEEP_PM_OPS macro, which is defined under CONFIG_PM_SLEEP. So if CONFIG_PM_SLEEP is not cofigured but CONFIG_PM_RUNTIME is, the following warning message appeared: drivers/virtio/virtio_pci.c:770:12: warning: ?virtio_pci_freeze? defined but not used [-Wunused-function] static int virtio_pci_freeze(struct device

The virtio_pci_freeze/restore are defined under CONFIG_PM but is used by SET_SYSTEM_SLEEP_PM_OPS macro, which is defined under CONFIG_PM_SLEEP. So if CONFIG_PM_SLEEP is not cofigured but CONFIG_PM_RUNTIME is, the following warning message appeared: drivers/virtio/virtio_pci.c:770:12: warning: ?virtio_pci_freeze? defined but not used [-Wunused-function] static int virtio_pci_freeze(struct device

I built a v4.11-rc1 kernel, and booted it in a KVM guest and got this oops during startup. My config is attached: [ 2.386786] virtio-pci 0000:00:07.0: virtio_pci: leaving for legacy driver [ 2.395650] BUG: unable to handle kernel paging request at ffff97a3ec5f4000 [ 2.396005] IP: string+0x43/0x80 [ 2.396005] PGD 2d25b067 [ 2.396005] PUD 2d25f067 [ 2.396005] PMD 12c696063 [

I built a v4.11-rc1 kernel, and booted it in a KVM guest and got this oops during startup. My config is attached: [ 2.386786] virtio-pci 0000:00:07.0: virtio_pci: leaving for legacy driver [ 2.395650] BUG: unable to handle kernel paging request at ffff97a3ec5f4000 [ 2.396005] IP: string+0x43/0x80 [ 2.396005] PGD 2d25b067 [ 2.396005] PUD 2d25f067 [ 2.396005] PMD 12c696063 [

This replaces find_vq/del_vq with find_vqs/del_vqs virtio operations, and updates all drivers. This is needed for MSI support, because MSI needs to know the total number of vectors upfront. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/block/virtio_blk.c | 11 +++--- drivers/char/hw_random/virtio-rng.c | 11 +++--- drivers/char/virtio_console.c | 27

This replaces find_vq/del_vq with find_vqs/del_vqs virtio operations, and updates all drivers. This is needed for MSI support, because MSI needs to know the total number of vectors upfront. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/block/virtio_blk.c | 11 +++--- drivers/char/hw_random/virtio-rng.c | 11 +++--- drivers/char/virtio_console.c | 27

Hi, These patches add support for S4 to virtio (pci) and all drivers. For each driver, all vqs are removed before hibernation, and then re-created after restore. Some driver-specific uninit and init work is also done in the freeze and restore functions. All the drivers in testing work fine: * virtio-blk is used for the only disk in the VM, IO works fine before and after. * virtio-console: