[Qemu-devel] Slow booting with large Initrd

[Qemu-devel] Slow booting with large Initrd

[Dyweni - Qemu-Devel]

 Hi List,

 This morning I ran across a thread on this list from Oct'11 about slow
 booting with large initrd images. Reading through that thread, I didn't
 really see any sort of definitive resolution to the problem.

 Also, this morning, I upgraded Qemu-KVM to latest git master
 (9d636ae7488edfa9c7f03ceee62c838d505aac3e). I do not see any 
 improvement /
 resolution of the issue.



 ** I'd like to find out where the QEMU-KVM list / community is at on
 resolving this problem. **



 My setup is this:

 Host Kernel: 3.1.6

 Guest Kernel: 3.2.0-rc7
 Guest Kernel Size: 3.7MB (bzImage)
 Guest Initrd Size: 84MB (init ram fs)

 QEMU Start comamnd line:

 qemu-system-x86_64
  -curses
  -m 512
  -drive file=/dev/mapper/flashcow2,cache=writeback
  -drive file=/dev/mapper/datacow2,cache=writeback
  -net nic,macaddr=00:AA:00:FF:61:AA,vlan=0 -net
 tap,vlan=0,ifname=tap40,script=no
  -net nic,macaddr=00:AA:00:1E:F8:BB,vlan=1 -net
 tap,vlan=1,ifname=tap47,script=no

-- 
 Thanks,
 Dyweni

Re: [Qemu-devel] Slow booting with large Initrd

[Michael Tokarev]

On 15.02.2012 16:35, Dyweni - Qemu-Devel wrote:
> Hi List,
>
> This morning I ran across a thread on this list from Oct'11 about slow
> booting with large initrd images. Reading through that thread, I didn't
> really see any sort of definitive resolution to the problem.

There's been several mentions of alternative ways - like, booting from
an .iso cdrom image instead of using -kernel/-initrd - that one works
fast.  Creating an .iso out of kernel+initrd is trivial.

/mjt