similar to: Set correct path to pygrub and hvmloader

Package: xen-utils-3.2-1 Version: 3.2.0-5 Severity: important virtinst Debian package is pointing the pygrub path to /usr/bin/ and hvmloader to /usr/lib/xen/boot/. I suggest ajust the path creating a symbolic link of /usr/lib/xen-3.2-1/bin/pygrub to /usr/bin/pygrub and /usr/lib/xen-3.2-1/boot/hvmloader to /usr/lib/xen/boot/hvmloader. In the last case, need ajust the directory

On Mon, Jul 21, 2008 at 9:07 PM, Marco Sinhoreli <msinhore at gmail.com> wrote: > In virtinst package, we are pointing the pygrub and hvmloader to > /etc/xen-default/bin directory files. To us, this is sufficient to fix > our package issue. I suggest to use alternatives to point these to > /usr/bin and so, standardize with another distros. Well, I think this > is the easy way

I just tripped over this issue with pygrub. The code is written such that saying bootloader="pygrub" should cause the correct path to be used, the attached patch simply fixes this path to be correct. I don't have an HVM capable test machine handy (so I can't actually confirm this works) but I think changing the default "kernel" for an HVM guest to point to the correct

Hi, I just stumbled over this bug. Firstofall, it's nice that opposed to two years ago you now include pygrub at all. Thank you for that. Second, as pointed out, the FHS is not an issue as the selected path was in /usr/lib. Furthermore, if you re-read the text you should find that we're talking symlinks here, which surely are executable, but not binaries. I think it was for a reason FHS

Package: xen-utils-3.2-1 Version: 3.2.0-3~bpo4+2 Severity: normal Hi, pygrub has problems parsing block devices partitioned with Lenny Beta 2 and ext3 on paravirt guests: # /usr/lib/xen-3.2-1/bin/pygrub /var/lib/xen/images/test2.img Traceback (most recent call last): File "/usr/lib/xen-3.2-1/bin/pygrub", line 653, in ? chosencfg = run_grub(file, entry, fs) File

