Hi, I''m trying to run Windows XP guest on a b90 host. No matter what I''ve tried doing, I always get "Device 0 (vif) could not be connected. Backend device not found." when I try creating a guest with a vif. Unfortunately, the host uses an Asus P5K-VM motherboard with Marvell 88E8056 PCI-E Gigabit Ethernet Controller, and had to go through some bells and hoops to make it work (see link to bells and hoops article below), including the installation of a driver from SysKonnect''s website. I feel a bit sheepish for not being able to find the proper explanation for Xen and networking in Solaris (is there such a thing?). But from what I collected on the Internet I /think/ the driver may be an old GLDv2, and Xen requires GLDv3 architected drivers to work with network. Is that correct? Finally, I wanted to give up on ''real'' networking from my machine and let Solaris route the traffic using something akin to ''host only networking'', and still couldn''t find the proper explanation for Xen and networking in Solaris. What other vif types are there other than ioemu and bridge, and where do I read about them? Bottom line is: what''s the path you''d recommend to get me a running Windows XP box with networking? Thanks, - Yaniv (bells and hoops galore http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6546335) This message posted from opensolaris.org
> Hi, > > I''m trying to run Windows XP guest on a b90 host. No > matter what I''ve tried doing, I always get "Device 0 > (vif) could not be connected. Backend device not > found." when I try creating a guest with a vif. > > Unfortunately, the host uses an Asus P5K-VM > motherboard with Marvell 88E8056 PCI-E Gigabit > Ethernet Controller, and had to go through some bells > and hoops to make it work (see link to bells and > hoops article below), including the installation of a > driver from SysKonnect''s website. > > I feel a bit sheepish for not being able to find the > proper explanation for Xen and networking in Solaris > (is there such a thing?). But from what I collected > on the Internet I /think/ the driver may be an old > GLDv2, and Xen requires GLDv3 architected drivers to > work with network. Is that correct?Yes> > Finally, I wanted to give up on ''real'' networking > from my machine and let Solaris route the traffic > using something akin to ''host only networking'', and > still couldn''t find the proper explanation for Xen > and networking in Solaris. What other vif types are > there other than ioemu and bridge, and where do I > read about them? > > Bottom line is: what''s the path you''d recommend to > get me a running Windows XP box with networking?Buy RTL 8169SC (1) or RTL 8139 (2) and plug card into PCI slot Reinstall Nevada. I guess :- (1) bash-3.2# dladm show-link LINK CLASS MTU STATE OVER rge0 (?) phys 1500 up -- (2) bash-3.2# dladm show-link LINK CLASS MTU STATE OVER rlts0 phys 1500 up -- svccfg -s xvm/xend setprop config/vncpasswd = astring: \"secret\" svccfg -s xvm/xend setprop config/vnc-listen = astring: \"0.0.0.0\" svccfg -s xvm/xend setprop config/default-nic="rge0" (" rlts0") svcadm refresh xvm/xend svcadm restart xvm/xend Virt-install WinXP. Realtek adapters work for sure.> > Thanks, > - Yaniv > > (bells and hoops galore > http://bugs.opensolaris.org/bugdatabase/view_bug.do?bu > g_id=6546335)This message posted from opensolaris.org
Probably at mean time that is not your concern. However ,view :- http://www.opensolaris.org/jive/thread.jspa?threadID=61454&tstart=0 ******************************************************************************************************** Box1:- C2D E8400 ASUS, P5K Premium/WIFI, 4 GB RAM default-nic="rge0" Box2:- C2D E6600 ASUS P5B Deluxe + RTL8139 (plugged into PCI slot), 4GB RAM default-nic="rtls0" Attempt to install SNV90 DomU at SNV91 Dom0 (the most recent Xen bits installed) in DHCP mode failed on Box1 (dhcp timed out) and succeded on Box2 Both Box1 and Box2 are located on the same LAN and on he same dhcp bridge (ADSL modem) ******************************************************************************************************** Actually, first board has RTL 8169SC integrated as second NIC. So, i am not quite sure that with RTL 8169SC ,plugged in PCI slot, you would be able install WinXP HVM in DHCP mode ( what gives Internet access and etc). Finally , from my very personal standpoint RTL 8139 ($4-$5) is the best solution for your purposes. RTL 8169SC is more expensive and much better as NIC. But Bug 6703227 provides no information about Nevada Build in which it''s supposed to be fixed. What causes very serious trouble even in Lab''s environment. This message posted from opensolaris.org
There is one more exciting solution to put Marvell Yukon in work right away. It is install instead of Nevada Dom0 any Linux Dom0 (F8,CentOS 5.1,OpenSuse 10.3, Ubuntu HH (GG), Debian Etch,.....) . All of them would work with Xen Bridge attached to Marvell Yukon Ethernet interface just fine. This message posted from opensolaris.org
Thanks for the suggestions Boris, I''d rather stay with Solaris in Dom0 and (if possible) not take up another PCI slot, especially as I''m willing to go with Xen''s equivalent of "host only networking", if any. Other alternatives? This message posted from opensolaris.org
> Thanks for the suggestions Boris, I''d rather stay > with Solaris in Dom0 and (if possible) not take up > another PCI slot, especially as I''m willing to go > with Xen''s equivalent of "host only networking", if > any. > > Other alternatives?http://blogs.sun.com/roamer/entry/n_in_nemo_nics_powered This message posted from opensolaris.org