Hello everyone,
I have the following problem.
I setup a new KVM guest and added a qcow2 hdd. After that I mounted the qcow2 image on the host like this
and tried to create a new filesystem like this
At this point the process got stuck and I saw this in the kern.log:
Information about my server:
Please let me know if you need any more information.
I have the following problem.
I setup a new KVM guest and added a qcow2 hdd. After that I mounted the qcow2 image on the host like this
Code:
qemu-nbd -c /dev/nbd0 /path/vm-image.qcow2
Code:
mkfs.ext4 /dev/nbd0At this point the process got stuck and I saw this in the kern.log:
Code:
Feb 28 02:19:01 node1 kernel: nbd (pid 5708: qemu-nbd) got signal 9
Feb 28 02:21:16 node1 kernel: INFO: task qemu-nbd:5706 blocked for more than 120 seconds.
Feb 28 02:21:16 node1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 28 02:21:16 node1 kernel: qemu-nbd D ffff881765516d90 0 5706 1 0 0x00000000
Feb 28 02:21:16 node1 kernel: ffff8817654f5ad8 0000000000000082 0000000000000000 ffff8817654f5dc0
Feb 28 02:21:16 node1 kernel: ffff8817654f5dc8 ffff8817654f5dd0 ffff8817654f5ea8 ffff8817654f5da8
Feb 28 02:21:16 node1 kernel: ffff8817654f5db0 ffff881765517340 ffff8817654f5fd8 ffff8817654f5fd8
Feb 28 02:21:16 node1 kernel: Call Trace:
Feb 28 02:21:16 node1 kernel: [<ffffffff81529085>] schedule_timeout+0x215/0x2e0
Feb 28 02:21:16 node1 kernel: [<ffffffff81030b4e>] ? physflat_send_IPI_mask+0xe/0x10
Feb 28 02:21:16 node1 kernel: [<ffffffff8102ade9>] ? native_smp_send_reschedule+0x49/0x60
Feb 28 02:21:16 node1 kernel: [<ffffffff81054a9d>] ? task_rq_lock+0x5d/0xa0
Feb 28 02:21:16 node1 kernel: [<ffffffff81528cf3>] wait_for_common+0x123/0x190
Feb 28 02:21:16 node1 kernel: [<ffffffff81059f10>] ? default_wake_function+0x0/0x20
Feb 28 02:21:16 node1 kernel: [<ffffffff810857c9>] ? signal_wake_up+0x39/0x40
Feb 28 02:21:16 node1 kernel: [<ffffffff81528e1d>] wait_for_completion+0x1d/0x20
Feb 28 02:21:16 node1 kernel: [<ffffffff8119ebb7>] do_coredump+0x3a7/0xbf0
Feb 28 02:21:16 node1 kernel: [<ffffffff81084835>] ? __sigqueue_free+0x45/0x50
Feb 28 02:21:16 node1 kernel: [<ffffffff810888ad>] get_signal_to_deliver+0x1ed/0x470
Feb 28 02:21:16 node1 kernel: [<ffffffff8100a335>] do_signal+0x75/0x800
Feb 28 02:21:16 node1 kernel: [<ffffffff8100984c>] ? __switch_to+0x1ac/0x320
Feb 28 02:21:16 node1 kernel: [<ffffffff81010000>] ? find_oprom+0x210/0x3b0
Feb 28 02:21:16 node1 kernel: [<ffffffff81043837>] ? is_prefetch+0xb7/0x240
Feb 28 02:21:16 node1 kernel: [<ffffffff8100ab50>] do_notify_resume+0x90/0xc0
Feb 28 02:21:16 node1 kernel: [<ffffffff8100bc1c>] retint_signal+0x48/0x8c
Feb 28 02:21:16 node1 kernel: INFO: task qemu-nbd:5708 blocked for more than 120 seconds.
Feb 28 02:21:16 node1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 28 02:21:16 node1 kernel: qemu-nbd D ffff880ba3674b90 0 5708 1 0 0x00000000
...Information about my server:
Code:
pve-manager: 2.2-32 (pve-manager/2.2/3089a616)
running kernel: 2.6.32-17-pve
proxmox-ve-2.6.32: 2.2-83
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-34
qemu-server: 2.0-72
pve-firmware: 1.0-21
libpve-common-perl: 1.0-41
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.3-10
ksm-control-daemon: 1.1-1Please let me know if you need any more information.
