I've made some significant progress on the freebsd.org xen hosting
machines (no dom0 support yet, but I'm working on it).

I've installed a netbsd-current dom0 and the 3.3.2 xen hypervisor on
xen1.freebsd.org and started up a freebsd-current DomU with the XENHVM
kernel installed.  I've attached the dmesg and the xen config for
"xen2.freebsd.org" to this message.

I've been crashing the hypervisor pretty reliably by setting the DomU to
use multiple CPUs.  Not sure if this is a Xen or NetBSD thing, but for
now i'm leaving vcpus set to 1.

1.  How do I switch the networking vif entry to use the netfront xn0
driver instead of emulating a e1000?

2.  What tests would people like to see on this?

3.  Is anyone working on OpenStack or Ganetti for Free/NetBSD?

# Python configuration setup for 'xm create'.
# This script sets the parameters used when a domain is created using 'xm 
# You use a separate script for each domain you want to create, or 
# you can set the parameters for the domain on the xm command line.

# Kernel image file.
kernel = "/usr/pkg/lib/xen/boot/hvmloader"

device_model = '/usr/lib/xen/bin/qemu-dm'


# Initial memory allocation (in megabytes) for the new domain.
memory = 4098

# number of CPUS
vcpus = 1

# A name for your domain. All domains must have different names.
name = "fbsd9"

#Network interface. By default emules a realtek 8139. For a NetBSD guest you
# have to disable re(4) and let rtk attach to use it.
# ne2k_pci emulates a pci ne2000 clone; this his cpu-hungry in dom0
# pcnet emulates a AMD PCnet-PCI controller; but it corrupts packets with
# pcn(4) under NetBSD.
#vif = [ 'mac=00:16:3e:00:00:14, bridge=bridge0, type=ioemu' ]
vif = [ 'mac=00:16:3e:00:00:14, bridge=bridge0, model=e1000' ]

# device model to use: only qemu-dm available for now
device_model = '/usr/pkg/libexec/qemu-dm'

# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.
# For hvm domains you can only use hda to hdd. You can set extra types
# (e.g. cdrom)

disk = [

# floppy images; this doesn't seem to work currently. Use a iso image instead.
#fda = '/home/domains/boot1.fs'

# boot device: a = floppy, c= hard drive, d= cdrom (with the disk entry
# before)

# By default, 'xm create' will try to open an X window on the current display
# for the virtal framebuffer. You can have the virtal framebuffer in vnc
# instead, and connect using a vnc client (using localhost:$vncdisplay)
# If vncunused is set to 1 (this is the default value), vncdisplay
# will be set to the first unused port; so it's recommended to
vnc = 1
vncdisplay = 1
vncunused = 1

#Xen emulates a PS/2 mouse, but the pointer in the guest has difficulties
# tracking the absolute position. Xen can emulate a USB tablet in addition
# to the mouse which will report the absolute position of the pointer,
# and make the mouse much easier to use. 


From:   Sean Bruno <sbr...@xen2.freebsd.org>
To:     sbr...@freebsd.org <sbr...@freebsd.org>
Subject:        dmesg from xenhvm on netbsd dom0
Date:   Tue, 24 May 2011 15:10:29 -0700

Copyright (c) 1992-2011 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.0-CURRENT #0 r222239: Tue May 24 12:06:26 PDT 2011
    root@xen2:/usr/obj/usr/home/sbruno/head/sys/XENHVM amd64
WARNING: WITNESS option enabled, expect reduced performance.
CPU: Intel(R) Xeon(R) CPU           L5420  @ 2.50GHz (2493.82-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x10676  Family = 6  Model = 17  Stepping = 6
  AMD Features=0x20100800<SYSCALL,NX,LM>
  AMD Features2=0x1<LAHF>
real memory  = 4297064448 (4098 MB)
avail memory = 4113154048 (3922 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: <Xen HVM>
ioapic0: Changing APIC ID to 1
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0 <Version 1.1> irqs 0-47 on motherboard
kbd1 at kbdmux0
acpi0: <Xen> on motherboard
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x1f48-0x1f4b on acpi0
cpu0: <ACPI CPU> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
isab0: <PCI-ISA bridge> at device 1.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX3 WDMA2 controller> port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc160-0xc16f at device 1.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
pci0: <bridge> at device 1.2 (no driver attached)
uhci0: <Intel 82371SB (PIIX3) USB controller> port 0xc140-0xc15f irq 23 at 
device 1.3 on pci0
usbus0: controller did not stop
usbus0: <Intel 82371SB (PIIX3) USB controller> on uhci0
vgapci0: <VGA-compatible display> mem 
0xf0000000-0xf1ffffff,0xf3020000-0xf3020fff at device 2.0 on pci0
xenpci0: <Xen Platform Device> port 0xc000-0xc0ff mem 0xf2000000-0xf2ffffff irq 
28 at device 3.0 on pci0
xenstore0: <XenStore> on xenpci0
em0: <Intel(R) PRO/1000 Legacy Network Connection 1.0.3> port 0xc100-0xc13f mem 
0xf3000000-0xf301ffff irq 32 at device 4.0 on pci0
em0: Ethernet address: 00:16:3e:00:00:14
attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
Event timer "RTC" frequency 32768 Hz quality 0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model IntelliMouse Explorer, device ID 4
fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: does not respond
device_attach: fdc0 attach returned 6
uart0: <Non-standard ns8250 class UART with FIFOs> port 0x3f8-0x3ff irq 4 flags 
0x10 on acpi0
ppc0: <Parallel port> port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
ppbus0: <Parallel port bus> on ppc0
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounters tick every 10.000 msec
usbus0: 12Mbps Full Speed USB v1.0
xenbusb_front0: <Xen Frontend Devices> on xenstore0
ugen0.1: <Intel> at usbus0
uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
ada0 at ata0 bus 0 scbus0 target 0 lun 0
ada0: <QEMU HARDDISK 0.9.0> ATA-7 device
ada0: 16.700MB/s transfers (WDMA2, PIO 8192bytes)
ada0: 28385MB (58134400 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad0
xbd0: 653MB <Virtual Block Device> at device/vbd/5632 on xenbusb_front0
xbd0: attaching as ad2
xn0: <Virtual Network Interface> at device/vif/0 on xenbusb_front0
xn0: Ethernet address: 00:16:3e:00:00:14
xenbusb_back0: <Xen Backend Devices> on xenstore0
xctrl0: <Xen Control Device> on xenstore0
xbd1: 28385MB <Virtual Block Device> at device/vbd/768 on xenbusb_front0
xbd1: attaching as ad0
cd0 at ata1 bus 0 scbus1 target 0 lun 0
cd0: <QEMU QEMU CD-ROM 0.9.> Removable CD-ROM SCSI-0 device 
cd0: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes)
cd0: cd present [334610 x 2048 byte records]
Timecounter "TSC" frequency 2493815955 Hz quality 800
WARNING: WITNESS option enabled, expect reduced performance.
g_dev_taste: make_dev_p() failed (gp->name=ad0, error=17)
g_dev_taste: make_dev_p() failed (gp->name=ad0p1, error=17)
g_dev_taste: make_dev_p() failed (gp->name=ad0p2, error=17)
g_dev_taste: make_dev_p() failed (gp->name=ad0p3, error=17)
Root mount waiting for: usbus0
uhub0: 2 ports with 2 removable, self powered
Root mount waiting for: usbus0
ugen0.2: <QEMU 0.9.0> at usbus0
ums0: <Endpoint1 Interrupt Pipe> on usbus0
Trying to mount root from ufs:/dev/ada0p2 [rw]...
WARNING: / was not properly dismounted
freebsd-xen@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

Reply via email to