All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Young <dyoung@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] virtio-blk: add default serial id
Date: Tue, 09 Oct 2012 10:27:26 +0800	[thread overview]
Message-ID: <50738B8E.1080303@redhat.com> (raw)
In-Reply-To: <20121005081458.GC1399@stefanha-thinkpad.redhat.com>

On 10/05/2012 04:14 PM, Stefan Hajnoczi wrote:

> On Sun, Sep 23, 2012 at 10:37:09AM +0800, Dave Young wrote:
>> For the serial number decreasing issue, I think there's only these two ways to
>> select, there's no ideal way to resolve this issue.
>> My use case for this is for the kdump kernel to find proper disks,
>> after 1st kernel crashing 2nd kernel need find right disk to dump vmcore.
>> In this case v1 and v2 aproaches are both find to me.
>>
>> From my point of view, patch v1 is better though, I think unpluging 100000 is
>> not a sane use case. It's not likely to happen.
> 
> I'm not sure auto-assigning serial numbers is a good idea.  The guest can use
> the serial number in /etc/fstab or other places where it expects the serial
> number to be persistent.
> 
> Your patch does not provide persistent serial numbers, so a change to the QEMU
> invocation could result in different serial numbers.  The guest will get
> confused or perhaps refuse to boot.


Yes, it introduce confusion, but in this way at least the serial number
can be persistent across guest reboot. Traditionally ide disks use this
way as well, such as QEMU_HARDISK_00001, I think guest should not use
this in /etc/fstab.

> 
> I'd prefer if we don't expose a temporary serial number at all in order to
> avoid issues like this.
> 
> Stefan



-- 
Thanks
Dave

  reply	other threads:[~2012-10-09  2:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21 13:30 [Qemu-devel] [PATCH v2] virtio-blk: add default serial id Dave Young
2012-09-21 14:15 ` Eric Blake
2012-09-23  2:37   ` Dave Young
2012-10-05  8:14     ` Stefan Hajnoczi
2012-10-09  2:27       ` Dave Young [this message]
2012-10-09  8:31         ` Stefan Hajnoczi
2012-10-10  2:07           ` Dave Young
2012-10-11  8:24             ` Stefan Hajnoczi

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=50738B8E.1080303@redhat.com \
    --to=dyoung@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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.