I modified /usr/share/eucalyptus/gen_kvm_libvirt_xml as follows,
95c95
cmdlineroot=/dev/sda1 console=ttyS0/cmdline
---
cmdlineroot=/dev/vda1 console=ttyS0/cmdline
105c105
target dev='sda'/
---
target dev='vda' bus='virtio'/
110c110
model
How did you configure the NC to use virtio instead of the default block
device?
Is the guest still running after attaching the device?
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Low
** Changed in: qemu-kvm (Ubuntu)
Status: New = Incomplete
** Summary changed:
- unable
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 2.6.32-21-generic-pae (bui...@rothera) (gcc
version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #32-Ubuntu SMP Fri Apr 16 09:39:35 UTC
2010 (Ubuntu 2.6.32-21.32-generic-pae
using virtio is definitely not a supported/tested path. As far as I
know, neither are even configurable other than by hacking files on the
node.
If this is reproducible, could you please attach the console output of
the instance (euca-get-console-output).
--
unable to ssh to guest vm after
Additionally, if I start the guest vm without virtio enabled in kvm,
then there are no issues.
--
unable to ssh to guest vm after volume attach
https://bugs.launchpad.net/bugs/577027
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I was using virtio so the argument was -d /dev/vdb
--
unable to ssh to guest vm after volume attach
https://bugs.launchpad.net/bugs/577027
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mailing
