Re: Starting a VM reboots my machine

Yaniv Kaul
2007-11-05T18:54:15Z

Common configuration errors I've encountered (made):
- Firewall on Machine B
- Wrong MAC for Machine B (typo)
- eth0 on Machine A was not used
- They were not on the same subnet.

I'd verify with tcpdump that packets are indeed being sent & received.
Use 'tcpdump -i eth0 -n port 12345' to catch those packets.
You can create your own dmesg entries by running something like:
echo 'test' > /dev/kmsg

HTH,
Y.

-----Original Message-----
From: Cam Macdonell [mailto:cam-edFDblaTWIyXbbII50Afww@public.gmane.org]
Sent: Monday, November 05, 2007 8:08 PM
To: Yaniv Kaul
Cc: Dor Laor; kvm-devel
Subject: Re: [kvm-devel] Starting a VM reboots my machine

Yaniv Kaul wrote:
> Hi Cam,
>
> The MAC should be of the default gateway, if the listener's IP is not
on
> the same subnet as the client's.
>

Hi Yaniv,

Well, I started netconsole as a module on "machine A". It loads fine
and I get this in dmesg

netconsole: local port 6665
netconsole: interface eth0
netconsole: remote port 12345
netconsole: remote IP <machine B's IP>
netconsole: remote ethernet address <machine B's MAC>
netconsole: local IP <machine A's IP>
netconsole: network logging started

However, when I run "nc -dul 12345" on machine B I get nothing
displayed, even as messages get added to dmesg on machine A. Are there
any common problems with netconsole that I may not be handling?

Thanks,
Cam