similar to: vscsi

Hi, I am working as a system administrator at an internet platform service provider, and I am currently seeking to re-new our Xen virtualization infrastructure for which I am mostly responsible for. Currently, we run Xen 3.4.2/3.4.3 on RHEL/CentOS 5.x (5.7) as Dom0 with CentOS 5.x pv-guests. Based on my experiments, I am currently looking into Xen 4.1.2 on RHEL/CentOS 6.x (6.2), with a

Hi, everyone! We google a lot, but can''t find how to config the pvscsi on our ubuntu13.04 PV on HVM.There are some links http://wiki.xen.org/wiki/Paravirtualized_SCSI http://wiki.xen.org/wiki/Xen_Configuration_File_Options And we use the config option above Configure PVSCSI devices vscsi = [ ''/dev/sdc, 0:0:0:0'' ] I pass sdc to the hvm, but in our pvhvm (ubuntu13.04)

I''m trying to compile pvscsi out-of-tree, and I''m getting an error that set_phys_to_machine is not defined when I try to load the module (with the warning to that effect at compile time too). This used to work fine in pvops. It seems that netfront uses that symbol in a module so I''m confused as to why pvscsi can''t... any suggestions? Is it one of the virtues of

Hi there. I cannot start xen, I''m getting this error System: Linux netwarrior 2.6.31.13 #5 SMP Wed Jun 30 13:25:47 ART 2010 x86_64 AMD Athlon(tm) II X4 630 Processor AuthenticAMD GNU/Linux xend.log le "/usr/lib64/python2.6/site-packages/xen/xend/xenstore/xstransact.py", line 355, in Mkdir complete(path, lambda t: t.mkdir(*args)) File

Hello everyone! I''m new with Xen and i''ve been dealing with the same error the last week. I''m pretty much lost, i don''t know what else to do so i ask for your help. In my case i installed Xen on a amd64 Pc, with Gentoo. I installed the following packages: xen, xen-tools and xen-sources from the gentoo repositories. I''m using 2.6.31-xen-r10 gentoo

Need a scripting help to sort out a list and list all the duplicate lines. My data looks somethings like this host6:dev406mum.dd.mum.test.com:22:11:11:no host7:dev258mum.dd.mum.test.com:36:17:19:no host7:dev258mum.dd.mum.test.com:36:17:19:no host17:dev258mum.dd.mum.test.com:31:17:19:no host12:dev258mum.dd.mum.test.com:41:17:19:no host2:dev258mum.dd.mum.test.com:36:17:19:no

This is probably unreproducible, but I just got a panic whilst scrubbing a simple mirrored pool on scxe snv124. Evidently on of the disks went offline for some reason and shortly thereafter the panic happened. I have the dump and the /var/adm/messages containing the trace. Is there any point in submitting a bug report? The panic starts with: Jan 19 13:27:13 host6

This patch implements the hotplug support for virtio-scsi. When there is a device attached/detached, the virtio-scsi driver will be signaled via event virtual queue and it will add/remove the scsi device in question automatically. v2: handle no_event event Signed-off-by: Cong Meng <mc at linux.vnet.ibm.com> Signed-off-by: Sen Wang <senwang at linux.vnet.ibm.com> ---

This patch implements the hotplug support for virtio-scsi. When there is a device attached/detached, the virtio-scsi driver will be signaled via event virtual queue and it will add/remove the scsi device in question automatically. v2: handle no_event event Signed-off-by: Cong Meng <mc at linux.vnet.ibm.com> Signed-off-by: Sen Wang <senwang at linux.vnet.ibm.com> ---

This patch implements the hotplug support for virtio-scsi. When there is a device attached/detached, the virtio-scsi driver will be signaled via event virtual queue and it will add/remove the scsi device in question automatically. v2: handle no_event event v3: add handle event dropped, and typo fix Signed-off-by: Sen Wang <senwang at linux.vnet.ibm.com> Signed-off-by: Cong Meng <mc at

