search for: fsimag

...er. Using syslog is simple. Example /var/log/messages log: Jul 19 11:59:53 ovs030 [2012-07-19 11:59:53,504 7112] ERROR (pygrub:848) [Errno 95] Operation not supported Traceback (most recent call last): File "/share/repos/xen-unstable/tools/pygrub/src/pygrub", line 828, in ? fs = fsimage.open(file, offset, bootfsoptions) IOError: [Errno 95] Operation not supported Jul 19 11:59:53 ovs030 [2012-07-19 11:59:53,508 7112] ERROR (pygrub:892) Unable to find partition containing kernel ''7112'' is the pygrub PID, so we can distinguish each process. Also in this patch:...

...pd of=mail2.img bs=1M At least this is the only thing I can remember doing. Since then when I try to start it, I get the following: [root@xen3 xen]# xm create wspd -n Using config file "./wspd". Traceback (most recent call last): File "/usr/bin/pygrub", line 651, in ? fs = fsimage.open(file, get_fs_offset(file)) IOError: [Errno 95] Operation not supported No handlers could be found for logger "xend" Error: Boot loader didn''t return any data! Usage: xm create <ConfigFile> [options] [vars] Create a domain based on <ConfigFile>. My con...

...hich to place the disk image. This space is also mounted on the XCP server. In both cases, the NFS filesystem is mounted under /mnt. The following steps are taken on the BUILD host where /usr/src has already been compiled with buiidworld and buildkernel targets. ==BEGIN== export FSIMAGE="FreeBSD-PV.img" truncate -s 10G /mnt/${FSIMAGE} # Create the file where the image will reside. mdconfig -a -t vnode -f /mnt/${FSIMAGE} -u 0 # Create the image itself fdisk -BI md0 # Write the DOS partition table # Create an inital BSD Label...

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 guest configuration file: CENTOS_PV.cfg name = "CENTOS_PV_GUEST" #kernel = "/mnt/temp/images/xen/vmlin...

...st. I believe the issue has something to do with Fedora 16 using grub2... When I attempt to start the VM (via xm create), I get this error: Using config file "/etc/xen/fedora-workstation". Traceback (most recent call last): File "/usr/bin/pygrub", line 686, in ? fs = fsimage.open(file, get_fs_offset(file)) IOError: [Errno 95] Operation not supported No handlers could be found for logger "xend" Error: Boot loader didn't return any data! In my kickstart, I had to create a partition for F16 as: part biosboot --fstype=biosboot --size=1 I didn't read...

This time make world on Ubuntu 10.04 gives following error gcc -O2 -fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD -MF .fsimage.so.d -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -I../../../tools/libfsimage/common/ -Werror -L../common/ -shared -o fsimage.so fsys_reiserfs.opic -lfsimage ../../../tools/cross-install -d -m0755 -p /usr/src/xen-4.0.1/dist/instal...

...serve over the wire to client machines. I have a kernel and a file system image that I've put on a USB stick, and it boots fine from there. However, I have something strange happening when I try to serve it all across the network with gpxelinux. The kernel seems to load and boot just fine. The fsimage gets served up, and mounted. The newly booted system then goes through its usual antics for a few seconds, and then I see this on the console: Activating swap...done. Checking root file system...cramfs: bad compressed blocksize 281427494 fsck 1.40-WIP (14-Nov-2006) fsck.cramfs: error while loadin...

...d these are the instructions: http://wiki.debian.org/Xen#DomU.28guest.29 Installation was successfully. But restart not. I got: xm create -c xm-debian.cfg Using config file "./xm-debian.cfg". Traceback (most recent call last): File "/usr/bin/pygrub", line 651, in ? fs = fsimage.open(file, get_fs_offset(file)) IOError: [Errno 95] Operation not supported No handlers could be found for logger "xend" Error: Boot loader didn''t return any data! Usage: xm create <ConfigFile> [...] Thank you _______________________________________________ X...

