search for: tapdev1

...t work to minimize upgrade efforts. http://lxr.xensource.com/lxr/source/tools/blktap2/README also still mention tap:tapdisk, and not tap2:tapdisk. Second problem, using that combination, blktap2 devices was not cleanly freed. /sys/class/blktap2/devices and tapdisk devices keep increasing (tapdev0, tapdev1, etc.). The strange thing is, when using Xen 4.0.1 hypervisor but with Xen 4.0.0 userland, tap:tapdisk and blktap2 device cleanup works as expected. -- Fajar _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello, I''m currently trying to understand some problems I had in the past with mixing look-back with blktap(2) for HV and PV domains. I''m stuck reading the source code, so I''d like to get some help from the list. Interrupt me if I got something fundamentally wrong in my understanding so far: 1. With pure-HV the domU gets an emulated IDE (or whatever) disk. The

...3 04:23:29.252379 tap.activate: Launched Tapdisk(vhd:/mnt/c95af56f-799f-49ad-a64f-82eca3299b50.vhd, pid=12901, minor=1, state=R) [12866] 2012-05-23 04:23:29.252704 DeviceNode(/dev/sm/backend/42cbc4a3-dae2-e756-d122-01b87ed871c2/c95af56f-799f-49ad-a64f-82eca3299b50) -> /dev/xen/blktap-2/tapdev1 [12866] 2012-05-23 04:23:29.253008 lock: released /var/lock/sm/c95af56f-799f-49ad-a64f-82eca3299b50/vdi [12866] 2012-05-23 04:23:29.253116 lock: closed /var/lock/sm/c95af56f-799f-49ad-a64f-82eca3299b50/vdi [12866] 2012-05-23 04:23:29.253281 lock: closed /var/lock/sm/42cbc4a3-dae2-e75...