On Wed, Jun 2, 2010 at 9:58 PM, Jim Fehlig <[email protected]> wrote:
> Hmm, I haven't seen the netif option used before. IIUC, it enables the domU
> to act a network backend - aka driver domain.
i'd added it to my opensuse guests' configs a long while back to solve
"some problem" -- honestly, too long ago to tell you why ... other
than it still works. for opensuse guests, anyway.
> Does the domU boot progress if this setting is removed?
nope. still hangs at:
...
Initalizing network drop monitor service
Write protecting the kernel read-only data: 483k
>> XENBUS: Device with no driver: device/console/0
>>
>
> A pv driver issue in the boot image?
Possible. I know next to nothing about Centos' images. The boot img
is a netinstall disk. Perhaps a bit "short" on it's capabilities ...
aria2c is dl'ing the full DVD to test as I type here ...
> Not much in the logs. Does 'xm dmesg' or /var/log/messages in host contain
> anything enlightening?
unclear. take a look:
tail -f /var/log/messages
-------------------------------------------------------
...
...
Jun 2 22:10:31 server logger: /etc/xen/scripts/block: Writing
backend/vbd/9/51744/physical-device fd:18 to xenstore.
Jun 2 22:10:31 server kernel: [14586.162087] (cdrom_add_media_watch()
file=/usr/src/packages/BUILD/kernel-xen-2.6.34/linux-2.6.34/drivers/xen/blkback/cdrom.c,
line=108) nodename:backend/vbd/9/51744
Jun 2 22:10:31 server kernel: [14586.174821] (cdrom_is_type()
file=/usr/src/packages/BUILD/kernel-xen-2.6.34/linux-2.6.34/drivers/xen/blkback/cdrom.c,
line=95) type:0
Jun 2 22:10:31 server logger: /etc/xen/scripts/block: Writing
backend/vbd/9/51744/hotplug-status connected to xenstore.
Jun 2 22:10:32 server logger: /etc/xen/scripts/block: Writing
backend/vbd/9/5632/node /dev/loop0 to xenstore.
Jun 2 22:10:32 server logger: /etc/xen/scripts/block: Writing
backend/vbd/9/5632/physical-device 7:0 to xenstore.
Jun 2 22:10:32 server kernel: [14587.117890] (cdrom_add_media_watch()
file=/usr/src/packages/BUILD/kernel-xen-2.6.34/linux-2.6.34/drivers/xen/blkback/cdrom.c,
line=108) nodename:backend/vbd/9/5632
Jun 2 22:10:32 server kernel: [14587.131459] (cdrom_is_type()
file=/usr/src/packages/BUILD/kernel-xen-2.6.34/linux-2.6.34/drivers/xen/blkback/cdrom.c,
line=95) type:1
Jun 2 22:10:32 server kernel: [14587.138519] (cdrom_add_media_watch()
file=/usr/src/packages/BUILD/kernel-xen-2.6.34/linux-2.6.34/drivers/xen/blkback/cdrom.c,
line=110) is a cdrom
Jun 2 22:10:32 server logger: /etc/xen/scripts/block: Writing
backend/vbd/9/5632/hotplug-status connected to xenstore.
Jun 2 22:10:32 server kernel: [14587.150294] (cdrom_add_media_watch()
file=/usr/src/packages/BUILD/kernel-xen-2.6.34/linux-2.6.34/drivers/xen/blkback/cdrom.c,
line=112) xenstore wrote OK
Jun 2 22:10:32 server kernel: [14587.157834] (cdrom_is_type()
file=/usr/src/packages/BUILD/kernel-xen-2.6.34/linux-2.6.34/drivers/xen/blkback/cdrom.c,
line=95) type:1
Jun 2 22:10:41 server kernel: [14596.275638] blkback: ring-ref 2312,
event-channel 21, protocol 1 (x86_64-abi)
Jun 2 22:10:41 server kernel: [14596.397827] blkback: ring-ref 2313,
event-channel 22, protocol 1 (x86_64-abi)
Jun 2 22:10:41 server kernel: [14596.517850] blkback: ring-ref 2314,
event-channel 23, protocol 1 (x86_64-abi)
Jun 2 22:10:41 server kernel: [14596.636992] blkback: ring-ref 2315,
event-channel 24, protocol 1 (x86_64-abi)
( ... HANGS HERE ... )
-------------------------------------------------------
and,
xm dmesg
-------------------------------------------------------
(XEN) Xen version 4.0.0_21087_01-38.1 (abuild@) (gcc version 4.4.1
[gcc-4_4-branch revision 150839] (SUSE Linux) ) Fri Apr 2 22:30:04
UTC 2010
(XEN) Latest ChangeSet: 21087
(XEN) Command line: loglvl=all loglvl_guest=all apic_verbosity=debug
dom0_mem=1024M vga=gfx-1280x1024x32 console_timestamps
console=vga,com1 com1=57600,8n1 iommu=1 dom0_max_vcpus=4
dom0_vcpus_pin=true sched=credit cpuidle=1 cpufreq=xen
clocksource=acpi numa=on
(XEN) Video information:
...
(XEN) [2010-06-03 01:07:46] allocated vector 31 for irq 21
(XEN) [2010-06-03 01:07:47] PCI add device 00:14.2
(XEN) [2010-06-03 01:07:47] PCI add device 04:00.0
(XEN) [2010-06-03 01:07:48] PCI add device 01:05.0
(XEN) [2010-06-03 01:09:00] cpupool_add_domain(dom=1,pool=0) n_dom 2
(XEN) [2010-06-03 01:09:20] mm.c:799:d1 Non-privileged (1) attempt to
map I/O space 000000f0
(XEN) [2010-06-03 01:31:34] cpupool_rm_domain(dom=1,pool=0) n_dom 1
(XEN) [2010-06-03 01:32:45] cpupool_add_domain(dom=2,pool=0) n_dom 2
(XEN) [2010-06-03 01:33:38] mm.c:799:d2 Non-privileged (2) attempt to
map I/O space 000000f0
(XEN) [2010-06-03 01:59:34] cpupool_rm_domain(dom=2,pool=0) n_dom 1
(XEN) [2010-06-03 02:33:34] cpupool_add_domain(dom=3,pool=0) n_dom 2
(XEN) [2010-06-03 02:35:38] cpupool_rm_domain(dom=3,pool=0) n_dom 1
(XEN) [2010-06-03 02:44:59] cpupool_add_domain(dom=4,pool=0) n_dom 2
(XEN) [2010-06-03 02:46:00] cpupool_rm_domain(dom=4,pool=0) n_dom 1
(XEN) [2010-06-03 02:46:14] cpupool_add_domain(dom=5,pool=0) n_dom 2
(XEN) [2010-06-03 02:50:37] cpupool_rm_domain(dom=5,pool=0) n_dom 1
(XEN) [2010-06-03 03:46:56] cpupool_add_domain(dom=6,pool=0) n_dom 2
(XEN) [2010-06-03 03:53:09] cpupool_rm_domain(dom=6,pool=0) n_dom 1
(XEN) [2010-06-03 04:27:59] cpupool_add_domain(dom=7,pool=0) n_dom 2
(XEN) [2010-06-03 04:29:24] cpupool_rm_domain(dom=7,pool=0) n_dom 1
(XEN) [2010-06-03 05:04:51] cpupool_add_domain(dom=8,pool=0) n_dom 2
(XEN) [2010-06-03 05:10:18] cpupool_rm_domain(dom=8,pool=0) n_dom 1
(XEN) [2010-06-03 05:10:27] cpupool_add_domain(dom=9,pool=0) n_dom 2
r...@server /root >
-------------------------------------------------------
not sure if those last few lines are suspicious, or not.
rather surprising how *little* info there is, or at least that i've
found, on non-Opensuse Guests on Opensuse Host :-/
hope to get this one working !
p.s. Unrelated, but worth mentioning -- at some point in the last few
weeks' (maybe longer) of system/kernel/xen upgrades, service "xend"
stopped launching on boot. a bit of digging about led me to an
apparently NEW requirement, the need for:
lsmod | grep evt
evtchn 38288 4
for whatever reason, not getting auto-added to initrd @ kernel upgrades/
adding that module to /etc/sysconfig/kernel cures the problem.
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