This patch implements the hotplug support for virtio-scsi. When there is a device attached/detached, the virtio-scsi driver will be signaled via event virtual queue and it will add/remove the scsi device in question automatically. v2: handle no_event event v3: add handle event dropped, and typo fix Signed-off-by: Sen Wang <senwang at linux.vnet.ibm.com> Signed-off-by: Cong Meng <mc at

vqs are freed in virtscsi_freeze but the hotcpu_notifier is not unregistered. We will have a use-after-free usage when the notifier callback is called after virtscsi_freeze. Signed-off-by: Asias He <asias at redhat.com> --- drivers/scsi/virtio_scsi.c | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/drivers/scsi/virtio_scsi.c b/drivers/scsi/virtio_scsi.c

vqs are freed in virtscsi_freeze but the hotcpu_notifier is not unregistered. We will have a use-after-free usage when the notifier callback is called after virtscsi_freeze. Signed-off-by: Asias He <asias at redhat.com> --- drivers/scsi/virtio_scsi.c | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/drivers/scsi/virtio_scsi.c b/drivers/scsi/virtio_scsi.c

vscsi->num_queues counts the number of request virtqueue which does not include the control and event virtqueue. It is wrong to subtract VIRTIO_SCSI_VQ_BASE from vscsi->num_queues. This patch fixes the following panic. (qemu) device_del scsi0 BUG: unable to handle kernel NULL pointer dereference at 0000000000000020 IP: [<ffffffff8179b29f>] __virtscsi_set_affinity+0x6f/0x120 PGD 0

vscsi->num_queues counts the number of request virtqueue which does not include the control and event virtqueue. It is wrong to subtract VIRTIO_SCSI_VQ_BASE from vscsi->num_queues. This patch fixes the following panic. (qemu) device_del scsi0 BUG: unable to handle kernel NULL pointer dereference at 0000000000000020 IP: [<ffffffff8179b29f>] __virtscsi_set_affinity+0x6f/0x120 PGD 0

Pe?a wrote: > Hi Dan, > i get a segfault on windows-pr if i run mulitple tails by threading, one thread for each host i''m tailing. > > C:\family\ruby\win-eventlog>dtail.rb > thread/tail-ing Security on host1 > thread/tail-ing Security on host2 > thread/tail-ing Security on host3 > thread/tail-ing Security on host4 > thread/tail-ing Security on host5 >

From: Asias He <asias.hejun at gmail.com> vqs are freed in virtscsi_freeze but the hotcpu_notifier is not unregistered. We will have a use-after-free usage when the notifier callback is called after virtscsi_freeze. Fixes: 285e71ea6f3583a85e27cb2b9a7d8c35d4c0d558 ("virtio-scsi: reset virtqueue affinity when doing cpu hotplug") Cc: stable at vger.kernel.org Signed-off-by: Asias

From: Asias He <asias.hejun at gmail.com> vqs are freed in virtscsi_freeze but the hotcpu_notifier is not unregistered. We will have a use-after-free usage when the notifier callback is called after virtscsi_freeze. Fixes: 285e71ea6f3583a85e27cb2b9a7d8c35d4c0d558 ("virtio-scsi: reset virtqueue affinity when doing cpu hotplug") Cc: stable at vger.kernel.org Signed-off-by: Asias

Note: for consistency, and to avoid sparse errors, convert all fields, even those no longer in use for virtio v1.0. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> Acked-by: Paolo Bonzini <pbonzini at redhat.com> --- include/linux/virtio_scsi.h | 32 +++++++++++++++------------- drivers/scsi/virtio_scsi.c | 51 ++++++++++++++++++++++++++++----------------- 2 files changed,

Note: for consistency, and to avoid sparse errors, convert all fields, even those no longer in use for virtio v1.0. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> Acked-by: Paolo Bonzini <pbonzini at redhat.com> --- include/linux/virtio_scsi.h | 32 +++++++++++++++------------- drivers/scsi/virtio_scsi.c | 51 ++++++++++++++++++++++++++++----------------- 2 files changed,