NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: installing on a VPS



Hello,

Thank you for emailing me.

After many failures, I finally found a way to get the NetBSD kernel to boot. Rackspace would not boot the xen kernel. It would crash before it was completely loaded. The generic kernel boots.

I thought that at this point I would be through the worst of installing NetBSD on rackspace, but there is a new issue. The network seems to stop working for a few seconds and then it goes back to normal. Checking the dmesg I get this:

# dmesg | grep re0
re0 at pci0 dev 4 function 0: RealTek 8139C+ 10/100BaseTX (rev. 0x20)
re0: interrupting at ioapic0 pin 32
re0: Ethernet address bc:76:4e:20:7a:b8
re0: using 64 tx descriptors
rlphy0 at re0 phy 0: Realtek internal PHY
re0: watchdog timeout
re0: watchdog timeout
re0: watchdog timeout
re0: watchdog timeout

After searching about this, it seems this exists in more than just NetBSD.

Here is a link:
http://openbsd-archive.7691.n7.nabble.com/XenServer-and-re0-watchdog- timeout-td219092.html

From what they say the best way to solve this problem is to change the network card that the virtualizer is emulating. I put in a support ticket at rackspace to see if they can do this. I am not sure that this will be an option with rackspace. Is there a better solution?

Kind Regards,
Al






On Aug 30, 2016, at 4:41 PM, Brian Buhrow wrote:

hello. Some years ago, I installed NetBSD-5 on a Rackspace server. What
I remember doing, and it has been a while, was to put the machine into
recovery mode, then, dd a preformatted image on to the disk. As I recall,
once the image was on and booted, I was able to log in and configure a
raid1 mirror, since the image thought it was part of a raid1 raid set and
things worked quite reliably while we needed it.
	If this is a xen installation for the VPS, I'd suggest doing the same
thing. Make sure you have the network configured in the image you lay down with a fixed address that you know and which you can reach, so once
you tell the system to boot, you can log in remotely.

	You may need to try several times with creating the image before it
works, but I think it will be pretty straightforward, once you figure out
how to use the Rackspace tools.

-Brian

On Aug 30,  3:52pm, Al Zick wrote:
} Subject: installing on a VPS
} Hi,
}
} I really hope that there is someone who can help me. I want to
} install NetBSD on a rackspace VPS. I have NetBSD running on a VPS
} hosted by someone else, and they use a very different system for the
} install and I could mount a NetBSD ISO to do the install. This worked } well. However, the install on rackspace is more of a problem. I would
} like to create an image of the running VPS with dd and ssh. Then I
} would like to put the rackspace VPS in recovery mode and once again
} use dd to install it on /dev/xvdb (which will be /dev/xvda after
} switching back from recovery mode).  They said on rackspace that I
} don't need a Xen kernel.
}
} I would like to use the NetBSD boot loader, but the current install
} of Linux uses grub. What boot loader should I be using?
}
} If dd is successful, then I should only have an 8GB root partition on } rackspace, but rackspace is giving me 150GB of disk space. Is there a
} way to either expand the root partition, or should I create separate
} partitions for /var, /usr, and /home? I could then use "dump |
} restore" to move their contents from root to their own partitions.
}
} Is there a better way to install on rackspace? They talk about using } a VHD image. Can I convert an image created with dd into a VHD image?
}
} Also, there is an example of using iPXE. Is this something that is
} supported by NetBSD?
}
} Kind Regards,
} Al
}
}
}
}
-- End of excerpt from Al Zick




Home | Main Index | Thread Index | Old Index