...on: (xend.err "Error creating domain: Boot loader didn't return any data!") If you drop to the command line to see what pygrub gets back, you get: # pygrub /var/lib/xen/images/fedora12.img Traceback (most recent call last): File "/usr/bin/pygrub", line 677, in ? fs = fsimage.open(file, get_fs_offset(file)) IOError: [Errno 95] Operation not supported The kickstart worked perfectly in Fedora 11 on a CentOS 5.4 dom0. I've tried investigating all sorts of grub options and even tried copying kernel and initramfs files out from the domU to dom0 and booting from those...

...see which image or snap shot belongs to which VM. The names all are blank when we look at the storage. Also, if I randomly mount an image to a VM, it does not boot. It produces an error that says: Traceback (most recent call last): - File "/usr/binpygrub", line 808, in ? - fs = fsimage.open(file,part_offs[0[, bootfsoptions) - IOError: [Errno 95] Operation not supported. The system kept the VM information as we destroyed the pool and then created a new one but it looks like we only see snapshots through XenCenter. Its like the real .vhd that were running are not showing up....

...ave to be refreshed manually, but at least some of the no longer needed ones would be gone from there. What likely needs better review is some of the new things which I did not pick for the binary package because they were not used before and nothing seemed to complain about them missing (like some fsimage lib IIRC). -Stefan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20160930/b5048059/atta...

...ge provided." f = fs.open_file(self.cf.filename) buf = f.read() del f @@ -763,9 +766,9 @@ if __name__ == "__main__": break fs = None - except: + except (IOError, NotFoundError): # IOErrors raised by fsimage.open - # RuntimeErrors raised by run_grub if no menu.lst present + # NotFoundError raised by run_grub if no menu.lst present fs = None continue _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com...

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

2. update ZFS in libfsimage from illumos for pygrub diff -r 7c12aaa128e3 -r c2e11847cac0 tools/libfsimage/Rules.mk --- a/tools/libfsimage/Rules.mk Thu Oct 24 22:46:20 2013 +0100 +++ b/tools/libfsimage/Rules.mk Sat Oct 26 20:03:06 2013 +0400 @@ -2,11 +2,19 @@ include $(XEN_ROOT)/tools/Rules.mk CFLAGS += -Wno-unknown-pragm...

Package: xen-utils-4.11 Severity: important Dear Maintainer, We have discovered that the `pygrub` binaries, expected under `/usr/lib/xen-4.11/bin`, are no longer present in the xen-utils-4.11 package. Reviewing the source package reveals that the binary is still present under `tools/pygrub/src/pygrub`, however it is not referenced anywhere obvious in the package build configurations, nor is

...+ for word in out.split(): + if word.startswith("TYPE"): + self._LoopImageCreator__fstype = word.split("=")[1].strip("\"") + + except IOError, e: + raise CreatorError("Failed to determine fsimage TYPE: %s" % e ) + + + def _get_fslable(self): + dev_null = os.open("/dev/null", os.O_WRONLY) + try: + out = subprocess.Popen(["/sbin/e2label", self._image], + stdout = subprocess.PIPE, +...

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

..., During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -Wno-unused-but-set-variable -D__XEN_TOOLS__ -MMD -MF .fsimage.so.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wno-unknown-pragmas -I/?PKGBUILDDIR?/debian/build/build-utils_amd64/tools/libfsimage/ext2fs-lib/../../../tools/libfsimage/common/ -Werror -D_GNU_SOURCE -Wl,--no-as-needed -L../common/ -Wl,-rpath,'${ORIGIN}/../..' -shared -o fsimage.so ex...

Package: xen-utils-3.4 Version: 3.4.0-1 Severity: important The current version of the package does not contain the IOEMU tools. This makes HVM domains, and PV domains with emulated features like VFB impossible to run. There might be good reasons for this, but then at least the package description should contain a warning that makes this obvious, so that users know that they can not simply

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...