search for: config_imag

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

...table (3.3-unstable+hg17961-1) unstable; urgency=low * New upstream snapshot. --- debian/patches/tools-python-xen-xm-relative-path.diff 2008-12-04 16:50:04.000000000 -0500 +++ debian/patches/tools-python-xen-xm-relative-path.diff 2008-12-04 16:57:38.000000000 -0500 @@ -23,10 +23,10 @@ + config_image.append([ 'kernel', abspath(vals.kernel, 'boot') ]) if vals.ramdisk: - config_image.append([ 'ramdisk', os.path.abspath(vals.ramdisk) ]) -+ config_image.append([ 'ramdisk', abspath(vals.kernel, 'boot') ]) ++ config_image.append([ &...

...ches/tools-python-xen-xm-relative-path.diff?op=file Please, please, please, please fix it before releasing a broken xen 3.4.0 into Debian. --- xen-3/debian/patches/tools-python-xen-xm-relative-path.diff +++ xen-3/debian/patches/tools-python-xen-xm-relative-path.diff @@ -23,10 +23,10 @@ + config_image.append([ 'kernel', abspath(vals.kernel, 'boot') ]) if vals.ramdisk: - config_image.append([ 'ramdisk', os.path.abspath(vals.ramdisk) ]) -+ config_image.append([ 'ramdisk', abspath(vals.kernel, 'boot') ]) ++ config_image.append([ &...

...-utils-unstable, it is impossible to boot any paravirtualized guest that has an initrd (which is basically all paravirtualized guests), because the erroneous debian/patches/tools-python-xen-xm-relative-path.diff causes the path to the ramdisk to be replaced with the path to the kernel: - config_image.append([ 'ramdisk', os.path.abspath(vals.ramdisk) ]) + config_image.append([ 'ramdisk', abspath(vals.kernel, 'boot') ]) This is a very bad regression over xen-utils-3.2, and an obvious typo with an easy and well-tested fix.

...39;, val=''NAME'', + fn=set_value, default=''default'', + use="Guest OS type running in HVM") gopts.var(''stdvga'', val=''no|yes'', fn=set_bool, default=0, @@ -733,7 +737,9 @@ def configure_hvm(config_image, vals): ''localtime'', ''serial'', ''stdvga'', ''isa'', ''nographic'', ''soundhw'', ''vnc'', ''vncdisplay'', ''vncunused'', ...

...val=''audiodev'', + fn=set_value, default='''', + use="Should device models enable audio device?") gopts.var(''vnc'', val='''', fn=set_value, default=None, @@ -630,7 +630,7 @@ def configure_hvm(config_image, vals): """Create the config for HVM devices. """ args = [ ''device_model'', ''pae'', ''vcpus'', ''cdrom'', ''boot'', ''fda'', ''fdb'', -...

> Thanks all point about security, I''ll do as follows. > I thought that the point was the following two. > > > 1. Storage place of encrypted password > Should I store it in /etc/xen/passwd ? > Or, should I wait for DB of Xen that will be released in > the future? The xend life cycle management patches were posted by Alistair a couple of months back.

...39;, ''sdl'', ''display'', ''ne2000'', + ''acpi'', ''apic'', ''xauthority'', ''usb'', ''usbdevice'' ] for a in args: if (vals.__dict__[a]): config_image.append([a, vals.__dict__[a]]) @@ -847,17 +853,20 @@ """If vnc was specified, spawn a vncviewer in listen mode and pass its address to the domain on the kernel command line. """ - if not (vals.vnc and vals.vncviewer) or vals.dryrun: return - vnc_di...

This is a proposal for modifying 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