Re: [Xen-API] XCP iSCSI boot fails at "Starting the XCP networking daemon"

[Rob Hoes <Rob.Hoes@xxxxxxxxxx>]

The xcp-networkd daemon is new in XCP 1.6. Where the old system used the CentOS 
way of configuring the network using /etc/sysconfig/network-scripts, the 
network daemon uses more general Linux networking commands to get things done 
(this makes it suitable to run on Debian-based systems as well).

I am not sure how all this interacts with booting from iSCSI, though. If it 
helps, you could try switching off the network daemon using "chkconfig 
xcp-networkd off" (if I recall correctly), and then configure the management 
interface yourself.

Cheers,
Rob

> -----Original Message-----
> From: xen-api-bounces@xxxxxxxxxxxxx [mailto:xen-api-
> bounces@xxxxxxxxxxxxx] On Behalf Of Damon Smith
> Sent: 13 November 2012 3:27 AM
> To: Adrian Costin
> Cc: xen-api@xxxxxxxxxxxxx
> Subject: Re: [Xen-API] XCP iSCSI boot fails at "Starting the XCP networking
> daemon"
> 
> Adrian,
> 
> Thanks for your quick response. Unfortunately I wasn't able to get this
> working.
> 
> I had to *create* the following files (they were not already present):
> 
> /etc/sysconfig/network-scripts/ifcfg-eth0:
> DEVICE=eth0
> BOOTPROTO=dhcp
> ONBOOT=yes
> XENMANAGED=no
> 
> /etc/sysconfig/network-scripts/ifcfg-xenbr0:
> DEVICE=xenbr0
> BOOTPROTO=dhcp
> ONBOOT=yes
> XENMANAGED=no
> 
> 
> At boot I recive notifications about bringing up eth0 and configuring it, but 
> I
> also see failures that "xenbr0 does not exist".
> 
> I'll admit I know very little about CentOS, especially networking, so do
> correct me if I completely misinterpreted what you said.
> 
> Any other ideas? Does the xenbr0 interface have a different MAC address
> that might cause it to obtain a different IP address from DHCP? Anything
> else?
> 
> Thanks,
> Damon
> 
> ----- Original Message -----
> From: "Adrian Costin" <adrian.costin@xxxxxxxxx>
> To: xen-api@xxxxxxxxxxxxx
> Cc: apple@xxxxxxxxxxxxxx
> Sent: Saturday, November 10, 2012 1:22:01 AM
> Subject: Re: [Xen-API] XCP iSCSI boot fails at "Starting the XCP networking
> daemon"
> 
> Hi,
> 
> I've managed to get XCP 1.5 to boot off iSCSI which also has this problem.
> What I've done is edit ifcfg-xenbr0 (or whichever bridge you boot off) and
> set XENMANAGED=no and assigned the IP directly into the ifcfg file (in your
> case I guess it can be set to DHCP).
> 
> It also has a problem when rebooting that it shuts down the network
> interfaces before it finishes the reboot and then it just stays there unable 
> to
> continue the reboot.
> 
> Best regards,
> Adrian Costin
> 
> 
> On Sat, Nov 10, 2012 at 7:41 AM, Damon Smith < apple@xxxxxxxxxxxxxx >
> wrote:
> 
> 
> Hello,
> I am working on getting an XCP host to boot via iSCSI. I have had pretty good
> success getting it installed and configured thus far, needing only a few hacks
> to get it to a bootable state, but appear to have run into an issue.
> 
> Upon booting, the system loads fine until it reaches "Starting the XCP
> networking daemon". This command will eventually time-out and a few
> seconds later I will start getting errors about journal writing. It seems to 
> me
> like the "Starting the XCP networking daemon" interrupts my connection to
> my iSCSI target. Presumably xcp-networkd brings the interfaces down in
> order to reconfigure them, but after bringing them down is unable to finish
> as it can no longer access the filesystem.
> 
> I've tried various options in /etc/xcp/network.conf: both "bridge" and
> "openvswitch" fail in the same manner.
> 
> Are there any additional configuration options I can use to resolve this?
> Would modifying my init files help? Can I just disable xcp-networkd
> completely and manage the networking configuration myself?
> 
> I feel that once this issue is resolved I will have a working XCP system
> booting from iSCSI, which would be very useful.
> 
> I am running the latest version of XCP and am using DHCP to configure my
> network. The iSCSI target is running FreeNAS.
> 
> Any thoughts?
> 
> Damon
> 
> _______________________________________________
> Xen-api mailing list
> Xen-api@xxxxxxxxxxxxx
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
> 
> 
> Hi,
> 
> I've managed to get XCP 1.5 to boot off iSCSI which also has this problem.
> What I've done is edit ifcfg-xenbr0 (or whichever bridge you boot off) and
> set XENMANAGED=no and assigned the IP directly into the ifcfg file (in your
> case I guess it can be set to DHCP).
> 
> It also has a problem when rebooting that it shuts down the network
> interfaces before it finishes the reboot and then it just stays there
> unable to continue the reboot.
> 
> Best regards,
> Adrian Costin
> 
> 
> On Sat, Nov 10, 2012 at 7:41 AM, Damon Smith <apple@xxxxxxxxxxxxxx>
> wrote:
> 
> > Hello,
> > I am working on getting an XCP host to boot via iSCSI. I have had pretty
> > good success getting it installed and configured thus far, needing only a
> > few hacks to get it to a bootable state, but appear to have run into an
> > issue.
> >
> > Upon booting, the system loads fine until it reaches "Starting the XCP
> > networking daemon". This command will eventually time-out and a few
> seconds
> > later I will start getting errors about journal writing. It seems to me
> > like the "Starting the XCP networking daemon" interrupts my connection
> to
> > my iSCSI target. Presumably xcp-networkd brings the interfaces down in
> > order to reconfigure them, but after bringing them down is unable to
> finish
> > as it can no longer access the filesystem.
> >
> > I've tried various options in /etc/xcp/network.conf: both "bridge" and
> > "openvswitch" fail in the same manner.
> >
> > Are there any additional configuration options I can use to resolve this?
> > Would modifying my init files help? Can I just disable xcp-networkd
> > completely and manage the networking configuration myself?
> >
> > I feel that once this issue is resolved I will have a working XCP system
> > booting from iSCSI, which would be very useful.
> >
> > I am running the latest version of XCP and am using DHCP to configure my
> > network. The iSCSI target is running FreeNAS.
> >
> > Any thoughts?
> >
> > Damon
> >
> > _______________________________________________
> > Xen-api mailing list
> > Xen-api@xxxxxxxxxxxxx
> > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
> >
> 
> _______________________________________________
> Xen-api mailing list
> Xen-api@xxxxxxxxxxxxx
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api