Hi James, I''m trying to find a way to temporarily attach a disk to a machine running Windows 20008r2 + gplpv_fre_wlh_x86_0.10.0.98-dontuse.msi on top of Xen 3.4.1. However I can''t seem to get the following to work : - with iscsi : I had to disable checksum offload, but even then I can''t get the disk shows up (iscsi target connected just fine). The disk shows up correctly without GPLPV - xm block-attach : block-attach success, but the disk didn''t show up even when I rescan disk in Windows. Then again it didn''t work even withour GPLPV. Is there something in GPLPV that''s preventing MS iscsi initiator from working properly? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Hi James, > > I''m trying to find a way to temporarily attach a disk to a machine > running Windows 20008r2 + gplpv_fre_wlh_x86_0.10.0.98-dontuse.msi on > top of Xen 3.4.1. However I can''t seem to get the following to work : > - with iscsi : I had to disable checksum offload, but even then I > can''t get the disk shows up (iscsi target connected just fine). The > disk shows up correctly without GPLPV > - xm block-attach : block-attach success, but the disk didn''t show up > even when I rescan disk in Windows. Then again it didn''t work even > withour GPLPV. > > Is there something in GPLPV that''s preventing MS iscsi initiator from > working properly? >Can you try the latest 0.10.0.130 release? It''s unlikely that the bug fixes there are relevant to you but it''s worth a shot. Can you tell me the exact block-attach syntax you are using, and what appears in /var/log/xen/qemu-<domname>.log when you do? James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Oct 19, 2009 at 11:46 AM, James Harper <james.harper@bendigoit.com.au> wrote:> Can you try the latest 0.10.0.130 release? It''s unlikely that the bug > fixes there are relevant to you but it''s worth a shot.Done. I used zfs-rollback and installed latest version.> Can you tell me the exact block-attach syntax you are using, and what > appears in /var/log/xen/qemu-<domname>.log when you do?# xm block-attach win2008-template phy:/dev/sda hdb w at this time the windows console says a new xen vbd device is installed successfully. At least this is different from the last version. After that, a popup appears asking to restart, and device manager shows a new xen block device with exclamation mark, and properties says "This driver is not configured correctly (Code 1). You need to restart your computer before the changes you made to this device will take effect." qemu-dm log attached. After restart, I can safely remove the disk using "xm block-detach" and Windows says "safe to remove hardware". Attach-detach the disk (or other disk image) as hdb works as expected now. However attaching it as another device (e.g. xvda) brings the "you need to restart" dialog. So for "xm block-attach", it seems to work, but with the issue of Windows needs to restart once after recognizing a new block device. Why is that?. As for iscsi, after I connect to iscsi server, the Device section of iscsi initiator simply says "Name: Disk-1, Address: Port 4: Bus 0: Target 0: Lun 0". No volume path, legacy device name, or device interface name. Device Manager has "Microsoft iscsi initiator", disk drive does not show any new disks. Disconnect doesn''t work (it simply display hourglass cursor). I had to destroy domU, and recreate it. When booting with NOGPLPV, iscsi initiator works as expected. Volume Path says "E:\;F:\", Legacy device name "\\.\PhysicalDrive1". Do you also need qemu-dm log for this? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Matthieu Patou
2009-Oct-22 07:21 UTC
Re: [Xen-users] Re: iscsi and block-attach with GPLPV
Hi fajar, I''m taking the opportunity to share my 2 cent tips: every month there is a guy comming to our facility to update software with an external hard drive for our windows 2008 server (not r2) runned as a xen HVM virtual server so I had to find a way to allow easily connect the hard drive. For some reason usb_add do not work well with usb hard drives with windows so I am using xm block-attach. I turns out that to me not all the frontend devices are equivalent as for some of w2k8 saw them completely and for some others I had the "This driver is not configured correctly". Right now I use xm block-attach w2k8dom phy:/dev/sdc hdd w and it''s OK and with hdb it''s not ! I found that if I want to be able to readd a disk for this frontend device I have to do more than xm block-detach w2k8dom frontend_id, more precisely before issuing this command I go in the device manager an search for the "Xen PV DISK SCSI Disk Device" that correspond to the hard drive that I want to remove (I do xm block-list w2k8dom to get the frontend_id then I look at the parent attribute in properties -> Detail the last number is the frontend_id), and then I do a right click -> Uninstall. I''ve been working like this for more than 1 year and most of the time it''s Ok (once I had to reboot the server because it didn''t wanted to see the hard drive). My setup is a bit different from your: * xen 3.2.1 (from debian) * pv drivers 0.10.0.86 (worked also like this with 0.9.xxx) * windows 2008 server HTH Matthieu.> > # xm block-attach win2008-template phy:/dev/sda hdb w > > at this time the windows console says a new xen vbd device is > installed successfully. At least this is different from the last > version. After that, a popup appears asking to restart, and device > manager shows a new xen block device with exclamation mark, and > properties says "This driver is not configured correctly (Code 1). You > need to restart your computer before the changes you made to this > device will take effect." > > qemu-dm log attached. > > After restart, I can safely remove the disk using "xm block-detach" > and Windows says "safe to remove hardware". Attach-detach the disk (or > other disk image) as hdb works as expected now. However attaching it > as another device (e.g. xvda) brings the "you need to restart" dialog. > So for "xm block-attach", it seems to work, but with the issue of > Windows needs to restart once after recognizing a new block device. > Why is that?. >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users