Hello,
Friday, March 16, 2007, 8:59:35 AM, you wrote:
j> On Fri, Mar 16, 2007 at 07:31:40AM +1100, Russell Robinson wrote:
>> Hi,
>>
>> Sorry, spoke too soon
>>
>> Friday, March 16, 2007, 7:10:22 AM, you wrote:
>> RR> I *knew* it was something simple:
>> RR> ifconfig veth3 IPAddr up
>>
>> This made IPAddr respond to ping, but it's not the guest/domU.
>>
>> The Wiki docs don't seem to be correct....missing lots of information
>> and my dom0 doesn't have a peth0 interface created by the bridge, as
>> described (is that the problem)?
>>
j> Yeah, I was just prep'ing a reply to tell you not to get too excited.
j> A working bridge configuration for you should look like:
j> $ brctl show
j> bridge name bridge id STP enabled interfaces
j> xenbr0 8000.feffffffffff no vif0.0
j> peth0
j> vif3.0
j> At the moment it appears that the xen network-bridge script was
j> very unsuccessful in putting your eth0 interface onto the bridge.
j> Can you check the xen logfiles as well of the syslog to see if there is
j> any indication of why this failed.
j> My initial gut feeling was that it was because you were using aliases
j> (ie you have an interface called eth0:0). I recommend that you take down
j> that eth0:0 interface and try again.
OK, finally got rid of the old aliasing.
I briefly saw the peth0 and vif0.0 interface after doing a "service start xend".
I thought, AHA! So, I switched off any IPTABLES stuff and rebooted
dom0.
No peth0 or vif0.0.
Also, "service start xend" says nothing and "xend status" says nothing
either.
/var/log/xen/xend.log has this:
[2007-03-16 09:30:48 xend 6160] WARNING (XendAuthSessions:27) python-pam is requ
ired for XenAPI support.
Warning doesn't sound fatal, and a package called "python-pam" does
not exist anywhere on the internet (well, it's referenced as ancient).
Is this the problem?
xend.log also has this from the boot process:
[2007-03-16 09:25:38 xend 5208] WARNING (XendAuthSessions:27) python-pam is
required for XenAPI support.
[2007-03-16 09:25:38 xend 5239] INFO (SrvDaemon:322) Xend Daemon started
[2007-03-16 09:25:38 xend 5239] INFO (SrvDaemon:326) Xend changeset:
unavailable.
[2007-03-16 09:25:38 xend 5239] INFO (SrvDaemon:333) Xend version: Unknown.
[2007-03-16 09:25:38 xend.XendDomainInfo 5239] INFO (XendDomainInfo:135)
Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at
/local/domain/0
[2007-03-16 09:25:38 xend.XendDomainInfo 5239] WARNING (XendDomainInfo:149)
/local/domain/0/vm is missing. recreate is confused, trying our best to recover
This doesn't look good, but who knows what it means?
Nothing should be this hard....it makes Microsoft look good (which is
almost impossible).
--
Best regards,
Russell mailto:russellr@xxxxxxxxxxxxxxxxxxx
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home