search for: bootargs

...ompressed xen.gz). My uboot sequence looks like this: mw.l 800000 0 10000 scsi scan ext2load scsi 0 0x800000 xen.bin ext2load scsi 0 0x1000000 vmlinuz setenv kernsize $filesize ext2load scsi 0 0x2000000 initrd.img setenv initsize $filesize # Tried dtuart=/soc/serial@fff36000 as well without setenv bootargs "sync_console console=dtuart dtuart=serial" fdt addr 0x1000 fdt resize fdt set /chosen bootargs \"$bootargs\" fdt mknod /chosen modules # Tried with <1> and <2> for both as I was not sure wnether those numbers # are related to number of modules fdt set /chosen/module...

Hi, Now that the Arndale board is supported in upstream Xen I don''t get any output on the serial console. I followed the instructions on the wiki with no luck: The xen repository I''m using is: git://xenbits.xen.org/xen.git last commit: 61c6dfce3296da2643c4c4f90eaab6fa3c1cf8b3 The linux repository is: git://xenbits.xen.org/people/julieng/linux-arm.git last commit:

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

Hi I have been using pygrub for most of the needs. Was trying out some stuff on SLES 10 SP1. It seems that it does not have pygrub!! On the other hand,they have domUloader.py which requires bootargs="--entry=hda:/boot/vmlinuz...., path to ramdisk. It is quite strange to be asking for the path of the kernel and the ramdisk to be supplied in the conf file!!. Am I missing something here ? PyGrub does not require all these details. For example : on one of my images, the path is /bo...

Hi I have been using pygrub for most of the needs. Was trying out some stuff on SLES 10 SP1. It seems that it does not have pygrub!! On the other hand,they have domUloader.py which requires bootargs="--entry=hda:/boot/vmlinuz...., path to ramdisk. It is quite strange to be asking for the path of the kernel and the ramdisk to be supplied in the conf file!!. Am I missing something here ? PyGrub does not require all these details. For example : on one of my images, the path is /bo...

...emely limited selection of peripherals (the guest is supposed to use virtual devices instead), add "xen,xenvm" to the list of compatible machines in mach-vexpress. Changes in v2: - remove include skeleton; - use #address-cells = <2> and #size-cells = <2>; - remove the debug bootargs; - use memory@80000000 instead of memory; - remove the ranges and interrupt-map from the motherboard node; - set the machine compatible to "xen,xenvm-4.2", "xen,xenvm"; - rename the dts file to xenvm-4.2.dts; - add "xen,xenvm" to the list of compatible DT strings to ma...

...ng <olaf@aepfle.de> # Date 1346945306 -7200 # Node ID 8a2eef481d3ab3ca5692dd0083c95cf314fe1da3 # Parent 19d367bf07b7687b831c212a57a70e73ea14d3b7 pygrub: always append --args If a bootloader entry in menu.lst has no additional kernel command line options listed and the domU.cfg has ''bootargs="--args=something"'' the additional arguments from the config file are not passed to the kernel. The reason for that incorrect behaviour is that run_grub appends arg only if the parsed config file has arguments listed. Fix this by appending args from image section and the config...

