I've got a couple of different iSCSI targets, one supplies the root drive
for network booting, the other provides additional storage volumes.
For the root drive, it's preferable to have the noop timeouts switched to
0, but I'd ideally like noop to be turned on for the other iSCSI targets
(and
On Mon, Jul 10, 2017 at 05:57:57AM -0700, George Kennedy wrote:
> Also, 'iscsid' is runnig prior to the bond interface setup.
If you run it as 'iscsid -d ' do you see any extra output when the
network interface goes down?
Thanks.
>
> On Friday, July 7, 2017 at 2:33:29 PM UTC-4, George Kennedy
On Wed, Jul 05, 2017 at 09:03:43AM +0200, Ulrich Windl wrote:
> > Note, during the development of my /dev/random implementation, I added the
> > getrandom-like blocking behavior to /dev/urandom (which is the equivalent to
> > Jason's patch except that it applies to user space). The boot process
Running RHEL 6.7 with a Xen guest that's an iSCSI target and a second Xen
guest that
installs to the iSCSI target, the subsequent iSCSI boot from the iSCSI
target fails
if network bonding is configured in the second Xen guest.
iSCSI boot works ok if network bonding is not setup in the second
On Wed, Jul 05, 2017 at 09:16:09AM -0400, Paul Koning wrote:
>
> In the implementations I know, /dev/random and /dev/urandom are the
> same driver, the only difference is that when you read from
> /dev/random there's a check for the current entropy level.
It's in the same driver but /dev/random
Also, 'iscsid' is runnig prior to the bond interface setup.
On Friday, July 7, 2017 at 2:33:29 PM UTC-4, George Kennedy wrote:
>
> Running RHEL 6.7 with a Xen guest that's an iSCSI target and a second Xen
> guest that
> installs to the iSCSI target, the subsequent iSCSI boot from the iSCSI
>
