All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Milan Holzäpfel" <lists@mjh.name>
To: xen-devel@lists.sourceforge.net
Subject: Re: bug in starting xen machines - expectation of /dev/sda1 existing on *host*
Date: Thu, 30 Dec 2004 12:53:07 +0100	[thread overview]
Message-ID: <20041230125307.4c609245.lists@mjh.name> (raw)
In-Reply-To: <20041230104930.GN7161@lkcl.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 30 Dec 2004 10:49:30 +0000
Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:

> [...]
> 
> ... what has the existence or otherwise of /dev/sda1 on the
> xen master machine got to do with the guest OSes?

Xend does a stat on /dev/<dev-to-be-used-in-xenU-domain> to find the
device numbers (which the virtual block device driver is then providing
inside the xenU-domain.)  

But since you usually are likely to have either an IDE or an SCSI hard
disk, you should be able to use hda1 instead.  I'd guess that the only
difference between sda1 and hda1 with respect to the virtual block
device driver should be the device number, isn't it?

On the other hand, this finding out aboud device name <-> number mapping
is probably not very elegant, but simple.  Anyone familiar with Python
may fix it in the file site-packages/xen/xend/server/blkif.py; probably
modifying the function "blkdev_name_to_number" at the top.

> [...]
>   File "/lib/python/xen/xend/server/blkif.py", line 335, in configure
>     raise VmError('vbd: Device not found: %s' % self.dev)
> VmError: vbd: Device not found: sda1

(on your setup, /lib/python/xen/xend/server/blkif.py is the exact path
to that file; usually the xen directory is
/usr/lib/python2.3/site-packages.)

Regards,
Milan

PS: Sorry for sending it to only to you, Luke, I forgot to change the
recipient...

- -- 

                   Milan Holzäpfel alias jagdfalke alias jag

Antworten direkt an mich                             Answers directly to me
gehen bitte an eine Addresse,                        go to an address one
die man hier finden kann:                            can find here, please:

Kontaktinfos sowie                                   Contact infos as well as
Öff GnuPG-Schlüssel    <URL:http://con.mjh.name/>    GnuPG Public Key
GnuPG Fingerabdruck     4C8A 5FAF 5D32 6125 89D1     GnuPG Fingerprint
                        0CE5 DB0C AF4F 6583 7966



                    http://www.deppenleerzeichen.de/ 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFB0+wj2wyvT2WDeWYRAnoCAJ46J91+0WU+0KAZJ6LOAPFVopwpPQCgibrn
fg18qXwETMEZJmJTStVh4HQ=
=MNpf
-----END PGP SIGNATURE-----


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

  parent reply	other threads:[~2004-12-30 11:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-30 10:49 bug in starting xen machines - expectation of /dev/sda1 existing on *host* Luke Kenneth Casson Leighton
2004-12-30 10:49 ` Fajar A. Nugraha
2004-12-30 14:27   ` M.A. Williamson
2004-12-30 11:53 ` Milan Holzäpfel [this message]
2004-12-30 14:25 ` M.A. Williamson
2004-12-30 22:43   ` Luke Kenneth Casson Leighton
2004-12-30 22:49     ` Michael Day
2004-12-31 11:29   ` Nuutti Kotivuori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041230125307.4c609245.lists@mjh.name \
    --to=lists@mjh.name \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.