Hi!
I read a news today about Xen being enabled and tried it out with the
Jan 15th snapshot
SHA256 (install59.iso) =
8d16aeb686a1dcc3ce6e8c5192f8708d3878f7690429c843176c5e755386e4f9
on Xen v. 4.5.1 compiled from Xen sources on Debian v. 8 Jessie running
on an ordinary amd64 Intel platform. (Actually i am using this very Xen
platform to run my workstation as another virtual guest, so platform
itselt is running solid.)
I booted it with
# cat openbsd.cfg
builder = "hvm"
name = "openbsd"
memory = "512"
vcpus = 1
vif = [ 'mac=00:16:3e:79:22:22,bridge=xenbr0' ]
disk = [ 'phy:/dev/vg_data_wd_1tb/openbsd,hda,w',
'file:/tmp/install59.iso-20160115-ss.iso,hdd:cdrom,r']
boot="dc"
vnc=1
then connected with VNC and installed OpenBSD S.S.
It boots afterwards ok and when configuring xnf0 network device with
ifconfig xnf0 192.168.10.128 (or with dhclient) i can ping it from
outside and it seems to work forever. Also i can see other lan packets
passing by xnf0 with tcpdump. But when i connect from outside say with
ssh client then it hangs (i.e. cant enter anything from vnc window,
created simple cronjob within OpenBSD and i see it stops updateing log
file etc). While connecting i see this traffic on dom0
root@moraal-dom0:/etc/xen# tcpdump -ni vif43.0 host 192.168.10.128
19:55:05.985258 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [S],
seq 3673277459, win 29200, options [mss 1460,sackOK,TS val 40346540 ecr
0,nop,wscale 7], length 0
19:55:05.985611 IP 192.168.10.128.22 > 192.168.10.10.33616: Flags [S.],
seq 3141065115, ack 3673277460, win 16384, options [mss
1460,nop,nop,sackOK,nop,wscale 3,nop,nop,TS val 345100460 ecr 40346540],
length 0
19:55:05.986017 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [.],
ack 1, win 229, options [nop,nop,TS val 40346540 ecr 345100460], length
0
19:55:05.987116 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.],
seq 1:33, ack 1, win 229, options [nop,nop,TS val 40346541 ecr
345100460], length 32
19:55:06.012874 IP 192.168.10.128.22 > 192.168.10.10.33616: Flags [P.],
seq 1:22, ack 33, win 2168, options [nop,nop,TS val 345100460 ecr
40346541], length 21
19:55:06.013151 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [.],
ack 22, win 229, options [nop,nop,TS val 40346547 ecr 345100460], length
0
19:55:06.022554 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [.],
seq 33:1481, ack 22, win 229, options [nop,nop,TS val 40346549 ecr
345100460], length 1448
19:55:06.022562 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.],
seq 1481:2001, ack 22, win 229, options [nop,nop,TS val 40346549 ecr
345100460], length 520
19:55:06.023068 IP 192.168.10.128.22 > 192.168.10.10.33616: Flags [.],
ack 2001, win 1926, options [nop,nop,TS val 345100460 ecr 40346549],
length 0
19:55:06.023416 IP 192.168.10.128.22 > 192.168.10.10.33616: Flags [P.],
seq 22:998, ack 2001, win 1926, options [nop,nop,TS val 345100460 ecr
40346549], length 976
19:55:06.026537 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.],
seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40346550 ecr
345100460], length 48
19:55:06.226645 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.],
seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40346601 ecr
345100460], length 48
19:55:06.430626 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.],
seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40346652 ecr
345100460], length 48
19:55:06.838658 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.],
seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40346754 ecr
345100460], length 48
19:55:07.654663 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.],
seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40346958 ecr
345100460], length 48
19:55:09.290635 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.],
seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40347367 ecr
345100460], length 48
19:55:12.558753 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.],
seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40348184 ecr
345100460], length 48
19:55:19.102779 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.],
seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40349820 ecr
345100460], length 48
19:55:32.174732 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.],
seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40353088 ecr
345100460], length 48
19:55:58.350805 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.],
seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40359632 ecr
345100460], length 48
.....
Xen logs dont say much, what i can see approx. 1 minute after hang is
guest rx stalled
[1897100.139144] vif vif-43-0 vif43.0: Guest Rx ready
...
[1897216.889975] vif vif-43-0 vif43.0: Guest Rx stalled
I am using Open vSwitch on Xen dom0 with quite simple configuration,
xenbr0 being OVS switch.
Interestingly, when i use PCI passthru network device instead of vif
device, all seems to work all rigth, with domU config like
builder = "hvm"
name = "openbsd"
memory = "512"
vcpus = 1
disk = [ 'phy:/dev/vg_data_wd_1tb/openbsd,hda,w' ]
pci = [ '08:05.0' ]
vnc=1
If you suggest something to make it work with xnf i would love to hear
about it. Or i can somehow help debugging it further. (I once tried to
use Xen v. 4.6.0 with expectation to start using UEFI but it didnt quite
work out and 4.6.0 felt unstable to me also otherwise so i settled with
old 4.5.x.)
Other than this network issue i am glad to see disk IO is great (ca
50-80 MByte/s i.e. just what is available from my hardware i believe),
saying 'halt -p' actually stop guest (i.e. it does not show in xl list
any more). I imagine being able to use OpenBSD firewall as Xen guest it
opens up new rich possiblities using it as virtual guest doing
networking and packet filtering part of the job; and Linux guests doing
network traffic analysis, some specific application services etc. and it
all happens in one physical box.
Best regards,
Imre
# dmesg
OpenBSD 5.9-beta (GENERIC) #1711: Fri Jan 15 09:29:33 MST 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 511700992 (487MB)
avail mem = 492113920 (469MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xfc001000 (11 entries)
bios0: vendor Xen version "4.5.1" date 07/12/2015
bios0: Xen HVM domU
acpi0 at bios0: rev 2
acpi0: sleep states S3 S4 S5
acpi0: tables DSDT FACP APIC HPET WAET SSDT SSDT
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
ioapic0 at mainbus0: apid 1 pa 0xfec00000, version 11, 48 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU E5-1603 0 @ 2.80GHz, 2800.43 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,HV,NXE,LONG
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 100MHz
acpihpet0 at acpi0: 62500000 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!)
pvbus0 at mainbus0: Xen 4.5
xen0 at pvbus0
xen0: hypercall page at va 0xffffffff81002000 pa 0x1002000
xen0: version 4.5.1
xen0: features 705<PIRQ,PVCLOCK,CBVEC,AUTOPMAP,WPT>
xen0: shared info page at va 0xffff8000000d6000 pa 0x1ef2d000
xen0: registered callback IDT vector 112
xen0: grant table frames allocated 32/32
xen0: xenstore event channel 1
xen0: xenstore ring at va 0xffff80000dff1000 pa 0xfeffc000
xen0: xenstore interrupt established for port 1
"vbd" at xen0: device/vbd/768 not configured
"vkbd" at xen0: device/vkbd/0 not configured
xnf0 at xen0: event channel 5, address 00:16:3e:79:22:22
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA,
channel 0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: <QEMU HARDDISK>
wd0: 16-sector PIO, LBA48, 16384MB, 33554432 sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
pciide0: channel 1 disabled (no drives)
piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: SMBus
disabled
xspd0 at pci0 dev 2 function 0 "XenSource Platform Device" rev 0x01
vga1 at pci0 dev 3 function 0 "Cirrus Logic CL-GD5446" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
isa0 at pcib0
isadma0 at isa0
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 1: density unknown
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
nvram: invalid checksum
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
root on wd0a (2bec112b40ffe2bf.a) swap on wd0b dump on wd0b
WARNING: / was not properly unmounted
clock: unknown CMOS layout
# sysctl hw
hw.machine=amd64
hw.model=Intel(R) Xeon(R) CPU E5-1603 0 @ 2.80GHz
hw.ncpu=1
hw.byteorder=1234
hw.pagesize=4096
hw.disknames=wd0:2bec112b40ffe2bf,fd0:
hw.diskcount=2
hw.cpuspeed=2800
hw.vendor=Xen
hw.product=HVM domU
hw.version=4.5.1
hw.serialno=866cd008-22b2-4b91-a90b-7cfa1ea4dc60
hw.uuid=866cd008-22b2-4b91-a90b-7cfa1ea4dc60
hw.physmem=511700992
hw.usermem=511688704
hw.ncpufound=1
hw.allowpowerdown=1
