[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH] blktap2: blktap2 and pygrub (xen-unstable)


  • To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: eXeC001er <execooler@xxxxxxxxx>
  • Date: Sun, 11 Jul 2010 17:18:47 +0400
  • Delivery-date: Sun, 11 Jul 2010 06:19:44 -0700
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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"

Attachment: blkpat2_pygrub.patch
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.