> How big is your initrd image ? There was a QEMU bug which causes the
> end of the initrd to be overwritten by the kernel if the initd was
> larger than 1 MB IIRC. Upstream QEMU CVS has the patch, but the current
> KVM SVN repo does not seem to have it. I'm attaching the patch we applied
> to KV
On Mon, Apr 30, 2007 at 11:45:36AM -0700, David Brown wrote:
> > Host cpu type, host bitness, guest bitness, and qemu command line please.
> >
>
> [EMAIL PROTECTED]:~# cat /root/bin/start-debian
> #!/bin/bash
>
> KVER="2.6.18-4-686"
> INITRD_BASE="initrd"
> INITRD_APPEND=".img"
> APPEND="ro root=
David Brown wrote:
>> > qemu -kernel "/root/boot/vmlinuz-${KVER}" \
>> >-initrd "/root/boot/${INITRD_BASE}${INITRD_APPEND}-${KVER}" \
>> >-append "${APPEND}" \
>> >-m 512 --no-rtc \
>> >\
>> >-usb \
>> >-soundhw es1370 \
>> >-net nic,vlan0,macaddr=52:54:56:34:12:00 \
>>
> > qemu -kernel "/root/boot/vmlinuz-${KVER}" \
> >-initrd "/root/boot/${INITRD_BASE}${INITRD_APPEND}-${KVER}" \
> >-append "${APPEND}" \
> >-m 512 --no-rtc \
> >\
> >-usb \
> >-soundhw es1370 \
> >-net nic,vlan0,macaddr=52:54:56:34:12:00 \
> >-net tap,vlan=0,ifname=
David Brown wrote:
>> Host cpu type, host bitness, guest bitness, and qemu command line
>> please.
>>
>
> Oh sorry, forgot about that stuff.
>
> model name : Genuine Intel(R) CPU U2500 @ 1.20GHz
>
Ugh, a Core-not-2. I'll see if I can find one here.
>
> qemu -kernel "/root/boot/v
> Host cpu type, host bitness, guest bitness, and qemu command line please.
>
Oh sorry, forgot about that stuff.
[EMAIL PROTECTED]:~# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Genuine Intel(R) CPU U250
David Brown wrote:
> Yeah, for some reason part way through the boot up of a guest OS it
> just stops booting, there isn't any sort of defined place where it
> stops either. However, the guest OS does always get to the initrd (but
> that maybe because the kernel is so simple). Sometimes it will get
Yeah, for some reason part way through the boot up of a guest OS it
just stops booting, there isn't any sort of defined place where it
stops either. However, the guest OS does always get to the initrd (but
that maybe because the kernel is so simple). Sometimes it will get all
the way to the root ha
