> Fun, this seems to be related to t1.micro vs m1.large (and maybe
> larger). I am able to successfully replace the kernel on a m1.large. But
> the t1.micro is, as you say, not even bothering updating the console
> messages. And you said kvm boots fine. Was that with just a single vcpu?
I just verified with todays image that it boots fine in kvm with 2cpu:
kvm -boot a -fda natty-server-uec-amd64-floppy -drive
file=natty-server-uec-amd64.img,if=virtio,boot=on -curses -smp 2
The path in kvm is slightly different as it a different init that runs
before /sbin/init is run, but in the end, it boots fine.
Its different disks though (kvm virtio versus xen block devices)
On Fri, 12 Nov 2010, Stefan Bader wrote:
> Fun, this seems to be related to t1.micro vs m1.large (and maybe
> larger). I am able to successfully replace the kernel on a m1.large. But
> the t1.micro is, as you say, not even bothering updating the console
> messages. And you said kvm boots fine. Was that with just a single vcpu?
I just verified with todays image that it boots fine in kvm with 2cpu: uec-amd64- floppy -drive natty-server- uec-amd64. img,if= virtio, boot=on -curses -smp 2
kvm -boot a -fda natty-server-
file=
The path in kvm is slightly different as it a different init that runs
before /sbin/init is run, but in the end, it boots fine.
Its different disks though (kvm virtio versus xen block devices)