This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Live migrate and device numbers

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Live migrate and device numbers
From: Pim van Riezen <pi+lists@xxxxxxxxxxxx>
Date: Tue, 11 Dec 2007 11:35:52 +0100
Delivery-date: Tue, 11 Dec 2007 02:36:22 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Good day,

Using 3.0.3-13.fc6, I ran into the following issue during a live migrate (on the receiving host):

[2007-12-11 11:12:45 xend 5539] DEBUG (blkif:24) exception looking up device number for hda2: [Errno 2] No such file or directory: '/dev/hda2'

Apparently, the host that guests are migrated to looks up the block device major/minor by searching for the device node inside /dev on dom0. After this fails, xen restarts the guest and it finds its blockdevices just fine.

The obvious workaround I found for now is running MAKEDEV hda inside /dev on all our dom0s, but the entire issue seems kind of silly. Should I report this somewhere, or has this already been covered by newer releases?


Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Live migrate and device numbers, Pim van Riezen <=