search for: dagon

...fs-tools/hooks/intel_microcode which will be called during initamfs generation. It seems to call iucode_tool, from the iucode-tool package. That's a binary tool which seems to include its own cpio writer implementation, I've no idea if that is like a 'newc' or not. However: ijc at dagon:tmp$ find iucode-tool/ | cpio -o > normal.cpio 828 blocks ijc at dagon:tmp$ find iucode-tool/ | cpio -o -H newc > newc.cpio 840 blocks ijc at dagon:tmp$ file *.cpio newc.cpio: ASCII cpio archive (SVR4 with no CRC) normal.cpio: cpio archive So the fact that yours reports the same as newc.cp...

...ber of shares defined on the server, including one for / so that I can get to anything on the machine with one mount: [slash] path = / browseable = yes writable = yes valid users = aad On the server: <=>lovecraft<=>id uid=5001(aad) gid=5000(overlay) On the OS X client: [dagon:~/scratch] aad% id uid=502(aad) gid=502(aad) groups=502(aad), 80(admin), 5000(overlay), 2147483647 I can't find a consistent way to mount this share at start up, but this forum problably isn't the place to persue that. The issue is that once I do get it mounted, I have problems when movin...

> > according to the documentation the option ucode=scan should tell XEN to > > look for a microcode update in an uncompressed initrd. > > > > While I don?t use the Debian kernel the tools to generate the initrd are > > part of Debian. The command ?cpio -i < /boot/initrd.img-4.0.2-Dom0? > > creates the directory structure

On Fri, May 15, 2015 at 08:26:42AM +0100, Ian Campbell wrote: >Here's an idea. First extract the real initrd from the back half of the >initrd: > ijc at dagon:tmp$ cat /boot/initrd.img | ( cpio -t >&2 ; cat ) > initrd.real > kernel > kernel/x86 > kernel/x86/microcode > kernel/x86/microcode/GenuineIntel.bin > 16 blocks > ijc at dagon:tmp$ file initrd.real > initrd.real: gzip c...

On Tue, 2015-05-19 at 13:31 +0200, Stephan Seitz wrote: > On Fri, May 15, 2015 at 08:26:42AM +0100, Ian Campbell wrote: > >Here's an idea. First extract the real initrd from the back half of the > >initrd: > > ijc at dagon:tmp$ cat /boot/initrd.img | ( cpio -t >&2 ; cat ) > initrd.real > > kernel > > kernel/x86 > > kernel/x86/microcode > > kernel/x86/microcode/GenuineIntel.bin > > 16 blocks > > ijc at dagon:tmp$ file initrd.real &...

Your message dated Fri, 06 Sep 2013 09:09:48 +0100 with message-id <1378454988.3057.2.camel at dagon.hellion.org.uk> and subject line Re: [Pkg-xen-devel] Bug#710522: Problem found has caused the Debian Bug report #710522, regarding xen-hypervisor-4.1-amd64: Boot hang with Linux 3.2+Xen, works with linux 2.6.32+Xen or 3.2 raw to be marked as done. This means that you claim that the problem has...

...;ian.campbell@citrix.com> Cc: Rafael J. Wysocki <rjw@sisk.pl> Cc: Jeremy Fitzhardinge <Jeremy.Fitzhardinge@citrix.com> Cc: xen-devel <xen-devel@lists.xensource.com> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Link: http://lkml.kernel.org/r/1318713254.11016.52.camel@dagon.hellion.org.uk Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> --- drivers/xen/events.c | 2 - include/linux/interrupt.h | 3 ++ kernel/irq/pm.c | 48 +++++++++++++++++++++++++++++++++++++++------- 3 files c...

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: important Dear Maintainer, We are having a problem on several Supermicro servers (I'll include more details on the configuration later) : when booting Linux 3.2 linux-image-3.2.0-4-amd64 (Wheezy) as a DOM0 on Xen 4.1 (xen-hypervisor-4.1-amd64 from Wheezy), the system hangs after : [ 3.716174] scsi1 : ata_piix [

Package: xen-hypervisor-4.1-amd64 Version: 4.1.1-3 Severity: important Whenever I try to start a domU, xm create failed for 'Boot loader didn't return any data!'. % sudo xm create -c squeeze.cfg Using config file "/etc/xen/squeeze.cfg". Error: Boot loader didn't return any data! It seems related to the following error in dmesg [1440.163935] pygrub[3654] trap invalid

Package: xen-utils-common Version: 4.1.2-1 Severity: normal Hi, I was doing some experiments today with XL TOOLSTACK, and found few problems when trying to do PV domU boot. I was trying to run kfreebsd9 or linux-3.2 kernel in qemu using PV i386, and with simple configuration without any disks, nics or virtual framebuffer, kernel boots (and then kernel itselfs correctly fails with information