search for: blktap_validate_param

Displaying 4 results from an estimated 4 matches for "blktap_validate_param".

Did you mean: blktap_validate_params
Dom0 reboot when several VM reboot at the same time
2010 Jun 25
6
Dom0 reboot when several VM reboot at the same time
.../guest/VM-420A07DA/disk10369/image.vhd: 4 Jun 25 03:10:41 r21b02004 kernel: blktap_ring_open: opening device blktap3 Jun 25 03:10:41 r21b02004 kernel: blktap_ring_open: opened device 3 Jun 25 03:10:41 r21b02004 kernel: blktap_ring_mmap: blktap: mapping pid is 16340 Jun 25 03:10:41 r21b02004 kernel: blktap_validate_params: vhd:/guest/VM-420A07DA/disk10369/image.vhd: capacity: 419430400, sector-size: 512 Jun 25 03:10:41 r21b02004 kernel: blktap_validate_params: vhd:/guest/VM-420A07DA/disk10369/image.vhd: capacity: 419430400, sector-size: 512 Jun 25 03:10:41 r21b02004 kernel: blktap_device_create: minor 3 sectors 419...
Dom0 reboot when several VM reboot at the same time
2010 Jun 25
6
Dom0 reboot when several VM reboot at the same time
.../guest/VM-420A07DA/disk10369/image.vhd: 4 Jun 25 03:10:41 r21b02004 kernel: blktap_ring_open: opening device blktap3 Jun 25 03:10:41 r21b02004 kernel: blktap_ring_open: opened device 3 Jun 25 03:10:41 r21b02004 kernel: blktap_ring_mmap: blktap: mapping pid is 16340 Jun 25 03:10:41 r21b02004 kernel: blktap_validate_params: vhd:/guest/VM-420A07DA/disk10369/image.vhd: capacity: 419430400, sector-size: 512 Jun 25 03:10:41 r21b02004 kernel: blktap_validate_params: vhd:/guest/VM-420A07DA/disk10369/image.vhd: capacity: 419430400, sector-size: 512 Jun 25 03:10:41 r21b02004 kernel: blktap_device_create: minor 3 sectors 419...
Interesting lockdep message coming out of blktap
2010 Mar 29
0
Interesting lockdep message coming out of blktap
I''m getting this: blktap_validate_params: aio:/dev/vg_lilith-raid/xen-f13-64: capacity: 20971520, sector-size: 512 blktap_validate_params: aio:/dev/vg_lilith-raid/xen-f13-64: capacity: 20971520, sector-size: 512 blktap_device_create: minor 0 sectors 20971520 sector-size 512 blktap_device_create: creation of 253:0: 0 INFO: trying to regis...
BLKTAP2_IOCTL_CREATE_DEVICE vs. struct blktap2_params' name member
2012 Mar 02
0
BLKTAP2_IOCTL_CREATE_DEVICE vs. struct blktap2_params' name member
What is the purpose of the name member? And why is it that it''s being left uninitialized (causing the kernel driver to print garbage [in the 2.6.18 driver''s blktap_validate_params()] or even fail [in pv-ops'' blktap_device_validate_params()]) in tapdisk_control_open_image()? Thanks, Jan