Date: Sat, 21 May 2011 19:25:11 -0700 From: Sean Bruno <seanbru@yahoo-inc.com> To: "freebsd-xen@freebsd.org" <freebsd-xen@freebsd.org> Subject: Panic XENHVM Message-ID: <1306031111.2703.6.camel@hitfishpass-lx.corp.yahoo.com>
next in thread | raw e-mail | index | archive | help
Installed a freebsd-current non-xen kernel from a few months ago and
used it to compile and installworld/kern from the largeSMP branch.
In addition, the Dom0 is NetBSD and the Hypervisor is xen 4.1
There is a significant possibility that I don't know what I'm doing and
was looking for your thoughts here.
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
cd0 at ata1 bus 0 scbus1 target 0 lun 0
cd0: <QEMU QEMU DVD-ROM 0.10> Removable CD-ROM SCSI-0 device
cd0: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes)
cd0: cd present [211588 x 2048 byte records]
xn0: <Virtual Network Interface> at device/vif/0 on xenbusb_front0
xn0: Error 2 parsing device/vif/0/mac
xn0: Fatal error. Transitioning to Closing State
panic: do something smart
cpuid = 0
KDB: enter: panic
[ thread pid 0 tid 100000 ]
Stopped at kdb_enter+0x3b: movq $0,0x90f4d2(%rip)
db> trace
Tracing pid 0 tid 100000 td 0xffffffff810b9c80
kdb_enter() at kdb_enter+0x3b
panic() at panic+0x180
netfront_attach() at netfront_attach+0x19a
device_attach() at device_attach+0x69
xenbusb_probe_children() at xenbusb_probe_children+0xdf
xenbusb_attach() at xenbusb_attach+0x11c
device_attach() at device_attach+0x69
bus_generic_attach() at bus_generic_attach+0x1a
xs_attach_deferred() at xs_attach_deferred+0x21
run_interrupt_driven_config_hooks() at run_interrupt_driven_config_hooks
+0x73
boot_run_interrupt_driven_config_hooks() at
boot_run_interrupt_driven_config_hooks+0x2c
mi_startup() at mi_startup+0x77
btext() at btext+0x2c
---- xen config for this DomU----
#============================================================================
# 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/pkg/lib/xen/boot/hvmloader"
device_model = '/usr/lib/xen/bin/qemu-dm'
builder='hvm'
# Initial memory allocation (in megabytes) for the new domain.
memory = 4098
# number of CPUS
vcpus = 4
# 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' ]
#----------------------------------------------------------------------------
# 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 = [
'file:/var/virt/FreeBSD-9.0-CURRENT-201101-amd64-disc1.iso,hdc:cdrom,r',
'file:/var/virt/vmtest9_amd64.bin,hda,w'
]
# 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='c'
# 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
vncpasswd=''
#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'
serial='pty'
on_reboot='restart'
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1306031111.2703.6.camel>