RE: Re: [Qemu-devel] cdrom hardcoded index

RE: Re: [Qemu-devel] cdrom hardcoded index

[Armistead, Jason]

On Monday, 28 August 2006 10:08 PM (AEST) Míguel wrote:

>> What about something like -hdX test.iso,hw=cdrom with default hw being
disk?
>
>And why not a shorted and more standard solution?
>
>-ideN [hd:|cd:]filename
>
>Examples:
>
>-ide0 /tmp/myimage.dsk
>Set primary master as harddisk (hd: is the default)
>
>-ide1 hd:/tmp/myimage.dsk
>Set primary slave as harddisk (hd: is not necessary in this case, as
>it's the default).
>
>-ide3 cd:/dev/cdrom
>Set secondary slave as cdrom using device /dev/cdrom
>
>-ide0 cd:/tmp/myimage.iso
>Set primary master as cdrom using an ISO image file.
>
>Of course, the previous parameters (hda, hdb, hdc, hdd and cdrom)
>should be also available for compatibility reasons.
>
>And you could also add -fd0 (for -fda) and -fd1(for -fdb) for
>consistency with the rest of parameters.
>
>Just my two cents.


And what about non-PC guest environments like Sparcs where there are no IDE
drives, only SCSI ones for hard disk, CD and (I think) for floppy drives ?
How would you expand that syntax ?

Not everyone running QEMU is seeking to run a "PC in PC" configurations.

Cheers

Jason

Re: [Qemu-devel] cdrom hardcoded index

[Paul Brook]

On Monday 28 August 2006 13:20, Armistead, Jason wrote:
> On Monday, 28 August 2006 10:08 PM (AEST) Míguel wrote:
> >> What about something like -hdX test.iso,hw=cdrom with default hw being
>
> disk?
>
> >And why not a shorted and more standard solution?
> >
> >-ideN [hd:|cd:]filename
>
> And what about non-PC guest environments like Sparcs where there are no IDE
> drives, only SCSI ones for hard disk, CD and (I think) for floppy drives ?
> How would you expand that syntax ?
>
> Not everyone running QEMU is seeking to run a "PC in PC" configurations.

If you' are changing these options you may as well make if possible to use 
scsi on x86 targets. All the device emulation is there (commented out in 
pc.c) it's just missing the user-visible options to turn it on.

My current thinking is that instead of a fixed set of block devices, the host 
device emulation (IDE controller, SCSI HBA) would register named device with 
qemu. Each adapter is given a name (ide0, scsi0, etc), and has numbered slots 
for attaching storage devices. Then use a commandline syntax similar to 
the -net options to connect disks. Something like:

-disk dev=ide0,id=0,file=foo.iso,type=cdrom -disk scsi0,3,bar.img

Gives you an ide cdrom on  primary master channel, and a scsi harddrive with 
SCSI ID3 on the scsi controller.

I guess we probably want to model a dual-channel IDE controller as two 
separate controllers for these purposes.

If done properly I'd expect this scheme to allow hot-plugging of devices, and 
automatic selection of the emulated hardware based on what devices the user 
requests. I'd also hope it would fit nicely into future config file 
structure.

Paul

[Qemu-devel] Asking about testing a character device on Qemu ARM system

[Tieu Ma Dau]

[-- Attachment #1: Type: text/plain, Size: 532 bytes --]


Hi all,
I use Qemu to simulate ARM system. I add a simple LED device at IO port
address 0x1b000000 (because this address is marked "reserved" in
IntegratorCP documentation). 
So I want to ask you the following questions:
1. Is there any problem if I use address 0x1b000000 for my new device?
2. How can I test this device?
Do you have any ideas to help me for these questions?
Thanks a lot
Tieu

 
 		
---------------------------------
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls.  Great rates starting at 1¢/min.

[-- Attachment #2: Type: text/html, Size: 729 bytes --]

Re: [Qemu-devel] Asking about testing a character device on Qemu ARM system

[Paul Brook]

On Monday 28 August 2006 15:12, Tieu Ma Dau wrote:
> Hi all,
> I use Qemu to simulate ARM system. I add a simple LED device at IO port
> address 0x1b000000 (because this address is marked "reserved" in
> IntegratorCP documentation).
> So I want to ask you the following questions:
> 1. Is there any problem if I use address 0x1b000000 for my new device?
> 2. How can I test this device?

Treat it exactly like you would real hardware.

Paul