It seems to be happening when launching micro instances, as memory is low (about 600M)<div>Launching it as a small instance, anaconda is executed, but there seems to be a problem related with dbus :</div><div><br></div><font class="Apple-style-span" face="'courier new', monospace">Greetings.<br>
anaconda installer init version 15.20.1 starting<br>mounting /proc filesystem... done<br><br>(process:1): GLib-CRITICAL **: g_hash_table_lookup_extended: assertion `hash_table != NULL' failed<br>creating /dev filesystem... done<br>
starting udev...done</font><br><font class="Apple-style-span" face="'courier new', monospace">mounting /dev/pts (unix98 pty) filesystem... done<br>mounting /sys filesystem... done<br><br>(process:1): GLib-CRITICAL **: g_hash_table_lookup_extended: assertion `hash_table != NULL' failed<br>
anaconda installer init version 15.20.1 using /dev/hvc0 as console<br>trying to remount root filesystem read write... done<br>mounting /tmp as tmpfs... done<br><br>(process:1): GLib-CRITICAL **: g_hash_table_lookup_extended: assertion `hash_table != NULL' failed<br>
running install...<br>running /sbin/loader<br><br> %Gdetecting hardware...<br>waiting for hardware to initialize...<br>detecting hardware...<br>waiting for hardware to initialize...<br><br>** (loader:49): WARNING **: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory<br>
<br>** (loader:49): WARNING **: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory<br><br>** (loader:49): WARNING **: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory<br>
<br>** (loader:49): WARNING **: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory<br><br>** (loader:49): WARNING **: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory<br>
<br>** (loader:49): WARNING **: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory<br><br>** (loader:49): WARNING **: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory<br>
<br>** (loader:49): WARNING **: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory</font><br><br>2011/3/10 Raphaël De GIUSTI <<a href="mailto:raphael.degiusti@guardis.com">raphael.degiusti@guardis.com</a>><br>
><br>> Hi,<br>> I simply tried to boot on the fedora 15 alpha kernel from there :<br>> <a href="http://ftp.esat.net/mirrors/download.fedora.redhat.com/pub/fedora/linux/releases/test/15-Alpha/Fedora/i386/os/images/pxeboot/">http://ftp.esat.net/mirrors/download.fedora.redhat.com/pub/fedora/linux/releases/test/15-Alpha/Fedora/i386/os/images/pxeboot/</a><br>
> and I'm getting this error :<br>>><br>>> root (hd0,0)<br>>><br>>> Filesystem type is ext2fs, partition type 0x83<br>>> kernel /boot/vmlinuz-PAE<br>>> initrd /boot/initrd-PAE.img<br>
>> ERROR: mmu_update failed with rc=-22<br>>> Do_exit called!<br>>> base is 0x26617ba8 caller is 0x45c87<br>>> base is 0x26617bd8 caller is 0x50336<br>>> base is 0x26617c38 caller is 0x504c0<br>
>> base is 0x26617c88 caller is 0x506a3<br>>> base is 0x2661fd08 caller is 0x479d7<br>>> base is 0x2661fd48 caller is 0x5613b<br>>> base is 0x2661fd58 caller is 0x54698<br>>> base is 0x2661fd98 caller is 0x55a79<br>
>> base is 0x2661fde8 caller is 0x55811<br>>> base is 0x2661fe08 caller is 0x3b0c<br>>> base is 0x2661fe38 caller is 0x3bc4<br>>> base is 0x2661fe48 caller is 0x7af7<br>>> base is 0x2661fe58 caller is 0xa243<br>
>> base is 0x2661fe78 caller is 0xfe69<br>>> base is 0x2661fef8 caller is 0x10489<br>>> base is 0x2661ff68 caller is 0x3eb2<br>>> base is 0x2661ff78 caller is 0x4729d<br>>> base is 0x2661fff0 caller is 0x31ad<br>
><br>> I just wondered where it does come from ?<br>> Any idea ?<br>><br>> 2011/2/8 Raphaël De GIUSTI <<a href="mailto:raphael.degiusti@guardis.com">raphael.degiusti@guardis.com</a>><br>>><br>>> So if we put aside how the kickstart would be generated, what would be the starting point in all of this ?<br>
>> I was working with Centos55 when I made it to the partitioning phase (and I don't really know why it went wrong), but I couldn't even get the F14 kernel to load.<br>>> In other words :<br>>> - Which fedora kernel / initrd combination should I use in my grub.conf ?<br>
>> - Should any of those two be altered in any way ?<br>>> I'm also willing to put some time in it if I may be useful... but like I said I'm no expert.<br>>> On Wed, Feb 2, 2011 at 9:48 PM, Brian LaMere <<a href="mailto:brian@cukerinteractive.com">brian@cukerinteractive.com</a>> wrote:<br>
>>>><br>>>>> Maybe I'm missing something: why would you ever want an instance to<br>>>>> kickstart at boot time? You should create an image for every role you<br>>>>> care about and then boot the appropriate one for every instance you<br>
>>>> need.<br>>>><br>>>> roles change, updates happen frequently, and I'd rather a machine spin up with the latest packages. I've always found that updating a pre-built machine is slower, sometimes substantially so, than just building a fresh image with the newest rpms.<br>
>>> That said, some roles can (and often should) be fairly rigid and slow to be updated. But there's not much less of a need for flexible, dynamic builds in the cloud than there is in a local server room; do you build all new local servers based on a pre-built image that you just replicate? Would seem to negate the purpose of a kickstart server ;)<br>
>>> Brian<br>>>> _______________________________________________<br>>>> cloud mailing list<br>>>> <a href="mailto:cloud@lists.fedoraproject.org">cloud@lists.fedoraproject.org</a><br>>>> <a href="https://admin.fedoraproject.org/mailman/listinfo/cloud">https://admin.fedoraproject.org/mailman/listinfo/cloud</a><br>
>>><br>>><br>><br>