WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] xen assing nic

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xen assing nic
From: rainbow <lvqq05@xxxxxxxxx>
Date: Sun, 2 Oct 2011 22:17:40 +0800
Delivery-date: Sun, 02 Oct 2011 07:19:12 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=J30cQuK5JVOQhoQvQI+BFRCqk7q4u+NPXCOdZ3NRo0k=; b=VaWplY95U+5C0sQALQj2nPdzKpMNrihGBwo62FvW4VF3ISeiGXu2uhn3Jda7HHexsv eS/I5iHlmaaKwgpKYeq8+kKBkvoAGThkfxb1BKWoo0Q9Nb0KQJj82lrPBeCZs80OSPbl yhpR3Ig27vjMxEpnmlWZp/Zmb6rkbkXeblKNw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

Hi,all, I install Xen for linux-3.0 and compile the kernel with iommu.  my domu kernel is the same kernel with the host machine. I hide nic  as http://wiki.xen.org/xenwiki/VTdHowTo procedure.
If I add pci=['10:00.0'] at guest config file, then I will get
NET: Registered protocol family 36
Registering the dns_resolver key type
registered taskstats version 1
blkfront: xvda2: barriers disabled
blkfront: xvda1: barriers disabled
XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s...
XENBUS: Timeout connecting to device: device/pci/0 (local state 3, remote state 1)
XENBUS: Device with no driver: device/console/0
Freeing unused kernel memory: 716k freed
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (xvda2): mounted filesystem with writeback data mode
udev[862]: starting version 164
input: PC Speaker as /devices/platform/pcspkr/input/input0
Adding 131068k swap on /dev/xvda1.  Priority:-1 extents:1 across:131068k SS
EXT3-fs (xvda2): using internal journal
sshd (1291): /proc/1291/oom_adj is deprecated, please use /proc/1291/oom_score_adj instead.
eth0: no IPv6 routers present

Then I log on to guest os:
#lspci
get no output. but if I run #xm pci-list my_dom
then I will get pci information. I don't know why.

