I''ve searched all night long on google, discussions, threads, and the
xen wiki... but I can''t find how to do this:
vif = [''type=ioemu,mac=XX:XX:XX:XX:XX:XX,model=ne2k_pci'']
where should I put this?
I have sxce94, dom0 works nicely, and domUs too, but I''d like to select
ne2k for an hvm openbsd dom0 that I''ve created because I''ve
read that it doesn''t to the annoying timeouts that the emulated realtek
does.
So long if I dump the xml configuration of my hvm domU it says (I had to swap
<> with {} or this forum didn''t let me post the config, but
it''s the same):
{interface type=''bridge''}
{source bridge=''nge0 ''/}
{target dev=''vif-1.0''/}
{mac address=''00:16:3e:17:f4:46''/}
{script path=''vif-vnic''/}
{/interface}
if I try to add the model=ne2k_pci here in any way it doesn''t want to
reimport the xml, otherwise it works fine.
If I look at the config.sxp (I know I shouldn''t, but still...) it says:
(device
(vif
(bridge ''nge0 '')
(mac 00:16:3e:17:f4:46)
(script vif-vnic)
(uuid 54edd73e-27ec-7684-1101-f6e50807e9dd)
(backend 0)
)
Is there a way to specify this with SXCE94 with the included xVM version
3.1.4-xvm ?
tnx in advance
This message posted from opensolaris.org
I can''t see a way to do this with the libvirt XML. You could switch to using .py files, in which case your ''vif = ...'' line will work. A less clean alternative is to patch the default type, which is in /usr/lib/python2.4/vendor-packages/xen/xend/image.py, but this will get over-written by any upgrades. On Thu, Jul 31, 2008 at 10:31:32PM -0700, Diego Righi wrote:> I''ve searched all night long on google, discussions, threads, and the xen wiki... but I can''t find how to do this: > vif = [''type=ioemu,mac=XX:XX:XX:XX:XX:XX,model=ne2k_pci''] > where should I put this? > I have sxce94, dom0 works nicely, and domUs too, but I''d like to select ne2k for an hvm openbsd dom0 that I''ve created because I''ve read that it doesn''t to the annoying timeouts that the emulated realtek does. > So long if I dump the xml configuration of my hvm domU it says (I had to swap <> with {} or this forum didn''t let me post the config, but it''s the same): > > {interface type=''bridge''} > {source bridge=''nge0 ''/} > {target dev=''vif-1.0''/} > {mac address=''00:16:3e:17:f4:46''/} > {script path=''vif-vnic''/} > {/interface} > > if I try to add the model=ne2k_pci here in any way it doesn''t want to reimport the xml, otherwise it works fine. > If I look at the config.sxp (I know I shouldn''t, but still...) it says: > > (device > (vif > (bridge ''nge0 '') > (mac 00:16:3e:17:f4:46) > (script vif-vnic) > (uuid 54edd73e-27ec-7684-1101-f6e50807e9dd) > (backend 0) > ) > > Is there a way to specify this with SXCE94 with the included xVM version 3.1.4-xvm ? > > tnx in advance > > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
tnx for the reply :) I''ll try to switch to .py files since I don''t want to mess with system files... ...but I really can''t understand if this is a valid option why isn''t possible to select it from the virt-install command line :/ This message posted from opensolaris.org
I''ve finally managed to find the simpler way to do what I wanted: 1) I''ve created a simple .py file with the: vif = [''type=ioemu,mac=XX:XX:XX:XX:XX:XX,model=ne2k_pci''] line 2) then I''ve done an xm create -f filename -n the useful -n option does a dry-run and dumps to you the resulting .sxp 3) made a diff with the previous .sxp created by virsh and seen that it added just this line to the network definition: (model ne2k_pci) 4) I''ve deleted and recreated the domU with xm create -F newfile.sxp 5) then, just for the sake of it, I did a virsh dumpxml of that same domain, and you know what the only difference was? with ne2k target dev=''vif8.0'' with default realtek nick emulation it was target dev=''vif1.0'' I don''t know where all of this is documented but maybe it should be added to this excellent howto: http://www.opensolaris.org/os/community/xen/docs/xvm_how_to_V2.0.pdf just my 2c :) This message posted from opensolaris.org
With the ne2k device the domU networking works ok and no more device timeouts in the dmesg so I wanted to share the .sxp config and the resulting dmesg and some other useful data: http://www.sickness.it/dmesgxvmsxce94dom0obsd43domuhvm.txt :) This message posted from opensolaris.org
Hi Diego,
I''m trying to follow in your footsteps. First I installed OpenBSD
using:
virt-install --name puffy --hvm --ram 1024 --vnc --file
/dev/zvol/dsk/tank/watsen.net-root-disk --cdrom
/tank/install43_amd64.iso --noautoconsole --os-type=unix
--os-variant=openbsd4 --vcpus=1
and then I used `vrish dumpxml puffy > puffy.xml`, which I then edited
to replace "vif-1.0" with "vif-8.0". But when I read it
back in with
`virsh define puffy.xml`, the setting gets lost... Is there any way to
use XML files, or do I have to use SXP files? - is it because libvirt
doesn''t support the option yet?
BTW, it took a long time (~40 min) for openbsd 4.3 to install its media,
which is forever compared to when I install it outside Xen - did you
have a similar experience? If not, then I wonder what could be my
system''s problem? - I''m using b97 and Bonnie says
I''m getting ~300M/sec
block-output and ~600M/sec block-input, which seems like it should scream...
Thanks,
Kent
Diego Righi wrote:> With the ne2k device the domU networking works ok and no more device
timeouts in the dmesg so I wanted to share the .sxp config and the resulting
dmesg and some other useful data:
> http://www.sickness.it/dmesgxvmsxce94dom0obsd43domuhvm.txt
>
> :)
>
>
> This message posted from opensolaris.org
> _______________________________________________
> xen-discuss mailing list
> xen-discuss@opensolaris.org
>