All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Ross Maxfield <rmaxfiel@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Missing CDROM media
Date: Mon, 10 Apr 2006 13:27:08 -0500	[thread overview]
Message-ID: <443AA37C.9070807@us.ibm.com> (raw)
In-Reply-To: <443A2AA0.DD28.00D3.0@novell.com>

Ross Maxfield wrote:
> If the 'cdrom=' option is specified in the definition file but media is not found in the CD drive then main() in vl.c exits and the guest appears to hang.  This patch modifies vl.c slightly to check for the presents of media.  If the cdrom cannot be opened then the cd entry is removed from hd_filename[] and bs_table[] allowing the guest to continue initializing. If the guest requires the CD media then the guest should report, gracefully or otherwise, that it's missing.
>   

This is desired behavior.

The cdrom is always attached to the guest.  The cdrom option doesn't 
necessary attach a cdrom but rather attaches the media to the already 
existing cdrom.  If you wish to later change the media, use the "change" 
option in the monitor.

Moving away from QEmu semantics is only going to make merging later more 
difficult.  You could perhaps add a check to Xend that remove the cdrom 
option if media wasn't present.  Then can expose the user interface we 
want without moving further away from QEmu.

Regards,

Anthony Liguori

> I would like to see this patch applied to 3.0.2-testing as well.
>
> Thanks,
> Ross
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>   

      reply	other threads:[~2006-04-10 18:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-10 15:57 [PATCH] Missing CDROM media Ross Maxfield
2006-04-10 18:27 ` Anthony Liguori [this message]

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=443AA37C.9070807@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=rmaxfiel@novell.com \
    --cc=xen-devel@lists.xensource.com \
    /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.