No, not the kernel config.  See attached example.

Sean


On Tue, 2012-01-03 at 08:16 -0800, Richard Kojedzinszky wrote:
> Dear Sean,
> 
> Attached.
> 
> Thanks in advance,
> 
> 
> Kojedzinszky Richard
> Euronet Magyarorszag Informatikai Zrt.
> 
> On Tue, 3 Jan 2012, Sean Bruno wrote:
> 
> > Date: Tue, 03 Jan 2012 08:00:28 -0800
> > From: Sean Bruno <sean...@yahoo-inc.com>
> > To: Richard Kojedzinszky <kri...@tvnetwork.hu>
> > Cc: "freebsd-xen@freebsd.org" <freebsd-xen@freebsd.org>
> > Subject: Re: 8.2 releng
> > 
> > Can you send in your xen domu config?
> >
> > Sean
> >
> > On Tue, 2012-01-03 at 01:56 -0800, Richard Kojedzinszky wrote:
> >> Dear users,
> >>
> >> I forget to mention, If i remove pf and pflog from the config, then the
> >> built kernel boots well under xen.
> >>
> >> Regards,
> >>
> >>
> >> Kojedzinszky Richard
> >> Euronet Magyarorszag Informatikai Zrt.
> >>
> >> On Tue, 3 Jan 2012, Richard Kojedzinszky wrote:
> >>
> >>> Date: Tue, 3 Jan 2012 10:40:13 +0100 (CET)
> >>> From: Richard Kojedzinszky <kri...@tvnetwork.hu>
> >>> To: freebsd-xen@FreeBSD.org
> >>> Subject: 8.2 releng
> >>>
> >>> Dear xen developers,
> >>>
> >>> I have a xen domU with the attached config, and unfortunately it does not
> >>> boot. I am compiling it with:
> >>> $ make kernel KERNCONF=DB WERROR=
> >>>
> >>> And it only makes a crash dump in the hosts xm dmesg.
> >>>
> >>> It is a recent 8.2 releng src tree.
> >>>
> >>> What should I change to make this work?
> >>>
> >>> Regards,
> >>>
> >>> Kojedzinszky Richard
> >>> Euronet Magyarorszag Informatikai Zrt.
> >> _______________________________________________
> >> freebsd-xen@freebsd.org mailing list
> >> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
> >> To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
> >
> >

============================================================================
# Python configuration setup for 'xm create'.
# This script sets the parameters used when a domain is created using 'xm 
create'.
# 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/lib/xen/boot/hvmloader"
kernel = "/var/virt/freebsd-8-stable-i386-domu-kernel"

#----------------------------------------------------------------------------
# device model to use: only qemu-dm available for now
#device_model = '/usr/lib64/xen/bin/qemu-dm'

#builder='hvm'

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

# number of CPUS
vcpus = 1

# A name for your domain. All domains must have different names.
name = "ref8-xen32"
arch = "i386"

#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:01, bridge=xenbr0, type=ioemu' ]
vif = [ 'mac=00:16:3e:00:00:01, bridge=xenbr0, type=vbd' ]

# 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 = [
        'file:/var/virt/ref8-xen32.bin,hda,w'
        ]

extra = "vfs.root.mountfrom=ufs:/dev/ad0s1a"
# 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)
#
# boot CDROM image
#boot='d' 
# boot from DISK file
#boot='c'
# boot from DHCP/PXE then DISK file
boot='nc'

# 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
#vfb = [ "type = vnc, vncdisplay = 1, vncunused = 0, display = TEST"  ]

#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. 
# 
usb=1
usbdevice='tablet'
#usbdevice='mouse'

apci = 1
serial='pty'
on_reboot='restart'
#============================================================================

_______________________________________________
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

Reply via email to