On Fri, Oct 04, 2013 at 05:39:22PM +0100, Patrick Welche wrote:
> On Fri, Oct 04, 2013 at 06:35:49PM +0200, Manuel Bouyer wrote:
> > On Fri, Oct 04, 2013 at 05:05:10PM +0100, Patrick Welche wrote:
> > > builder = "hvm"
> > > name = "dfly"
> > > vcpus = 1
> > > memory = 512
> > > disk = ['phy:/dev/mapper/vg0-dfly,hda,w',
> > > 'file:/store/iso/dfly-x86_64-3.4.3_REL.iso,cd0,r']
> > > vif = ['mac=00:1e:8c:5e:52:c8,bridge=bridge0']
> > > boot="d"
> >
> > Sorry, I didn't pay attention to the config. A lot of things
> > are missing for a HVM domU here (ioemu type for vif for example,
> > the kerne, console settings, etc...)
> >
> > look at the examples in share/examples/xen/
>
> Really? The only lines not commented out in share/examples/xen/xlexample.hvm
> are:
>
> builder = "hvm"
> name = "example.hvm"
> memory = 128
> vcpus = 2
> vif = [ '' ]
> disk = [ '/dev/vg/guest-volume,raw,xvda,rw' ]
> sdl = 1
Ha yes, xen 4.2 ... I looked at the example in xen 4.1
>
>
> So the only line I haven't got is "sdl" which has to do with the X display.
if you don't have it I guess you have no console.
I still suspect your config is missing something.
attached is an example of a working file (for me)
--
Manuel Bouyer <bou...@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--
#============================================================================
# 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"
builder='hvm'
# Initial memory allocation (in megabytes) for the new domain.
memory = 1024
vcpus = 2
# A name for your domain. All domains must have different names.
name = "winxp"
#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:13, bridge=bridge0, type=ioemu, model=ne2k_pci' ]
#vif = [ 'mac=00:16:3e:00:00:13, bridge=bridge0, type=ioemu, model=pcnet' ]
#vif = [ 'mac=00:16:3e:00:00:14, bridge=bridge0, type=ioemu, model=e1000' ]
#vif = [ 'mac=00:16:3e:00:00:11, bridge=bridge0, type=ioemu' ]
vif = [ 'mac=00:16:3e:00:00:11, bridge=bridge0' ]
#----------------------------------------------------------------------------
# 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:/domains/redmond.vnd,ioemu:hda,w']
#disk = [ 'file:/domains/winxp.vnd,ioemu:hda,w',
'file:/domains/win2003.cd,ioemu:hdc:cdrom,r' ]
disk = [ 'file:/domains/winxp.vnd,ioemu:hda,w',
'file:/domains/eb-5.4.2-rtl8139.iso,ioemu:hdc:cdrom,r' ]
# 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 = 0
vnclisten = '127.0.0.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.
#
usb=1
usbdevice='tablet'
#usbdevice='mouse'
#============================================================================
#on_poweroff = 'preserve'
#on_reboot = 'preserve'
#on_crash = 'preserve'
