similar to: [PATCH] Update pygrub for new Solaris directory names

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

# HG changeset patch # User Zhigang Wang <zhigang.x.wang@oracle.com> # Date 1342720736 14400 # Node ID ec9655b30a5fa5b5abb3e05505f681f9be559613 # Parent 43e21ce7f22151524b800a6cf0ac4ba1233b34a7 pygrub: add syslog support to pygrub Currently, when pygrub failed, we don''t know the reason because xend/xl will not capture the stderr message. This patch will log the error message to

any idea what the reason for this error is? [2006-11-07 13:59:31 xend 3167] DEBUG (__init__:1072) exception looking up device number for 0: [Errno 2] No such file or directory: ''/dev/0'' my config file looks like this: name = "solaris" memory = "400" kernel = "/solaris/platform/i86xen/kernel/amd64/unix" extra =

Hello, I''ve installed a OpenSolaris dom0 snv_44 on a x4100 server, and booted a 32-bit xen kernel. I''m trying to create a OpenSolaris DOMU (snv_44) by following the howto described at http://www.opensolaris.org/os/community/xen/howto/create-osox-domu/. I did not manage to create a diskless environment by using SUNWCXall. I''ve created SUNWCreq instead and add the

Hello, on a v20z, we have as DOM 0 a Solaris XEN on snv44 64bits and we have as DOM U a Solaris XEN on snv44 64 bits. We then install a pseudo driver in the Solaris DOM 1 XEN snv44: installation is ok and driver works as expected. But on reboot of DOM 1, the driver is no more there (in modinfo, driver not found). Is there something special to do after a pseudo driver installation in a Solaris

Hi, I have an x86 box with two boot disks. Each disk contains a BE, and I upgrade from one to the other. When trying to do a lumake from 75 to 76, and again from 76 to 77 I have the following error from lumake: ERROR: The system must be rebooted after applying required patches. Please reboot and try again. ERROR: Cannot make the boot environment. I only get this error if I''m

"yum update" has been run first on CentOS 5.1 box. ************************ Installation profile : ************************ name = "Solaris81PVM" vcpus = 1 memory = "1024" kernel = "/usr/lib/xen-solaris/unix-81" ramdisk = "/usr/lib/xen-solaris/x86.miniroot-81" extra = "/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom"

After BFU-ing my system to b75 I ended up with a panicing system when booting into Xen: grub> #---------- ADDED BY BOOTADM - DO NOT EDIT ---------- grub> title Solaris on Xen grub> kernel$ /boot/$ISADIR/xen.gz grub> module$ /platform/i86xpv/kernel/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/unix -B console=ttyb grub> module$ /platform/i86pc/$ISADIR/boot_archive grub>

Let me thank everyone in advance. I''ve read a number of posts here and it helped tremendously in getting the install done. I have a couple of remaining issues which I can''t seem to overcome. Here are the basics: dom0 - CentOS 5.2 32-bit Xen 3.2.1 compiles from source domU - os200805.iso The install config: [root@internetpowagroup oshman]# cat opensolaris.install name =

Hi Lin, In addition to bug 6541114... Bug ID 6541114 Synopsis GRUB/ZFS fails to load files from a default compressed (lzjb) root ... I found yet another way to get the "Error 16: Inconsistent filesystem structure" from GRUB. This time when trying to boot a Xen Dom0 from a zfs bootfs Synopsis: grub/zfs-root: cannot boot xen from a zfs root

I''ve hit this bug on my home machine couple of times and finally decided to log it since I''ve spend 2 days configuring my "OpenSolaris 2008.11 snv_101b_rc2 X86" and after installing the SUNWsmbfskr package I ended up in the grub> menu. The package contains a necessary module for CIFS. After pkg install SUNWsmbfskr, I rebooted the box. There was no grub menu anymore

I am trying to build Xen from on-src-b79. According to opensolaris website, all xVM sources should be in the on-src-b79 tree, and no additional sources are required. I followed the procedure for doing the nightly build, and I expected that, as a result I will build, along with the Solaris kernel, the xen.gz image. I was hoping to copy that xen.gz image to my test machine, so I can boot with my own

Copied ramdisk and kernel to Dom0 root@ServerXen331:/mnt/home/boris/isos# cat copy.sh mount -o loop,ro os200906.iso /mnt cp /mnt/boot/x86.microroot /home/boris/solaris cp /mnt/platform/i86xpv/kernel/amd64/unix /home/boris/solaris Created profile like for osol 2008.11 root@ServerXen331:/mnt/home/boris/solaris# cat osol200906.install name = "sol0906" vcpus = 1 memory =

I''ve got a CentOS 5.3 dom0 with Xen 3.4.1-rc5 (or so). I''ve tried the same stuff below with 3.4.0, no difference. I''m trying to install 2009.06 PV domU based on instructions from [1] and [2]. I can run the install fine, I can also get the kernel and boot archive (from [2]) after the install. But for the life of me I can''t get the installed domU to boot. If I

************************ Installation profile ************************ [root@ServerRHL51 vm]# cat snv85.install name = "Solaris85pvm" vcpus = 1 memory = "1024" kernel = "/usr/lib/xen-solaris/unix-85" ramdisk = "/usr/lib/xen-solaris/x86.miniroot-85" extra = "/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom" disk =

Hi, I''m trying to create OpenSolaris (2008.11) domU on RedHat Linux dom0. I''m using a file backed VBD. I used the iso image to first launch and install OpenSolaris into the file VBD. Once that process is complete, I''m trying to run it using the config file below: name = ''opensolaris'' vcpus = 1 memory = "512" vif =

From: pbonzini@redhat.com # HG changeset patch # User Paolo Bonzini <pbonzini@redhat.com> # Date 1319096986 -7200 # Node ID bd1f7361d3d7f4c767af21317fb4ec7ea1372f42 # Parent 1b110e895e285f43f14532e14c77597e54a0bcd2 pygrub will still try the next partition if run_grub exits with a "real" error, thus hiding the root cause from the trace. Defining a separate exception for "no

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

Thanks to everyone who works on the opensolaris project. I think it would be helpful to update the documentation on this page: http://opensolaris.org/os/community/xen/docs/linux-dom0/ The crucial steps of mounting the boot environment, updating the boot_archive, copying the boot_archive back to dom0, finding the ZFS-ID of the boot environment, and finally adding that ZFS-ID to the kernel

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