 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] [PATCH] blktap2: blktap2 and pygrub (xen-unstable)
| To: | Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] [PATCH] blktap2: blktap2 and pygrub (xen-unstable) |
| From: | eXeC001er <execooler@xxxxxxxxx> |
| Date: | Sun, 11 Jul 2010 17:18:47 +0400 |
| Delivery-date: | Sun, 11 Jul 2010 06:19:44 -0700 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=jlbx1gyabMEpYA5PlCB8/IjJYonLhdmig2W+/rk/yEc=; b=PHmuMX6m+5zkHoUMnR3jr9qzyLKCGAi1gxXwStataEo72buvu50EXVjAhMpv6bF0HE pNSRyzMU6SDHb0ipQz9BaHJ0VN6aHgV9j43++HX9Hkva5WztZh7u5CGMnqt6a2HEw/3Y eO5dkO4ftq7sqzpify5MBFxHYMRdiyJvCrMvQ= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=wmoT6JL+bN+Xd/HrezszqjjeZjRXg2DEhLp+gD4vGvTrXXFHTkHryRBpazlsCwT3QH RpT2jBiDrZVRgXQIbA+HH8caZF/9Hcni5fbEyiZxOatuQ+41INdjM+BIJk8k9IPALJYj JmUXlhBH4EmlYvq01tl3JnG1BgQOvEuQoKavA= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
1. Bug fix for error: "Error: Device /dev/xvdp (51952, tap2) is already connected." 2. Bug fix for error: "Error: Device 51952 not connected" process of booting DomU with 'mounted-blktap2' (VHD for example) and 'pygrub' as bootloader:
1. Connect boot-device to Dom0 as '/dev/xpvd' 2. Pygrub get info for load DomU 3. Disconnect boot-device from Dom0 4. Boot DomU During step 3 created device disconnecting from Dom0, but xenstore does not scrape away after device disconnected from Dom0 => result:
"Error: Device /dev/xvdp (51952, tap2) is already connected."
During step 3 created device disconnecting from Dom0, but 'destroyDevice' method is passed 'tap' always => result: "Error: Device 51952 not connected"
_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] [PATCH] blktap/blktap2: Fix for incorrect parse disk configuration (xen-unstable), Boris Derzhavets |
|---|---|
| Next by Date: | Re: [Xen-devel] [PATCH] blktap2: blktap2 and pygrub (xen-unstable), Boris Derzhavets |
| Previous by Thread: | [Xen-devel] [PATCH] blktap/blktap2: Fix for incorrect parse disk configuration (xen-unstable), eXeC001er |
| Next by Thread: | Re: [Xen-devel] [PATCH] blktap2: blktap2 and pygrub (xen-unstable), Boris Derzhavets |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
