similar to: Xen PVSCSI: status, issues and some tests

Hello, does anyone knows, if and when pvscsi will be available in the official linux kernel? Kind regards. Christian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

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)

Hello, http://pasik.reaktio.net/xen/patches/xen-pvscsi-drivers-linux-2.6.32.27-pvops-v01.diff This is the first version of Xen PVSCSI drivers, both the scsiback backend and scsifront frontend, ported from Novell SLES11SP1 2.6.32 Xenlinux kernel to pvops xen/stable-2.6.32.x branch. At the moment it''s *only* compile-tested with the latest xen/stable-2.6.32.x git kernel as of today

I''m not sure if this is a debian thing or if debian is using an older version, but I see this in xend debug log when I try to use vscsi: cat: /sys/bus/scsi/devices/host6/vendor: No such file or directory cat: /sys/bus/scsi/devices/host6/model: No such file or directory cat: /sys/bus/scsi/devices/host6/type: No such file or directory cat: /sys/bus/scsi/devices/host6/rev: No such file or

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

Porting the pvSCSI backend driver to the pvops kernel is turning out to be a bit harder than first thought, mostly because all the Linux routines that might be useful are written with the assumption that they would be passed a mapped buffer and they would then build an sg list out of that. pvSCSI already has an sg list, and all the routines that it makes use of have been deprecated since 2.6.18

Hi, As for xm create and xm new, an error may not occur even if wrong vscsi configuration is given. e.g. vscsi = [ ''0:0:0:0,0:0:0:0'', ''0:0:0:0,1:0:0:0'' ] # xm create vm1 Using config file "/etc/xen/vm1". Started domain vm1 (id=8) # xm scsi-list vm1 Idx BE state host phy-hctl phy vir-hctl devstate 0 0 1 0 0:0:0:0

I''m updating the gplpv pvscsi driver to support the pvscsi driver in 3.3, and it''s not working properly. The first command windows issues is a ''report luns'' command, with a 16 byte buffer. The response that Dom0 gives me says that this was executed successfully. Windows then issues another ''report luns'' command that is also returned from Dom0

Hi Alok, Joining this a bit late as this was just brought to my attention. It would have been nice to CC the virtualization mailing list. Please do in future submissions. Alok Kataria wrote: > VMware PVSCSI driver - v4. > / > > diff --git a/drivers/scsi/pvscsi.h b/drivers/scsi/pvscsi.h > new file mode 100644 > index 0000000..96bb655 > --- /dev/null > +++

Hi Alok, Joining this a bit late as this was just brought to my attention. It would have been nice to CC the virtualization mailing list. Please do in future submissions. Alok Kataria wrote: > VMware PVSCSI driver - v4. > / > > diff --git a/drivers/scsi/pvscsi.h b/drivers/scsi/pvscsi.h > new file mode 100644 > index 0000000..96bb655 > --- /dev/null > +++

All, I've updated the open-vm-tools packages that have been floating around to the latest release - 4/25/2010 - for those that are interested. There is quite a bit of new additions/changes over the past year such as the addition of a fuse driver for vmblock devices, vmxnet3, pvscsi, etc. SRPMS and .spec's available here: http://www.davehollis.com/packages/open-vm-tools-kmod.spec

According to the xen 4.1 release notes linked from here: http://xen.org/products/xen_source.html Some features are missing from xen 4.1. i.e. *List of missing features from xl/libxl in Xen 4.1:* ** - *PVUSB (for more info see PVUSB sections of: XenUSBPassthrough<http://wiki.xen.org/xenwiki/XenUSBPassthrough.html> )* - *PVSCSI (for more info see:

pvSCSI backend driver Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com> Signed-off-by: Jun Kamada <kama@jp.fujitsu.com> ----- Jun Kamada _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

pvscsi appears to be missing from the pvops kernel. Is there a specific reason for this or has it just not been done yet? James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, I am trying out Xen for the first time and I am having a few problems with getting it working. The computer is a quad core Intel Xeon with VT enabled, 8gb of RAM and 2 x 15,000rpm SAS drives in RAID1. I have installed CentOS 5 64bit and installed Xen 3.3.0 via yum. I have successfully booted in to dom0. Here is my grub.conf on dom0: > # grub.conf generated by anaconda > # > #

Forgot to copy the virtualization list.. On Wed, 2009-09-30 at 11:53 -0700, Alok Kataria wrote: > Hi James, > > Given that their are no more modification requests, I think this driver > should be ready for prime time now. I have incorporated the remaining > few outstanding comments while rebasing the patch for 32-rc1. > > Please consider this for the SCSI tree. Also let me

Forgot to copy the virtualization list.. On Wed, 2009-09-30 at 11:53 -0700, Alok Kataria wrote: > Hi James, > > Given that their are no more modification requests, I think this driver > should be ready for prime time now. I have incorporated the remaining > few outstanding comments while rebasing the patch for 32-rc1. > > Please consider this for the SCSI tree. Also let me

Hello, I'm using CentOS 5.5 / 16bit as a virtual machine in VMWare Workstation and have installed the "VMWare Tools" by running vmware-install.pl and vmware-config-tools.pl but can't figure out how to make the VM shutdown, when I shutdown the Windows PC hosting it. Does anybody please have any hints or scripts? Do I need to use any VMWare modules if I just want to shutdown the

Hi I am attempting to setup Xen 4.10 with kernel 4.9.86-30 ( virt7-xen-410-testing, virt7-common-testing ) on CentOS7 After installing everything, the machine was unable to boot and hung in dracut stating it could not find its root device. The testsystem I use is a somewhat aged Dell M915 Blade (Quad opteron 61xx), using an MPT SAS controller for it's SAS boot drives. Stock CentOS 7

This series implements virtio-scsi queue steering, which gives performance improvements of up to 50% (measured both with QEMU and tcm_vhost backends). The patches build on top of the new virtio APIs at http://permalink.gmane.org/gmane.linux.kernel.virtualization/18431; the new API simplifies the locking of the virtio-scsi driver nicely, thus it makes sense to require them as a prerequisite.