search for: get_fs_offset

...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 config file looks like this:...

...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 readily find the error when go...

...tructions: 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 _______________________________________________ Xen-users mailing list Xen-...

...;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 with no luck. The only th...

Hi, I made a patch for GPT support. As you see, this patch uses ad-hoc approach. If you give me an advice, it would be appreciated Signed-off-by: Shinya Kuwamura <kuwa@jp.fujitsu.com> Signed-off-by: Tomohiro Takahashi <takatom@jp.fujitsu.com> Thanks, Tomohiro Takahashi. diff -r 1bde28f762a6 -r 8e08fd1ffa24 tools/pygrub/src/pygrub --- a/tools/pygrub/src/pygrub Mon Apr 09 13:40:25

...K So far so good! I can mount the filesystem and verify it to be 3GB. Now on to trying to boot the domU again: > xm create -c hc24.cfg Using config file "./test.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! If I understand this correctly the diskimage does not contain a valid MBR that satisfies pygrub. I have tried two thing...

..., 0, 1) Partition 2 has different physical/logical endings: phys=(1023, 3, 32) logical=(76405, 3, 32) #pygrub try pygrub /root/benchvm/bin/img-xen-guest/image-0.img Traceback (most recent call last): File "/usr/bin/pygrub", line 655, in <module> fs = fsimage.open(file, get_fs_offset(file)) File "/usr/bin/pygrub", line 117, in get_fs_offset offset += get_solaris_slice(file, offset) File "/usr/bin/pygrub", line 80, in get_solaris_slice raise RuntimeError, "Invalid disklabel magic" RuntimeError: Invalid disklabel magic My guest config:...