Re: [Qemu-devel] qemu - SCSI disk "Device Model", "Serial Number", and "Firmware Version"?

From: Markus Armbruster <armbru@redhat.com>
To: dave@seddon.ca
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu - SCSI disk "Device Model", "Serial Number", and "Firmware Version"?
Date: Wed, 08 Jun 2011 08:29:55 +0200	[thread overview]
Message-ID: <m3vcwg4yzg.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <1307489210.28149.157.camel@das-HP-EliteBook-8530w> (Dave Seddon's message of "Wed, 08 Jun 2011 09:26:50 +1000")

Dave Seddon <dave@seddon.ca> writes:

> Greetings,
>
> Thanks for all the responses.
>
> Overall it sounds like supporting this is capability would be fairly
> easy.  However, Sadly for me it sounds like this won't be useful to
> people generally unless they are trying to virtulize something that
> relies on these codes. 
>
> Answers to:
> ------------------------------------------------
> Paulo:
>
> Statement:  Here we should perhaps try to improve the ATA emulation.
> Response:  It would probably be helpful to improve both SCSI and ATA
> emulation.
>
> ------------------------------------------------
> Markus:
>
> Question:  That's not what I see.  What version of QEMU are you using?
> Answer:  Using current package for Ubuntu 0.12.5 (that's probably a bad
> word, give all the @redhat emails. sorry :) )  What do you see?  I did
> download the source and check, hence the grep snippet.

We take patches even from Ubuntu users ;)

0.12.5 is pretty old.

> Statement:  No.  Hardcoded to "QEMU HARDDISK   ".
> Response:  Why couldn't this be a configuration item?
>
> Thanks for your reference to: docs/qdev-device-use.txt
> And also for the 'scsi-hd' example.  I can't see why, if the
> "serial=S,ver=V" options are supported, that "model=" couldn't also be
> added.  - I will try this.

Use "ver" as example to follow.  "serial" carries some backward
compatibility baggage.

> Statement:  Doubt it would be difficult.  But would it be useful?
> Agree with what your saying about specific calls, however, in my case
> I'm trying to run a vendor supplied image which "only supports" certain
> disks.  It is currently borking because it doesn't like the disks.  I
> strongly doubt it does any disk specific calls.  They are doing this to
> stop us installing disks bigger than 500GB, for example.  I'm trying to
> make "appliance" software run virtually.

Ha.

I don't know wether a patch would be accepted, but there's just one way
to find out.

[...]