And a strange thing is when I start guest os first , I wii get the following information on the host dmesg:
181.154722] ------------[ cut here ]------------
 [  181.163039] WARNING: at arch/x86/xen/mmu.c:486 xen_make_pte_debug+0x99/0xfa()
 [  181.173959] Hardware name: ProLiant DL380 G6
 [  181.182005] 0x95bd3000 is using VM_IO, but it is 0x105dd8000!
 [  181.191559] Modules linked in: radeon ttm hpwdt drm_kms_helper bnx2 r8169 [last unloaded: scsi_wait_scan]
 [  181.205115] Pid: 3505, comm: xend Not tainted 3.0.0-xen2-iommu #2
 [  181.215108] Call Trace:
 [  181.221439]  [<ffffffff81006215>] ? xen_make_pte_debug+0x99/0xfa
 [  181.231354]  [<ffffffff81045d03>] warn_slowpath_common+0x80/0x99
 [  181.241248]  [<ffffffff81045dff>] warn_slowpath_fmt+0x69/0x6b
 [  181.250821]  [<ffffffff81006871>] ? xen_force_evtchn_callback+0xd/0xf
 [  181.261145]  [<ffffffff81006871>] ? xen_force_evtchn_callback+0xd/0xf
 [  181.271391]  [<ffffffff81006f12>] ? check_events+0x12/0x20
 [  181.280741]  [<ffffffff81007649>] ? get_phys_to_machine+0x26/0x5f
 [  181.290610]  [<ffffffff81004a2a>] ? pfn_to_mfn+0x12/0x2f
 [  181.299720]  [<ffffffff81006215>] xen_make_pte_debug+0x99/0xfa
 [  181.309293]  [<ffffffff810044cf>] __raw_callee_save_xen_make_pte_debug+0x11/0x1e
 [  181.320501]  [<ffffffff8100485b>] ? pfn_pte+0x33/0x35
 [  181.329317]  [<ffffffff810066cd>] remap_area_mfn_pte_fn+0x24/0x64
 [  181.339190]  [<ffffffff810cee32>] apply_to_page_range+0x20e/0x298
 [  181.349064]  [<ffffffff81006871>] ? xen_force_evtchn_callback+0xd/0xf
 [  181.359239]  [<ffffffff810066a9>] ? xen_set_domain_pte+0x7a/0x7a
 [  181.368912]  [<ffffffff81004cc0>] xen_remap_domain_mfn_range+0x97/0xef
 [  181.379136]  [<ffffffff811f0a28>] ? cpumask_any_but+0x1f/0x2c
 [  181.388454]  [<ffffffff810b8c84>] ? __alloc_pages_nodemask+0x13e/0x610
 [  181.398563]  [<ffffffff81038aee>] ? need_resched+0x1e/0x28
 [  181.407532]  [<ffffffff81271069>] mmap_batch_fn+0x32/0x51
 [  181.416364]  [<ffffffff81270b00>] traverse_pages+0x8c/0xad
 [  181.425262]  [<ffffffff81271037>] ? privcmd_ioctl+0x375/0x375
 [  181.434506]  [<ffffffff81270fde>] privcmd_ioctl+0x31c/0x375
 [  181.443515]  [<ffffffff811b8645>] ? inode_has_perm+0x2f/0x31
 [  181.452583]  [<ffffffff810fb4a4>] vfs_ioctl+0x18/0x2f
 [  181.461009]  [<ffffffff810fb9c2>] do_vfs_ioctl+0x437/0x48a
 [  181.469721]  [<ffffffff810fba6c>] sys_ioctl+0x57/0x7a
 [  181.477889]  [<ffffffff81513892>] system_call_fastpath+0x16/0x1b
 [  181.487033] ---[ end trace 3a9b3e835521feaa ]---
 [  181.781960] ADDRCONF(NETDEV_UP): vif1.0: link is not ready
 [  182.082542] device vif1.0 entered promiscuous mode
 [  182.135754] ADDRCONF(NETDEV_UP): vif1.0: link is not ready
 [  183.603896] xen-blkback:ring-ref 8, event-channel 9, protocol 1 (x86_64-abi)
 [  183.643943] xen-blkback:ring-ref 9, event-channel 10, protocol 1 (x86_64-abi)
 [  183.668937] ADDRCONF(NETDEV_CHANGE): vif1.0: link becomes ready
 [  183.678210] eth2: port 2(vif1.0) entering forwarding state
 [  183.686973] eth2: port 2(vif1.0) entering forwarding state
 [  194.547265] vif1.0: no IPv6 routers present
 [  246.549091] eth2: port 2(vif1.0) entering forwarding state
 [  246.557979] eth2: port 2(vif1.0) entering disabled state
 [  254.022803] ADDRCONF(NETDEV_UP): vif2.0: link is not ready
 [  254.320923] device vif2.0 entered promiscuous mode
 [  254.353327] ADDRCONF(NETDEV_UP): vif2.0: link is not ready
 [  255.045265] xen-blkback:ring-ref 9, event-channel 10, protocol 1 (x86_64-abi)
 [  255.100907] xen-blkback:ring-ref 10, event-channel 11, protocol 1 (x86_64-abi)
 [  255.125760] ADDRCONF(NETDEV_CHANGE): vif2.0: link becomes ready
 [  255.134859] eth2: port 2(vif2.0) entering forwarding state
 [  255.143391] eth2: port 2(vif2.0) entering forwarding state
 [  265.875280] vif2.0: no IPv6 routers present
 [ 1761.378188] eth2: port 2(vif2.0) entering forwarding state
 [ 1761.393523] eth2: port 2(vif2.0) entering disabled state
 [ 1805.767069] ADDRCONF(NETDEV_UP): vif3.0: link is not ready
 [ 1806.087673] device vif3.0 entered promiscuous mode
 [ 1806.132934] ADDRCONF(NETDEV_UP): vif3.0: link is not ready
 [ 1806.624631] xen-blkback:ring-ref 8, event-channel 9, protocol 1 (x86_64-abi)
 [ 1806.708691] xen-blkback:ring-ref 9, event-channel 10, protocol 1 (x86_64-abi)
 [ 1806.744669] ADDRCONF(NETDEV_CHANGE): vif3.0: link becomes ready
 [ 1806.753718] eth2: port 2(vif3.0) entering forwarding state
 [ 1806.762315] eth2: port 2(vif3.0) entering forwarding state
 [ 1817.123275] vif3.0: no IPv6 routers present

If I start the guest os again. there is no such information.
I am very sorry for my english and I search many hours from the list but can not solve the problem. Thank you for your help!!
--
Qingquan Lv
School of Information Science & Engineering , Lanzhou University.
mail: lvqq05@xxxxxxxxx
Do what you like,
Enjoy your life.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] xen assing nic, rainbow <=