[pve-devel] virtiodisk ordering bug in current implementation + proposal for new qemu device syntax

Alexandre DERUMIER aderumier at odiso.com
Mon Aug 29 07:56:27 CEST 2011


>This is a serious problem - how do you want to handle that?

>I also thought about doing it that way, but assign an unique addr to all devices (This only 
>works if we have enough pci slots available (pve-to-pci bridge). Or we simply guarantee
>a defined address for the first 10 devices for now?

>virtio0 -> addr10
>virtio9 -> addr19
>net0 -> addr20
>net9 -> addr29

>We can extend that guarantee once the pci-to-pci bridge code works.

>What do you think?


Yes, this is the simplest and easiest model.(it is the way i use in my patch for proxmox 1.8).

The question is, do you want to limit the virtio disk to X number, and nics to X number ?
I don't if some proxmox users want 20 disk or 20 nics by example.
Also maybe we need to keep 1 or 2 slots for pci devices passthrough

Personnaly, for my professional use, I never use more than 3 disk and 3 nics ;)


And yes, maybe is the future (6 months?) with pci bridge we can add more devices.

So maybe a config file for all devices slots mapping can be the solution, so we can extend it in the future.

Currently, i'm using this model config: (just an example)

pci: device=video0,bus=0,addr=2
pci: device=balloon,bus=0,addr=3
pci: device=audio0,bus=0,addr=4
pci: device=scsi0,bus=0,addr=5
pci: device=scsi1,bus=0,addr=6
pci: device=virtio0,bus=0,addr=10
pci: device=virtio1,bus=0,addr=11
pci: device=virtio2,bus=0,addr=12
pci: device=virtio3,bus=0,addr=13
pci: device=virtio4,bus=0,addr=14
pci: device=virtio5,bus=0,addr=15
pci: device=virtio6,bus=0,addr=16
pci: device=virtio7,bus=0,addr=17
pci: device=virtio8,bus=0,addr=18
pci: device=virtio9,bus=0,addr=19
pci: device=virtio10,bus=0,addr=20
pci: device=net0,bus=0,addr=21
pci: device=net1,bus=0,addr=22
pci: device=net2,bus=0,addr=23
pci: device=net3,bus=0,addr=24
pci: device=net4,bus=0,addr=25
pci: device=net5,bus=0,addr=26
pci: device=net6,bus=0,addr=27
pci: device=net7,bus=0,addr=28
pci: device=net8,bus=0,addr=29
pci: device=net9,bus=0,addr=30

what do you think about it ?







----- Mail original ----- 

De: "Dietmar Maurer" <dietmar at proxmox.com> 
À: "Alexandre DERUMIER" <aderumier at odiso.com>, pve-devel at pve.proxmox.com 
Envoyé: Lundi 29 Août 2011 07:25:44 
Objet: RE: virtiodisk ordering bug in current implementation + proposal for new qemu device syntax 

> In pve-manager side, 
> - disk form is the same (only numbers for virtio disk index change). 

I do not get that - why/how do we need to change disk index numbers? 

> - nic form, just add a "device number" field, like disks. 
> I think it's important to have the choice of slot device for nic too, because if you 
> to order your nic you can (you can switch eth0/eth1 by changing slot number). 

looks OK for me. 

- Dietmar 



-- 

-- 




	
	Alexandre Derumier 
Ingénieur système 
e-mail : aderumier at odiso.com 
Tél : +33 (0)3 20 68 88 90 
Fax : +33 (0)3 20 68 90 81 
45 Bvd du Général Leclerc 
59100 ROUBAIX - FRANCE 













-------------- next part --------------
A non-text attachment was scrubbed...
Name: aderumier.vcf
Type: text/x-vcard
Size: 183 bytes
Desc: not available
URL: <http://pve.proxmox.com/cgi-bin/mailman/private/pve-devel/attachments/20110829/83cf5b5c/attachment.vcf>


More information about the pve-devel mailing list