Re: Cannot see boot messages with DomU

["Sarton O'Brien" <bsd-xen%roguewrt.org@localhost>]

Manuel Bouyer wrote:
> On Mon, Feb 11, 2008 at 04:06:56PM +1100, Sarton O'Brien wrote:
> > Hi John,
> >
> > John Hayward wrote:
> > > newserver: {69} xm create -c netbd
> > > Using config file "./netbd".
> > > newserver: {70} Error: Device 0 (vif) could not be connected. Hotplug 
> > > scripts not working.
> > > ====
> > >
> > > It takes about 2 minuites between when I xm create and when the error
> > > occures.
> > >
> > > dmesg reveals:
> > > ====
> > > xvif1.0: Ethernet address aa:00:00:51:02:f0
> > > xvif1.0: disconnecting
> > > xvif2.0: Ethernet address aa:00:00:51:02:f0
> > > xvif2.0: disconnecting
> > > xvif3.0: Ethernet address aa:00:00:51:02:f0
> > > xvif3.0: disconnecting
> > > ====
> > >
> > > My netbd config file has:
> > > ====
> > > kernel = "/netbsd-INSTALL_XEN3_DOMU"
> > > memory = 256
> > > name = "netbd"
> > > #cpu = -1   # leave to Xen to pick
> > > #nics = 1
> > > vif = [ 'mac=aa:00:00:50:02:f0, bridge=bridge0' ]
> > > disk = [ 'phy:/dev/wd0f,0x01,w', 'phy:/dev/cd0a,0x2,r' ]
> > > root = "/dev/wd0a"
> > > ===
> > >
> > > /dev/wd0f is not mounted and is available
> > I'd say it's possible it's rejecting the mac address you are using. 
>
> No, it should be fine. I do have  domUs with adresses prefixed aa:00:00

Ahhh ... ok. I was thinking back to when I first set up xen and I seemed 
to remember that was a requirment. My mistake, sorry.

Sarton