19 messages in com.xensource.lists.xen-develRe: [Xen-devel] Network issues with S...
FromSent OnAttachments
Keir Fraser07 Nov 2003 08:43 
Gregory Newby07 Nov 2003 13:53 
Ian Pratt07 Nov 2003 14:03 
Gregory Newby07 Nov 2003 14:35 
Ian Pratt07 Nov 2003 14:53 
Gregory Newby07 Nov 2003 16:29 
Ian Pratt07 Nov 2003 16:36 
Gregory Newby07 Nov 2003 17:07 
Ian Pratt07 Nov 2003 17:21 
Gregory Newby07 Nov 2003 17:38 
Ian Pratt07 Nov 2003 17:57 
Gregory Newby07 Nov 2003 18:55 
Torne Wuff07 Nov 2003 20:20 
Keir Fraser08 Nov 2003 00:48 
Gregory Newby10 Nov 2003 10:48 
Ian Pratt10 Nov 2003 12:32 
Gregory Newby10 Nov 2003 15:09 
Ian Pratt10 Nov 2003 15:25 
Torne Wuff10 Nov 2003 16:55 
Subject:Re: [Xen-devel] Network issues with SuSE firewall
From:Ian Pratt (Ian.@cl.cam.ac.uk)
Date:11/07/2003 05:21:41 PM
List:com.xensource.lists.xen-devel

$ xenctl script -f/etc/xen-mydom (the default script) $ xenctl domain start -n2

The /etc/xen-mydom should automatically start the domain.

It doesn't. (You saw my prior "xenctl domain list" output, which said it was stopped.)

This is really odd. The last line of the script contains a "domain start". Is there a missing LF or something?

As I mentioned in my other message, it would be great to be able to see console messages, but they are either being firewalled or otherwise redirected.

Have you been using xen_read_console? You should be able to watch the other domain booting, and check that it comes up OK.

I run it (in the background) but never see anything. Even when I reboot, I don't get shutdown messages (they don't appear on the physical console).

Very odd. Any chance you can get a serial line on the system? The other domain's boot messages should also come out on serial.

Please can you send me the output from running xenctl, and the console message from the booting domain.

Yep. Maybe the output from the "xenctl script..." startup is informative. This is with the default /etc/xen-mynewdom, containing:

I take it that you're wanting to boot with the initrd copied off the CD, and use the CD for the new domain's /usr ?

peabody(root) ~ [6] > telnet 169.254.1.3 22 Trying 169.254.1.3... telnet: connect to address 169.254.1.3: Connection refused

AFAIK, Our CD doesn't run a telnetd by default. There should be an sshd, but I think your problem lies elsewhere...

Connection refused is a slightly odd message. If the domain was totally dead, I'd expect the telnet to hang.

What happens if you run tcpdump in domain0. Do you see any packets arriving at 169.254.1.0 ?

Ian

------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/

_______________________________________________ Xen-devel mailing list Xen-@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel