search for: typeraw

...; type='qcow2'/> It booted without issue. I'm not clear how that got changed on the?original domain. It was in use without issue about a week ago. :/ I then ran the clone again and it cloned fine, but had the boot issueagain. I checked the cloned domain.xml file and again it said typeraw. I changed it again to qcow2 and it booted fine. Bug? Shouldn't it keep the type in the config the same? Anyway, thanks for help and especially the quick responses! Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/lib...

...ex 13dec84..d01a650 100644 --- a/com32/chain/partiter.h +++ b/com32/chain/partiter.h @@ -42,7 +42,7 @@ /* status */ -enum {PI_OK, PI_DONE, PI_INSANE, PI_ERRLOAD}; +enum {PI_ERRLOAD = -31, PI_INSANE, PI_OK = 0, PI_DONE}; /* flags */ @@ -103,11 +103,6 @@ extern const struct itertype * const typeraw; struct part_iter *pi_begin(const struct disk_info *, int flags); void pi_del(struct part_iter **); -static inline int pi_errored(struct part_iter *iter) -{ - return iter->status > PI_DONE; -} - /* inline virtuals */ static inline int pi_next(struct part_iter *iter) { -- 1.7.10.4

...i_dtor_, - .next = &pi_dos_next, -}, [1] = { - .dtor = &pi_dtor_, - .next = &pi_gpt_next, -}, [2] = { - .dtor = &pi_dtor_, - .next = &pi_next_, -}}; - -const struct itertype * const typedos = types; -const struct itertype * const typegpt = types+1; -const struct itertype * const typeraw = types+2; - -/* pi_dtor_() - common/raw iterator cleanup */ -static void pi_dtor_(struct part_iter *iter) -{ - /* syslinux's free is null resilient */ - free(iter->data); -} - -/* pi_ctor() - common/raw iterator initialization */ -static int pi_ctor(struct part_iter *iter, - const str...

...i_dtor_, - .next = &pi_dos_next, -}, [1] = { - .dtor = &pi_dtor_, - .next = &pi_gpt_next, -}, [2] = { - .dtor = &pi_dtor_, - .next = &pi_next_, -}}; - -const struct itertype * const typedos = types; -const struct itertype * const typegpt = types+1; -const struct itertype * const typeraw = types+2; - -/* pi_dtor_() - common/raw iterator cleanup */ -static void pi_dtor_(struct part_iter *iter) -{ - /* syslinux's free is null resilient */ - free(iter->data); -} - -/* pi_ctor() - common/raw iterator initialization */ -static int pi_ctor(struct part_iter *iter, - const str...

This is a bit updated set of chain.c32 changes that simplifies a few things (and in partiter part), fixes few minor issues and adds a few new features. Details are in the following commits, below is the summary and pull details at the end. Shao - any chance to peek over them ? Most of those are relatively simple changes and well tested, though of course something might have slipped my attention.

So last week I was wondering if XFS was still working -- even with its last on-disk structure changes -- and it _suprisingly_ worked as expected. Right, now I can finally get rid of GRUB and use Syslinux to boot my Linux on EFI from a rootfs with xfs. Shit, I have two partitions (the first one being the required ESP) so there is no way to access the other partitions since because Syslinux does not

This small set fixes few bugs, improves gpt handling (under buggy conditions) and implements strict flag with more fine grained control which should fix issues with sanity checks against disk sizes. If this set is allright I'd want to do what I mentioned in older discussion with Ady - backport missing patches from 6.x to 5.x and 4.x so all versions have up to date chain version. Michal

Hello, the following patches should get multidisk access working. The syntax accepted is the following: (hdx,y)/path/to/file where x is the disk number and start at 0 and the y is the partition number starting at 1. So (hd0,1) is the first partition of the first disk. the other accepted syntax is using MBR's 32 bits disk signature so for example: (mbr:0x12345678,2)/foo/bar would address