search for: bootentry

...ifying the interface for domU bootloaders (i.e. something that provides us with a kernel and ramdisk file with which the domain can be booted). The current interface, as is, has a number of problems, including: 1) the first disk specified is assumed to be the disk containing the files 2) ''bootentry'' is highly pygrub-specific. There is no easy facility to specify any options for custom bootloaders 3) bootloaders are forced to return configuration params like ''args'', since the code assumes it knows all with regards to image.py 4) users need to configure '...

Fix for pygrub path on Solaris. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/tools/python/xen/xend/XendDomainInfo.py b/tools/python/xen/xend/XendDomainInfo.py --- a/tools/python/xen/xend/XendDomainInfo.py +++ b/tools/python/xen/xend/XendDomainInfo.py @@ -37,7 +37,7 @@ from xen.util.blkif import blkdev_uname_ from xen.util.blkif import blkdev_uname_to_file from xen.util

...e same. What now? I suppose I could create new volumes using reiserfs and rsync the data across, but I''d rather use them as is. Thanks! Here are the relevant lines from the "unknown" vm config. kernel = "/boot/vmlinuz-xenpae" ramdisk = "/boot/initrd-xenpae" bootentry="/boot/kernels/vmlinuz-2.6.9-22.0.1.EL,/boot/kernels/initrd-2.6.9-22.0.1.EL.img" memory = 64 name = "unknown" vif = [ '''' ] disk = [ ''phy:/dev/vg20/vol01,sdb1,w'',''phy:/dev/vg20/vol02,sdb2,w'' ] dhcp="dhcp" root = &quo...

...e:85:b5:60'' ] root = ''/dev/hda1'' localtime = 0 on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' extra = '' TERM=xterm'' bootloader = ''/usr/lib/xen/boot/domUloader.py'' bootentry = ''hda1:/boot/vmlinuz-2.6.16-xen,/boot/initrd-2.6.16-xen.img'' And the configuration of my-network-script, which is used to bind xenbr0 and xenbr1 to specific nic cards #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=eth0 &qu...

...9; extra = '' initrd=initrd textmode=1'' kernel = ''/boot/vmlinux-2.6.16.21-0.25-xen.gz'' ramdisk = ''/boot/initrd-2.6.16.21-0.25-xen'' root = ''/mnt/boot/x86_64/root'' #bootloader = ''/usr/lib/xen/boot/domUloader.py'' #bootentry = ''hda1:/boot/vmlinuz-xen,/boot/initrd-xen'' ----- An "xm create -c test" gets this far: -------- [...] NET: Registered protocol family 2 IP route cache hash table entries: 262144 (order: 9, 2097152 bytes) TCP established hash table entries: 262144 (order: 10, 4194304 by...

I have installed the 210 gplpv (debug), when I try to update them with current gplpv I get a BSOD even so when I try to uninstall them. Now I have made a bootentry that specifies NOGPLPV, what gives me a bootable system after such a crash, I found (uninstalling the leftover driver packages after getting bsod during uninstall of the main package) that uninstalling the net driver leads to bsod. Now I booted in safe mode (nogplpv) and uninstalled the disabled ne...

...e:85:b5:60'' ] root = ''/dev/hda1'' localtime = 0 on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' extra = '' TERM=xterm'' bootloader = ''/usr/lib/xen/boot/domUloader.py'' bootentry = ''hda1:/boot/vmlinuz-2.6.16-xen,/boot/initrd-2.6.16-xen.img'' my-network-script (to enable bridging to specific NICs) #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=eth0 "$dir/network-bridge" "$@" vifnum...

...ostype="opensuse" uuid="fa0be596..." memory=384 vcpus=1 on_crash="destroy" on_poweroff="destroy" on_reboot="restart" localtime=0 builder="linux" bootloader="/usr/lib/xen/boot/domUloader.py" bootentry="xvda1:/boot/vmlinuz-xen,/boot/initrd-xen" #extra=" " extra=" TERM=xterm" disk=[ ''phy:/dev/vg01/pv-sys,xvda,w'', ''phy:/dev/vg01/pv-swap,xvdb,w'' ] vif=[ ''mac=00:12:34:56:78:9a...

...d interact with dom0. However, if we run "xm top", its interface is very unresponsive. Could writing to the xenstore be taking longer and longer? Could there be possible contention for vmlinuz and initrd since they are being used by every VM to boot? Would it be better to use bootloader/bootentry and store the vmlinuz and initrd within each VM? Any insight would be appreciated. brian carb unisys corporation, malvern pa ----- domU config file 002.cfg ----- kernel = "/boot/vmlinuz-xen" ramdisk = "/boot/initrd-xen" root = "/dev/sda2 ro" disk = [ ''ph...

...16:3e:f3:64:e9'',''bridge=xenbr0''] localtime = 0 on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' extra = '' TERM=xterm'' bootloader = ''/usr/lib/xen/boot/domUloader.py'' bootentry = ''hda2:/boot/vmlinuz-xen,/boot/initrd-xen'' boot="c" out put of brctl show: bridge name bridge id STP enabled interfaces xenbr0 8000.feae66791813 no vif0.0 peth0...

I''ve just made my first ever attempt at an Nullsoft installer, so if you want to try it download "Xen PV Drivers 0.9.5.exe" from http://www.meadowcourt.org/downloads/ The installer should detect the version of windows you are running and install the drivers. At the moment you''ll need to install the shutdown monitor service manually, but you can do that from the start

I''ve just made my first ever attempt at an Nullsoft installer, so if you want to try it download "Xen PV Drivers 0.9.5.exe" from http://www.meadowcourt.org/downloads/ The installer should detect the version of windows you are running and install the drivers. At the moment you''ll need to install the shutdown monitor service manually, but you can do that from the start

Suse 10.1 AMD64 Xen3 New to Xen. The dom0 is up and running. I am trying to get my first domU working. My approach is to use precompiled images from jailtime.org. After some manual tinkering with the .cfg file the domU proceeds to boot but stalls with the following error. I cannot get past this - any ideas ? Brian Using config file "/etc/xen/vm/vm1". Started domain vm1 Bootdata ok