AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Xenserver virtualmachine boot order3/28/2023 One other side note, if I go the "shell" mode via the Xenserver installer, none of the ethernet NICs have any configuration, so something is definitely missing. As far as UCS is concerned, I think I have the iscsi LUN connected successfully - the trick, how do I get Xenserver (or any VMWare, or any other hypervisor for that matter) to recognize the remote iscsi LUN when installing? I see the iscsi connection being made successfully so I know that is working (see attached screen shots).ġ) I can see the iscsi LUN being connected to the blade via the Cisco VIC (iscsi vNIC)Ģ) I can see the iscsi LUN connection at the adapter via the FIģ) I can see the iscsi LUN connection at the NetApp backend storageĤ) I'm choosing the recommended option at the Citrix Xenserver installer splash screen which is supposed to allow the presentation of a remote LUN to the installer We have B200M2 blades with the M81KR adapter. Initiator_error_code: ISCSI_BOOT_NIC_NO_ERRORĭoing Multipath iscsi boot is a whole other animal at this point - I'll tackle that one next Not sure why the "State" of the target is "INVALID"Ĭonnect adapter x/y/z (chassis/blade/adapter#) One other thing : running the following commands from the FI shows the output below. OxNas1-F2> Mon Jun 4 10:12:34 EST : ISCSI: New session from initiator :xenucs02 at IP addr Incidentally, I see the following message on the NetApp right before seeing the subsequent "Initialize error 1" message on the blade - SO, it appears the iscsi connection is being made to the NetApp, however, I still see the error on the blade. If I go through the normal install steps on Xenserver it will load ot the local disks, even though my local disk configuration is set as "No Disk Policy".Ĭan anyone please send me in the right direction? I figure if I can just get Xen loaded then it will boot correctly since I see the iscsi connection to the backend storage - I just can't tell what the problem is at this point. So at this point, I'm not sure if it's a problem witt my iscsi vnic setup on the UCS or if it's a problem with XenServer itself. I have Xenserver running when installed on the local storage (does not require iscsi vnics) however I can not get the iscsi boot working.Īfter reading all the documentation I can find on the subject, at the Xenserver install screen you are supposed to enter multipath mode but that's not actually a real option here since I'm not doing multipath to the backend storage for my dev Xen environment.Īt any rate, when I'm booting up the blade I do see an iscsi initiator connection on our NetApp so I think the iscsi vnic is working correctly (my boot policy is set as CD-ROM then ISCSI boot). Note the location may be different if you used step 1 to edit the registry, the path in that case would be HKLM\TempSoftSystem\CurrentControlSet.Anyone tried this yet? I know a lot of VMWare people are probably doing this. hklm:\\System\CurrentControlSet\Control\Class\\UpperFilters You should then be able to access the VM with the default drivers. Instructions of how to do this can be found here.Ģ) Remove the following keys from the registry, unload the hive as per the step 1 document and reboot. Load the operating systems registry hive so that it can be edited. If you are able to get in with safe mode, this article might help with uninstalling the XenServer drivers manually instead.ġ) Boot into Windows recovery mode if you can't get in with safe mode. The fix is to boot into recovery mode and remove the UpperFilters keys from the registry. Also if you have updated or uninstalled the XenServer drivers inside an XenServer environment you may also find that the VM doesn't boot and just blue screens. If you have done a migration from XenServer to VMWare on a Windows VM and find that the VM doesn't boot, it could be related to the XenServer drivers.
0 Comments
Read More
Leave a Reply. |