> I want to configure a Xen Guest to boot to a physically attached
> Opensuse install DVD, and init the guest with the default 'xl' toolstack.

I was informed in #xen that 'pygrub' is not a "real bootloader", and
can't boot to DVD.  In order to successfully do that, I'd need to boot
an HVM guest.

Switching my config to:

cat test.cfg
        name = 'test'
        kernel = '/usr/lib/xen/boot/hvmloader'
        builder = 'hvm'
        #device_model = '/usr/lib64/xen/bin/qemu-dm'
        acpi = 1
        apic = 1
        disk = [ 'phy:/dev/VG0/boot,xvda,w', 'phy:/dev/VG0/swap,xvdb,w',
        'phy:/dev/VG0/root,xvdc,w', 'phy:/dev/cdrom,xvdd:cdrom,r', ]
        vif = [ 'mac=00:16:3E:55:00:01, model=rtl8139, type=ioemu,
        bridge=br0, vifname=vifO',]
        vfb = [ 'type=vnc, vncdisplay=1, vnclisten=127.0.0.1' ]
        boot = 'f'
        maxmem = 2048
        vcpus = 4
        localtime = 0
        netif = 'yes'
        on_shutdown = 'destroy'
        on_reboot = 'destroy'
        on_crash = 'destroy'

Guest launch still fails, but differently,

xl create -c test.cfg
        Parsing config from test.cfg
        xc: info: VIRTUAL MEMORY ARRANGEMENT:
          Loader:        0000000000100000->000000000019e028
          TOTAL:         0000000000000000->000000007f800000
          ENTRY ADDRESS: 0000000000100000
        xc: info: PHYSICAL MEMORY ALLOCATION:
          4KB PAGES: 0x0000000000000200
          2MB PAGES: 0x00000000000003fb
          1GB PAGES: 0x0000000000000000
        libxl: error: libxl_create.c:901:domcreate_rebuild_done: cannot
        (re-)build domain: -3
        libxl: error: libxl_dm.c:1251:libxl__destroy_device_model: could
        not find device-model's pid for dom 37
        libxl: error: libxl.c:1429:libxl__destroy_domid:
        libxl__destroy_device_model failed for 37

Can someone contribute a working config to boot a Xen Guest -- hvm or pv
-- from the Opensuse installer and launch it for access via VNC?
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to