Hi Chris.
On Friday, 24 July 2009 08:03:29 -0400,
Chris Dukes wrote:
http://zeniv.linux.org.uk/~pakrat/obsd45
3 configs, 3 kernels.
All work on a Core2 Duo T7300 running 2.6.27-7-generic (From ubuntu
intrepid) crammed onto a laptop that's mostly running hardy.
The OpenBSD virtual machines have 256M allocated, e1000 NIC, and vde
backing it.
Firstly, thank you very much by to take the trouble to test and to put
the files in a site.
I was testing the compiled kernels that you provided to me in the VM
with OpenBSD 4.5 in my host with KVM-88 running Ubuntu Hardy Heron
server amd64 on a Athlon 64 X2 3800+ using a kernel 2.6.24-19-server.
The boot parameters were the following:
# OpenBSD
$KVM -hda /dev/vm/fugu-disk -m 512 -boot c -net \
nic,vlan=0,macaddr=00:16:3e:00:00:35,model=ne2k_pci -net tap \
-daemonize -vnc :4 -k es -localtime -serial \
telnet:localhost:4001,server,nowait
bsd.kvm3 and bsd.kvm4 boots without problems and the VM has connectivity
with the rest of my LAN, nevertheless bsd.kvm3l boots without problems
but the network interface does not take the static IP assigned (in none
of the three cases it uses DHCP).
With kernel bsd.kvm3l:
fugu:~# ifconfig
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33204
priority: 0
groups: lo
inet 127.0.0.1 netmask 0xff00
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
enc0: flags=0 mtu 1536
priority: 0
With kernel bsd.kvm[34]:
fugu:~# ifconfig
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33204
priority: 0
groups: lo
inet 127.0.0.1 netmask 0xff00
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
ne3: flags=8863UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST mtu 1500
lladdr 00:16:3e:00:00:35
priority: 0
groups: egress
media: Ethernet 10baseT full-duplex
inet 10.1.0.12 netmask 0xff00 broadcast 10.1.0.255
inet6 fe80::216:3eff:fe00:35%ne3 prefixlen 64 scopeid 0x1
enc0: flags=0 mtu 1536
priority: 0
On the other hand, also I tried to compile the kernel with the
configuration files that you provided to me booting the operating system
with a kernel GENERIC and the option --no-acpi of kvm so that boot
finishes successful (although this way did not have connectivity),
although under these circumstances some of the locally compiled kernels
did not work.
KVM4 boots without problems, but giving a 'ne3: device timeout' and the
VM loses connectivity with the LAN even though the network interface is
configured with its static IP. KVM3 boots OK and it doesn't presents
networking problems. KVM3L boots OK but the interface is not configured
with its static IP as in the previous case with the kernel compiled for
you.
Also I was trying to boot the VM with the KVM option model=e1000. In
this case, the kernels locally compiled with KVM3 and KVM3L didn't
present problems when boot or with the configuration of network,
nevertheless, with kernel locally compiled with KVM4L were rebooted
after mttr similar to as it happened with GENERIC kernel:
mtrr: Pentium Pro MTRR support
uk OpenBSD/i386 BOOT 3.02
boot
booting hd0a:/bsd: 6039964+1059784 [52+336688+318896]=0x7657ec
entry point at 0x200120
and occasionally the boot finishes with:
mtrr: Pentium Pro MTRR support
uvm_fault(0xd080d9e0, 0x0, 0, 1) - e
kernel: page fault trap, code=0
kernel: page fault trap,
code=0
Skernel: page fault trap, code=0
Skernel: page fault trap, code=0
Skernel: page fault trap, code=0
Skernel: page fault trap, code=0
Sstray interrupt 12
kkernel: page fault trap, code=0
Stopped at kernel: page fault trap, code=0
Stopped at kernel: page fault trap, code=0
Stopped at kernel: page fault trap, code=0
Stopped at kernel: page fault trap, code=0
Stopped at kernel: page fault trap, code=0
Stopped at kernel: page fault trap, code=0
Stopped at kernel: page fault trap, code=0
Stopped at kernel: page fault trap, code=0
Stopped at kernel: page fault trap, code=0
Stopped at kernel: page fault trap, code=0
Stopped at kernel: page fault trap, code=0
Stopped at kernel: page fault trap, code=0
Stopped at kernel: page fault trap, code=0
Stopped at kernel: page fault trap, code=0
Stopped at kernel: page fault trap, code=0
Stopped at kernel: page fault trap, code=0
--db_more--
With the three compiled kernels that you provided to me, I didn't have
no kind of problem during boot or of networking using model=e1000,
although it draws attention to me to observe these differences that
commented to you. This difference will be related to hardware that I am
using?
CPU: Athlon 64 X2 3800+
Motherboard: M2N32 SLI
Network interface: 2 x nVidia MCP55
I don't have much experience compiling OpenBSD kernel, but the procedure
that I used was the following one:
* Download
