I think that you can basically ignore my comment #5.
When I was seeing this issue, when booting with kvm, I was not booting with 'boot=on'.
After booting with boot=on, the problem goes away. boot=on is generated in the kvm command line by eucalyptus, so I don't think this will be an issue there.
I think that you can basically ignore my comment #5.
When I was seeing this issue, when booting with kvm, I was not booting with 'boot=on'.
After booting with boot=on, the problem goes away. boot=on is generated in the kvm command line by eucalyptus, so I don't think this will be an issue there.