similar to: pvscsi and report luns command

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

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

Add vscsiif.h Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com> Signed-off-by: Jun Kamada <kama@jp.fujitsu.com> Signed-off-by: Akira Hayakawa <hayakawa.akira@jp.fujitsu.com> ----- Jun Kamada _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Add "white list" control to SCSI command emulation. Current setting allows following mandatory and safe commands. TEST UNIT READY REZERO UNIT REQUEST SENSE FORMAT UNIT READ BLOCK LIMITS READ(06) WRITE(06) WRITE FILEMARKS SPACE INQUIRY ERASE MODE SENSE(06) SEND DIAGNOSTIC READ CAPACITY READ(10) WRITE(10) REPORT LUN Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com>

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

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

1. Shouldn''t the GPLPV drivers take care of the (bad) clock drift I''m experiencing in my Windows XP HVM? Or is there some other way around this problem that I haven''t been able to find on Google? How can I tell if the GPLPV drivers are active? I''ve added the /gplpv switch to the boot.ini file and the virtual NIC is definitely using the GPLPV version but other

On Sun, Jun 8, 2008 at 3:28 PM, James Harper <james.harper@bendigoit.com.au> wrote: > I''ve just uploaded 0.9.8 to http://www.meadowcourt.org/downloads > > As a reminder, the wiki page is > http://wiki.xensource.com/xenwiki/XenWindowsGplPv > > This release fixes a bug which could be hit under high disk load (high > number of outstanding requests with fragmented

So I successfully installed the GPLPV drivers in a Windows installation I have running under Xen. Turns out SP2 is needed - I wish this was slightly better documented somewhere, as the machine ended up bluescreening and I had to use /NOGPLPV to get it to boot again so I could upgrade it to SP2. My question is this: I ended up using ''disable'' in device manager for the rtl8139 and

A user has pointed out a problem with GPLPV under Xen 4.2 when using PoD. I''m using the difference between XENMEM_maximum_reservation and XENMEM_current_reservation to tell me how much I should balloon down to account for PoD, but when the user has ballooned down to 1G (from 4Gb or 8GB), GPLPV logs the following: 13005008825593: XenPCI XENMEM_maximum_reservation = 262400

Attached is my first attempt at getting the backend pvscsi driver (scsiback) working under the latest pvops kernel. I have tested it with the scsi frontend driver in gplpv, and have restored about 20GB of data from a HP LTO3 tape drive successfully, so it appears to be working fine. There are quite a few changes compared to the version in 2.6.18. The main change is that I get the vaddr for each

I''ve just made my first ever attempt at an Nullsoft installer, so if you want to try it download "Xen PV Drivers 0.9.5.exe" from http://www.meadowcourt.org/downloads/ The installer should detect the version of windows you are running and install the drivers. At the moment you''ll need to install the shutdown monitor service manually, but you can do that from the start

I''ve just made my first ever attempt at an Nullsoft installer, so if you want to try it download "Xen PV Drivers 0.9.5.exe" from http://www.meadowcourt.org/downloads/ The installer should detect the version of windows you are running and install the drivers. At the moment you''ll need to install the shutdown monitor service manually, but you can do that from the start

What is the state of GPLPV and Windows 8? I am currently running tests with Windows 8 and GPLPV rev956 and operations (disk IO, net IO) look good. There seems to be a problem with shutdown/reboot where Windows hangs somewhat and displays a warning about improper shutdown on next reboot. Regards Andreas

Just reporting some iperf results. In each case, Dom0 is iperf server, DomU is iperf client: (1) Dom0: Intel Core2 3.16 GHz, CentOS 5.2, xen 3.0.3. DomU: Windows XP SP3, GPLPV 0.9.12-pre13, file based. Iperf: 1.17 Gbits/sec (2) Dom0: Intel Core2 2.33 GHz, CentOS 5.2, xen 3.0.3. DomU: Windows XP SP3, GPLPV 0.9.12-pre13, file based. Iperf: 725 Mbits/sec (3) Dom0: Intel Core2 2.33 GHz,

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

Hi, DomU is a Win2008 R2 64 When i install the GPLPV drivers the network latency goes from 15ms to random numbers up to 1200ms and eventually dies. If you run a ping from the DomU to another host the network stays alive but the high latency is still there. Further more if i try and uninstall the network driver i am unable to use the old one (realtek) as it cannot detect the device.

I am having problems with save/restore under 3.3.1 in the GPLPV drivers. I call hvm_shutdown(xpdd, SHUTDOWN_suspend), but as soon as I lower IRQL (enabling interrupts), qemu goes to 100% CPU and the DomU load goes right up too. Xentrace is showing a whole lot of this going on: CPU0 200130258143212 (+ 770) hypercall [ rip = 0x000000008020632a, eax = 0xffffffff ] CPU0 200130258151107 (+

Hi Is it true that the GPLPV drivers is incompatible with QCOW images? The Windows DomU works fine with raw standard "file:/" images, and paravirtualized Linux DomU works fine with QCOW and raw images. If i use QCOW images with my Windows DomU''s i get a stop error: 0x00000007b (inaccessible boot device). It looks like the blkback.3.hda process, that normally starts with

I''ve just uploaded a couple of .bat files to http://www.meadowcourt.org/downloads/gplpv_uninstall_bat.zip that will manually (and forcibly) uninstall GPLPV from your computer, which seems to be necessary before doing upgrades from some versions. Run the uninstaller, reboot, then install. There is a 0.9.x and a 0.10.x uninstaller, which differ slightly, but the basic steps performed are: