Hi All, First time mucking around with the xVM hypervisor. I''ve followed the guides at: http://blogs.sun.com/agupta/entry/install_windows_as_a_hvm as well as: http://blogs.sun.com/ptelles/entry/sun_xvm_hypervisor_part_i http://blogs.sun.com/ptelles/entry/sun_xvm_hypervisor_part_ii On a snv_118 x64 system xVM is running just fine, and I''ve successfully installed with practically no hassles Windows 7/XPSP2/Windows Server 2008. Didn''t even need to alter the ZFS ARC However, on all three guests I am flummoxed as to how to enable networking. pfexec dladm show-link displays the presence of a vnic running over bge0, doing a virsh dumpxml shows that a network bridge is successfully configured. The dom0''s network is fine, has full outbound access etc. However in all cases I cannot ping out nor into the domU. Doesn''t matter if they are using DHCP or a fixed IP address. Is there any post-install configuration or special sauce I need to do to get this working (e.g. on Virtualbox default behavior is for the guest to be NATed behind the host)? Sorry in advance if this is obvious. Cheers Dave -- This message posted from opensolaris.org
On 19 Aug 2009, at 12:01pm, Dave Koelmeyer wrote:> On a snv_118 x64 system xVM is running just fine, and I''ve > successfully installed with practically no hassles Windows 7/XPSP2/ > Windows Server 2008. Didn''t even need to alter the ZFS ARC However, > on all three guests I am flummoxed as to how to enable networking. > > pfexec dladm show-link displays the presence of a vnic running over > bge0, doing a virsh dumpxml shows that a network bridge is > successfully configured. The dom0''s network is fine, has full > outbound access etc. > > However in all cases I cannot ping out nor into the domU. Doesn''t > matter if they are using DHCP or a fixed IP address. Is there any > post-install configuration or special sauce I need to do to get this > working (e.g. on Virtualbox default behavior is for the guest to be > NATed behind the host)?There shouldn''t be any specific configuration to perform. Can you confirm that the guests see a Realtek network adaptor (RTL8139), and they they are happy that it is working (driver okay, etc.)?
What''s the IP/netmask of dom0 and domU? If you do snoop on bge0 interface in dom0 and run ping from domU to dom0 can you see anything? You need to provide more details on your configuration. -- Robert Milkowski http://milek.blogspot.com -- This message posted from opensolaris.org
Hi David (and Milek)
Thanks for your reply, yes, in my Windows XP SP2 guest (for example) I can see
that Realtek network adaptor, and Windows reports it is functioning fine.
Here is some other information I have obtained on my configuration:
$ pfexec virsh list
Id Name State
----------------------------------
0 Domain-0 running
15 WinXPSP2 blocked
$ pfexec virsh dumpxml WinXPSP2
<domain type=''xen'' id=''15''>
<name>WinXPSP2</name>
<uuid>e75a8148-6407-560b-4451-6f6c84979c2f</uuid>
<os>
<type>hvm</type>
<loader>/usr/lib/xen/boot/hvmloader</loader>
<boot dev=''hd''/>
</os>
<memory>1048576</memory>
<vcpu>1</vcpu>
<on_poweroff>destroy</on_poweroff>
<on_reboot>destroy</on_reboot>
<on_crash>destroy</on_crash>
<distro name=''winxp''/>
<features>
<pae/>
</features>
<clock offset=''localtime''/>
<devices>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
<interface type=''bridge''>
<source bridge=''bge0 ''/>
<target dev=''vif15.0''/>
<mac address=''00:16:3e:1f:83:85''/>
<script path=''vif-vnic''/>
</interface>
<disk type=''block'' device=''disk''>
<driver name=''phy''/>
<source dev=''/dev/zvol/dsk/rpool/WinXPSP2''/>
<target dev=''hda''/>
</disk>
<disk type=''file'' device=''cdrom''>
<driver name=''file''/>
<source
file=''/export/home/dkoe001/xVMISOs/xpsp2.iso''/>
<target dev=''hdc''/>
<readonly/>
</disk>
<input type=''mouse'' bus=''ps2''/>
<graphics type=''vnc'' port=''5900''/>
<input type=''tablet'' bus=''usb''/>
<console tty=''/dev/pts/4''/>
</devices>
</domain>
$ pfexec dladm show-vnic
LINK OVER SPEED MACADDRESS MACADDRTYPE VID
xvm15_0 bge0 100 0:16:3e:1f:83:85 fixed
0
$ pfexec dladm show-link
LINK CLASS MTU STATE OVER
bge0 phys 1500 up --
xvm15_0 vnic 1500 up bge0
$ pfexec dladm show-phys
LINK MEDIA STATE SPEED DUPLEX DEVICE
bge0 Ethernet up 100 full bge0
--
This message posted from opensolaris.org
$ pfexec virsh dumpxml WinXPSP2
domain type=''xen'' id=''15''
name WinXPSP2 name
uuid e75a8148-6407-560b-4451-6f6c84979c2f uuid
os
type hvm type
loader usr lib xen boot hvmloader loader
boot dev=''hd''
os
memory 1048576 memory
vcpu 1 vcpu
on_poweroff destroy on_poweroff
on_reboot destroy on_reboot
on_crash destroy on_crash
distro name=''winxp''
features
pae
features
clock offset=''localtime''
devices
emulator usr lib xen bin qemu-dm emulator
interface type=''bridge''
source bridge=''bge0 ''
target dev=''vif15.0''
mac address=''00:16:3e:1f:83:85''
script path=''vif-vnic''
interface
disk type=''block'' device=''disk''
driver name=''phy''
source dev='' dev zvol dsk rpool WinXPSP2''
target dev=''hda''
disk
disk type=''file'' device=''cdrom''
driver name=''file''
source file='' export home dkoe001 xVMISOs xpsp2.iso''
target dev=''hdc''
readonly
disk
input type=''mouse'' bus=''ps2''
graphics type=''vnc'' port=''5900''
input type=''tablet'' bus=''usb''
console tty='' dev pts 4''
devices
domain
--
This message posted from opensolaris.org
Hi Milek, Here we are: 169.254.26.252 is the IP address of the domU, and its hostname is UOA-816A8C6D4A8. # snoop | grep -i ''169.254'' All I see are groups of messages like this: 169.254.26.252 -> 239.255.255.250 IGMP v2 membership report 169.254.26.252 -> 239.255.255.250 IGMP v2 membership report 169.254.26.252 -> 169.254.255.255 NBT Datagram Service Type=17 Source=UOA-816A8C6D4A8[0] 169.254.26.252 -> 169.254.255.255 NBT NS Query Request for WORKGROUP[1b], Success 169.254.26.252 -> 169.254.255.255 NBT NS Query Request for WORKGROUP[1b], Success 169.254.26.252 -> 169.254.255.255 NBT NS Query Request for WORKGROUP[1b], Success This is bound to be something simple which I am missing... Cheers, Dave -- This message posted from opensolaris.org
On 20 Aug 2009, at 5:58am, Dave Koelmeyer wrote:> Hi Milek, > > Here we are: > > 169.254.26.252 is the IP address of the domU, and its hostname is > UOA-816A8C6D4A8. > > # snoop | grep -i ''169.254'' > > All I see are groups of messages like this: > > 169.254.26.252 -> 239.255.255.250 IGMP v2 membership report > 169.254.26.252 -> 239.255.255.250 IGMP v2 membership report > 169.254.26.252 -> 169.254.255.255 NBT Datagram Service Type=17 > Source=UOA-816A8C6D4A8[0] > 169.254.26.252 -> 169.254.255.255 NBT NS Query Request for > WORKGROUP[1b], Success > 169.254.26.252 -> 169.254.255.255 NBT NS Query Request for > WORKGROUP[1b], Success > 169.254.26.252 -> 169.254.255.255 NBT NS Query Request for > WORKGROUP[1b], SuccessThis suggests that packets are getting out, so at least something is working. Please just snoop the vnic (''snoop vnic27'', or whatever is the right one) and attempt ''ping'' in another window.
Thanks David, here we are:
dkoe001@turrican:~# dladm show-link
LINK CLASS MTU STATE OVER
bge0 phys 1500 up --
xvm2_0 vnic 1500 up bge0
dkoe001@turrican:~# snoop -d xvm2_0 turrican
Using device xvm2_0 (promiscuous mode)
If I run the above and ping dom0 from domU, with the domU in its default
as-installed configuration, I see nothing - no feedback, no activity picked up
with snoop. On the domU running the ping command it reports "Destination
host unreachable".
If in the domU I configure a fixed IP address/netmask/DNS server (using the
correct settings as I would for the same network the dom0 is on) I see from
snoop on the dom0:
techsetup -> turrican ICMP Echo request (ID: 512 Sequence number: 256)
turrican -> techsetup ICMP Echo reply (ID: 512 Sequence number: 256)
I can ping dom0 OK, and dom0 can ping domU. I cannot however ping any other
device from the domU, nor can I connect to any other network resource
(regardless of using DNS).
I might add that the dom0 is also in an as-installed state, aside from updating
to snv_118 and disabling NWAM, I haven''t fiddled with it at all really.
Cheers,
Dave
--
This message posted from opensolaris.org
On 21 Aug 2009, at 2:55am, Dave Koelmeyer wrote:> Thanks David, here we are: > > dkoe001@turrican:~# dladm show-link > LINK CLASS MTU STATE OVER > bge0 phys 1500 up -- > xvm2_0 vnic 1500 up bge0 > > dkoe001@turrican:~# snoop -d xvm2_0 turrican > Using device xvm2_0 (promiscuous mode) > > If I run the above and ping dom0 from domU, with the domU in its > default as-installed configuration, I see nothing - no feedback, no > activity picked up with snoop. On the domU running the ping command > it reports "Destination host unreachable". > > If in the domU I configure a fixed IP address/netmask/DNS server > (using the correct settings as I would for the same network the dom0 > is on) I see from snoop on the dom0: > > techsetup -> turrican ICMP Echo request (ID: 512 Sequence > number: 256) > turrican -> techsetup ICMP Echo reply (ID: 512 Sequence number: > 256) > > I can ping dom0 OK, and dom0 can ping domU. I cannot however ping > any other device from the domU, nor can I connect to any other > network resource (regardless of using DNS). > > I might add that the dom0 is also in an as-installed state, aside > from updating to snv_118 and disabling NWAM, I haven''t fiddled with > it at all really.Dave, given that dom0 <-> domU connectivity seems to be working, I''m puzzled. Is it possible that the switch port to which bge0 is connected could be filtering traffic?
Hi David Doh!! Thinking about it this is exactly what it will be. Sorry I didn''t think of this before posting! I''ll have a chat to our network guys and verify this, and post back if it does resolve the issue - which I''m sure it will. Have a great weekend :) Dave -- This message posted from opensolaris.org