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. Besides the fact you probably don't want any white space in your vif line (I'm not sure if this is detrimental or not but I think it may be from memory), xen requires the use of a specific mac address, at least wrt the first 3 octets. These are:
00:16:3e:Best way to generate this address though is to start a domu with no mac entry just vif = [ 'bridge=bridge0' ] and note down the mac address created when within the domu, then use that address within your config. Doing this will allow you to test the domu and at least remove that whitespace in the interim.
You won't require the root line for a NetBSD domu, but if you did it would be /dev/xbd0a.
You can also remove the commented cpu and nics line as I believe they are not valid for xen3.
Give that a try and if you still have issues just holler. Sarton