...l domU Config File: | name = "fennec" | memory = 1024 | maxmem = 1024 | cpus = "2-7" | disk = [ | ''phy:/dev/VPS/fennec,xvda,w'', | ''phy:/dev/VPS/fennec-swap,xvdb,w'' | ] | vif = [''''] | bootloader = "pygrub" | bootargs = "--kernel=/boot/vmlinuz --ramdisk=/boot/initrd" I have tried this with and without the bootargs line without any success. About The Filesystem: /dev/VPS is a vg on a RAID-1 array /dev/VPS/fennec is an lv on VPS vg The fennec lv has a single ext3 partition of 40GB xend.log Output: [201...

This series of patches makes Xen pass a (somewhat) valid device tree to dom0. The device tree for dom0 is the same as the one supplied to Xen except the memory and chosen nodes are adjusted appropriately. We don''t yet make use of the device tree to map MMIO regions or setup interrupts for the guest and we still include the UART used for Xen''s console. Note that loading Linux

...thub.com/torvalds/linux.git, I attached my config as it might be of some use for others. I''m using the latest Xen unstable branch git://xenbits.xen.org/xen.git and my device tree comes from: git://xenbits.xen.org/people/sstabellini/device-trees.git . These are my xen and kernel arguments: bootargs = "dom0_mem=128M dom0_max_vcpus=1 console=com1,vga"; xen,dom0-bootargs = "earlyprintk=xenboot console=ttyAMA0 root=/dev/mmcblk0 init=/bin/bash rw ip=dhcp"; This is how I launch the model ( where the variables of course contain the right paths ): ./model_shell ../resources/Cort...

Hi, I have searched the question which I am asking.But if some one has mentioned on their blog or link some where they have mentioned as how they installed CentOS as DomU on Debian Lenny (dom0)running xen-3.2.1 and I should have a look Then please share it here. -- Tapas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

...ion="vdrserver for my clients" memory=768 maxmem=2048 vcpus=1 cpus="1" cpu_weight = 128 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" localtime=0 keymap="de" builder="linux" bootloader="/usr/bin/pygrub" bootargs="" extra="console=hvc0 tmem cgroup_disable=memory independent_wallclock=1 iommu=soft" nographic=1 keymap = ''de'' disk=[ ''phy:/dev/mapper/xenimages-vdrserver,xvda1,w'', ''phy:/dev/mapper/xenimages-swap_vdrserver,xvda2,w'', ]...

...ion="vdrserver for my clients" memory=768 maxmem=2048 vcpus=1 cpus="1" cpu_weight = 128 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" localtime=0 keymap="de" builder="linux" bootloader="/usr/bin/pygrub" bootargs="" extra="console=hvc0 tmem cgroup_disable=memory independent_wallclock=1 iommu=soft" nographic=1 keymap = ''de'' disk=[ ''phy:/dev/mapper/xenimages-vdrserver,xvda1,w'', ''phy:/dev/mapper/xenimages-swap_vdrserver,xvda2,w'', ]...

...opensuse" ostype="opensuse" uuid="b24449ce-e89a-b107-a96a-da91ce26651f" memory=384 vcpus=1 on_crash="destroy" on_poweroff="destroy" on_reboot="restart" localtime=0 builder="linux" bootloader="/usr/lib/xen/boot/domUloader.py" bootargs="--entry=xvda2:/boot/vmlinuz-xenpae,/boot/initrd-xenpae" disk=[ ''file:/srv/xen/opencave/hda,xvda,w'', ] vif=[ ''mac=00:16:3e:00:00:01'', ] nographic=1 pci=[ ''01,00,0'', ''01,01,0'' ] I don''t belive it is the openS...

...t;openSUSE" name = "VM1" memory = 1890 vcpus=1 uuid="0a4a2999-bac9-6561-f9e0-a1494751c275" on_crash="destroy" on_poweroff="destroy" on_reboot="restart" localtime=0 builder="linux" bootloader="/usr/lib/xen/boot/domUloader.py" bootargs="--entry=xvda3:/boot/vmlinux-2.6.18.8-0.9-xen.gz,/boot/initrd-2.6.18.8-0.9-xen" extra="TERM=xterm xencons=tty " nographic=1 vif = [''mac=00:18:A4:78:F4:34,bridge=bridge0''] disk=[ ''phy:/dev/sda8,xvda3,w'', ''phy:/dev/sda7,xvda2,w...

Hi I have my xen domu config file as follows: root=''/dev/nfs'' extra =''ro console=/dev/tty1 xencons=tty'' nfs_server=''10.0.1.182'' nfs_root=''/dom2.nfs'' I can access the nfs server to mount the 10.0.1.182:/dom2.nfs at the physical host where the domu resides. Yet, I get the boot process stuck, the output is as follows:

...Where the variable XENBUS_PATH is set ? Here is my config file to create the VM: name="sles11-2" memory=4096 vcpus=4 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" localtime=0 builder="linux" bootloader="/usr/bin/pygrub" bootargs="" extra=" " disk=[''npiv:100000051e022b19-2100001b3214face-2000001b3214face-50060e801042c152-7,xvda,w''] vif=[ ''mac='', ] vfb=[''type=vnc,vncunused=1''] loglevel=all Thank, joel ____________________________________...

Hi I have my xen domu config file as follows: root=''/dev/nfs'' extra =''ro console=/dev/tty1 xencons=tty'' nfs_server=''10.0.1.182'' nfs_root=''/dom2.nfs'' I can access the nfs server to mount the 10.0.1.182:/dom2.nfs at the physical host where the domu resides. Yet, I get the boot process stuck, the output is as follows:

...l.dom.ext import PrettyPrint as XMLPrettyPrint ImportError: No module named ext On the Host I installed xen-4.0.2_02-4.7.1.x86_64 xen-libs-4.0.2_02-4.7.1.x86_64 xen-tools-4.0.2_02-4.7.1.x86_64 The config file I''m using is bootloader = ''/usr/lib/xen/boot/domUloader.py'' bootargs = ''--entry=xvda1:vmlinuz-xen,/boot/initrd-xen'' builder = ''linux'' disk = [''phy:/dev/VG0/Guest,xvda,w''] extra = ''textmode=1 xencons=xvc0'' maxmem = 1024 memory = 1024 name = ''guest'' on_crash = ''destroy...

Hi Ian, I try compile the bootwrapper for cubieboard2 like this: joshzhao@joshzhao-ThinkCentre-M58p:~/project/Xen/A20/boot-wrapper$ make cubieboard2_defconfig CROSS_COMPILE=arm-linux-gnueabihf- # # configuration written to .config # joshzhao@joshzhao-ThinkCentre-M58p:~/project/Xen/A20/boot-wrapper$ make CROSS_COMPILE=arm-linux-gnueabihf- make -C scripts/kconfig -f Makefile.bootwrapper