similar to: [PATCH] pygrub: add syslog support to pygrub

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

Package: xen-utils-4.0 Version: 4.0.1-1 Severity: normal File: pygrub The pygrub awesome error messages are captured below. Please tell me what pygrub was doing and why it failed. I also don't understand why <image> is supposed to be an integer. # '/usr/lib/xen-4.0/bin/pygrub' '--kernel=/vmlinuz' '--ramdisk=/initrd.img' '/dev/sda3' linux (kernel

I recently updated the kernel on an Ubuntu 11.04 PVM domU. The dom0 is an up to date Debian Squeeze host (Xen 4.0.1). Attempting to start the domU after this with xm create gives "Error: Boot loader didn''t return any data!". I ran pygrub against the domU manually, I got the following: Traceback (most recent call last): File "/usr/lib/xen-default/bin/pygrub", line

# HG changeset patch # Parent aa479945f718ff775c18afa2f37a391fca573114 # User carnold@suse.com # Date 1350668686 21600 pygrub: Add option to list grub entries The argument to "--entry" allows 2 syntaxes, either directly the entry number in menu.lst, or the whole string behind the "title" key word. This poses the following issue: From Dom0 there is no way to guess the number

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

Package: xen-utils-4.0 Version: 4.0.1-2 Severity: normal Trying to get a system that I've long had runing on the bare metal to boot as a VM, I discovered that pygrub would not parse my menu.lst. The problematic entry is this: # This is a divider, added to separate the menu items below from the Debian # ones. title Other operating systems: root pygrub's parser seems to

We had a XCP 1.5 pool with 2 machines as hosts. The storage pool which as NFS mounted lost its ability to export the filesystem with the VM images on it. We contacted the vendor and we were able to restore it. However, they had recommended that we delete the XCP Pool, recreate it, add the hosts back in, and then mount the storage. That is where we are at now. We can see the storage and

When I am trying to create a PV guest on DQ35, i am getting following error: >xm create CENTOS_PV.cfg -c Traceback (most recent call last): File "/usr/bin/pygrub", line 680, in ? zfsinfo = fsimage.getbootstring(fs) AttributeError: ''module'' object has no attribute ''getbootstring'' Error: Boot loader didn''t return any data! PV

Preamble: dom0: Xen 3.0.4 running on Ubuntu 6.06 x86_64. domU: Xen 3.0.4 or 3.1.0 kernel booting from host pygrub. File backed. ------------- I am having this strange problem getting pygrub to load consistently. When I start a domU, I sometimes get this. Error: Boot loader didn''t return any data! ... and nothing else. When I look in the xend-debug.log log, I see this.

Populate-on-demand: Check pages being returned by the balloon driver This patch series is the second result of my work last summer on decreasing fragmentation of superpages in a guests'' p2m when using populate-on-demand. This patch series is against 4.1; I''m posting it to get feedback on the viability of getting a ported version of this patch into 4.2. As with the previous

Hi! Is anybody able to boot FreeBSD 5.x-STABLE from a ATAPI ZIP 750 .? I tried to, but it didn't work. I mounted the ZIP from a running 5.X-STABLE and made the normal release procedure (installworld / installkernel .). I also gave bootcfg a try. But nothing helped. Or is there no way of booting a FreeBSD 5.X-STABLE from ZIP? Yours Stefan

On 2020/7/16 ??7:23, Zhu Lingshan wrote: > This commit replaced irq_request/free() with helpers in vDPA > core, so that it can request/free irq and setup irq offloading > on order. > > Signed-off-by: Zhu Lingshan <lingshan.zhu at intel.com> > Suggested-by: Jason Wang <jasowang at redhat.com> > --- > drivers/vdpa/ifcvf/ifcvf_main.c | 14 +++++++++----- > 1

Running a heavily modified xen-unstable changset 19590:f80cf52a4fb6 with debugger_attached set, I was seeing the debug traps getting lost from the EXCEPTION_BITMAP in vmx_update_guest_cr() when transitioning from real to protected mode. In my codebase, I could fix this trivially by clearing the debug_state_latch and letting vmx_do_resume() reapply the setting. However, while it looks like a valid

I''ve followed the howto at virtuatopia.com<http://www.virtuatopia.com/index.php/Building_a_Xen_Virtual_Guest_Filesystem_on_a_Disk_Image_%28Cloning_Host_System%29>to clone existing machines, then create them as PV guests. It has worked a couple of times for me, but I''ve run into a problem I don''t understand. When I run "xm create name", I get an error that

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

Hello, I must be missing something very very basic. Because I am having trouble launching some vm''s that I recently built whereas I don''t have any problem at all launching some older images I made in very much the same way! First there is vm01 which works just fine: [root@lcent5-1:/etc/xen]$:xm create vm01 Using config file "./vm01". Started domain vm01

Hello, I must be missing something very very basic. Because I am having trouble launching some vm''s that I recently built whereas I don''t have any problem at all launching some older images I made in very much the same way! First there is vm01 which works just fine: [root@lcent5-1:/etc/xen]$:xm create vm01 Using config file "./vm01". Started domain vm01

Hi, All I''m just new to this list, I''m started to dealing with OSS Xen to XCP migration earlier this week, seem the domUs installed via virt-install are function well, but domUs copied via dom0 are failed during bootup process, finally I realize if I could fix this on my OSS Xen will resolve all. Can I have any suggestion from you please ? *Details* *Source XenHost* OS:

Attached fixes running pygrub with many kernels to do proper scrolling Signed-off-by: Jeremy Katz <katzj@redhat.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I attempted to install Ubuntu 10.04 as a domU on my CentOS dom0. The process I used was: wget http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/xm-debian.cfg Edited the config file to use the proper logical volume for its install, and stepped through the install, installed GRUB to the MBR, and all seemed well. However, upon xm create -c NAME