Here is a generic (but working) example of a config file. What I am not using in this example is the 'root' option.
name="os13.2pv" description="None" uuid="09e84b64-5b3d-bb48-7fe3-488e7058878d" memory=1024 maxmem=1024 vcpus=2 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" localtime=0 keymap="en-us" builder="linux" kernel="/usr/lib/grub2/x86_64-xen/grub.xen" disk=[ '/dev/dm-0,raw,xvda,w,backendtype=phy', ] vif=[ 'mac=00:16:3e:0d:cb:82,bridge=br0', ] vfb=['type=vnc,vncunused=1'] - Charles >>> On 10/30/2015 at 02:07 PM, PGNet Dev <[email protected]> wrote: > On 10/30/2015 12:49 PM, Charles Arnold wrote: >> I think that is what I was meant to say. A config file using grub.xen on the >> kernel line can be started with xl create -f <config file>. You don't >> need to actually run the installer tools or have libvirt in the picture. > > Something's still amiss > > Given > > cat test.cfg > name = 'test' > builder = 'linux' > kernel = '/usr/lib/grub2/x86_64-xen/grub.xen' > disk = [ 'phy:/dev/VG0/testBOOT,xvda,w', > 'phy:/dev/VG0/testROOT,xvdc,w', > ] > root = '(xen/xvdc,msdos1)' > ... > > exec of > > xl create -c test.cfg > > still drops me to a grub prompt, instead of booting the guest, > > grub> ls > (proc) (memdisk) (xen/xvda) (xen/xvda,msdos1) (xen/xvdb) > (xen/xvdb,msdos1) (xen > /xvdc) (xen/xvdc,msdos1) > grub> > > Using ANY of those^^ in the root= line does the same -- grub prompt. > > This is with > > vgchange -an > kpartx -av /dev/VG0/testBOOT > mount /dev/mapper/VG0-testBOOT1 /mnt/TEMP > tree -L 1 /mnt/TEMP/grub2 > /mnt/TEMP/grub2 > ├── backgrounds > ├── custom.cfg > ├── device.map > ├── device.map.old > ├── fonts > ├── grub.cfg > ├── grubenv > ├── i386-pc > ├── locale > └── themes > > What's missing? -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