Package: xen-utils-3.2-1 Version: 3.2.0-4 Severity: important Tags: patch pygrub uses tools/libfsimage to read a guest filesystem. Unfortunately the grub derived code does not support 256 byte inodes. Grub itself has been patched (see #463236 and #463123) and this patch has now been applied to the upstream Xen tree. See <http://xenbits.xensource.com/staging/xen-unstable.hg?rev/c777e572a467>

Following your suggestions (except 1) :- 1. Made direct port Xen 3.4.2 to Ubuntu Jaunty Server & applied ext4 patch for pygrub from Mark Johnson (MRJ) 2. Edited xend-config.sxp (xend-http-server yes) # service xend restart # ln -s /usr/local/bin/pygrub /usr/lib/xen-default/bin/pygrub # apt-get install virt-manager libvirt-bin kvm # export VIRSH_DEFAULT_CONNECT_URI="xen:///" #

Package: xen-utils-unstable Version: 3.3-unstable+hg17192-1 Severity: important Tags: patch In tools/firmware/Makefile, INST_DIR is $(DESTDIR)/usr/$(PREFIX)/boot but $(PREFIX) is empty. hvmloader doesn't get installed. diff -ru xen-unstable-3.3-unstable+hg17192.orig/debian/patches/tools-prefix.diff xen-unstable-3.3-unstable+hg17192/debian/patches/tools-prefix.diff ---

Package: xen-utils-4.0 Version: 4.0.1~rc3-1 Severity: important When invoking pygrub either via command line or via bootloader being set in the configuration file, pygrub fails because it cannot import xen.lowlevel.xc. Example output: # /usr/lib/xen-default/bin/pygrub Traceback (most recent call last): File "/usr/lib/xen-default/bin/pygrub", line 20, in <module> import

Package: xen-utils-4.3 Version: 4.3.0-3 Severity: important Tags: upstream patch When using Xen compiled with seabios-1.7.4-1 (now in unstable/testing), HVMs fail immediately upon starting with a VCPU triple fault: (XEN) HVM1: Loading SeaBIOS ... (XEN) hvm.c:1253:d1 Triple fault on VCPU0 - invoking HVM shutdown action 1. This is because SeaBIOS can now be greater than 128k, which breaks an

Package: xen-utils-4.0 Version: 4.0.1-1 Severity: normal Tags: patch pygrub could not boot a newly-updated Debian/testing domU with a non-chained grub2. The traceback was: Using <class 'grub.GrubConf.Grub2ConfigFile'> to parse /grub/grub.cfg WARNING:root:Unknown directive load_video WARNING:root:Unknown directive terminal_output Traceback (most recent call last): File

Hi All, Debian squeeze, Xen 4.0, 2.6.32-5 I successfully installed opensolaris, but when trying to convert to pygrub it just hangs. root@vhost2:/var/log/xen# xm create /etc/xen/opensolaris.cfg -c Using config file "/etc/xen/opensolaris.cfg". root@vhost2:/etc/xen# xm list Name ID Mem VCPUs State Time(s) Domain-0

Package: xen-utils-common Version: 3.2.0-2 Severity: wishlist Hi, It would be very useful it /usr/bin/pygrub was available -- it should be a symlink (or wrapper) that points to the real version in the Xen hypervisor. That would mean that the domain configuration for xen domains could be (relatively) static when upgrades are occuring between hypervisor versions. Thanks, Anand -- System

Package: xen-utils-4.1 Version: 4.1.3-7 Severity: normal pygrub looks for extlinux config files "/boot/isolinux/isolinux.cfg" and "/boot/extlinux.conf", but the default Debian installation uses the config file "/boot/extlinux/extlinux.conf". (See /usr/lib/xen-4.1/bin/pygrub lines 405-407.) ...Marvin -- System Information: Debian Release: 7.0 APT prefers testing

Package: xen-utils-3.4 Version: 3.4.3~rc3-1 Severity: wishlist the upstream version of pygrub in 3.4.3 already supports grub2. It would be very nice to update pygrub in your package to the current version. Thanks in advance. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64)

Package: xen-utils-4.1 Version: 4.1.3-7 Severity: normal The grub.cfg created by a default Debian installation uses many configuration statements that pygrub does not recognize, and pygrub is unable to find any kernel to load. ...Marvin -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500,

Package: xen-utils-4.1 Version: 4.1.3-7 Severity: normal pygrub does not recognize the include statement in extlinux.conf. The default Debian installation of extlinux creates a stub extlinux.conf which includes linux.cfg, where all the linux image entries are. This means that even if bugs 697407 and 697409 are fixed, pygrub still can't find the right kernel on a default Debian installation

Forwarding to the list, as others might also be interested to check it out. -------- Original Message -------- Subject: Re: [Pkg-xen-devel] Virtual Machine Driver Pack for Linux from Novell Date: Mon, 23 Jul 2007 12:31:11 -0300 From: Marco Sinhoreli <msinhore at gmail.com> To: Henning Sprang <henning_sprang at gmx.de> References: <20fe3cf60707201018i269ed886m21f53e691c933fbe

Package: xen-utils-3.4 Version: 3.4.0-1 Severity: important pygrub uses the fsimage library to read contents of the filesystems to boot. This package install the plugins for different filesystems at /usr/lib/xen-3.4/lib/fs/, but searches for them under /usr//usr/lib/fs. (The debian patch tools-libfsimage-prefix.diff explicitly tinkers with this path, but it fails.) This breaks pygrub. --

Package: xen-utils-4.1 Version: 4.1.3-7 Severity: normal The function is_disk_image in /usr/lib/xen-4.1/bin/pygrub at line 45 distinguishes a partitioned disk from a partition by looking for 0xaa55 at offset 0x1fe in the image, but this is the bootsector signature, not the partition table signature. extlinux and other bootloaders put this signature there on bootable partitions (which don't