Michael Cook
2010-Jun-06 19:52 UTC
[Xen-users] Hotplug scripts not working - Networking woes on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
Anyone can help me with this problem I''ve described here: https://bugzilla.novell.com/show_bug.cgi?id=612006 I''ve had XEN4.0 working on CentOS 5.4 platform without these problems. I''m trying to do the same now with a newer laptop and CentOS didn''t recognise half hte drivers. The latest opensuse 11.3 does have these drivers and specifically nouveau integration and XEN which has got me 98% of the way there... I''m presently stuck on the networking part which looks different/problematic compared my experience on CentOS machine. Now the VMs launch but I see various Hotplug scripts not working messages and the VM instantly stops running. Thanks in advance, Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Michael Cook
2010-Jun-06 21:34 UTC
Re: [Xen-users] Hotplug scripts not working - Networking woes on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
Thanks for the suggestion, I assume I should keep the br0/br1... but trying your
suggestion I still see the same error. If I comment out the vif in the HVM
config file, I get a similar error hotplug script but for the disk.
After mucking about with this some more I think the HVM should boot (and not
timeout) even if I have the wrong bridges/network scripts. I''m not at
the stage yet where I have no connectivity... the VM doesn''t''
stay up long enough because of these hotplugin script timeout/crash.
Hence my ramblings towards the end of the bug about finding postings on MAKEDEV
and missing /dev/ entries but haven''t managed to add these as MAKEDEV
doesn''t seem to exist on my vanilla installation and I''ve not
had to do this on say a Centos XEN environment but that doens''t work
for other reasons (hw support) on my newer laptop.
--- On Sun, 6/6/10, Mark Pryor <tlviewer@yahoo.com> wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes on
opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 5:04 PM
Mike,
In your Xen config: xend-config.sxp
try to comment out
#(network-script network-bridge)
and uncomment
(network-script network-dummy)
and restart xend.
once you have a manual bridge, there is no need for Xen''s
network-bridge script.
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com> wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: [Xen-users] Hotplug scripts not working - Networking woes on opensuse
11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Date: Sunday, June 6, 2010, 12:52 PM
Anyone can help me with this problem I''ve described here:
https://bugzilla.novell.com/show_bug.cgi?id=612006
I''ve had XEN4.0 working on CentOS 5.4 platform without these problems.
I''m trying to do the same now with a newer laptop and CentOS
didn''t recognise half hte drivers. The latest opensuse 11.3 does have
these drivers and specifically nouveau integration and XEN which has got me 98%
of the way there... I''m presently stuck on the networking part which
looks different/problematic compared my experience on CentOS machine.
Now the VMs launch but I see various Hotplug scripts not working messages and
the VM instantly stops running.
Thanks in advance,
Mike
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Michael Cook
2010-Jun-07 03:58 UTC
Re: [Xen-users] Hotplug scripts not working - Networking woes on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
Hi Mark,
Thanks for your help. I will try and provide you some info. Some background
first may help. But please let me know if there are other logs of interest.
I''ve tried many distributions from my original use of Centos5.3 with
XEN3.x. I have the following domUs which work well in CentOS but I now wanted to
move to a newer, faster host.
domUs: WinXP, Ubuntu 10.04 and RHEL5.3.
The first two are hvms, the second is a pvm, which I''ve not tried yet
and I really want the first two to work as WinXP cannot run as a PVM from what I
know.
I originally found Ubuntu 10.04 supported this W510 laptop pretty well although
they are busy writing driver fixes for USB and screen. Mostly NVIDIA and
Nouveau. Running dom0 Ubunut with NVIDIA or Nouveau doesn''t work well
at all. I think there is an mmap issue from what I''ve read about it,
circa March2010 there were hacks to get it work which have yet to appear within
the kernel drivers and manually trying to add these to the kernel from XEN git
for Ubuntu (Jeremys'') didn''t work.
Ubuntu 10.04 (2.6.32.x) came up nicely on bare-metal. I then thought/hoped I
could find a number of guides that would get me Ubuntu 10.04 dom0. This took
some work but there are a couple of guides to recompiling and installing with
XEN4.0 - then I got stuck with an earlier kernel which didn''t seem to
support any recent updates to W510 drivers (including wlan) and there was still
Nouveau bug fixes for the W510 chipset which to be honest I gave up on trying to
manually fix.
I also wasn''t happy with 800x600 resolution and finally found Opensuse
11.3 milestone 7 worked as Opensuse 11.2 is 2.6.31.x and nothing worked on the
W510. CentOS5.4 on the W510 was even worse and with limited interest &
support on CentOS I figured it would be a fair time until they support W510.
There is a wiki on the W510 which shows a lot of activity in Ubuntu to fix up
the drivers etc for W510 in Ubuntu 10.04. So I''m guessing by U10.10
things will be sorted but I doubt XEN will be well integrated... it seems
unlikely from all the forum readings I''ve found on the subject.
I''ve added my findings so far wrt XEN to this wiki which keeps track of
the major issues for W510 (mostly in Ubuntu distro)
http://www.thinkwiki.org/wiki/Category:W510
This brought me to opensuse which I dont know very well. The networking piece
is quite different to Ubuntu and even in Ubuntu their Network Manager drives me
nuts. Opensuse seem to have a Network Manager too through which I created br0
and br1 after reading the comment in the xend-config.sxp file saying
"Opensuse users should not configure anything here but use the YaST Network
configuration tool". So I''ve probably not set this up properly.
None the less I was surprised as you point out that br0 didn''t have an
IP addr and doesn''t seem able to be tied to the wlan0 interface
(operation not supported message).
Further more the basic network provisioning between eth0 and wlan0 seems awkward
and quirky as when eth0 is not connected it still gets an IP addr. Oddly, it
has not done this on this most recent bootup... eth0 is now provisioned but not
assigned an address. "Change Default Route via DHCP" has always been
set. So this is yet another puzzle with YaST Network Settings. Both br0 and
br1 (I tried to bridge one to eth0 and one to wlan0) are set to DHCP but only
one bridge manages to bridge to eth0. br1 doesn''t because
"operation not supported" (presumably from ethtool or mii) for the
wlan0 driver (new chipset support for this laptop?).
linux-oit2:/etc/xen # brctl show
bridge name bridge id STP enabled interfaces
br0 8000.00262dfac618 no eth0
br1 8000.000000000000 no
pan0 8000.000000000000 no
Anyway, I was expecting to see peth0 and xenbr0 and the scripts I''ve
run on centos5.3 which create these bridges to specific physical devices
doesn''t seem to work well at all.
Right now I dont know what to trust and obviously I''m using a
pre-release of Opensuse. I''m hoping its a simple case of
misprovisioning the native network settings along iwth the XEN installation.
I used the example HVM file with XEN4.0 virt-manager under /etc/xen//examples/
and simply updated the UUID, vif and harddrive image with that of these domUs.
I get the same behaviour in all of them... timeout with some hotplug script not
working.
So for the BIOS, yes, VT-d was disabled and xm info didn''t show any hvm
support. I enabled this in the W510 BIOS and then virt-manager would allow me
to create a new HVM based VM. However... it would then complain
"couldn''t find image" although it wouldn''t let me
(couldn''t find) a place to define the name of this image. I assume
only creating an image from CD has been tested, then it complained I had no CD
in the drive.
I can try creating a VM (para-virtual for example from scratch) but my hope was
to move these three VMs which are in themselves complete systems I dont realy
want to rebuild from scratch. I also have other RHEL5.3 VMs that cannot be
easily rebuilt.
Obviously I will try and create a new VM from scratch using the Virt-Manager
wizard.
During the opensuse installation I chose partition based disk-set which is
similar ot the Ubuntu installation. The CentOS one uses LVM but I dont think
this would make any difference to running these domUs. Eg config script which
works on CentOS dom0:
name = "WinXP_sp3"
uuid = "79178fd8-d542-4c76-36ec-4791e104aad9"
maxmem = 512
memory = 512
cpus = 1
builder = "hvm"
kernel = "/usr/lib/xen/boot/hvmloader"
boot = "c"
pae = 1
acpi = 1
apic = 1
localtime = 1
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
device_model = "/usr/lib64/xen/bin/qemu-dm"
usb = 1
usbdevice = "tablet"
sdl = 0
vnc = 1
vncunused = 1
keymap = "en-us"
disk = [ "file:/var/lib/libvirt/images/XP-Pro_sp3.img,hda,w" ]
vif = [ "mac=00:16:36:f7:27:39,bridge=xenbr0,script=vif-bridge" ]
parallel = "none"
serial = "pty"
I''d be very interested in working with you to figure out this mystery
as I feel I''m very close after a couple of weeks of pulling my hair out
over kernel support for the W510 and trying to work with XEN.
Ideally, I''d rather not use another distro like opensuse but it has
been the least painful way to at least get XEN & Linux & W510 working
together and fortunately the latest candidate release does do this in a pretty
stable environment. This final hurdle of hotplg scripts is hopefully not too
complicated to figure out.
lsmod, lspci and xm info follow....
linux-oit2:/etc/xen # xm info
host : linux-oit2
release : 2.6.34-8-xen
version : #1 SMP 2010-05-17 17:30:24 +0200
machine : x86_64
nr_cpus : 8
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 2
cpu_mhz : 1596
hw_caps :
bfebfbff:28100800:00000000:00001b40:0098e3fd:00000000:00000001:00000000
virt_caps : hvm hvm_directio
total_memory : 8088
free_memory : 149
free_cpus : 0
max_free_memory : 7495
max_para_memory : 7491
max_hvm_memory : 7465
node_to_cpu : node0:0-7
node_to_memory : node0:149
node_to_dma32_mem : node0:89
max_node_id : 0
xen_major : 4
xen_minor : 0
xen_extra : .0_21091_05-2.1
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : 21091
xen_commandline : vgamode=0x314 iommu=1
cc_compiler : gcc version 4.5.0 20100420 [gcc-4_5-branch revision
158562] (SU
cc_compile_by : abuild
cc_compile_domain :
cc_compile_date : Wed May 19 19:06:40 UTC 2010
xend_config_format : 4
linux-oit2:/etc/xen # lsmod
Module Size Used by
usbbk 23911 0
gntdev 8579 0
netbk 41281 0 [permanent]
rfcomm 81560 4
blkbk 28782 0 [permanent]
blkback_pagemap 2806 1 blkbk
snd_pcm_oss 53455 0
blktap 126702 2 [permanent]
snd_mixer_oss 18817 1 snd_pcm_oss
sco 20103 2
domctl 3227 2 blkbk,blktap
bnep 18047 2
xenbus_be 3706 4 usbbk,netbk,blkbk,blktap
snd_seq 67923 0
snd_seq_device 7834 1 snd_seq
l2cap 62034 16 rfcomm,bnep
edd 10176 0
bridge 85815 3
stp 2331 1 bridge
llc 6103 2 bridge,stp
nouveau 552206 2
ttm 68464 1 nouveau
drm_kms_helper 33008 1 nouveau
drm 220232 4 nouveau,ttm,drm_kms_helper
agpgart 42953 2 ttm,drm
i2c_algo_bit 6696 1 nouveau
af_packet 23133 8
fuse 77053 3
loop 18239 0
dm_mod 86435 0
snd_hda_codec_nvhdmi 15727 4
arc4 1601 2
firewire_ohci 26970 0
ecb 2495 2
firewire_core 61402 1 firewire_ohci
snd_hda_intel 29133 2
crc_itu_t 1747 1 firewire_core
snd_hda_codec 112731 2 snd_hda_codec_nvhdmi,snd_hda_intel
iwlagn 238807 0
uvcvideo 67755 0
iwlcore 299287 1 iwlagn
sdhci_pci 8668 0
snd_hwdep 7708 1 snd_hda_codec
iTCO_wdt 12406 0
mac80211 283755 2 iwlagn,iwlcore
ohci1394 33510 0
videodev 43764 1 uvcvideo
v4l1_compat 16833 2 uvcvideo,videodev
8250_pci 25671 0
snd_pcm 107675 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
btusb 18511 2
sdhci 23126 1 sdhci_pci
v4l2_compat_ioctl32 11225 1 videodev
8250 31155 1 8250_pci
video 25192 0
snd_timer 27486 2 snd_seq,snd_pcm
sr_mod 16396 0
e1000e 152237 0
bluetooth 108637 9 rfcomm,sco,bnep,l2cap,btusb
sg 32951 0
mmc_core 83419 1 sdhci
iTCO_vendor_support 3150 1 iTCO_wdt
pcspkr 2222 0
tpm_tis 13134 0
thinkpad_acpi 83412 0
xhci_hcd 98228 0
cfg80211 182345 3 iwlagn,iwlcore,mac80211
i2c_i801 11881 0
ieee1394 104278 1 ohci1394
i2c_core 32104 6
nouveau,drm_kms_helper,drm,i2c_algo_bit,videodev,i2c_i801
serial_core 25223 1 8250
output 2727 1 video
tpm 17388 1 tpm_tis
rfkill 21959 4 bluetooth,thinkpad_acpi,cfg80211
snd 83486 15
snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_codec_nvhdmi,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer,thinkpad_acpi
snd_page_alloc 9473 2 snd_hda_intel,snd_pcm
wmi 8750 0
battery 12270 0
soundcore 8757 1 snd
ac 4023 0
tpm_bios 6652 1 tpm
button 6925 1 nouveau
joydev 12230 0
ext4 395274 1
jbd2 98208 1 ext4
crc16 1715 2 l2cap,ext4
sd_mod 41170 3
ehci_hcd 60206 0
usbcore 233034 6 usbbk,uvcvideo,btusb,xhci_hcd,ehci_hcd
xenblk 26162 0
cdrom 43083 2 sr_mod,xenblk
xennet 37763 0
fan 4527 0
processor 42918 0
ahci 42648 2
libata 211362 1 ahci
scsi_mod 191176 4 sr_mod,sg,sd_mod,libata
thermal 20593 0
thermal_sys 18006 4 video,fan,processor,thermal
hwmon 2712 2 thinkpad_acpi,thermal_sys
linux-oit2:/etc/xen # lspci
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1
(rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System Management
Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and
Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System Control and
Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous
Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and
Protocol Registers (rev 11)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset
HECI Controller (rev 06)
00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series Chipset KT
Controller (rev 06)
00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network
Connection (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2
Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High
Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express
Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express
Root Port 2 (rev 06)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express
Root Port 4 (rev 06)
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express
Root Port 5 (rev 06)
00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express
Root Port 7 (rev 06)
00:1c.7 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express
Root Port 8 (rev 06)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2
Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface
Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port
SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller
(rev 06)
01:00.0 VGA compatible controller: nVidia Corporation GT216 [Quadro FX 880M]
(rev a2)
01:00.1 Audio device: nVidia Corporation High Definition Audio Controller (rev
a1)
03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 35)
0d:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01)
0d:00.1 System peripheral: Ricoh Co Ltd Device e230 (rev 01)
0f:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev
03)
17:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01)
17:00.3 FireWire (IEEE 1394): Ricoh Co Ltd Device e832 (rev 01)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture
Generic Non-Core Registers (rev 04)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture
System Address Decoder (rev 04)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 04)
ff:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller (rev 04)
ff:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Target Address Decoder (rev 04)
ff:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Test Registers (rev 04)
ff:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Control Registers (rev 04)
ff:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Address Registers (rev 04)
ff:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Rank Registers (rev 04)
ff:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Thermal Control Registers (rev 04)
ff:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Control Registers (rev 04)
ff:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Address Registers (rev 04)
ff:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Rank Registers (rev 04)
ff:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Thermal Control Registers (rev 04)
--- On Sun, 6/6/10, Mark Pryor <tlviewer@yahoo.com> wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes on
opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 9:48 PM
Mike,
Let me give you a broad checklist of things that may be important.
I just did a search of the lists.xensource.com/xen-users list and there are no
posts about
your hardware.
The Thinkpad w510 Notebook.
------------
many times a notebook like this will have a stealth bios, or a limited bios.
Are you
sure that HVM is enabled?
Your choice of suse 11.3 is good and should make it much easier to get Xen 4.0
working. I like the way your Network looks, but I didn''t see any IP
address for your
br0- why not? This should work with a non-xen kernel too.
Your first domU is Winxp sp3. This might be a problem if your HD needs AHCI or
strange raid/SATA drivers not included with Winxp.
I think a better domU would be the same source you used for dom0. This should
work PV and won''t depend if your bios
supports HVM.
Oh, can you post your
#xm info
#lsmod
#lspci
for dom0
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com> wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes on
opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: "Mark Pryor" <tlviewer@yahoo.com>
Date: Sunday, June 6, 2010, 3:40 PM
Yes, I tried this, and
hte same error. I then removed the vif altogether and the similiar hotplugin
error appeared for the harddrive. Following that, found the MAKEDEV issue but
I''m not sure what needs to be done there.
--- On Sun, 6/6/10, Mark Pryor <tlviewer@yahoo.com> wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes on
opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 5:57 PM
Mike,
Manual bridge is br0/br1.
In your HVM guest config, you should
have
vif = [ ''bridge=br0'' ]
if you put xenbr0 above that would explain the problem too.
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com> wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes on
opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Date: Sunday, June 6, 2010, 2:34 PM
Thanks for the suggestion,
I assume I should keep the br0/br1... but trying your suggestion I still see
the same error. If I comment out the vif in the HVM config file, I get a
similar error hotplug script
but for the disk.
After mucking about with this some more I think the HVM should boot (and not
timeout) even if I have the wrong bridges/network scripts. I''m not at
the stage yet where I have no connectivity... the VM doesn''t''
stay up long enough because of these hotplugin script timeout/crash.
Hence my ramblings towards the end of the bug about finding postings on MAKEDEV
and missing /dev/ entries but haven''t managed to add these as MAKEDEV
doesn''t seem to exist on my vanilla installation and I''ve not
had to do this on say a Centos XEN environment but that doens''t work
for other reasons (hw support) on my newer laptop.
--- On Sun, 6/6/10, Mark Pryor <tlviewer@yahoo.com> wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes on
opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 5:04 PM
Mike,
In your Xen config: xend-config.sxp
try to comment out
#(network-script network-bridge)
and uncomment
(network-script
network-dummy)
and restart xend.
once you have a manual bridge, there is no need for Xen''s
network-bridge script.
--
Mark
--- On Sun, 6/6/10, Michael Cook
<michaelcook_mjc@yahoo.com> wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: [Xen-users] Hotplug scripts not working - Networking woes on opensuse
11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Date: Sunday, June 6, 2010, 12:52 PM
Anyone can help me with this problem I''ve described here:
https://bugzilla.novell.com/show_bug.cgi?id=612006
I''ve had XEN4.0 working on CentOS 5.4 platform without these problems.
I''m trying to do the same now with a newer
laptop and CentOS didn''t recognise half hte drivers. The latest
opensuse 11.3 does have these drivers and specifically nouveau integration and
XEN which has got me 98% of the way
there... I''m presently stuck on the networking part which looks
different/problematic compared my experience on CentOS machine.
Now the VMs launch but I see various Hotplug scripts not working messages and
the VM instantly stops running.
Thanks in advance,
Mike
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Helmut Wieser
2010-Jun-08 09:15 UTC
Re: [Xen-users] Hotplug scripts not working - Networking woes on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
Does it not even come up after you rebooted the dom0? Because that''s the issue I experienced. At first I thougt it was different module load order, or different kernel parameters, but in the end it turned out that a dom0 reboot is required to "fix" the hotplug scripts not working issue. Some people say that downgrading udev to <= 151 works for them. Unfortunately I''m not one of them. Can you verify that? regards, Helmut On 07.06.2010 05:58, Michael Cook wrote:> Hi Mark, > > Thanks for your help. I will try and provide you some info. Some > background first may help. But please let me know if there are other > logs of interest. > > I''ve tried many distributions from my original use of Centos5.3 with > XEN3.x. I have the following domUs which work well in CentOS but I now > wanted to move to a newer, faster host. > > domUs: WinXP, Ubuntu 10.04 and RHEL5.3. > > The first two are hvms, the second is a pvm, which I''ve not tried yet > and I really want the first two to work as WinXP cannot run as a PVM > from what I know. > > I originally found Ubuntu 10.04 supported this W510 laptop pretty well > although they are busy writing driver fixes for USB and screen. > Mostly NVIDIA and Nouveau. Running dom0 Ubunut with NVIDIA or Nouveau > doesn''t work well at all. I think there is an mmap issue from what > I''ve read about it, circa March2010 there were hacks to get it work > which have yet to appear within the kernel drivers and manually trying > to add these to the kernel from XEN git for Ubuntu (Jeremys'') didn''t work. > > Ubuntu 10.04 (2.6.32.x) came up nicely on bare-metal. I then > thought/hoped I could find a number of guides that would get me Ubuntu > 10.04 dom0. This took some work but there are a couple of guides to > recompiling and installing with XEN4.0 - then I got stuck with an > earlier kernel which didn''t seem to support any recent updates to W510 > drivers (including wlan) and there was still Nouveau bug fixes for the > W510 chipset which to be honest I gave up on trying to manually fix. > > I also wasn''t happy with 800x600 resolution and finally found Opensuse > 11.3 milestone 7 worked as Opensuse 11.2 is 2.6.31.x and nothing > worked on the W510. CentOS5.4 on the W510 was even worse and with > limited interest & support on CentOS I figured it would be a fair time > until they support W510. > > There is a wiki on the W510 which shows a lot of activity in Ubuntu to > fix up the drivers etc for W510 in Ubuntu 10.04. So I''m guessing by > U10.10 things will be sorted but I doubt XEN will be well > integrated... it seems unlikely from all the forum readings I''ve found > on the subject. I''ve added my findings so far wrt XEN to this wiki > which keeps track of the major issues for W510 (mostly in Ubuntu distro) > > http://www.thinkwiki.org/wiki/Category:W510 > > This brought me to opensuse which I dont know very well. The > networking piece is quite different to Ubuntu and even in Ubuntu their > Network Manager drives me nuts. Opensuse seem to have a Network > Manager too through which I created br0 and br1 after reading the > comment in the xend-config.sxp file saying "Opensuse users should not > configure anything here but use the YaST Network configuration tool". > So I''ve probably not set this up properly. > > None the less I was surprised as you point out that br0 didn''t have an > IP addr and doesn''t seem able to be tied to the wlan0 interface > (operation not supported message). > > Further more the basic network provisioning between eth0 and wlan0 > seems awkward and quirky as when eth0 is not connected it still gets > an IP addr. Oddly, it has not done this on this most recent bootup... > eth0 is now provisioned but not assigned an address. "Change Default > Route via DHCP" has always been set. So this is yet another puzzle > with YaST Network Settings. Both br0 and br1 (I tried to bridge one > to eth0 and one to wlan0) are set to DHCP but only one bridge manages > to bridge to eth0. br1 doesn''t because "operation not supported" > (presumably from ethtool or mii) for the wlan0 driver (new chipset > support for this laptop?). > > linux-oit2:/etc/xen # brctl show > bridge name bridge id STP enabled interfaces > br0 8000.00262dfac618 no eth0 > br1 8000.000000000000 no > pan0 8000.000000000000 no > > > Anyway, I was expecting to see peth0 and xenbr0 and the scripts I''ve > run on centos5.3 which create these bridges to specific physical > devices doesn''t seem to work well at all. > > Right now I dont know what to trust and obviously I''m using a > pre-release of Opensuse. I''m hoping its a simple case of > misprovisioning the native network settings along iwth the XEN > installation. > > I used the example HVM file with XEN4.0 virt-manager under > /etc/xen//examples/ and simply updated the UUID, vif and harddrive > image with that of these domUs. I get the same behaviour in all of > them... timeout with some hotplug script not working. > > So for the BIOS, yes, VT-d was disabled and xm info didn''t show any > hvm support. I enabled this in the W510 BIOS and then virt-manager > would allow me to create a new HVM based VM. However... it would then > complain "couldn''t find image" although it wouldn''t let me (couldn''t > find) a place to define the name of this image. I assume only > creating an image from CD has been tested, then it complained I had no > CD in the drive. > > I can try creating a VM (para-virtual for example from scratch) but my > hope was to move these three VMs which are in themselves complete > systems I dont realy want to rebuild from scratch. I also have other > RHEL5.3 VMs that cannot be easily rebuilt. > > Obviously I will try and create a new VM from scratch using the > Virt-Manager wizard. > > During the opensuse installation I chose partition based disk-set > which is similar ot the Ubuntu installation. The CentOS one uses LVM > but I dont think this would make any difference to running these > domUs. Eg config script which works on CentOS dom0: > > name = "WinXP_sp3" > uuid = "79178fd8-d542-4c76-36ec-4791e104aad9" > maxmem = 512 > memory = 512 > cpus = 1 > builder = "hvm" > kernel = "/usr/lib/xen/boot/hvmloader" > boot = "c" > pae = 1 > acpi = 1 > apic = 1 > localtime = 1 > on_poweroff = "destroy" > on_reboot = "restart" > on_crash = "restart" > device_model = "/usr/lib64/xen/bin/qemu-dm" > usb = 1 > usbdevice = "tablet" > sdl = 0 > vnc = 1 > vncunused = 1 > keymap = "en-us" > disk = [ "file:/var/lib/libvirt/images/XP-Pro_sp3.img,hda,w" ] > vif = [ "mac=00:16:36:f7:27:39,bridge=xenbr0,script=vif-bridge" ] > parallel = "none" > serial = "pty" > > I''d be very interested in working with you to figure out this mystery > as I feel I''m very close after a couple of weeks of pulling my hair > out over kernel support for the W510 and trying to work with XEN. > > Ideally, I''d rather not use another distro like opensuse but it has > been the least painful way to at least get XEN & Linux & W510 working > together and fortunately the latest candidate release does do this in > a pretty stable environment. This final hurdle of hotplg scripts is > hopefully not too complicated to figure out. > > lsmod, lspci and xm info follow.... > > linux-oit2:/etc/xen # xm info > host : linux-oit2 > release : 2.6.34-8-xen > version : #1 SMP 2010-05-17 17:30:24 +0200 > machine : x86_64 > nr_cpus : 8 > nr_nodes : 1 > cores_per_socket : 4 > threads_per_core : 2 > cpu_mhz : 1596 > hw_caps : > bfebfbff:28100800:00000000:00001b40:0098e3fd:00000000:00000001:00000000 > virt_caps : hvm hvm_directio > total_memory : 8088 > free_memory : 149 > free_cpus : 0 > max_free_memory : 7495 > max_para_memory : 7491 > max_hvm_memory : 7465 > node_to_cpu : node0:0-7 > node_to_memory : node0:149 > node_to_dma32_mem : node0:89 > max_node_id : 0 > xen_major : 4 > xen_minor : 0 > xen_extra : .0_21091_05-2.1 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : 21091 > xen_commandline : vgamode=0x314 iommu=1 > cc_compiler : gcc version 4.5.0 20100420 [gcc-4_5-branch > revision 158562] (SU > cc_compile_by : abuild > cc_compile_domain : > cc_compile_date : Wed May 19 19:06:40 UTC 2010 > xend_config_format : 4 > > > linux-oit2:/etc/xen # lsmod > Module Size Used by > usbbk 23911 0 > gntdev 8579 0 > netbk 41281 0 [permanent] > rfcomm 81560 4 > blkbk 28782 0 [permanent] > blkback_pagemap 2806 1 blkbk > snd_pcm_oss 53455 0 > blktap 126702 2 [permanent] > snd_mixer_oss 18817 1 snd_pcm_oss > sco 20103 2 > domctl 3227 2 blkbk,blktap > bnep 18047 2 > xenbus_be 3706 4 usbbk,netbk,blkbk,blktap > snd_seq 67923 0 > snd_seq_device 7834 1 snd_seq > l2cap 62034 16 rfcomm,bnep > edd 10176 0 > bridge 85815 3 > stp 2331 1 bridge > llc 6103 2 bridge,stp > nouveau 552206 2 > ttm 68464 1 nouveau > drm_kms_helper 33008 1 nouveau > drm 220232 4 nouveau,ttm,drm_kms_helper > agpgart 42953 2 ttm,drm > i2c_algo_bit 6696 1 nouveau > af_packet 23133 8 > fuse 77053 3 > loop 18239 0 > dm_mod 86435 0 > snd_hda_codec_nvhdmi 15727 4 > arc4 1601 2 > firewire_ohci 26970 0 > ecb 2495 2 > firewire_core 61402 1 firewire_ohci > snd_hda_intel 29133 2 > crc_itu_t 1747 1 firewire_core > snd_hda_codec 112731 2 snd_hda_codec_nvhdmi,snd_hda_intel > iwlagn 238807 0 > uvcvideo 67755 0 > iwlcore 299287 1 iwlagn > sdhci_pci 8668 0 > snd_hwdep 7708 1 snd_hda_codec > iTCO_wdt 12406 0 > mac80211 283755 2 iwlagn,iwlcore > ohci1394 33510 0 > videodev 43764 1 uvcvideo > v4l1_compat 16833 2 uvcvideo,videodev > 8250_pci 25671 0 > snd_pcm 107675 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec > btusb 18511 2 > sdhci 23126 1 sdhci_pci > v4l2_compat_ioctl32 11225 1 videodev > 8250 31155 1 8250_pci > video 25192 0 > snd_timer 27486 2 snd_seq,snd_pcm > sr_mod 16396 0 > e1000e 152237 0 > bluetooth 108637 9 rfcomm,sco,bnep,l2cap,btusb > sg 32951 0 > mmc_core 83419 1 sdhci > iTCO_vendor_support 3150 1 iTCO_wdt > pcspkr 2222 0 > tpm_tis 13134 0 > thinkpad_acpi 83412 0 > xhci_hcd 98228 0 > cfg80211 182345 3 iwlagn,iwlcore,mac80211 > i2c_i801 11881 0 > ieee1394 104278 1 ohci1394 > i2c_core 32104 6 > nouveau,drm_kms_helper,drm,i2c_algo_bit,videodev,i2c_i801 > serial_core 25223 1 8250 > output 2727 1 video > tpm 17388 1 tpm_tis > rfkill 21959 4 bluetooth,thinkpad_acpi,cfg80211 > snd 83486 15 > snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_codec_nvhdmi,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer,thinkpad_acpi > snd_page_alloc 9473 2 snd_hda_intel,snd_pcm > wmi 8750 0 > battery 12270 0 > soundcore 8757 1 snd > ac 4023 0 > tpm_bios 6652 1 tpm > button 6925 1 nouveau > joydev 12230 0 > ext4 395274 1 > jbd2 98208 1 ext4 > crc16 1715 2 l2cap,ext4 > sd_mod 41170 3 > ehci_hcd 60206 0 > usbcore 233034 6 usbbk,uvcvideo,btusb,xhci_hcd,ehci_hcd > xenblk 26162 0 > cdrom 43083 2 sr_mod,xenblk > xennet 37763 0 > fan 4527 0 > processor 42918 0 > ahci 42648 2 > libata 211362 1 ahci > scsi_mod 191176 4 sr_mod,sg,sd_mod,libata > thermal 20593 0 > thermal_sys 18006 4 video,fan,processor,thermal > hwmon 2712 2 thinkpad_acpi,thermal_sys > > > linux-oit2:/etc/xen # lspci > 00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11) > 00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root > Port 1 (rev 11) > 00:08.0 System peripheral: Intel Corporation Core Processor System > Management Registers (rev 11) > 00:08.1 System peripheral: Intel Corporation Core Processor Semaphore > and Scratchpad Registers (rev 11) > 00:08.2 System peripheral: Intel Corporation Core Processor System > Control and Status Registers (rev 11) > 00:08.3 System peripheral: Intel Corporation Core Processor > Miscellaneous Registers (rev 11) > 00:10.0 System peripheral: Intel Corporation Core Processor QPI Link > (rev 11) > 00:10.1 System peripheral: Intel Corporation Core Processor QPI > Routing and Protocol Registers (rev 11) > 00:16.0 Communication controller: Intel Corporation 5 Series/3400 > Series Chipset HECI Controller (rev 06) > 00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series > Chipset KT Controller (rev 06) > 00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network > Connection (rev 06) > 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset > USB2 Enhanced Host Controller (rev 06) > 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset > High Definition Audio (rev 06) > 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI > Express Root Port 1 (rev 06) > 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI > Express Root Port 2 (rev 06) > 00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI > Express Root Port 4 (rev 06) > 00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI > Express Root Port 5 (rev 06) > 00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI > Express Root Port 7 (rev 06) > 00:1c.7 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI > Express Root Port 8 (rev 06) > 00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset > USB2 Enhanced Host Controller (rev 06) > 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6) > 00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC > Interface Controller (rev 06) > 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series > Chipset 6 port SATA AHCI Controller (rev 06) > 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus > Controller (rev 06) > 01:00.0 VGA compatible controller: nVidia Corporation GT216 [Quadro FX > 880M] (rev a2) > 01:00.1 Audio device: nVidia Corporation High Definition Audio > Controller (rev a1) > 03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 > (rev 35) > 0d:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01) > 0d:00.1 System peripheral: Ricoh Co Ltd Device e230 (rev 01) > 0f:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host > Controller (rev 03) > 17:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01) > 17:00.3 FireWire (IEEE 1394): Ricoh Co Ltd Device e832 (rev 01) > ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath > Architecture Generic Non-Core Registers (rev 04) > ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath > Architecture System Address Decoder (rev 04) > ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04) > ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 > (rev 04) > ff:03.0 Host bridge: Intel Corporation Core Processor Integrated > Memory Controller (rev 04) > ff:03.1 Host bridge: Intel Corporation Core Processor Integrated > Memory Controller Target Address Decoder (rev 04) > ff:03.4 Host bridge: Intel Corporation Core Processor Integrated > Memory Controller Test Registers (rev 04) > ff:04.0 Host bridge: Intel Corporation Core Processor Integrated > Memory Controller Channel 0 Control Registers (rev 04) > ff:04.1 Host bridge: Intel Corporation Core Processor Integrated > Memory Controller Channel 0 Address Registers (rev 04) > ff:04.2 Host bridge: Intel Corporation Core Processor Integrated > Memory Controller Channel 0 Rank Registers (rev 04) > ff:04.3 Host bridge: Intel Corporation Core Processor Integrated > Memory Controller Channel 0 Thermal Control Registers (rev 04) > ff:05.0 Host bridge: Intel Corporation Core Processor Integrated > Memory Controller Channel 1 Control Registers (rev 04) > ff:05.1 Host bridge: Intel Corporation Core Processor Integrated > Memory Controller Channel 1 Address Registers (rev 04) > ff:05.2 Host bridge: Intel Corporation Core Processor Integrated > Memory Controller Channel 1 Rank Registers (rev 04) > ff:05.3 Host bridge: Intel Corporation Core Processor Integrated > Memory Controller Channel 1 Thermal Control Registers (rev 04) > > > > > > --- On *Sun, 6/6/10, Mark Pryor /<tlviewer@yahoo.com>/* wrote: > > > From: Mark Pryor <tlviewer@yahoo.com> > Subject: Re: [Xen-users] Hotplug scripts not working - Networking > woes on opensuse 11.3 m7 with XEN4 on W510 Thinkpad > To: michael@dtmc.ca > Received: Sunday, June 6, 2010, 9:48 PM > > Mike, > > Let me give you a broad checklist of things that may be important. > > I just did a search of the lists.xensource.com/xen-users list and > there are no posts about > your hardware. > > The Thinkpad w510 Notebook. > ------------ > many times a notebook like this will have a stealth bios, or a > limited bios. Are you > sure that HVM is enabled? > > Your choice of suse 11.3 is good and should make it much easier to > get Xen 4.0 working. I like the way your Network looks, but I > didn''t see any IP address for your > br0- why not? This should work with a non-xen kernel too. > > Your first domU is Winxp sp3. This might be a problem if your HD > needs AHCI or strange raid/SATA drivers not included with Winxp. > > I think a better domU would be the same source you used for dom0. > This should work PV and won''t depend if your bios supports HVM. > > Oh, can you post your > #xm info > > #lsmod > > #lspci > > for dom0 > > -- > Mark > > > > --- On *Sun, 6/6/10, Michael Cook /<michaelcook_mjc@yahoo.com>/* > wrote: > > > From: Michael Cook <michaelcook_mjc@yahoo.com> > Subject: Re: [Xen-users] Hotplug scripts not working - > Networking woes on opensuse 11.3 m7 with XEN4 on W510 Thinkpad > To: "Mark Pryor" <tlviewer@yahoo.com> > Date: Sunday, June 6, 2010, 3:40 PM > > Yes, I tried this, and hte same error. I then removed the vif > altogether and the similiar hotplugin error appeared for the > harddrive. Following that, found the MAKEDEV issue but I''m > not sure what needs to be done there. > > > --- On *Sun, 6/6/10, Mark Pryor /<tlviewer@yahoo.com>/* wrote: > > > From: Mark Pryor <tlviewer@yahoo.com> > Subject: Re: [Xen-users] Hotplug scripts not working - > Networking woes on opensuse 11.3 m7 with XEN4 on W510 Thinkpad > To: michael@dtmc.ca > Received: Sunday, June 6, 2010, 5:57 PM > > Mike, > > Manual bridge is br0/br1. > > In your HVM guest config, you should have > vif = [ ''bridge=br0'' ] > > if you put xenbr0 above that would explain the problem too. > > -- > Mark > > --- On *Sun, 6/6/10, Michael Cook > /<michaelcook_mjc@yahoo.com>/* wrote: > > > From: Michael Cook <michaelcook_mjc@yahoo.com> > Subject: Re: [Xen-users] Hotplug scripts not working - > Networking woes on opensuse 11.3 m7 with XEN4 on W510 > Thinkpad > To: xen-users@lists.xensource.com > Date: Sunday, June 6, 2010, 2:34 PM > > Thanks for the suggestion, I assume I should keep the > br0/br1... but trying your suggestion I still see the > same error. If I comment out the vif in the HVM > config file, I get a similar error hotplug script but > for the disk. > > After mucking about with this some more I think the > HVM should boot (and not timeout) even if I have the > wrong bridges/network scripts. I''m not at the stage > yet where I have no connectivity... the VM doesn''t'' > stay up long enough because of these hotplugin script > timeout/crash. > > Hence my ramblings towards the end of the bug about > finding postings on MAKEDEV and missing /dev/ entries > but haven''t managed to add these as MAKEDEV doesn''t > seem to exist on my vanilla installation and I''ve not > had to do this on say a Centos XEN environment but > that doens''t work for other reasons (hw support) on my > newer laptop. > > --- On *Sun, 6/6/10, Mark Pryor > /<tlviewer@yahoo.com>/* wrote: > > > From: Mark Pryor <tlviewer@yahoo.com> > Subject: Re: [Xen-users] Hotplug scripts not > working - Networking woes on opensuse 11.3 m7 with > XEN4 on W510 Thinkpad > To: michael@dtmc.ca > Received: Sunday, June 6, 2010, 5:04 PM > > Mike, > > In your Xen config: xend-config.sxp > try to comment out > #(network-script network-bridge) > > and uncomment > (network-script network-dummy) > > and restart xend. > once you have a manual bridge, there is no need > for Xen''s > network-bridge script. > > -- > Mark > > --- On *Sun, 6/6/10, Michael Cook > /<michaelcook_mjc@yahoo.com>/* wrote: > > > From: Michael Cook <michaelcook_mjc@yahoo.com> > Subject: [Xen-users] Hotplug scripts not > working - Networking woes on opensuse 11.3 m7 > with XEN4 on W510 Thinkpad > To: xen-users@lists.xensource.com > Date: Sunday, June 6, 2010, 12:52 PM > > Anyone can help me with this problem I''ve > described here: > > https://bugzilla.novell.com/show_bug.cgi?id=612006 > > I''ve had XEN4.0 working on CentOS 5.4 platform > without these problems. I''m trying to do the > same now with a newer laptop and CentOS didn''t > recognise half hte drivers. The latest > opensuse 11.3 does have these drivers and > specifically nouveau integration and XEN which > has got me 98% of the way there... I''m > presently stuck on the networking part which > looks different/problematic compared my > experience on CentOS machine. > > Now the VMs launch but I see various Hotplug > scripts not working messages and the VM > instantly stops running. > > Thanks in advance, > Mike > > > > -----Inline Attachment Follows----- > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > > > > -----Inline Attachment Follows----- > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Michael Cook
2010-Jun-08 12:22 UTC
Re: [Xen-users] Hotplug scripts not working - Networking woes on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
Does what not come up? The dom0 comes up everytime but the domUs start up and
then timeout, in a paused state, with hotplug scripts not working error every
time. Its very reproducable.
Was there any substance to the MAKEDEV posting circa 2006 as there are no vnd*
devices present for the psudeo-virtual-disks. I tried this (as per opensuse bug
comment I added yesterday) and MAKEDEV pumped out a bunch of errors. To be
honest I do not know what I''m doing, other than surfing for
workarounds/solutions. Hopefully someone on this list is more experienced.
Perhaps a XEN4.0 vs XEN3.x issue? Just guessing but all of this works fine on
XEN3.x on a CentOS 5.4 machine... but CentOS5.4 has no support for my latest
laptop.
I may try the udev downgrade. Do you have any suggestions on how to do
this, is it a package downgrade or do I need to recompile the kernel.
(I''m trying to avoid recompiling/manually compiling stuff as I dont
want to diverge from maintained releases ideally).
Thx,
Mike.
--- On Tue, 6/8/10, Helmut Wieser <helmut.wieser@ieee.org> wrote:
From: Helmut Wieser <helmut.wieser@ieee.org>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes on
opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Received: Tuesday, June 8, 2010, 5:15 AM
Does it not even come up after you rebooted the dom0? Because that''s
the issue I experienced.
At first I thougt it was different module load order, or different
kernel parameters, but in the end it turned out that a dom0 reboot is
required to "fix" the hotplug scripts not working issue. Some people
say that downgrading udev to <= 151 works for them. Unfortunately
I''m not one of them.
Can you verify that?
regards,
Helmut
On 07.06.2010 05:58, Michael Cook wrote:
Hi Mark,
Thanks for your help. I will try and provide you some info. Some
background first may help. But please let me know if there are other
logs of interest.
I''ve tried many distributions from my original use of Centos5.3 with
XEN3.x. I have the following domUs which work well in CentOS but I now
wanted to move to a newer, faster host.
domUs: WinXP, Ubuntu 10.04 and RHEL5.3.
The first two are hvms, the second is a pvm, which I''ve not tried yet
and I really want the first two to work as WinXP cannot run as a PVM
from what I know.
I originally found Ubuntu 10.04 supported this W510 laptop pretty well
although they are busy writing driver fixes for USB and screen. Mostly
NVIDIA and Nouveau. Running dom0 Ubunut with NVIDIA or Nouveau doesn''t
work well at all. I think there is an mmap issue from what I''ve read
about it, circa March2010 there were hacks to get it work which have
yet to appear within the kernel drivers and manually trying to add
these to the kernel from XEN git for Ubuntu (Jeremys'') didn''t
work.
Ubuntu 10.04 (2.6.32.x) came up nicely on bare-metal. I then
thought/hoped I could find a number of guides that would get me Ubuntu
10.04 dom0. This took some work but there are a couple of guides to
recompiling and installing with XEN4.0 - then I got stuck with an
earlier kernel which didn''t seem to support any recent updates to W510
drivers (including wlan) and there was still Nouveau bug fixes for the
W510 chipset which to be honest I gave up on trying to manually fix.
I also wasn''t happy with 800x600 resolution and finally found Opensuse
11.3 milestone 7 worked as Opensuse 11.2 is 2.6.31.x and nothing worked
on the W510. CentOS5.4 on the W510 was even worse and with limited
interest & support on CentOS I figured it would be a fair time
until they support W510.
There is a wiki on the W510 which shows a lot of activity in Ubuntu to
fix up the drivers etc for W510 in Ubuntu 10.04. So I''m guessing by
U10.10 things will be sorted but I doubt XEN will be well integrated...
it seems unlikely from all the forum readings I''ve found on the
subject. I''ve added my findings so far wrt XEN to this wiki which
keeps track of the major issues for W510 (mostly in Ubuntu distro)
http://www.thinkwiki.org/wiki/Category:W510
This brought me to opensuse which I dont know very well. The
networking piece is quite different to Ubuntu and even in Ubuntu their
Network Manager drives me nuts. Opensuse seem to have a Network
Manager too through which I created br0 and br1 after reading the
comment in the xend-config.sxp file saying "Opensuse users should not
configure anything here but use the YaST Network configuration tool".
So I''ve probably not set this up properly.
None the less I was surprised as you point out that br0 didn''t have an
IP addr and doesn''t seem able to be tied to the wlan0 interface
(operation not supported message).
Further more the basic network provisioning between eth0 and wlan0
seems awkward and quirky as when eth0 is not connected it still gets an
IP addr. Oddly, it has not done this on this most recent bootup...
eth0 is now provisioned but not assigned an address. "Change Default
Route via DHCP" has always been set. So this is yet another puzzle
with YaST Network Settings. Both br0 and br1 (I tried to bridge one to
eth0 and one to wlan0) are set to DHCP but only one bridge manages to
bridge to eth0. br1 doesn''t because "operation not
supported"
(presumably from ethtool or mii) for the wlan0 driver (new chipset
support for this laptop?).
linux-oit2:/etc/xen # brctl show
bridge name bridge id STP enabled interfaces
br0 8000.00262dfac618 no eth0
br1 8000.000000000000 no
pan0 8000.000000000000 no
Anyway, I was expecting to see peth0 and xenbr0 and the scripts I''ve
run on centos5.3 which create these bridges to specific physical
devices doesn''t seem to work well at all.
Right now I dont know what to trust and obviously I''m using a
pre-release of Opensuse. I''m hoping its a simple case of
misprovisioning the native network settings along iwth the XEN
installation.
I used the example HVM file with XEN4.0 virt-manager under
/etc/xen//examples/ and simply updated the UUID, vif and harddrive
image with that of these domUs. I get the same behaviour in all of
them... timeout with some hotplug script not working.
So for the BIOS, yes, VT-d was disabled and xm info didn''t show any hvm
support. I enabled this in the W510 BIOS and then virt-manager would
allow me to create a new HVM based VM. However... it would then
complain "couldn''t find image" although it wouldn''t
let me (couldn''t
find) a place to define the name of this image. I assume only creating
an image from CD has been tested, then it complained I had no CD in the
drive.
I can try creating a VM (para-virtual for example from scratch) but my
hope was to move these three VMs which are in themselves complete
systems I dont realy want to rebuild from scratch. I also have other
RHEL5.3 VMs that cannot be easily rebuilt.
Obviously I will try and create a new VM from scratch using the
Virt-Manager wizard.
During the opensuse installation I chose partition based disk-set which
is similar ot the Ubuntu installation. The CentOS one uses LVM but I
dont think this would make any difference to running these domUs. Eg
config script which works on CentOS dom0:
name = "WinXP_sp3"
uuid = "79178fd8-d542-4c76-36ec-4791e104aad9"
maxmem = 512
memory = 512
cpus = 1
builder = "hvm"
kernel = "/usr/lib/xen/boot/hvmloader"
boot = "c"
pae = 1
acpi = 1
apic = 1
localtime = 1
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
device_model = "/usr/lib64/xen/bin/qemu-dm"
usb = 1
usbdevice = "tablet"
sdl = 0
vnc = 1
vncunused = 1
keymap = "en-us"
disk = [ "file:/var/lib/libvirt/images/XP-Pro_sp3.img,hda,w" ]
vif = [ "mac=00:16:36:f7:27:39,bridge=xenbr0,script=vif-bridge" ]
parallel = "none"
serial = "pty"
I''d be very interested in working with you to figure out this mystery
as I feel I''m very close after a couple of weeks of pulling my hair out
over kernel support for the W510 and trying to work with XEN.
Ideally, I''d rather not use another distro like opensuse but it has
been the least painful way to at least get XEN & Linux & W510
working together and fortunately the latest candidate release does do
this in a pretty stable environment. This final hurdle of hotplg
scripts is hopefully not too complicated to figure out.
lsmod, lspci and xm info follow....
linux-oit2:/etc/xen # xm info
host : linux-oit2
release : 2.6.34-8-xen
version : #1 SMP 2010-05-17 17:30:24 +0200
machine : x86_64
nr_cpus : 8
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 2
cpu_mhz : 1596
hw_caps :
bfebfbff:28100800:00000000:00001b40:0098e3fd:00000000:00000001:00000000
virt_caps : hvm hvm_directio
total_memory : 8088
free_memory : 149
free_cpus : 0
max_free_memory : 7495
max_para_memory : 7491
max_hvm_memory : 7465
node_to_cpu : node0:0-7
node_to_memory : node0:149
node_to_dma32_mem : node0:89
max_node_id : 0
xen_major : 4
xen_minor : 0
xen_extra : .0_21091_05-2.1
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : 21091
xen_commandline : vgamode=0x314 iommu=1
cc_compiler : gcc version 4.5.0 20100420 [gcc-4_5-branch
revision 158562] (SU
cc_compile_by : abuild
cc_compile_domain :
cc_compile_date : Wed May 19 19:06:40 UTC 2010
xend_config_format : 4
linux-oit2:/etc/xen # lsmod
Module Size Used by
usbbk 23911 0
gntdev 8579 0
netbk 41281 0 [permanent]
rfcomm 81560 4
blkbk 28782 0 [permanent]
blkback_pagemap 2806 1 blkbk
snd_pcm_oss 53455 0
blktap 126702 2 [permanent]
snd_mixer_oss 18817 1 snd_pcm_oss
sco 20103 2
domctl 3227 2 blkbk,blktap
bnep 18047 2
xenbus_be 3706 4 usbbk,netbk,blkbk,blktap
snd_seq 67923 0
snd_seq_device 7834 1 snd_seq
l2cap 62034 16 rfcomm,bnep
edd 10176 0
bridge 85815 3
stp 2331 1 bridge
llc 6103 2 bridge,stp
nouveau 552206 2
ttm 68464 1 nouveau
drm_kms_helper 33008 1 nouveau
drm 220232 4 nouveau,ttm,drm_kms_helper
agpgart 42953 2 ttm,drm
i2c_algo_bit 6696 1 nouveau
af_packet 23133 8
fuse 77053 3
loop 18239 0
dm_mod 86435 0
snd_hda_codec_nvhdmi 15727 4
arc4 1601 2
firewire_ohci 26970 0
ecb 2495 2
firewire_core 61402 1 firewire_ohci
snd_hda_intel 29133 2
crc_itu_t 1747 1 firewire_core
snd_hda_codec 112731 2 snd_hda_codec_nvhdmi,snd_hda_intel
iwlagn 238807 0
uvcvideo 67755 0
iwlcore 299287 1 iwlagn
sdhci_pci 8668 0
snd_hwdep 7708 1 snd_hda_codec
iTCO_wdt 12406 0
mac80211 283755 2 iwlagn,iwlcore
ohci1394 33510 0
videodev 43764 1 uvcvideo
v4l1_compat 16833 2 uvcvideo,videodev
8250_pci 25671 0
snd_pcm 107675 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
btusb 18511 2
sdhci 23126 1 sdhci_pci
v4l2_compat_ioctl32 11225 1 videodev
8250 31155 1 8250_pci
video 25192 0
snd_timer 27486 2 snd_seq,snd_pcm
sr_mod 16396 0
e1000e 152237 0
bluetooth 108637 9 rfcomm,sco,bnep,l2cap,btusb
sg 32951 0
mmc_core 83419 1 sdhci
iTCO_vendor_support 3150 1 iTCO_wdt
pcspkr 2222 0
tpm_tis 13134 0
thinkpad_acpi 83412 0
xhci_hcd 98228 0
cfg80211 182345 3 iwlagn,iwlcore,mac80211
i2c_i801 11881 0
ieee1394 104278 1 ohci1394
i2c_core 32104 6
nouveau,drm_kms_helper,drm,i2c_algo_bit,videodev,i2c_i801
serial_core 25223 1 8250
output 2727 1 video
tpm 17388 1 tpm_tis
rfkill 21959 4 bluetooth,thinkpad_acpi,cfg80211
snd 83486 15
snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_codec_nvhdmi,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer,thinkpad_acpi
snd_page_alloc 9473 2 snd_hda_intel,snd_pcm
wmi 8750 0
battery 12270 0
soundcore 8757 1 snd
ac 4023 0
tpm_bios 6652 1 tpm
button 6925 1 nouveau
joydev 12230 0
ext4 395274 1
jbd2 98208 1 ext4
crc16 1715 2 l2cap,ext4
sd_mod 41170 3
ehci_hcd 60206 0
usbcore 233034 6 usbbk,uvcvideo,btusb,xhci_hcd,ehci_hcd
xenblk 26162 0
cdrom 43083 2 sr_mod,xenblk
xennet 37763 0
fan 4527 0
processor 42918 0
ahci 42648 2
libata 211362 1 ahci
scsi_mod 191176 4 sr_mod,sg,sd_mod,libata
thermal 20593 0
thermal_sys 18006 4 video,fan,processor,thermal
hwmon 2712 2 thinkpad_acpi,thermal_sys
linux-oit2:/etc/xen # lspci
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root
Port 1 (rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System
Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore
and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System
Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor
Miscellaneous Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link
(rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing
and Protocol Registers (rev 11)
00:16.0 Communication controller: Intel Corporation 5 Series/3400
Series Chipset HECI Controller (rev 06)
00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series
Chipset KT Controller (rev 06)
00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network
Connection (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset
High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 2 (rev 06)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 4 (rev 06)
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 5 (rev 06)
00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 7 (rev 06)
00:1c.7 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 8 (rev 06)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC
Interface Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset
6 port SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus
Controller (rev 06)
01:00.0 VGA compatible controller: nVidia Corporation GT216 [Quadro FX
880M] (rev a2)
01:00.1 Audio device: nVidia Corporation High Definition Audio
Controller (rev a1)
03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300
(rev 35)
0d:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01)
0d:00.1 System peripheral: Ricoh Co Ltd Device e230 (rev 01)
0f:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host
Controller (rev 03)
17:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01)
17:00.3 FireWire (IEEE 1394): Ricoh Co Ltd Device e832 (rev 01)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath
Architecture Generic Non-Core Registers (rev 04)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath
Architecture System Address Decoder (rev 04)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev
04)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0
(rev 04)
ff:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller (rev 04)
ff:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Target Address Decoder (rev 04)
ff:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Test Registers (rev 04)
ff:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Control Registers (rev 04)
ff:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Address Registers (rev 04)
ff:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Rank Registers (rev 04)
ff:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Thermal Control Registers (rev 04)
ff:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Control Registers (rev 04)
ff:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Address Registers (rev 04)
ff:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Rank Registers (rev 04)
ff:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Thermal Control Registers (rev 04)
--- On Sun, 6/6/10, Mark Pryor <tlviewer@yahoo.com>
wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 9:48 PM
Mike,
Let me give you a broad checklist of things that may be important.
I just did a search of the lists.xensource.com/xen-users list and there
are no posts about
your hardware.
The Thinkpad w510 Notebook.
------------
many times a notebook like this will have a stealth bios, or a
limited bios. Are you
sure that HVM is enabled?
Your choice of suse 11.3 is good and should make it much easier to get
Xen 4.0 working. I like the way your Network looks, but I didn''t see
any IP address for your
br0- why not? This should work with a non-xen kernel too.
Your first domU is Winxp sp3. This might be a problem if your HD needs
AHCI or strange raid/SATA drivers not included with Winxp.
I think a better domU would be the same source you used for dom0. This
should work PV and won''t depend if your bios supports HVM.
Oh, can you post your
#xm info
#lsmod
#lspci
for dom0
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com>
wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: "Mark Pryor" <tlviewer@yahoo.com>
Date: Sunday, June 6, 2010, 3:40 PM
Yes, I tried this, and hte same error. I then removed
the vif altogether and the similiar hotplugin error appeared for the
harddrive. Following that, found the MAKEDEV issue but I''m not sure
what needs to be done there.
--- On Sun, 6/6/10, Mark Pryor <tlviewer@yahoo.com>
wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 5:57 PM
Mike,
Manual bridge is br0/br1.
In your HVM guest config, you should have
vif = [ ''bridge=br0'' ]
if you put xenbr0 above that would explain the problem too.
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com>
wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Date: Sunday, June 6, 2010, 2:34 PM
Thanks
for the suggestion, I assume I should keep the br0/br1... but trying
your suggestion I still see the same error. If I comment out the vif
in the HVM config file, I get a similar error hotplug script but for
the disk.
After mucking about with this some more I think the HVM should boot
(and not timeout) even if I have the wrong bridges/network scripts.
I''m not at the stage yet where I have no connectivity... the VM
doesn''t'' stay up long enough because of these hotplugin script
timeout/crash.
Hence my ramblings towards the end of the bug about finding postings on
MAKEDEV and missing /dev/ entries but haven''t managed to add these as
MAKEDEV doesn''t seem to exist on my vanilla installation and
I''ve not
had to do this on say a Centos XEN environment but that doens''t work
for other reasons (hw support) on my newer laptop.
--- On Sun, 6/6/10,
Mark Pryor <tlviewer@yahoo.com> wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 5:04 PM
Mike,
In your Xen config: xend-config.sxp
try to comment out
#(network-script network-bridge)
and uncomment
(network-script network-dummy)
and restart xend.
once you have a manual bridge, there is no need for Xen''s
network-bridge script.
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com>
wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: [Xen-users] Hotplug scripts not working - Networking woes on
opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Date: Sunday, June 6, 2010, 12:52 PM
Anyone can help me with
this problem I''ve described here:
https://bugzilla.novell.com/show_bug.cgi?id=612006
I''ve had XEN4.0 working on CentOS 5.4 platform without these problems.
I''m trying to do the same now with a newer laptop and CentOS
didn''t
recognise half hte drivers. The latest opensuse 11.3 does have these
drivers and specifically nouveau integration and XEN which has got me
98% of the way there... I''m presently stuck on the networking part
which looks different/problematic compared my experience on CentOS
machine.
Now the VMs launch but I see various Hotplug scripts not working
messages and the VM instantly stops running.
Thanks in advance,
Mike
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Helmut Wieser
2010-Jun-08 12:41 UTC
Re: [Xen-users] Hotplug scripts not working - Networking woes on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
Hi Mike, Then you are definitely facing a different problem than I am. After a dom0 reboot, my domU machines come up and stay up fine. Did you try to unpause a domU using xm? Turn on a VNC console to track whats going on. I suspect it''s working, and then shut down after 100 seconds. Make sure all required modules are loaded, or built into the kernel. Also try to add devices as you go, start with a minimum VM first, and expand as you go. To downgrade udev you don''t need to compile a kernel. You need to update your initrd though. Some more info on downgrading can be found here: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1612 regards, Helmut On 08.06.2010 14:22, Michael Cook wrote:> > Does what not come up? The dom0 comes up everytime but the domUs > start up and then timeout, in a paused state, with hotplug scripts not > working error every time. Its very reproducable. > > Was there any substance to the MAKEDEV posting circa 2006 as there are > no vnd* devices present for the psudeo-virtual-disks. I tried this > (as per opensuse bug comment I added yesterday) and MAKEDEV pumped out > a bunch of errors. To be honest I do not know what I''m doing, other > than surfing for workarounds/solutions. Hopefully someone on this > list is more experienced. > > Perhaps a XEN4.0 vs XEN3.x issue? Just guessing but all of this works > fine on XEN3.x on a CentOS 5.4 machine... but CentOS5.4 has no support > for my latest laptop. > > I may try the udev downgrade. Do you have any suggestions on how to > do this, is it a package downgrade or do I need to recompile the > kernel. (I''m trying to avoid recompiling/manually compiling stuff as > I dont want to diverge from maintained releases ideally). > > Thx, > Mike. > > --- On *Tue, 6/8/10, Helmut Wieser /<helmut.wieser@ieee.org>/* wrote: > > > From: Helmut Wieser <helmut.wieser@ieee.org> > Subject: Re: [Xen-users] Hotplug scripts not working - Networking > woes on opensuse 11.3 m7 with XEN4 on W510 Thinkpad > To: xen-users@lists.xensource.com > Received: Tuesday, June 8, 2010, 5:15 AM > > Does it not even come up after you rebooted the dom0? Because > that''s the issue I experienced. > At first I thougt it was different module load order, or different > kernel parameters, but in the end it turned out that a dom0 reboot > is required to "fix" the hotplug scripts not working issue. Some > people say that downgrading udev to <= 151 works for them. > Unfortunately I''m not one of them. > > Can you verify that? > > regards, > Helmut > > On 07.06.2010 05:58, Michael Cook wrote: >> Hi Mark, >> >> Thanks for your help. I will try and provide you some info. >> Some background first may help. But please let me know if there >> are other logs of interest. >> >> I''ve tried many distributions from my original use of Centos5.3 >> with XEN3.x. I have the following domUs which work well in CentOS >> but I now wanted to move to a newer, faster host. >> >> domUs: WinXP, Ubuntu 10.04 and RHEL5.3. >> >> The first two are hvms, the second is a pvm, which I''ve not tried >> yet and I really want the first two to work as WinXP cannot run >> as a PVM from what I know. >> >> I originally found Ubuntu 10.04 supported this W510 laptop pretty >> well although they are busy writing driver fixes for USB and >> screen. Mostly NVIDIA and Nouveau. Running dom0 Ubunut with >> NVIDIA or Nouveau doesn''t work well at all. I think there is an >> mmap issue from what I''ve read about it, circa March2010 there >> were hacks to get it work which have yet to appear within the >> kernel drivers and manually trying to add these to the kernel >> from XEN git for Ubuntu (Jeremys'') didn''t work. >> >> Ubuntu 10.04 (2.6.32.x) came up nicely on bare-metal. I then >> thought/hoped I could find a number of guides that would get me >> Ubuntu 10.04 dom0. This took some work but there are a couple of >> guides to recompiling and installing with XEN4.0 - then I got >> stuck with an earlier kernel which didn''t seem to support any >> recent updates to W510 drivers (including wlan) and there was >> still Nouveau bug fixes for the W510 chipset which to be honest I >> gave up on trying to manually fix. >> >> I also wasn''t happy with 800x600 resolution and finally found >> Opensuse 11.3 milestone 7 worked as Opensuse 11.2 is 2.6.31.x and >> nothing worked on the W510. CentOS5.4 on the W510 was even worse >> and with limited interest & support on CentOS I figured it would >> be a fair time until they support W510. >> >> There is a wiki on the W510 which shows a lot of activity in >> Ubuntu to fix up the drivers etc for W510 in Ubuntu 10.04. So >> I''m guessing by U10.10 things will be sorted but I doubt XEN will >> be well integrated... it seems unlikely from all the forum >> readings I''ve found on the subject. I''ve added my findings so >> far wrt XEN to this wiki which keeps track of the major issues >> for W510 (mostly in Ubuntu distro) >> >> http://www.thinkwiki.org/wiki/Category:W510 >> >> This brought me to opensuse which I dont know very well. The >> networking piece is quite different to Ubuntu and even in Ubuntu >> their Network Manager drives me nuts. Opensuse seem to have a >> Network Manager too through which I created br0 and br1 after >> reading the comment in the xend-config.sxp file saying "Opensuse >> users should not configure anything here but use the YaST Network >> configuration tool". So I''ve probably not set this up properly. >> >> None the less I was surprised as you point out that br0 didn''t >> have an IP addr and doesn''t seem able to be tied to the wlan0 >> interface (operation not supported message). >> >> Further more the basic network provisioning between eth0 and >> wlan0 seems awkward and quirky as when eth0 is not connected it >> still gets an IP addr. Oddly, it has not done this on this most >> recent bootup... eth0 is now provisioned but not assigned an >> address. "Change Default Route via DHCP" has always been set. >> So this is yet another puzzle with YaST Network Settings. Both >> br0 and br1 (I tried to bridge one to eth0 and one to wlan0) are >> set to DHCP but only one bridge manages to bridge to eth0. br1 >> doesn''t because "operation not supported" (presumably from >> ethtool or mii) for the wlan0 driver (new chipset support for >> this laptop?). >> >> linux-oit2:/etc/xen # brctl show >> bridge name bridge id STP enabled interfaces >> br0 8000.00262dfac618 no eth0 >> br1 8000.000000000000 no >> pan0 8000.000000000000 no >> >> >> Anyway, I was expecting to see peth0 and xenbr0 and the scripts >> I''ve run on centos5.3 which create these bridges to specific >> physical devices doesn''t seem to work well at all. >> >> Right now I dont know what to trust and obviously I''m using a >> pre-release of Opensuse. I''m hoping its a simple case of >> misprovisioning the native network settings along iwth the XEN >> installation. >> >> I used the example HVM file with XEN4.0 virt-manager under >> /etc/xen//examples/ and simply updated the UUID, vif and >> harddrive image with that of these domUs. I get the same >> behaviour in all of them... timeout with some hotplug script not >> working. >> >> So for the BIOS, yes, VT-d was disabled and xm info didn''t show >> any hvm support. I enabled this in the W510 BIOS and then >> virt-manager would allow me to create a new HVM based VM. >> However... it would then complain "couldn''t find image" although >> it wouldn''t let me (couldn''t find) a place to define the name of >> this image. I assume only creating an image from CD has been >> tested, then it complained I had no CD in the drive. >> >> I can try creating a VM (para-virtual for example from scratch) >> but my hope was to move these three VMs which are in themselves >> complete systems I dont realy want to rebuild from scratch. I >> also have other RHEL5.3 VMs that cannot be easily rebuilt. >> >> Obviously I will try and create a new VM from scratch using the >> Virt-Manager wizard. >> >> During the opensuse installation I chose partition based disk-set >> which is similar ot the Ubuntu installation. The CentOS one uses >> LVM but I dont think this would make any difference to running >> these domUs. Eg config script which works on CentOS dom0: >> >> name = "WinXP_sp3" >> uuid = "79178fd8-d542-4c76-36ec-4791e104aad9" >> maxmem = 512 >> memory = 512 >> cpus = 1 >> builder = "hvm" >> kernel = "/usr/lib/xen/boot/hvmloader" >> boot = "c" >> pae = 1 >> acpi = 1 >> apic = 1 >> localtime = 1 >> on_poweroff = "destroy" >> on_reboot = "restart" >> on_crash = "restart" >> device_model = "/usr/lib64/xen/bin/qemu-dm" >> usb = 1 >> usbdevice = "tablet" >> sdl = 0 >> vnc = 1 >> vncunused = 1 >> keymap = "en-us" >> disk = [ "file:/var/lib/libvirt/images/XP-Pro_sp3.img,hda,w" ] >> vif = [ "mac=00:16:36:f7:27:39,bridge=xenbr0,script=vif-bridge" ] >> parallel = "none" >> serial = "pty" >> >> I''d be very interested in working with you to figure out this >> mystery as I feel I''m very close after a couple of weeks of >> pulling my hair out over kernel support for the W510 and trying >> to work with XEN. >> >> Ideally, I''d rather not use another distro like opensuse but it >> has been the least painful way to at least get XEN & Linux & W510 >> working together and fortunately the latest candidate release >> does do this in a pretty stable environment. This final hurdle >> of hotplg scripts is hopefully not too complicated to figure out. >> >> lsmod, lspci and xm info follow.... >> >> linux-oit2:/etc/xen # xm info >> host : linux-oit2 >> release : 2.6.34-8-xen >> version : #1 SMP 2010-05-17 17:30:24 +0200 >> machine : x86_64 >> nr_cpus : 8 >> nr_nodes : 1 >> cores_per_socket : 4 >> threads_per_core : 2 >> cpu_mhz : 1596 >> hw_caps : >> bfebfbff:28100800:00000000:00001b40:0098e3fd:00000000:00000001:00000000 >> virt_caps : hvm hvm_directio >> total_memory : 8088 >> free_memory : 149 >> free_cpus : 0 >> max_free_memory : 7495 >> max_para_memory : 7491 >> max_hvm_memory : 7465 >> node_to_cpu : node0:0-7 >> node_to_memory : node0:149 >> node_to_dma32_mem : node0:89 >> max_node_id : 0 >> xen_major : 4 >> xen_minor : 0 >> xen_extra : .0_21091_05-2.1 >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p >> hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 >> xen_scheduler : credit >> xen_pagesize : 4096 >> platform_params : virt_start=0xffff800000000000 >> xen_changeset : 21091 >> xen_commandline : vgamode=0x314 iommu=1 >> cc_compiler : gcc version 4.5.0 20100420 >> [gcc-4_5-branch revision 158562] (SU >> cc_compile_by : abuild >> cc_compile_domain : >> cc_compile_date : Wed May 19 19:06:40 UTC 2010 >> xend_config_format : 4 >> >> >> linux-oit2:/etc/xen # lsmod >> Module Size Used by >> usbbk 23911 0 >> gntdev 8579 0 >> netbk 41281 0 [permanent] >> rfcomm 81560 4 >> blkbk 28782 0 [permanent] >> blkback_pagemap 2806 1 blkbk >> snd_pcm_oss 53455 0 >> blktap 126702 2 [permanent] >> snd_mixer_oss 18817 1 snd_pcm_oss >> sco 20103 2 >> domctl 3227 2 blkbk,blktap >> bnep 18047 2 >> xenbus_be 3706 4 usbbk,netbk,blkbk,blktap >> snd_seq 67923 0 >> snd_seq_device 7834 1 snd_seq >> l2cap 62034 16 rfcomm,bnep >> edd 10176 0 >> bridge 85815 3 >> stp 2331 1 bridge >> llc 6103 2 bridge,stp >> nouveau 552206 2 >> ttm 68464 1 nouveau >> drm_kms_helper 33008 1 nouveau >> drm 220232 4 nouveau,ttm,drm_kms_helper >> agpgart 42953 2 ttm,drm >> i2c_algo_bit 6696 1 nouveau >> af_packet 23133 8 >> fuse 77053 3 >> loop 18239 0 >> dm_mod 86435 0 >> snd_hda_codec_nvhdmi 15727 4 >> arc4 1601 2 >> firewire_ohci 26970 0 >> ecb 2495 2 >> firewire_core 61402 1 firewire_ohci >> snd_hda_intel 29133 2 >> crc_itu_t 1747 1 firewire_core >> snd_hda_codec 112731 2 snd_hda_codec_nvhdmi,snd_hda_intel >> iwlagn 238807 0 >> uvcvideo 67755 0 >> iwlcore 299287 1 iwlagn >> sdhci_pci 8668 0 >> snd_hwdep 7708 1 snd_hda_codec >> iTCO_wdt 12406 0 >> mac80211 283755 2 iwlagn,iwlcore >> ohci1394 33510 0 >> videodev 43764 1 uvcvideo >> v4l1_compat 16833 2 uvcvideo,videodev >> 8250_pci 25671 0 >> snd_pcm 107675 3 >> snd_pcm_oss,snd_hda_intel,snd_hda_codec >> btusb 18511 2 >> sdhci 23126 1 sdhci_pci >> v4l2_compat_ioctl32 11225 1 videodev >> 8250 31155 1 8250_pci >> video 25192 0 >> snd_timer 27486 2 snd_seq,snd_pcm >> sr_mod 16396 0 >> e1000e 152237 0 >> bluetooth 108637 9 rfcomm,sco,bnep,l2cap,btusb >> sg 32951 0 >> mmc_core 83419 1 sdhci >> iTCO_vendor_support 3150 1 iTCO_wdt >> pcspkr 2222 0 >> tpm_tis 13134 0 >> thinkpad_acpi 83412 0 >> xhci_hcd 98228 0 >> cfg80211 182345 3 iwlagn,iwlcore,mac80211 >> i2c_i801 11881 0 >> ieee1394 104278 1 ohci1394 >> i2c_core 32104 6 >> nouveau,drm_kms_helper,drm,i2c_algo_bit,videodev,i2c_i801 >> serial_core 25223 1 8250 >> output 2727 1 video >> tpm 17388 1 tpm_tis >> rfkill 21959 4 bluetooth,thinkpad_acpi,cfg80211 >> snd 83486 15 >> snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_codec_nvhdmi,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer,thinkpad_acpi >> snd_page_alloc 9473 2 snd_hda_intel,snd_pcm >> wmi 8750 0 >> battery 12270 0 >> soundcore 8757 1 snd >> ac 4023 0 >> tpm_bios 6652 1 tpm >> button 6925 1 nouveau >> joydev 12230 0 >> ext4 395274 1 >> jbd2 98208 1 ext4 >> crc16 1715 2 l2cap,ext4 >> sd_mod 41170 3 >> ehci_hcd 60206 0 >> usbcore 233034 6 >> usbbk,uvcvideo,btusb,xhci_hcd,ehci_hcd >> xenblk 26162 0 >> cdrom 43083 2 sr_mod,xenblk >> xennet 37763 0 >> fan 4527 0 >> processor 42918 0 >> ahci 42648 2 >> libata 211362 1 ahci >> scsi_mod 191176 4 sr_mod,sg,sd_mod,libata >> thermal 20593 0 >> thermal_sys 18006 4 video,fan,processor,thermal >> hwmon 2712 2 thinkpad_acpi,thermal_sys >> >> >> linux-oit2:/etc/xen # lspci >> 00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11) >> 00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express >> Root Port 1 (rev 11) >> 00:08.0 System peripheral: Intel Corporation Core Processor >> System Management Registers (rev 11) >> 00:08.1 System peripheral: Intel Corporation Core Processor >> Semaphore and Scratchpad Registers (rev 11) >> 00:08.2 System peripheral: Intel Corporation Core Processor >> System Control and Status Registers (rev 11) >> 00:08.3 System peripheral: Intel Corporation Core Processor >> Miscellaneous Registers (rev 11) >> 00:10.0 System peripheral: Intel Corporation Core Processor QPI >> Link (rev 11) >> 00:10.1 System peripheral: Intel Corporation Core Processor QPI >> Routing and Protocol Registers (rev 11) >> 00:16.0 Communication controller: Intel Corporation 5 Series/3400 >> Series Chipset HECI Controller (rev 06) >> 00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series >> Chipset KT Controller (rev 06) >> 00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit >> Network Connection (rev 06) >> 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series >> Chipset USB2 Enhanced Host Controller (rev 06) >> 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series >> Chipset High Definition Audio (rev 06) >> 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series >> Chipset PCI Express Root Port 1 (rev 06) >> 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series >> Chipset PCI Express Root Port 2 (rev 06) >> 00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series >> Chipset PCI Express Root Port 4 (rev 06) >> 00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series >> Chipset PCI Express Root Port 5 (rev 06) >> 00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series >> Chipset PCI Express Root Port 7 (rev 06) >> 00:1c.7 PCI bridge: Intel Corporation 5 Series/3400 Series >> Chipset PCI Express Root Port 8 (rev 06) >> 00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series >> Chipset USB2 Enhanced Host Controller (rev 06) >> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge >> (rev a6) >> 00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC >> Interface Controller (rev 06) >> 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series >> Chipset 6 port SATA AHCI Controller (rev 06) >> 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset >> SMBus Controller (rev 06) >> 01:00.0 VGA compatible controller: nVidia Corporation GT216 >> [Quadro FX 880M] (rev a2) >> 01:00.1 Audio device: nVidia Corporation High Definition Audio >> Controller (rev a1) >> 03:00.0 Network controller: Intel Corporation Centrino Ultimate-N >> 6300 (rev 35) >> 0d:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01) >> 0d:00.1 System peripheral: Ricoh Co Ltd Device e230 (rev 01) >> 0f:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host >> Controller (rev 03) >> 17:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01) >> 17:00.3 FireWire (IEEE 1394): Ricoh Co Ltd Device e832 (rev 01) >> ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath >> Architecture Generic Non-Core Registers (rev 04) >> ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath >> Architecture System Address Decoder (rev 04) >> ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 >> (rev 04) >> ff:02.1 Host bridge: Intel Corporation Core Processor QPI >> Physical 0 (rev 04) >> ff:03.0 Host bridge: Intel Corporation Core Processor Integrated >> Memory Controller (rev 04) >> ff:03.1 Host bridge: Intel Corporation Core Processor Integrated >> Memory Controller Target Address Decoder (rev 04) >> ff:03.4 Host bridge: Intel Corporation Core Processor Integrated >> Memory Controller Test Registers (rev 04) >> ff:04.0 Host bridge: Intel Corporation Core Processor Integrated >> Memory Controller Channel 0 Control Registers (rev 04) >> ff:04.1 Host bridge: Intel Corporation Core Processor Integrated >> Memory Controller Channel 0 Address Registers (rev 04) >> ff:04.2 Host bridge: Intel Corporation Core Processor Integrated >> Memory Controller Channel 0 Rank Registers (rev 04) >> ff:04.3 Host bridge: Intel Corporation Core Processor Integrated >> Memory Controller Channel 0 Thermal Control Registers (rev 04) >> ff:05.0 Host bridge: Intel Corporation Core Processor Integrated >> Memory Controller Channel 1 Control Registers (rev 04) >> ff:05.1 Host bridge: Intel Corporation Core Processor Integrated >> Memory Controller Channel 1 Address Registers (rev 04) >> ff:05.2 Host bridge: Intel Corporation Core Processor Integrated >> Memory Controller Channel 1 Rank Registers (rev 04) >> ff:05.3 Host bridge: Intel Corporation Core Processor Integrated >> Memory Controller Channel 1 Thermal Control Registers (rev 04) >> >> >> >> >> >> --- On *Sun, 6/6/10, Mark Pryor /<tlviewer@yahoo.com>/* wrote: >> >> >> From: Mark Pryor <tlviewer@yahoo.com> >> Subject: Re: [Xen-users] Hotplug scripts not working - >> Networking woes on opensuse 11.3 m7 with XEN4 on W510 Thinkpad >> To: michael@dtmc.ca >> Received: Sunday, June 6, 2010, 9:48 PM >> >> Mike, >> >> Let me give you a broad checklist of things that may be >> important. >> >> I just did a search of the lists.xensource.com/xen-users list >> and there are no posts about >> your hardware. >> >> The Thinkpad w510 Notebook. >> ------------ >> many times a notebook like this will have a stealth bios, >> or a limited bios. Are you >> sure that HVM is enabled? >> >> Your choice of suse 11.3 is good and should make it much >> easier to get Xen 4.0 working. I like the way your Network >> looks, but I didn''t see any IP address for your >> br0- why not? This should work with a non-xen kernel too. >> >> Your first domU is Winxp sp3. This might be a problem if your >> HD needs AHCI or strange raid/SATA drivers not included with >> Winxp. >> >> I think a better domU would be the same source you used for >> dom0. This should work PV and won''t depend if your bios >> supports HVM. >> >> Oh, can you post your >> #xm info >> >> #lsmod >> >> #lspci >> >> for dom0 >> >> -- >> Mark >> >> >> >> --- On *Sun, 6/6/10, Michael Cook >> /<michaelcook_mjc@yahoo.com>/* wrote: >> >> >> From: Michael Cook <michaelcook_mjc@yahoo.com> >> Subject: Re: [Xen-users] Hotplug scripts not working - >> Networking woes on opensuse 11.3 m7 with XEN4 on W510 >> Thinkpad >> To: "Mark Pryor" <tlviewer@yahoo.com> >> Date: Sunday, June 6, 2010, 3:40 PM >> >> Yes, I tried this, and hte same error. I then removed >> the vif altogether and the similiar hotplugin error >> appeared for the harddrive. Following that, found the >> MAKEDEV issue but I''m not sure what needs to be done there. >> >> >> --- On *Sun, 6/6/10, Mark Pryor /<tlviewer@yahoo.com>/* >> wrote: >> >> >> From: Mark Pryor <tlviewer@yahoo.com> >> Subject: Re: [Xen-users] Hotplug scripts not working >> - Networking woes on opensuse 11.3 m7 with XEN4 on >> W510 Thinkpad >> To: michael@dtmc.ca >> Received: Sunday, June 6, 2010, 5:57 PM >> >> Mike, >> >> Manual bridge is br0/br1. >> >> In your HVM guest config, you should have >> vif = [ ''bridge=br0'' ] >> >> if you put xenbr0 above that would explain the >> problem too. >> >> -- >> Mark >> >> --- On *Sun, 6/6/10, Michael Cook >> /<michaelcook_mjc@yahoo.com>/* wrote: >> >> >> From: Michael Cook <michaelcook_mjc@yahoo.com> >> Subject: Re: [Xen-users] Hotplug scripts not >> working - Networking woes on opensuse 11.3 m7 >> with XEN4 on W510 Thinkpad >> To: xen-users@lists.xensource.com >> Date: Sunday, June 6, 2010, 2:34 PM >> >> Thanks for the suggestion, I assume I should keep >> the br0/br1... but trying your suggestion I still >> see the same error. If I comment out the vif in >> the HVM config file, I get a similar error >> hotplug script but for the disk. >> >> After mucking about with this some more I think >> the HVM should boot (and not timeout) even if I >> have the wrong bridges/network scripts. I''m not >> at the stage yet where I have no connectivity... >> the VM doesn''t'' stay up long enough because of >> these hotplugin script timeout/crash. >> >> Hence my ramblings towards the end of the bug >> about finding postings on MAKEDEV and missing >> /dev/ entries but haven''t managed to add these as >> MAKEDEV doesn''t seem to exist on my vanilla >> installation and I''ve not had to do this on say a >> Centos XEN environment but that doens''t work for >> other reasons (hw support) on my newer laptop. >> >> --- On *Sun, 6/6/10, Mark Pryor >> /<tlviewer@yahoo.com>/* wrote: >> >> >> From: Mark Pryor <tlviewer@yahoo.com> >> Subject: Re: [Xen-users] Hotplug scripts not >> working - Networking woes on opensuse 11.3 m7 >> with XEN4 on W510 Thinkpad >> To: michael@dtmc.ca >> Received: Sunday, June 6, 2010, 5:04 PM >> >> Mike, >> >> In your Xen config: xend-config.sxp >> try to comment out >> #(network-script network-bridge) >> >> and uncomment >> (network-script network-dummy) >> >> and restart xend. >> once you have a manual bridge, there is no >> need for Xen''s >> network-bridge script. >> >> -- >> Mark >> >> --- On *Sun, 6/6/10, Michael Cook >> /<michaelcook_mjc@yahoo.com>/* wrote: >> >> >> From: Michael Cook >> <michaelcook_mjc@yahoo.com> >> Subject: [Xen-users] Hotplug scripts not >> working - Networking woes on opensuse >> 11.3 m7 with XEN4 on W510 Thinkpad >> To: xen-users@lists.xensource.com >> Date: Sunday, June 6, 2010, 12:52 PM >> >> Anyone can help me with this problem I''ve >> described here: >> >> https://bugzilla.novell.com/show_bug.cgi?id=612006 >> >> I''ve had XEN4.0 working on CentOS 5.4 >> platform without these problems. I''m >> trying to do the same now with a newer >> laptop and CentOS didn''t recognise half >> hte drivers. The latest opensuse 11.3 >> does have these drivers and specifically >> nouveau integration and XEN which has got >> me 98% of the way there... I''m presently >> stuck on the networking part which looks >> different/problematic compared my >> experience on CentOS machine. >> >> Now the VMs launch but I see various >> Hotplug scripts not working messages and >> the VM instantly stops running. >> >> Thanks in advance, >> Mike >> >> >> >> -----Inline Attachment Follows----- >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> >> >> >> -----Inline Attachment Follows----- >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> >> >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users > > -----Inline Attachment Follows----- > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > </mc/compose?to=Xen-users@lists.xensource.com> > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Michael Cook
2010-Jun-08 12:54 UTC
Re: [Xen-users] Hotplug scripts not working - (opensuse 11.3 m7 with XEN4 on W510 Thinkpad)
If I try and unpause the domUs they start booting although the WinXP starts
complaining about scandisk and wants to run through that, if I skip that, I then
get to log in, but then the ~100sec timeout hits and simply closes the domU VM.
So the behaviour seems unrelated to the content in the VM IMO but rather
something XEN environment is waiting on.
This may also suggest that networking or disk access is actually fine and the
hotplug script error message is a bit of a red-herring.
I will try building a VM from scratch to see if this makes any difference but I
have several VMs I need running which would be time consuming to say the least
to re-create from scratch. Hence my hope for a solution to this timeout error.
Mike.
--
Text/Cell: +1.613.447.7407 Email: michael@dtmc.ca
--- On Tue, 6/8/10, Helmut Wieser <helmut.wieser@ieee.org> wrote:
From: Helmut Wieser <helmut.wieser@ieee.org>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes on
opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: "xen-users mailing list" <xen-users@lists.xensource.com>
Cc: michael@dtmc.ca, "Michael Cook" <michaelcook_mjc@yahoo.com>
Received: Tuesday, June 8, 2010, 8:41 AM
Hi Mike,
Then you are definitely facing a different problem than I am. After a
dom0 reboot, my domU machines come up and stay up fine.
Did you try to unpause a domU using xm? Turn on a VNC console to track
whats going on. I suspect it''s working, and then shut down after 100
seconds.
Make sure all required modules are loaded, or built into the kernel.
Also try to add devices as you go, start with a minimum VM first, and
expand as you go.
To downgrade udev you don''t need to compile a kernel. You need to
update your initrd though. Some more info on downgrading can be found
here: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1612
regards,
Helmut
On 08.06.2010 14:22, Michael Cook wrote:
Does what not come up? The dom0 comes up everytime but the domUs start
up and then timeout, in a paused state, with hotplug scripts not
working error every time. Its very reproducable.
Was there any substance to the MAKEDEV posting circa 2006 as there are
no vnd* devices present for the psudeo-virtual-disks. I tried this (as
per opensuse bug comment I added yesterday) and MAKEDEV pumped out a
bunch of errors. To be honest I do not know what I''m doing, other than
surfing for workarounds/solutions. Hopefully someone on this list is
more experienced.
Perhaps a XEN4.0 vs XEN3.x issue? Just guessing but all of this works
fine on XEN3.x on a CentOS 5.4 machine... but CentOS5.4 has no support
for my latest laptop.
I may try the udev downgrade. Do you have any suggestions on how to do
this, is it a package downgrade or do I need to recompile the kernel.
(I''m trying to avoid recompiling/manually compiling stuff as I dont
want to diverge from maintained releases ideally).
Thx,
Mike.
--- On Tue, 6/8/10, Helmut Wieser <helmut.wieser@ieee.org>
wrote:
From: Helmut Wieser <helmut.wieser@ieee.org>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Received: Tuesday, June 8, 2010, 5:15 AM
Does it not even come up after you rebooted the dom0? Because that''s
the issue I experienced.
At first I thougt it was different module load order, or different
kernel parameters, but in the end it turned out that a dom0 reboot is
required to "fix" the hotplug scripts not working issue. Some people
say that downgrading udev to <= 151 works for them. Unfortunately
I''m not one of them.
Can you verify that?
regards,
Helmut
On 07.06.2010 05:58, Michael Cook wrote:
Hi Mark,
Thanks for your help. I will try and provide you some info. Some
background first may help. But please let me know if there are other
logs of interest.
I''ve tried many distributions from my original use of Centos5.3 with
XEN3.x. I have the following domUs which work well in CentOS but I now
wanted to move to a newer, faster host.
domUs: WinXP, Ubuntu 10.04 and RHEL5.3.
The first two are hvms, the second is a pvm, which I''ve not tried yet
and I really want the first two to work as WinXP cannot run as a PVM
from what I know.
I originally found Ubuntu 10.04 supported this W510 laptop pretty well
although they are busy writing driver fixes for USB and screen. Mostly
NVIDIA and Nouveau. Running dom0 Ubunut with NVIDIA or Nouveau doesn''t
work well at all. I think there is an mmap issue from what I''ve read
about it, circa March2010 there were hacks to get it work which have
yet to appear within the kernel drivers and manually trying to add
these to the kernel from XEN git for Ubuntu (Jeremys'') didn''t
work.
Ubuntu 10.04 (2.6.32.x) came up nicely on bare-metal. I then
thought/hoped I could find a number of guides that would get me Ubuntu
10.04 dom0. This took some work but there are a couple of guides to
recompiling and installing with XEN4.0 - then I got stuck with an
earlier kernel which didn''t seem to support any recent updates to W510
drivers (including wlan) and there was still Nouveau bug fixes for the
W510 chipset which to be honest I gave up on trying to manually fix.
I also wasn''t happy with 800x600 resolution and finally found Opensuse
11.3 milestone 7 worked as Opensuse 11.2 is 2.6.31.x and nothing worked
on the W510. CentOS5.4 on the W510 was even worse and with limited
interest & support on CentOS I figured it would be a fair time
until they support W510.
There is a wiki on the W510 which shows a lot of activity in Ubuntu to
fix up the drivers etc for W510 in Ubuntu 10.04. So I''m guessing by
U10.10 things will be sorted but I doubt XEN will be well integrated...
it seems unlikely from all the forum readings I''ve found on the
subject. I''ve added my findings so far wrt XEN to this wiki which
keeps track of the major issues for W510 (mostly in Ubuntu distro)
http://www.thinkwiki.org/wiki/Category:W510
This brought me to opensuse which I dont know very well. The
networking piece is quite different to Ubuntu and even in Ubuntu their
Network Manager drives me nuts. Opensuse seem to have a Network
Manager too through which I created br0 and br1 after reading the
comment in the xend-config.sxp file saying "Opensuse users should not
configure anything here but use the YaST Network configuration tool".
So I''ve probably not set this up properly.
None the less I was surprised as you point out that br0 didn''t have an
IP addr and doesn''t seem able to be tied to the wlan0 interface
(operation not supported message).
Further more the basic network provisioning between eth0 and wlan0
seems awkward and quirky as when eth0 is not connected it still gets an
IP addr. Oddly, it has not done this on this most recent bootup...
eth0 is now provisioned but not assigned an address. "Change Default
Route via DHCP" has always been set. So this is yet another puzzle
with YaST Network Settings. Both br0 and br1 (I tried to bridge one to
eth0 and one to wlan0) are set to DHCP but only one bridge manages to
bridge to eth0. br1 doesn''t because "operation not
supported"
(presumably from ethtool or mii) for the wlan0 driver (new chipset
support for this laptop?).
linux-oit2:/etc/xen # brctl show
bridge name bridge id STP enabled interfaces
br0 8000.00262dfac618 no eth0
br1 8000.000000000000 no
pan0 8000.000000000000 no
Anyway, I was expecting to see peth0 and xenbr0 and the scripts I''ve
run on centos5.3 which create these bridges to specific physical
devices doesn''t seem to work well at all.
Right now I dont know what to trust and obviously I''m using a
pre-release of Opensuse. I''m hoping its a simple case of
misprovisioning the native network settings along iwth the XEN
installation.
I used the example HVM file with XEN4.0 virt-manager under
/etc/xen//examples/ and simply updated the UUID, vif and harddrive
image with that of these domUs. I get the same behaviour in all of
them... timeout with some hotplug script not working.
So for the BIOS, yes, VT-d was disabled and xm info didn''t show any hvm
support. I enabled this in the W510 BIOS and then virt-manager would
allow me to create a new HVM based VM. However... it would then
complain "couldn''t find image" although it wouldn''t
let me (couldn''t
find) a place to define the name of this image. I assume only creating
an image from CD has been tested, then it complained I had no CD in the
drive.
I can try creating a VM (para-virtual for example from scratch) but my
hope was to move these three VMs which are in themselves complete
systems I dont realy want to rebuild from scratch. I also have other
RHEL5.3 VMs that cannot be easily rebuilt.
Obviously I will try and create a new VM from scratch using the
Virt-Manager wizard.
During the opensuse installation I chose partition based disk-set which
is similar ot the Ubuntu installation. The CentOS one uses LVM but I
dont think this would make any difference to running these domUs. Eg
config script which works on CentOS dom0:
name = "WinXP_sp3"
uuid = "79178fd8-d542-4c76-36ec-4791e104aad9"
maxmem = 512
memory = 512
cpus = 1
builder = "hvm"
kernel = "/usr/lib/xen/boot/hvmloader"
boot = "c"
pae = 1
acpi = 1
apic = 1
localtime = 1
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
device_model = "/usr/lib64/xen/bin/qemu-dm"
usb = 1
usbdevice = "tablet"
sdl = 0
vnc = 1
vncunused = 1
keymap = "en-us"
disk = [ "file:/var/lib/libvirt/images/XP-Pro_sp3.img,hda,w"
]
vif = [ "mac=00:16:36:f7:27:39,bridge=xenbr0,script=vif-bridge" ]
parallel = "none"
serial = "pty"
I''d be very interested in working with you to figure out this mystery
as I feel I''m very close after a couple of weeks of pulling my hair out
over kernel support for the W510 and trying to work with XEN.
Ideally, I''d rather not use another distro like opensuse but it has
been the least painful way to at least get XEN & Linux & W510
working together and fortunately the latest candidate release does do
this in a pretty stable environment. This final hurdle of hotplg
scripts is hopefully not too complicated to figure out.
lsmod, lspci and xm info follow....
linux-oit2:/etc/xen # xm info
host : linux-oit2
release : 2.6.34-8-xen
version : #1 SMP 2010-05-17 17:30:24 +0200
machine : x86_64
nr_cpus : 8
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 2
cpu_mhz : 1596
hw_caps :
bfebfbff:28100800:00000000:00001b40:0098e3fd:00000000:00000001:00000000
virt_caps : hvm hvm_directio
total_memory : 8088
free_memory : 149
free_cpus : 0
max_free_memory : 7495
max_para_memory : 7491
max_hvm_memory : 7465
node_to_cpu : node0:0-7
node_to_memory : node0:149
node_to_dma32_mem : node0:89
max_node_id : 0
xen_major : 4
xen_minor : 0
xen_extra : .0_21091_05-2.1
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : 21091
xen_commandline : vgamode=0x314 iommu=1
cc_compiler : gcc version 4.5.0 20100420 [gcc-4_5-branch
revision 158562] (SU
cc_compile_by : abuild
cc_compile_domain :
cc_compile_date : Wed May 19 19:06:40 UTC 2010
xend_config_format : 4
linux-oit2:/etc/xen # lsmod
Module Size Used by
usbbk 23911 0
gntdev 8579 0
netbk 41281 0 [permanent]
rfcomm 81560 4
blkbk 28782 0 [permanent]
blkback_pagemap 2806 1 blkbk
snd_pcm_oss 53455 0
blktap 126702 2 [permanent]
snd_mixer_oss 18817 1 snd_pcm_oss
sco 20103 2
domctl 3227 2 blkbk,blktap
bnep 18047 2
xenbus_be 3706 4 usbbk,netbk,blkbk,blktap
snd_seq 67923 0
snd_seq_device 7834 1 snd_seq
l2cap 62034 16 rfcomm,bnep
edd 10176 0
bridge 85815 3
stp 2331 1 bridge
llc 6103 2 bridge,stp
nouveau 552206 2
ttm 68464 1 nouveau
drm_kms_helper 33008 1 nouveau
drm 220232 4 nouveau,ttm,drm_kms_helper
agpgart 42953 2 ttm,drm
i2c_algo_bit 6696 1 nouveau
af_packet 23133 8
fuse 77053 3
loop 18239 0
dm_mod 86435 0
snd_hda_codec_nvhdmi 15727 4
arc4 1601 2
firewire_ohci 26970 0
ecb 2495 2
firewire_core 61402 1 firewire_ohci
snd_hda_intel 29133 2
crc_itu_t 1747 1 firewire_core
snd_hda_codec 112731 2 snd_hda_codec_nvhdmi,snd_hda_intel
iwlagn 238807 0
uvcvideo 67755 0
iwlcore 299287 1 iwlagn
sdhci_pci 8668 0
snd_hwdep 7708 1 snd_hda_codec
iTCO_wdt 12406 0
mac80211 283755 2 iwlagn,iwlcore
ohci1394 33510 0
videodev 43764 1 uvcvideo
v4l1_compat 16833 2 uvcvideo,videodev
8250_pci 25671 0
snd_pcm 107675 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
btusb 18511 2
sdhci 23126 1 sdhci_pci
v4l2_compat_ioctl32 11225 1 videodev
8250 31155 1 8250_pci
video 25192 0
snd_timer 27486 2 snd_seq,snd_pcm
sr_mod 16396 0
e1000e 152237 0
bluetooth 108637 9 rfcomm,sco,bnep,l2cap,btusb
sg 32951 0
mmc_core 83419 1 sdhci
iTCO_vendor_support 3150 1 iTCO_wdt
pcspkr 2222 0
tpm_tis 13134 0
thinkpad_acpi 83412 0
xhci_hcd 98228 0
cfg80211 182345 3 iwlagn,iwlcore,mac80211
i2c_i801 11881 0
ieee1394 104278 1 ohci1394
i2c_core 32104 6
nouveau,drm_kms_helper,drm,i2c_algo_bit,videodev,i2c_i801
serial_core 25223 1 8250
output 2727 1 video
tpm 17388 1 tpm_tis
rfkill 21959 4 bluetooth,thinkpad_acpi,cfg80211
snd 83486 15
snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_codec_nvhdmi,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer,thinkpad_acpi
snd_page_alloc 9473 2 snd_hda_intel,snd_pcm
wmi 8750 0
battery 12270 0
soundcore 8757 1 snd
ac 4023 0
tpm_bios 6652 1 tpm
button 6925 1 nouveau
joydev 12230 0
ext4 395274 1
jbd2 98208 1 ext4
crc16 1715 2 l2cap,ext4
sd_mod 41170 3
ehci_hcd 60206 0
usbcore 233034 6 usbbk,uvcvideo,btusb,xhci_hcd,ehci_hcd
xenblk 26162 0
cdrom 43083 2 sr_mod,xenblk
xennet 37763 0
fan 4527 0
processor 42918 0
ahci 42648 2
libata 211362 1 ahci
scsi_mod 191176 4 sr_mod,sg,sd_mod,libata
thermal 20593 0
thermal_sys 18006 4 video,fan,processor,thermal
hwmon 2712 2 thinkpad_acpi,thermal_sys
linux-oit2:/etc/xen # lspci
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root
Port 1 (rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System
Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore
and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System
Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor
Miscellaneous Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link
(rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing
and Protocol Registers (rev 11)
00:16.0 Communication controller: Intel Corporation 5 Series/3400
Series Chipset HECI Controller (rev 06)
00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series
Chipset KT Controller (rev 06)
00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network
Connection (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset
High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 2 (rev 06)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 4 (rev 06)
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 5 (rev 06)
00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 7 (rev 06)
00:1c.7 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 8 (rev 06)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC
Interface Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset
6 port SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus
Controller (rev 06)
01:00.0 VGA compatible controller: nVidia Corporation GT216 [Quadro FX
880M] (rev a2)
01:00.1 Audio device: nVidia Corporation High Definition Audio
Controller (rev a1)
03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300
(rev 35)
0d:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01)
0d:00.1 System peripheral: Ricoh Co Ltd Device e230 (rev 01)
0f:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host
Controller (rev 03)
17:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01)
17:00.3 FireWire (IEEE 1394): Ricoh Co Ltd Device e832 (rev 01)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath
Architecture Generic Non-Core Registers (rev 04)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath
Architecture System Address Decoder (rev 04)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev
04)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0
(rev 04)
ff:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller (rev 04)
ff:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Target Address Decoder (rev 04)
ff:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Test Registers (rev 04)
ff:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Control Registers (rev 04)
ff:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Address Registers (rev 04)
ff:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Rank Registers (rev 04)
ff:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Thermal Control Registers (rev 04)
ff:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Control Registers (rev 04)
ff:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Address Registers (rev 04)
ff:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Rank Registers (rev 04)
ff:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Thermal Control Registers (rev 04)
--- On Sun, 6/6/10, Mark Pryor <tlviewer@yahoo.com>
wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 9:48 PM
Mike,
Let me give you a broad checklist of things that may be important.
I just did a search of the lists.xensource.com/xen-users list and there
are no posts about
your hardware.
The Thinkpad w510 Notebook.
------------
many times a notebook like this will have a stealth bios, or a
limited bios. Are you
sure that HVM is enabled?
Your choice of suse 11.3 is good and should make it much easier to get
Xen 4.0 working. I like the way your Network looks, but I didn''t see
any IP address for your
br0- why not? This should work with a non-xen kernel too.
Your first domU is Winxp sp3. This might be a problem if your HD needs
AHCI or strange raid/SATA drivers not included with Winxp.
I think a better domU would be the same source you used for dom0. This
should work PV and won''t depend if your bios supports HVM.
Oh, can you post your
#xm info
#lsmod
#lspci
for dom0
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com>
wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: "Mark Pryor" <tlviewer@yahoo.com>
Date: Sunday, June 6, 2010, 3:40 PM
Yes, I tried this, and hte same error. I then
removed
the vif altogether and the similiar hotplugin error appeared for the
harddrive. Following that, found the MAKEDEV issue but I''m not sure
what needs to be done there.
--- On Sun, 6/6/10, Mark Pryor <tlviewer@yahoo.com>
wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 5:57 PM
Mike,
Manual bridge is br0/br1.
In your HVM guest config, you should have
vif = [ ''bridge=br0'' ]
if you put xenbr0 above that would explain the problem too.
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com>
wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Date: Sunday, June 6, 2010, 2:34 PM
Thanks
for
the suggestion, I assume I should keep the br0/br1... but trying
your suggestion I still see the same error. If I comment out the vif
in the HVM config file, I get a similar error hotplug script but for
the disk.
After mucking about with this some more I think the HVM should boot
(and not timeout) even if I have the wrong bridges/network scripts.
I''m not at the stage yet where I have no connectivity... the VM
doesn''t'' stay up long enough because of these hotplugin script
timeout/crash.
Hence my ramblings towards the end of the bug about finding postings on
MAKEDEV and missing /dev/ entries but haven''t managed to add these as
MAKEDEV doesn''t seem to exist on my vanilla installation and
I''ve not
had to do this on say a Centos XEN environment but that doens''t work
for other reasons (hw support) on my newer laptop.
--- On Sun,
6/6/10,
Mark Pryor <tlviewer@yahoo.com>
wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 5:04 PM
Mike,
In your Xen config: xend-config.sxp
try to comment out
#(network-script network-bridge)
and uncomment
(network-script network-dummy)
and restart xend.
once you have a manual bridge, there is no need for Xen''s
network-bridge script.
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com>
wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: [Xen-users] Hotplug scripts not working - Networking woes on
opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Date: Sunday, June 6, 2010, 12:52 PM
Anyone can
help me with this problem I''ve described here:
https://bugzilla.novell.com/show_bug.cgi?id=612006
I''ve had XEN4.0 working on CentOS 5.4 platform without these problems.
I''m trying to do the same now with a newer laptop and CentOS
didn''t
recognise half hte drivers. The latest opensuse 11.3 does have these
drivers and specifically nouveau integration and XEN which has got me
98% of the way there... I''m presently stuck on the networking part
which looks different/problematic compared my experience on CentOS
machine.
Now the VMs launch but I see various Hotplug scripts not working
messages and the VM instantly stops running.
Thanks in advance,
Mike
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Michael Cook
2010-Jun-08 13:38 UTC
Re: [Xen-users] Hotplug scripts not working - netback_uevent+0x73/0x100 NULL ptr deref (opensuse 11.3 m7 with XEN4 on W510 Thinkpad)
Looking a bit further at this the XEND is actually de-referencing a null ptr
when starting up the VM. I''ve added the traceback to the opensuse
bugzilla report:
https://bugzilla.novell.com/show_bug.cgi?id=612006
[ 693.222999] BUG: unable to handle kernel NULL pointer dereference at
0000000000000150
[ 693.223015] IP: [<ffffffffa0889a63>] netback_uevent+0x73/0x100 [netbk]
[ 693.223038] PGD 189cef067 PUD 189d30067 PMD 0
[ 693.223052] Oops: 0000 [#1] SMP
[ 693.223061] last sysfs file: /sys/devices/xen-backend/vif-1-0/uevent
[ 693.223068] CPU 2
I''ve yet to look at netback_uevent (and dont really have the time to
;o( right now.
Mike.
--- On Tue, 6/8/10, Michael Cook <michaelcook_mjc@yahoo.com> wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - (opensuse 11.3 m7 with
XEN4 on W510 Thinkpad)
To: "xen-users mailing list" <xen-users@lists.xensource.com>,
"Helmut Wieser" <helmut.wieser@ieee.org>
Received: Tuesday, June 8, 2010, 8:54 AM
If I try and unpause the domUs they start booting although the WinXP starts
complaining about scandisk and wants to run through that, if I skip that, I then
get to log in, but then the ~100sec timeout hits and simply closes the domU VM.
So the behaviour seems unrelated to the content in the VM IMO but rather
something XEN environment is waiting on.
This may also suggest that networking or disk access is actually fine and the
hotplug script error message is a bit of a red-herring.
I will try building a VM from scratch to see if this makes any difference but I
have several VMs I need running which would be time consuming to say the least
to re-create from scratch. Hence my hope for a solution to this timeout error.
Mike.
--
Text/Cell: +1.613.447.7407 Email: michael@dtmc.ca
--- On Tue, 6/8/10, Helmut Wieser <helmut.wieser@ieee.org> wrote:
From: Helmut Wieser <helmut.wieser@ieee.org>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes on
opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: "xen-users mailing list" <xen-users@lists.xensource.com>
Cc: michael@dtmc.ca, "Michael Cook" <michaelcook_mjc@yahoo.com>
Received: Tuesday, June 8, 2010, 8:41 AM
Hi Mike,
Then you are definitely facing a different problem than I am. After a
dom0 reboot, my domU machines come up and stay up fine.
Did you try to unpause a domU using xm? Turn on a VNC console to track
whats going on. I suspect it''s working, and then shut down after 100
seconds.
Make sure all required modules are loaded, or built into the kernel.
Also try to add devices as you go, start with a minimum VM first, and
expand as you go.
To downgrade udev you don''t need to compile a kernel. You need to
update your initrd though. Some more info on downgrading can be found
here: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1612
regards,
Helmut
On 08.06.2010 14:22, Michael Cook wrote:
Does what not come up? The dom0 comes up everytime but the domUs start
up and then timeout, in a paused state, with hotplug scripts not
working error every time. Its very reproducable.
Was there any substance to the MAKEDEV posting circa 2006 as there are
no vnd* devices present for the psudeo-virtual-disks. I tried this (as
per opensuse bug comment I added yesterday) and MAKEDEV pumped out a
bunch of errors. To be honest I do not know what I''m doing, other than
surfing for workarounds/solutions. Hopefully someone on this list is
more experienced.
Perhaps a XEN4.0 vs XEN3.x issue? Just guessing but all of this works
fine on XEN3.x on a CentOS 5.4 machine... but CentOS5.4 has no support
for my latest laptop.
I may try the udev downgrade. Do you have any suggestions on how to do
this, is it a package downgrade or do I need to recompile the kernel.
(I''m trying to avoid recompiling/manually compiling stuff as I dont
want to diverge from maintained releases ideally).
Thx,
Mike.
--- On Tue, 6/8/10, Helmut Wieser <helmut.wieser@ieee.org>
wrote:
From: Helmut Wieser <helmut.wieser@ieee.org>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Received: Tuesday, June 8, 2010, 5:15 AM
Does it not even come up after you rebooted the dom0? Because that''s
the issue I experienced.
At first I thougt it was different module load order, or different
kernel parameters, but in the end it turned out that a dom0 reboot is
required to "fix" the hotplug scripts not working issue. Some people
say that downgrading udev to <= 151 works for them. Unfortunately
I''m not one of them.
Can you verify that?
regards,
Helmut
On 07.06.2010 05:58, Michael Cook wrote:
Hi Mark,
Thanks for your help. I will try and provide you some info. Some
background first may help. But please let me know if there are other
logs of interest.
I''ve tried many distributions from my original use of Centos5.3 with
XEN3.x. I have the following domUs which work well in CentOS but I now
wanted to move to a newer, faster host.
domUs: WinXP, Ubuntu 10.04 and RHEL5.3.
The first two are hvms, the second is a pvm, which I''ve not tried yet
and I really want the first two to work as WinXP cannot run as a PVM
from what I know.
I originally found Ubuntu 10.04 supported this W510 laptop pretty well
although they are busy writing driver fixes for USB and screen. Mostly
NVIDIA and Nouveau. Running dom0 Ubunut with NVIDIA or Nouveau doesn''t
work well at all. I think there is an mmap issue from what I''ve read
about it, circa March2010 there were hacks to get it work which have
yet to appear within the kernel drivers and manually trying to add
these to the kernel from XEN git for Ubuntu (Jeremys'') didn''t
work.
Ubuntu 10.04 (2.6.32.x) came up nicely on bare-metal. I then
thought/hoped I could find a number of guides that would get me Ubuntu
10.04 dom0. This took some work but there are a couple of guides to
recompiling and installing with XEN4.0 - then I got stuck with an
earlier kernel which didn''t seem to support any recent updates to W510
drivers (including wlan) and there was still Nouveau bug fixes for the
W510 chipset which to be honest I gave up on trying to manually fix.
I also wasn''t happy with 800x600 resolution and finally found Opensuse
11.3 milestone 7 worked as Opensuse 11.2 is 2.6.31.x and nothing worked
on the W510. CentOS5.4 on the W510 was even worse and with limited
interest & support on CentOS I figured it would be a fair time
until they support W510.
There is a wiki on the W510 which shows a lot of activity in Ubuntu to
fix up the drivers etc for W510 in Ubuntu 10.04. So I''m guessing by
U10.10 things will be sorted but I doubt XEN will be well integrated...
it seems unlikely from all the forum readings I''ve found on the
subject. I''ve added my findings so far wrt XEN to this wiki which
keeps track of the major issues for W510 (mostly in Ubuntu distro)
http://www.thinkwiki.org/wiki/Category:W510
This brought me to opensuse which I dont know very well. The
networking piece is quite different to Ubuntu and even in Ubuntu their
Network Manager drives me nuts. Opensuse seem to have a Network
Manager too through which I created br0 and br1 after reading the
comment in the xend-config.sxp file saying "Opensuse users should not
configure anything here but use the YaST Network configuration tool".
So I''ve probably not set this up properly.
None the less I was surprised as you point out that br0 didn''t have an
IP addr and doesn''t seem able to be tied to the wlan0 interface
(operation not supported message).
Further more the basic network provisioning between eth0 and wlan0
seems awkward and quirky as when eth0 is not connected it still gets an
IP addr. Oddly, it has not done this on this most recent bootup...
eth0 is now provisioned but not assigned an address. "Change Default
Route via DHCP" has always been set. So this is yet another puzzle
with YaST Network Settings. Both br0 and br1 (I tried to bridge one to
eth0 and one to wlan0) are set to DHCP but only one bridge manages to
bridge to eth0. br1 doesn''t because "operation not
supported"
(presumably from ethtool or mii) for the wlan0 driver (new chipset
support for this laptop?).
linux-oit2:/etc/xen # brctl show
bridge name bridge id STP enabled interfaces
br0 8000.00262dfac618 no eth0
br1 8000.000000000000 no
pan0 8000.000000000000 no
Anyway, I was expecting to see peth0 and xenbr0 and the scripts I''ve
run on centos5.3 which create these bridges to specific physical
devices doesn''t seem to work well at all.
Right now I dont know what to trust and obviously I''m using a
pre-release of Opensuse. I''m hoping its a simple case of
misprovisioning the native network settings along iwth the XEN
installation.
I used the example HVM file with XEN4.0 virt-manager under
/etc/xen//examples/ and simply updated the UUID, vif and harddrive
image with that of these domUs. I get the same behaviour in all of
them... timeout with some hotplug script not working.
So for the BIOS, yes, VT-d was disabled and xm info didn''t show any hvm
support. I enabled this in the W510 BIOS and then virt-manager would
allow me to create a new HVM based VM. However... it would then
complain "couldn''t find image" although it wouldn''t
let me (couldn''t
find) a place to define the name of this image. I assume only creating
an image from CD has been tested, then it complained I had no CD in the
drive.
I can try creating a VM (para-virtual for example from scratch) but my
hope was to move these three VMs which are in themselves complete
systems I dont realy want to rebuild from scratch. I also have other
RHEL5.3 VMs that cannot be easily rebuilt.
Obviously I will try and create a new VM from scratch using the
Virt-Manager wizard.
During the opensuse installation I chose partition based disk-set which
is similar ot the Ubuntu installation. The CentOS one uses LVM but I
dont think this would make any difference to running these domUs. Eg
config script which works on CentOS dom0:
name = "WinXP_sp3"
uuid = "79178fd8-d542-4c76-36ec-4791e104aad9"
maxmem = 512
memory = 512
cpus = 1
builder = "hvm"
kernel = "/usr/lib/xen/boot/hvmloader"
boot = "c"
pae = 1
acpi = 1
apic = 1
localtime = 1
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
device_model = "/usr/lib64/xen/bin/qemu-dm"
usb = 1
usbdevice = "tablet"
sdl = 0
vnc = 1
vncunused = 1
keymap = "en-us"
disk = [ "file:/var/lib/libvirt/images/XP-Pro_sp3.img,hda,w"
]
vif = [ "mac=00:16:36:f7:27:39,bridge=xenbr0,script=vif-bridge" ]
parallel = "none"
serial = "pty"
I''d be very interested in working with you to figure out this mystery
as I feel I''m very close after a couple of weeks of pulling my hair out
over kernel support for the W510 and trying to work with XEN.
Ideally, I''d rather not use another distro like opensuse but it has
been the least painful way to at least get XEN & Linux & W510
working together and fortunately the latest candidate release does do
this in a pretty stable environment. This final hurdle of hotplg
scripts is hopefully not too complicated to figure out.
lsmod, lspci and xm info follow....
linux-oit2:/etc/xen # xm info
host : linux-oit2
release : 2.6.34-8-xen
version : #1 SMP 2010-05-17 17:30:24 +0200
machine : x86_64
nr_cpus : 8
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 2
cpu_mhz : 1596
hw_caps :
bfebfbff:28100800:00000000:00001b40:0098e3fd:00000000:00000001:00000000
virt_caps : hvm hvm_directio
total_memory : 8088
free_memory : 149
free_cpus : 0
max_free_memory : 7495
max_para_memory : 7491
max_hvm_memory : 7465
node_to_cpu : node0:0-7
node_to_memory : node0:149
node_to_dma32_mem : node0:89
max_node_id : 0
xen_major : 4
xen_minor : 0
xen_extra : .0_21091_05-2.1
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : 21091
xen_commandline : vgamode=0x314 iommu=1
cc_compiler : gcc version 4.5.0 20100420 [gcc-4_5-branch
revision 158562] (SU
cc_compile_by : abuild
cc_compile_domain :
cc_compile_date : Wed May 19 19:06:40 UTC 2010
xend_config_format : 4
linux-oit2:/etc/xen # lsmod
Module Size Used by
usbbk 23911 0
gntdev 8579 0
netbk 41281 0 [permanent]
rfcomm 81560 4
blkbk 28782 0 [permanent]
blkback_pagemap 2806 1 blkbk
snd_pcm_oss 53455 0
blktap 126702 2 [permanent]
snd_mixer_oss 18817 1 snd_pcm_oss
sco 20103 2
domctl 3227 2 blkbk,blktap
bnep 18047 2
xenbus_be 3706 4 usbbk,netbk,blkbk,blktap
snd_seq 67923 0
snd_seq_device 7834 1 snd_seq
l2cap 62034 16 rfcomm,bnep
edd 10176 0
bridge 85815 3
stp 2331 1 bridge
llc 6103 2 bridge,stp
nouveau 552206 2
ttm 68464 1 nouveau
drm_kms_helper 33008 1 nouveau
drm 220232 4 nouveau,ttm,drm_kms_helper
agpgart 42953 2 ttm,drm
i2c_algo_bit 6696 1 nouveau
af_packet 23133 8
fuse 77053 3
loop 18239 0
dm_mod 86435 0
snd_hda_codec_nvhdmi 15727 4
arc4 1601 2
firewire_ohci 26970 0
ecb 2495 2
firewire_core 61402 1 firewire_ohci
snd_hda_intel 29133 2
crc_itu_t 1747 1 firewire_core
snd_hda_codec 112731 2 snd_hda_codec_nvhdmi,snd_hda_intel
iwlagn 238807 0
uvcvideo 67755 0
iwlcore 299287 1 iwlagn
sdhci_pci 8668 0
snd_hwdep 7708 1 snd_hda_codec
iTCO_wdt 12406 0
mac80211 283755 2 iwlagn,iwlcore
ohci1394 33510 0
videodev 43764 1 uvcvideo
v4l1_compat 16833 2 uvcvideo,videodev
8250_pci 25671 0
snd_pcm 107675 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
btusb 18511 2
sdhci 23126 1 sdhci_pci
v4l2_compat_ioctl32 11225 1 videodev
8250 31155 1 8250_pci
video 25192 0
snd_timer 27486 2 snd_seq,snd_pcm
sr_mod 16396 0
e1000e 152237 0
bluetooth 108637 9 rfcomm,sco,bnep,l2cap,btusb
sg 32951 0
mmc_core 83419 1 sdhci
iTCO_vendor_support 3150 1 iTCO_wdt
pcspkr 2222 0
tpm_tis 13134 0
thinkpad_acpi 83412 0
xhci_hcd 98228 0
cfg80211 182345 3 iwlagn,iwlcore,mac80211
i2c_i801 11881 0
ieee1394 104278 1 ohci1394
i2c_core 32104 6
nouveau,drm_kms_helper,drm,i2c_algo_bit,videodev,i2c_i801
serial_core 25223 1 8250
output 2727 1 video
tpm 17388 1 tpm_tis
rfkill 21959 4 bluetooth,thinkpad_acpi,cfg80211
snd 83486 15
snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_codec_nvhdmi,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer,thinkpad_acpi
snd_page_alloc 9473 2 snd_hda_intel,snd_pcm
wmi 8750 0
battery 12270 0
soundcore 8757 1 snd
ac 4023 0
tpm_bios 6652 1 tpm
button 6925 1 nouveau
joydev 12230 0
ext4 395274 1
jbd2 98208 1 ext4
crc16 1715 2 l2cap,ext4
sd_mod 41170 3
ehci_hcd 60206 0
usbcore 233034 6 usbbk,uvcvideo,btusb,xhci_hcd,ehci_hcd
xenblk 26162 0
cdrom 43083 2 sr_mod,xenblk
xennet 37763 0
fan 4527 0
processor 42918 0
ahci 42648 2
libata 211362 1 ahci
scsi_mod 191176 4 sr_mod,sg,sd_mod,libata
thermal 20593 0
thermal_sys 18006 4 video,fan,processor,thermal
hwmon 2712 2 thinkpad_acpi,thermal_sys
linux-oit2:/etc/xen # lspci
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root
Port 1 (rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System
Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore
and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System
Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor
Miscellaneous Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link
(rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing
and Protocol Registers (rev 11)
00:16.0 Communication controller: Intel Corporation 5 Series/3400
Series Chipset HECI Controller (rev 06)
00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series
Chipset KT Controller (rev 06)
00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network
Connection (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset
High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 2 (rev 06)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 4 (rev 06)
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 5 (rev 06)
00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 7 (rev 06)
00:1c.7 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 8 (rev 06)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC
Interface Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset
6 port SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus
Controller (rev 06)
01:00.0 VGA compatible controller: nVidia Corporation GT216 [Quadro FX
880M] (rev a2)
01:00.1 Audio device: nVidia Corporation High Definition Audio
Controller (rev a1)
03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300
(rev 35)
0d:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01)
0d:00.1 System peripheral: Ricoh Co Ltd Device e230 (rev 01)
0f:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host
Controller (rev 03)
17:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01)
17:00.3 FireWire (IEEE 1394): Ricoh Co Ltd Device e832 (rev 01)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath
Architecture Generic Non-Core Registers (rev 04)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath
Architecture System Address Decoder (rev 04)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev
04)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0
(rev 04)
ff:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller (rev 04)
ff:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Target Address Decoder (rev 04)
ff:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Test Registers (rev 04)
ff:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Control Registers (rev 04)
ff:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Address Registers (rev 04)
ff:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Rank Registers (rev 04)
ff:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Thermal Control Registers (rev 04)
ff:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Control Registers (rev 04)
ff:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Address Registers (rev 04)
ff:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Rank Registers (rev 04)
ff:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Thermal Control Registers (rev 04)
--- On Sun, 6/6/10, Mark Pryor <tlviewer@yahoo.com>
wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 9:48 PM
Mike,
Let me give you a broad checklist of things that may be important.
I just did a search of the lists.xensource.com/xen-users list and there
are no posts about
your hardware.
The Thinkpad w510 Notebook.
------------
many times a notebook like this will have a stealth bios, or a
limited bios. Are you
sure that HVM is enabled?
Your choice of suse 11.3 is good and should make it much easier to get
Xen 4.0 working. I like the way your Network looks, but I didn''t see
any IP address for your
br0- why not? This should work with a non-xen kernel too.
Your first domU is Winxp sp3. This might be a problem if your HD needs
AHCI or strange raid/SATA drivers not included with Winxp.
I think a better domU would be the same source you used for dom0. This
should work PV and won''t depend if your bios supports HVM.
Oh, can you post your
#xm info
#lsmod
#lspci
for dom0
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com>
wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: "Mark Pryor" <tlviewer@yahoo.com>
Date: Sunday, June 6, 2010, 3:40 PM
Yes, I tried this, and hte same error. I then
removed
the vif altogether and the similiar hotplugin error appeared for the
harddrive. Following that, found the MAKEDEV issue but I''m not sure
what needs to be done there.
--- On Sun, 6/6/10, Mark Pryor <tlviewer@yahoo.com>
wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 5:57 PM
Mike,
Manual bridge is br0/br1.
In your HVM guest config, you should have
vif = [ ''bridge=br0'' ]
if you put xenbr0 above that would explain the problem too.
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com>
wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Date: Sunday, June 6, 2010, 2:34 PM
Thanks
for
the suggestion, I assume I should keep the br0/br1... but trying
your suggestion I still see the same error. If I comment out the vif
in the HVM config file, I get a similar error hotplug script but for
the disk.
After mucking about with this some more I think the HVM should boot
(and not timeout) even if I have the wrong bridges/network scripts.
I''m not at the stage yet where I have no connectivity... the VM
doesn''t'' stay up long enough because of these hotplugin script
timeout/crash.
Hence my ramblings towards the end of the bug about finding postings on
MAKEDEV and missing /dev/ entries but haven''t managed to add these as
MAKEDEV doesn''t seem to exist on my vanilla installation and
I''ve not
had to do this on say a Centos XEN environment but that doens''t work
for other reasons (hw support) on my newer laptop.
--- On Sun,
6/6/10,
Mark Pryor <tlviewer@yahoo.com>
wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 5:04 PM
Mike,
In your Xen config: xend-config.sxp
try to comment out
#(network-script network-bridge)
and uncomment
(network-script network-dummy)
and restart xend.
once you have a manual bridge, there is no need for Xen''s
network-bridge script.
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com>
wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: [Xen-users] Hotplug scripts not working - Networking woes on
opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Date: Sunday, June 6, 2010, 12:52 PM
Anyone can
help me with this problem I''ve described here:
https://bugzilla.novell.com/show_bug.cgi?id=612006
I''ve had XEN4.0 working on CentOS 5.4 platform without these problems.
I''m trying to do the same now with a newer laptop and CentOS
didn''t
recognise half hte drivers. The latest opensuse 11.3 does have these
drivers and specifically nouveau integration and XEN which has got me
98% of the way there... I''m presently stuck on the networking part
which looks different/problematic compared my experience on CentOS
machine.
Now the VMs launch but I see various Hotplug scripts not working
messages and the VM instantly stops running.
Thanks in advance,
Mike
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Michael Cook
2010-Jun-08 14:27 UTC
Re: [Xen-users] Hotplug scripts not working - (opensuse 11.3 m7 with XEN4 on W510 Thinkpad)
NULL ptr work in progress:
http://lists.xensource.com/archives/html/xen-devel/2010-05/msg01590.html
FWIW if I comment out the "vif =" line this oops goes away, but the
hotscripts
plugin still persists. No dmesg/oops/xend-debug output this time ;o(
--- On Tue, 6/8/10, Michael Cook <michaelcook_mjc@yahoo.com> wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - netback_uevent+0x73/0x100
NULL ptr deref (opensuse 11.3 m7 with XEN4 on W510 Thinkpad)
To: "xen-users mailing list" <xen-users@lists.xensource.com>,
"Helmut Wieser" <helmut.wieser@ieee.org>
Received: Tuesday, June 8, 2010, 9:38 AM
Looking a bit further at this the XEND is actually de-referencing a null ptr
when starting up the VM. I''ve added the traceback to the opensuse
bugzilla report:
https://bugzilla.novell.com/show_bug.cgi?id=612006
[ 693.222999] BUG: unable to handle kernel NULL pointer dereference at
0000000000000150
[ 693.223015] IP: [<ffffffffa0889a63>] netback_uevent+0x73/0x100 [netbk]
[ 693.223038] PGD 189cef067 PUD 189d30067 PMD 0
[ 693.223052] Oops: 0000 [#1] SMP
[ 693.223061] last sysfs file: /sys/devices/xen-backend/vif-1-0/uevent
[ 693.223068] CPU 2
I''ve yet to look at netback_uevent (and dont really have the time to
;o( right
now.
Mike.
--- On Tue, 6/8/10, Michael Cook <michaelcook_mjc@yahoo.com> wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - (opensuse 11.3 m7 with
XEN4 on W510 Thinkpad)
To: "xen-users mailing list" <xen-users@lists.xensource.com>,
"Helmut Wieser" <helmut.wieser@ieee.org>
Received: Tuesday, June 8, 2010, 8:54 AM
If I try and unpause the domUs they start booting although the WinXP starts
complaining about scandisk and wants to run through that, if I skip that, I then
get to log in, but then the ~100sec timeout hits and simply closes the domU
VM. So the behaviour seems unrelated to the content in the VM IMO but rather
something XEN environment is waiting on.
This may also suggest that networking or disk access is actually fine and the
hotplug script error message is a bit of a red-herring.
I will try building a VM from scratch to see if this makes any difference but I
have several VMs I need running which would be time consuming to say the least
to re-create from scratch. Hence my hope for a solution to this timeout error.
Mike.
--
Text/Cell: +1.613.447.7407 Email: michael@dtmc.ca
--- On Tue, 6/8/10, Helmut Wieser <helmut.wieser@ieee.org> wrote:
From: Helmut Wieser <helmut.wieser@ieee.org>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes on
opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: "xen-users mailing list" <xen-users@lists.xensource.com>
Cc: michael@dtmc.ca, "Michael Cook" <michaelcook_mjc@yahoo.com>
Received: Tuesday, June 8, 2010, 8:41 AM
Hi Mike,
Then you are definitely facing a different problem than I am. After a
dom0 reboot, my domU machines come up and stay up fine.
Did you try to unpause a domU using xm? Turn on a VNC console to track
whats going on. I suspect it''s working, and then shut down after 100
seconds.
Make sure all required modules are loaded, or built into the kernel.
Also try to add devices as you go, start with a minimum VM first, and
expand as you go.
To downgrade udev you don''t need to compile a kernel. You need to
update your initrd though. Some more info on downgrading can be found
here: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1612
regards,
Helmut
On 08.06.2010 14:22, Michael Cook wrote:
Does what not come up? The dom0 comes up everytime but the domUs start
up and then timeout, in a paused state, with hotplug scripts not
working error every time. Its very reproducable.
Was there any substance to the MAKEDEV posting circa 2006 as there are
no vnd* devices present for the psudeo-virtual-disks. I tried this (as
per opensuse bug comment I added yesterday) and MAKEDEV pumped out a
bunch of errors. To be honest I do not know what I''m doing, other than
surfing for workarounds/solutions. Hopefully someone on this list is
more experienced.
Perhaps a XEN4.0 vs XEN3.x issue? Just guessing but all of this works
fine on XEN3.x on a CentOS 5.4 machine... but CentOS5.4 has no support
for my latest laptop.
I may try the udev downgrade. Do you have any suggestions on how to do
this, is it a package downgrade or do I need to recompile the kernel.
(I''m trying to avoid recompiling/manually compiling stuff as I dont
want to diverge from maintained releases ideally).
Thx,
Mike.
--- On Tue, 6/8/10, Helmut Wieser <helmut.wieser@ieee.org>
wrote:
From: Helmut Wieser <helmut.wieser@ieee.org>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Received: Tuesday, June 8, 2010, 5:15 AM
Does it not even come up after you rebooted the dom0? Because that''s
the issue I experienced.
At first I thougt it was different module load order, or different
kernel parameters, but in the end it turned out that a dom0 reboot is
required to "fix" the hotplug scripts not working issue. Some people
say that downgrading udev to <= 151 works for them. Unfortunately
I''m not one of them.
Can you verify that?
regards,
Helmut
On 07.06.2010 05:58, Michael Cook wrote:
Hi Mark,
Thanks for your help. I will try and provide you some info. Some
background first may help. But please let me know if there are other
logs of interest.
I''ve tried many distributions from my original use of Centos5.3 with
XEN3.x. I have the following domUs which work well in CentOS but I now
wanted to move to a newer, faster host.
domUs: WinXP, Ubuntu 10.04 and RHEL5.3.
The first two are hvms, the second is a pvm, which I''ve not tried yet
and I really want the first two to work as WinXP cannot run as a PVM
from what I know.
I originally found Ubuntu 10.04 supported this W510 laptop pretty well
although they are busy writing driver fixes for USB and screen. Mostly
NVIDIA and Nouveau. Running dom0 Ubunut with NVIDIA or Nouveau doesn''t
work well at all. I think there is an mmap issue from what I''ve read
about it, circa March2010 there were hacks to get it work which have
yet to appear within the kernel drivers and manually trying to add
these to the kernel from XEN git for Ubuntu (Jeremys'') didn''t
work.
Ubuntu 10.04 (2.6.32.x) came up nicely on bare-metal. I then
thought/hoped I could find a number of guides that would get me Ubuntu
10.04 dom0. This took some work but there are a couple of guides to
recompiling and installing with XEN4.0 - then I got stuck with an
earlier kernel which didn''t seem to support any recent updates to W510
drivers (including wlan) and there was still Nouveau bug fixes for the
W510 chipset which to be honest I gave up on trying to manually fix.
I also wasn''t happy with 800x600 resolution and finally found Opensuse
11.3 milestone 7 worked as Opensuse 11.2 is 2.6.31.x and nothing worked
on the W510. CentOS5.4 on the W510 was even worse and with limited
interest & support on CentOS I figured it would be a fair time
until they support W510.
There is a wiki on the W510 which shows a lot of activity in Ubuntu to
fix up the drivers etc for W510 in Ubuntu 10.04. So I''m guessing by
U10.10 things will be sorted but I doubt XEN will be well integrated...
it seems unlikely from all the forum readings I''ve found on the
subject. I''ve added my findings so far wrt XEN to this wiki which
keeps track of the major issues for W510 (mostly in Ubuntu distro)
http://www.thinkwiki.org/wiki/Category:W510
This brought me to opensuse which I dont know very well. The
networking piece is quite different to Ubuntu and even in Ubuntu their
Network Manager drives me nuts. Opensuse seem to have a Network
Manager too through which I created br0 and br1 after reading the
comment in the xend-config.sxp file saying "Opensuse users should not
configure anything here but use the YaST Network configuration tool".
So I''ve probably not set this up properly.
None the less I was surprised as you point out that br0 didn''t have an
IP addr and doesn''t seem able to be tied to the wlan0 interface
(operation not supported message).
Further more the basic network provisioning between eth0 and wlan0
seems awkward and quirky as when eth0 is not connected it still gets an
IP addr. Oddly, it has not done this on this most recent bootup...
eth0 is now provisioned but not assigned an address. "Change Default
Route via DHCP" has always been set. So this is yet another puzzle
with YaST Network Settings. Both br0 and br1 (I tried to bridge one to
eth0 and one to wlan0) are set to DHCP but only one bridge manages to
bridge to eth0. br1 doesn''t because "operation not
supported"
(presumably from ethtool or mii) for the wlan0 driver (new chipset
support for this laptop?).
linux-oit2:/etc/xen # brctl show
bridge name bridge id STP enabled interfaces
br0 8000.00262dfac618 no eth0
br1 8000.000000000000 no
pan0 8000.000000000000 no
Anyway, I was expecting to see peth0 and xenbr0 and the scripts I''ve
run on centos5.3 which create these bridges to specific physical
devices doesn''t seem to work well at all.
Right now I dont know what to trust and obviously I''m using a
pre-release of Opensuse. I''m hoping its a simple case of
misprovisioning the native network settings along iwth the XEN
installation.
I used the example HVM file with XEN4.0 virt-manager under
/etc/xen//examples/ and simply updated the UUID, vif and harddrive
image with that of these domUs. I get the same behaviour in all of
them... timeout with some hotplug script not working.
So for the BIOS, yes, VT-d was disabled and xm info didn''t show any hvm
support. I enabled this in the W510 BIOS and then virt-manager would
allow me to create a new HVM based VM. However... it would then
complain "couldn''t find image" although it wouldn''t
let me (couldn''t
find) a place to define the name of this image. I assume only creating
an image from CD has been tested, then it complained I had no CD in the
drive.
I can try creating a VM (para-virtual for example from scratch) but my
hope was to move these three VMs which are in themselves complete
systems I dont realy want to rebuild from scratch. I also have other
RHEL5.3 VMs that cannot be easily rebuilt.
Obviously I will try and create a new VM from scratch using the
Virt-Manager wizard.
During the opensuse installation I chose partition based disk-set which
is similar ot the Ubuntu installation. The CentOS one uses LVM but I
dont think this would make any difference to running these domUs. Eg
config script which works on CentOS dom0:
name = "WinXP_sp3"
uuid = "79178fd8-d542-4c76-36ec-4791e104aad9"
maxmem = 512
memory = 512
cpus = 1
builder = "hvm"
kernel = "/usr/lib/xen/boot/hvmloader"
boot = "c"
pae = 1
acpi = 1
apic = 1
localtime = 1
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
device_model = "/usr/lib64/xen/bin/qemu-dm"
usb = 1
usbdevice = "tablet"
sdl = 0
vnc = 1
vncunused = 1
keymap = "en-us"
disk = [ "file:/var/lib/libvirt/images/XP-Pro_sp3.img,hda,w"
]
vif = [ "mac=00:16:36:f7:27:39,bridge=xenbr0,script=vif-bridge" ]
parallel = "none"
serial = "pty"
I''d be very interested in working with you to figure out this mystery
as I feel I''m very close after a couple of weeks of pulling my hair out
over kernel support for the W510 and trying to work with XEN.
Ideally, I''d rather not use another distro like opensuse but it has
been the least painful way to at least get XEN & Linux & W510
working together and fortunately the latest candidate release does do
this in a pretty stable environment. This final hurdle of hotplg
scripts is hopefully not too complicated to figure out.
lsmod, lspci and xm info follow....
linux-oit2:/etc/xen # xm info
host : linux-oit2
release : 2.6.34-8-xen
version : #1 SMP 2010-05-17 17:30:24 +0200
machine : x86_64
nr_cpus : 8
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 2
cpu_mhz : 1596
hw_caps :
bfebfbff:28100800:00000000:00001b40:0098e3fd:00000000:00000001:00000000
virt_caps : hvm hvm_directio
total_memory : 8088
free_memory : 149
free_cpus : 0
max_free_memory : 7495
max_para_memory : 7491
max_hvm_memory : 7465
node_to_cpu : node0:0-7
node_to_memory : node0:149
node_to_dma32_mem : node0:89
max_node_id : 0
xen_major : 4
xen_minor : 0
xen_extra : .0_21091_05-2.1
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : 21091
xen_commandline : vgamode=0x314 iommu=1
cc_compiler : gcc version 4.5.0 20100420 [gcc-4_5-branch
revision 158562] (SU
cc_compile_by : abuild
cc_compile_domain :
cc_compile_date : Wed May 19 19:06:40 UTC 2010
xend_config_format : 4
linux-oit2:/etc/xen # lsmod
Module Size Used by
usbbk 23911 0
gntdev 8579 0
netbk 41281 0 [permanent]
rfcomm 81560 4
blkbk 28782 0 [permanent]
blkback_pagemap 2806 1 blkbk
snd_pcm_oss 53455 0
blktap 126702 2 [permanent]
snd_mixer_oss 18817 1 snd_pcm_oss
sco 20103 2
domctl 3227 2 blkbk,blktap
bnep 18047 2
xenbus_be 3706 4 usbbk,netbk,blkbk,blktap
snd_seq 67923 0
snd_seq_device 7834 1 snd_seq
l2cap 62034 16 rfcomm,bnep
edd 10176 0
bridge 85815 3
stp 2331 1 bridge
llc 6103 2 bridge,stp
nouveau 552206 2
ttm 68464 1 nouveau
drm_kms_helper 33008 1 nouveau
drm 220232 4 nouveau,ttm,drm_kms_helper
agpgart 42953 2 ttm,drm
i2c_algo_bit 6696 1 nouveau
af_packet 23133 8
fuse 77053 3
loop 18239 0
dm_mod 86435 0
snd_hda_codec_nvhdmi 15727 4
arc4 1601 2
firewire_ohci 26970 0
ecb 2495 2
firewire_core 61402 1 firewire_ohci
snd_hda_intel 29133 2
crc_itu_t 1747 1 firewire_core
snd_hda_codec 112731 2 snd_hda_codec_nvhdmi,snd_hda_intel
iwlagn 238807 0
uvcvideo 67755 0
iwlcore 299287 1 iwlagn
sdhci_pci 8668 0
snd_hwdep 7708 1 snd_hda_codec
iTCO_wdt 12406 0
mac80211 283755 2 iwlagn,iwlcore
ohci1394 33510 0
videodev 43764 1 uvcvideo
v4l1_compat 16833 2 uvcvideo,videodev
8250_pci 25671 0
snd_pcm 107675 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
btusb 18511 2
sdhci 23126 1 sdhci_pci
v4l2_compat_ioctl32 11225 1 videodev
8250 31155 1 8250_pci
video 25192 0
snd_timer 27486 2 snd_seq,snd_pcm
sr_mod 16396 0
e1000e 152237 0
bluetooth 108637 9 rfcomm,sco,bnep,l2cap,btusb
sg 32951 0
mmc_core 83419 1 sdhci
iTCO_vendor_support 3150 1 iTCO_wdt
pcspkr 2222 0
tpm_tis 13134 0
thinkpad_acpi 83412 0
xhci_hcd 98228 0
cfg80211 182345 3 iwlagn,iwlcore,mac80211
i2c_i801 11881 0
ieee1394 104278 1 ohci1394
i2c_core 32104 6
nouveau,drm_kms_helper,drm,i2c_algo_bit,videodev,i2c_i801
serial_core 25223 1 8250
output 2727 1 video
tpm 17388 1 tpm_tis
rfkill 21959 4 bluetooth,thinkpad_acpi,cfg80211
snd 83486 15
snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_codec_nvhdmi,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer,thinkpad_acpi
snd_page_alloc 9473 2 snd_hda_intel,snd_pcm
wmi 8750 0
battery 12270 0
soundcore 8757 1 snd
ac 4023 0
tpm_bios 6652 1 tpm
button 6925 1 nouveau
joydev 12230 0
ext4 395274 1
jbd2 98208 1 ext4
crc16 1715 2 l2cap,ext4
sd_mod 41170 3
ehci_hcd 60206 0
usbcore 233034 6 usbbk,uvcvideo,btusb,xhci_hcd,ehci_hcd
xenblk 26162 0
cdrom 43083 2 sr_mod,xenblk
xennet 37763 0
fan 4527 0
processor 42918 0
ahci 42648 2
libata 211362 1 ahci
scsi_mod 191176 4 sr_mod,sg,sd_mod,libata
thermal 20593 0
thermal_sys 18006 4 video,fan,processor,thermal
hwmon 2712 2 thinkpad_acpi,thermal_sys
linux-oit2:/etc/xen # lspci
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root
Port 1 (rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System
Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore
and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System
Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor
Miscellaneous Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link
(rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing
and Protocol Registers (rev 11)
00:16.0 Communication controller: Intel Corporation 5 Series/3400
Series Chipset HECI Controller (rev 06)
00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series
Chipset KT Controller (rev 06)
00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network
Connection (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset
High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 2 (rev 06)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 4 (rev 06)
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 5 (rev 06)
00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 7 (rev 06)
00:1c.7 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 8 (rev 06)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC
Interface Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset
6 port SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus
Controller (rev 06)
01:00.0 VGA compatible controller: nVidia Corporation GT216 [Quadro FX
880M] (rev a2)
01:00.1 Audio device: nVidia Corporation High Definition Audio
Controller (rev a1)
03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300
(rev 35)
0d:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01)
0d:00.1 System peripheral: Ricoh Co Ltd Device e230 (rev 01)
0f:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host
Controller (rev 03)
17:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01)
17:00.3 FireWire (IEEE 1394): Ricoh Co Ltd Device e832 (rev 01)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath
Architecture Generic Non-Core Registers (rev 04)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath
Architecture System Address Decoder (rev 04)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev
04)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0
(rev 04)
ff:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller (rev 04)
ff:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Target Address Decoder (rev 04)
ff:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Test Registers (rev 04)
ff:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Control Registers (rev 04)
ff:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Address Registers (rev 04)
ff:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Rank Registers (rev 04)
ff:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Thermal Control Registers (rev 04)
ff:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Control Registers (rev 04)
ff:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Address Registers (rev 04)
ff:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Rank Registers (rev 04)
ff:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Thermal Control Registers (rev 04)
--- On Sun, 6/6/10, Mark Pryor <tlviewer@yahoo.com>
wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 9:48 PM
Mike,
Let me give you a broad checklist of things that may be important.
I just did a search of the lists.xensource.com/xen-users list and there
are no posts about
your hardware.
The Thinkpad w510 Notebook.
------------
many times a notebook like this will have a stealth bios, or a
limited bios. Are you
sure that HVM is enabled?
Your choice of suse 11.3 is good and should make it much easier to get
Xen 4.0 working. I like the way your Network looks, but I didn''t see
any IP address for your
br0- why not? This should work with a non-xen kernel too.
Your first domU is Winxp sp3. This might be a problem if your HD needs
AHCI or strange raid/SATA drivers not included with Winxp.
I think a better domU would be the same source you used for dom0. This
should work PV and won''t depend if your bios supports HVM.
Oh, can you post your
#xm info
#lsmod
#lspci
for dom0
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com>
wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: "Mark Pryor" <tlviewer@yahoo.com>
Date: Sunday, June 6, 2010, 3:40 PM
Yes, I tried this, and hte same error. I then
removed
the vif altogether and the similiar hotplugin error appeared for the
harddrive. Following that, found the MAKEDEV issue but I''m not sure
what needs to be done there.
--- On Sun, 6/6/10, Mark Pryor <tlviewer@yahoo.com>
wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 5:57 PM
Mike,
Manual bridge is br0/br1.
In your HVM guest config, you should have
vif = [ ''bridge=br0'' ]
if you put xenbr0 above that would explain the problem too.
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com>
wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Date: Sunday, June 6, 2010, 2:34 PM
Thanks
for
the suggestion, I assume I should keep the br0/br1... but trying
your suggestion I still see the same error. If I comment out the vif
in the HVM config file, I get a similar error hotplug script but for
the disk.
After mucking about with this some more I think the HVM should boot
(and not timeout) even if I have the wrong bridges/network scripts.
I''m not at the stage yet where I have no connectivity... the VM
doesn''t'' stay up long enough because of these hotplugin script
timeout/crash.
Hence my ramblings towards the end of the bug about finding postings on
MAKEDEV and missing /dev/ entries but haven''t managed to add these as
MAKEDEV doesn''t seem to exist on my vanilla installation and
I''ve not
had to do this on say a Centos XEN environment but that doens''t work
for other reasons (hw support) on my newer laptop.
--- On Sun,
6/6/10,
Mark Pryor <tlviewer@yahoo.com>
wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 5:04 PM
Mike,
In your Xen config: xend-config.sxp
try to comment out
#(network-script network-bridge)
and uncomment
(network-script network-dummy)
and restart xend.
once you have a manual bridge, there is no need for Xen''s
network-bridge script.
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com>
wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: [Xen-users] Hotplug scripts not working - Networking woes on
opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Date: Sunday, June 6, 2010, 12:52 PM
Anyone can
help me with this problem I''ve described here:
https://bugzilla.novell.com/show_bug.cgi?id=612006
I''ve had XEN4.0 working on CentOS 5.4 platform without these problems.
I''m trying to do the same now with a newer laptop and CentOS
didn''t
recognise half hte drivers. The latest opensuse 11.3 does have these
drivers and specifically nouveau integration and XEN which has got me
98% of the way there... I''m presently stuck on the networking part
which looks different/problematic compared my experience on CentOS
machine.
Now the VMs launch but I see various Hotplug scripts not working
messages and the VM instantly stops running.
Thanks in advance,
Mike
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Michael Cook
2010-Jun-10 14:13 UTC
Re: [Xen-users] Hotplug scripts not working - (opensuse 11.3 m7 with XEN4 on W510 Thinkpad)
If I use Virt-Manager 0.8 there just doesn''t seem to be enough options
to build a XEN domU from installation or DVD. There seems to be some steps
missing to define these things and the summary of the machine to be created is
present, hit next and it complains either the DVD is missing or existing image
file.
Maybe I''m missing something but on the CentOS5.4 with XEN3.4 and
Virtual Manager 0.8 I get many more options to properly build a guest domU VM
(and it works).
Mike.
--- On Tue, 6/8/10, Michael Cook <michaelcook_mjc@yahoo.com> wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - (opensuse 11.3 m7 with
XEN4 on W510 Thinkpad)
To: "xen-users mailing list" <xen-users@lists.xensource.com>
Received: Tuesday, June 8, 2010, 10:27 AM
NULL ptr work in progress:
http://lists.xensource.com/archives/html/xen-devel/2010-05/msg01590.html
FWIW if I comment out the "vif =" line this oops goes away, but the
hotscripts
plugin still persists. No dmesg/oops/xend-debug output this time ;o(
--- On Tue, 6/8/10, Michael Cook <michaelcook_mjc@yahoo.com> wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - netback_uevent+0x73/0x100
NULL ptr deref (opensuse 11.3 m7 with XEN4 on W510 Thinkpad)
To: "xen-users mailing list" <xen-users@lists.xensource.com>,
"Helmut Wieser" <helmut.wieser@ieee.org>
Received: Tuesday, June 8, 2010, 9:38 AM
Looking a bit further at this the XEND is actually de-referencing a null ptr
when starting up the VM. I''ve added the traceback to the opensuse
bugzilla report:
https://bugzilla.novell.com/show_bug.cgi?id=612006
[ 693.222999] BUG: unable to handle kernel NULL pointer dereference at
0000000000000150
[ 693.223015] IP: [<ffffffffa0889a63>] netback_uevent+0x73/0x100 [netbk]
[ 693.223038] PGD 189cef067 PUD 189d30067 PMD 0
[ 693.223052] Oops: 0000 [#1] SMP
[ 693.223061] last sysfs file:
/sys/devices/xen-backend/vif-1-0/uevent
[ 693.223068] CPU 2
I''ve yet to look at netback_uevent (and dont really have the time to
;o( right
now.
Mike.
--- On Tue, 6/8/10, Michael Cook <michaelcook_mjc@yahoo.com> wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - (opensuse 11.3 m7 with
XEN4 on W510 Thinkpad)
To: "xen-users mailing list" <xen-users@lists.xensource.com>,
"Helmut Wieser" <helmut.wieser@ieee.org>
Received: Tuesday, June 8, 2010, 8:54 AM
If I try and unpause the domUs they start booting although the WinXP starts
complaining about scandisk and wants to run through that, if I skip that, I then
get to log in, but then the ~100sec timeout hits and simply closes the domU
VM. So the behaviour seems unrelated to the content in the VM IMO but rather
something XEN environment is waiting on.
This may also suggest that networking or disk access is actually fine and the
hotplug script error message is a bit of a red-herring.
I will try building a VM from scratch to see if this makes any difference but I
have several VMs I need running which would be time consuming to say the least
to re-create from scratch. Hence my hope for a solution to this timeout error.
Mike.
--
Text/Cell: +1.613.447.7407 Email: michael@dtmc.ca
--- On Tue, 6/8/10, Helmut Wieser <helmut.wieser@ieee.org> wrote:
From: Helmut Wieser <helmut.wieser@ieee.org>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes on
opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: "xen-users mailing list" <xen-users@lists.xensource.com>
Cc: michael@dtmc.ca, "Michael Cook" <michaelcook_mjc@yahoo.com>
Received: Tuesday, June 8, 2010, 8:41 AM
Hi Mike,
Then you are definitely facing a different problem than I am. After a
dom0 reboot, my domU machines come up and stay up fine.
Did you try to unpause a domU using xm? Turn on a VNC console to track
whats going on. I suspect it''s working, and then shut down after 100
seconds.
Make sure all required modules are loaded, or built into the kernel.
Also try to add devices as you go, start with a minimum VM first, and
expand as you go.
To downgrade udev you don''t need to compile a kernel. You need to
update your initrd though. Some more info on downgrading can be found
here: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1612
regards,
Helmut
On 08.06.2010 14:22, Michael Cook wrote:
Does what not come up? The dom0 comes up everytime but the domUs start
up and then timeout, in a paused state, with hotplug scripts not
working error every time. Its very reproducable.
Was there any substance to the MAKEDEV posting circa 2006 as there are
no vnd* devices present for the psudeo-virtual-disks. I tried this (as
per opensuse bug comment I added yesterday) and MAKEDEV pumped out a
bunch of errors. To be honest I do not know what I''m doing, other than
surfing for workarounds/solutions. Hopefully someone on this list is
more experienced.
Perhaps a XEN4.0 vs XEN3.x issue? Just guessing but all of this works
fine on XEN3.x on a CentOS 5.4 machine... but CentOS5.4 has no support
for my latest laptop.
I may try the udev downgrade. Do you have any suggestions on how to do
this, is it a package downgrade or do I need to recompile the kernel.
(I''m trying to avoid recompiling/manually compiling stuff as I dont
want to diverge from maintained releases ideally).
Thx,
Mike.
--- On Tue, 6/8/10, Helmut Wieser <helmut.wieser@ieee.org>
wrote:
From: Helmut Wieser <helmut.wieser@ieee.org>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Received: Tuesday, June 8, 2010, 5:15 AM
Does it not even come up after you rebooted the dom0? Because that''s
the issue I experienced.
At first I thougt it was different module load order, or different
kernel parameters, but in the end it turned out that a dom0 reboot is
required to "fix" the hotplug scripts not working issue. Some people
say that downgrading udev to <= 151 works for them. Unfortunately
I''m not one of them.
Can you verify that?
regards,
Helmut
On 07.06.2010 05:58, Michael Cook wrote:
Hi Mark,
Thanks for your help. I will try and provide you some info. Some
background first may help. But please let me know if there are other
logs of interest.
I''ve tried many distributions from my original use of Centos5.3 with
XEN3.x. I have the following domUs which work well in CentOS but I now
wanted to move to a newer, faster host.
domUs: WinXP, Ubuntu 10.04 and RHEL5.3.
The first two are hvms, the second is a pvm, which I''ve not tried yet
and I really want the first two to work as WinXP cannot run as a PVM
from what I know.
I originally found Ubuntu 10.04 supported this W510 laptop pretty well
although they are busy writing driver fixes for USB and screen. Mostly
NVIDIA and Nouveau. Running dom0 Ubunut with NVIDIA or Nouveau doesn''t
work well at all. I think there is an mmap issue from what I''ve read
about it, circa March2010 there were hacks to get it work which have
yet to appear within the kernel drivers and manually trying to add
these to the kernel from XEN git for Ubuntu (Jeremys'') didn''t
work.
Ubuntu 10.04 (2.6.32.x) came up nicely on bare-metal. I then
thought/hoped I could find a number of guides that would get me Ubuntu
10.04 dom0. This took some work but there are a couple of guides to
recompiling and installing with XEN4.0 - then I got stuck with an
earlier kernel which didn''t seem to support any recent updates to W510
drivers (including wlan) and there was still Nouveau bug fixes for the
W510 chipset which to be honest I gave up on trying to manually fix.
I also wasn''t happy with 800x600 resolution and finally found Opensuse
11.3 milestone 7 worked as Opensuse 11.2 is 2.6.31.x and nothing worked
on the W510. CentOS5.4 on the W510 was even worse and with limited
interest & support on CentOS I figured it would be a fair time
until they support W510.
There is a wiki on the W510 which shows a lot of activity in Ubuntu to
fix up the drivers etc for W510 in Ubuntu 10.04. So I''m guessing by
U10.10 things will be sorted but I doubt XEN will be well integrated...
it seems unlikely from all the forum readings I''ve found on the
subject. I''ve added my findings so far wrt XEN to this wiki which
keeps track of the major issues for W510 (mostly in Ubuntu distro)
http://www.thinkwiki.org/wiki/Category:W510
This brought me to opensuse which I dont know very well. The
networking piece is quite different to Ubuntu and even in Ubuntu their
Network Manager drives me nuts. Opensuse seem to have a Network
Manager too through which I created br0 and br1 after reading the
comment in the xend-config.sxp file saying "Opensuse users should not
configure anything here but use the YaST Network configuration tool".
So I''ve probably not set this up properly.
None the less I was surprised as you point out that br0 didn''t have an
IP addr and doesn''t seem able to be tied to the wlan0 interface
(operation not supported message).
Further more the basic network provisioning between eth0 and wlan0
seems awkward and quirky as when eth0 is not connected it still gets an
IP addr. Oddly, it has not done this on this most recent bootup...
eth0 is now provisioned but not assigned an address. "Change Default
Route via DHCP" has always been set. So this is yet another puzzle
with YaST Network Settings. Both br0 and br1 (I tried to bridge one to
eth0 and one to wlan0) are set to DHCP but only one bridge manages to
bridge to eth0. br1 doesn''t because "operation not
supported"
(presumably from ethtool or mii) for the wlan0 driver (new chipset
support for this laptop?).
linux-oit2:/etc/xen # brctl show
bridge name bridge id STP enabled interfaces
br0 8000.00262dfac618 no eth0
br1 8000.000000000000 no
pan0 8000.000000000000 no
Anyway, I was expecting to see peth0 and xenbr0 and the scripts I''ve
run on centos5.3 which create these bridges to specific physical
devices doesn''t seem to work well at all.
Right now I dont know what to trust and obviously I''m using a
pre-release of Opensuse. I''m hoping its a simple case of
misprovisioning the native network settings along iwth the XEN
installation.
I used the example HVM file with XEN4.0 virt-manager under
/etc/xen//examples/ and simply updated the UUID, vif and harddrive
image with that of these domUs. I get the same behaviour in all of
them... timeout with some hotplug script not working.
So for the BIOS, yes, VT-d was disabled and xm info didn''t show any hvm
support. I enabled this in the W510 BIOS and then virt-manager would
allow me to create a new HVM based VM. However... it would then
complain "couldn''t find image" although it wouldn''t
let me (couldn''t
find) a place to define the name of this image. I assume only creating
an image from CD has been tested, then it complained I had no CD in the
drive.
I can try creating a VM (para-virtual for example from scratch) but my
hope was to move these three VMs which are in themselves complete
systems I dont realy want to rebuild from scratch. I also have other
RHEL5.3 VMs that cannot be easily rebuilt.
Obviously I will try and create a new VM from scratch using the
Virt-Manager wizard.
During the opensuse installation I chose partition based disk-set which
is similar ot the Ubuntu installation. The CentOS one uses LVM but I
dont think this would make any difference to running these domUs. Eg
config script which works on CentOS dom0:
name = "WinXP_sp3"
uuid = "79178fd8-d542-4c76-36ec-4791e104aad9"
maxmem = 512
memory = 512
cpus = 1
builder = "hvm"
kernel = "/usr/lib/xen/boot/hvmloader"
boot = "c"
pae = 1
acpi = 1
apic = 1
localtime = 1
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
device_model = "/usr/lib64/xen/bin/qemu-dm"
usb = 1
usbdevice = "tablet"
sdl = 0
vnc = 1
vncunused = 1
keymap = "en-us"
disk = [ "file:/var/lib/libvirt/images/XP-Pro_sp3.img,hda,w"
]
vif = [ "mac=00:16:36:f7:27:39,bridge=xenbr0,script=vif-bridge" ]
parallel = "none"
serial = "pty"
I''d be very interested in working with you to figure out this mystery
as I feel I''m very close after a couple of weeks of pulling my hair out
over kernel support for the W510 and trying to work with XEN.
Ideally, I''d rather not use another distro like opensuse but it has
been the least painful way to at least get XEN & Linux & W510
working together and fortunately the latest candidate release does do
this in a pretty stable environment. This final hurdle of hotplg
scripts is hopefully not too complicated to figure out.
lsmod, lspci and xm info follow....
linux-oit2:/etc/xen # xm info
host : linux-oit2
release : 2.6.34-8-xen
version : #1 SMP 2010-05-17 17:30:24 +0200
machine : x86_64
nr_cpus : 8
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 2
cpu_mhz : 1596
hw_caps :
bfebfbff:28100800:00000000:00001b40:0098e3fd:00000000:00000001:00000000
virt_caps : hvm hvm_directio
total_memory : 8088
free_memory : 149
free_cpus : 0
max_free_memory : 7495
max_para_memory : 7491
max_hvm_memory : 7465
node_to_cpu : node0:0-7
node_to_memory : node0:149
node_to_dma32_mem : node0:89
max_node_id : 0
xen_major : 4
xen_minor : 0
xen_extra : .0_21091_05-2.1
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : 21091
xen_commandline : vgamode=0x314 iommu=1
cc_compiler : gcc version 4.5.0 20100420 [gcc-4_5-branch
revision 158562] (SU
cc_compile_by : abuild
cc_compile_domain :
cc_compile_date : Wed May 19 19:06:40 UTC 2010
xend_config_format : 4
linux-oit2:/etc/xen # lsmod
Module Size Used by
usbbk 23911 0
gntdev 8579 0
netbk 41281 0 [permanent]
rfcomm 81560 4
blkbk 28782 0 [permanent]
blkback_pagemap 2806 1 blkbk
snd_pcm_oss 53455 0
blktap 126702 2 [permanent]
snd_mixer_oss 18817 1 snd_pcm_oss
sco 20103 2
domctl 3227 2 blkbk,blktap
bnep 18047 2
xenbus_be 3706 4 usbbk,netbk,blkbk,blktap
snd_seq 67923 0
snd_seq_device 7834 1 snd_seq
l2cap 62034 16 rfcomm,bnep
edd 10176 0
bridge 85815 3
stp 2331 1 bridge
llc 6103 2 bridge,stp
nouveau 552206 2
ttm 68464 1 nouveau
drm_kms_helper 33008 1 nouveau
drm 220232 4 nouveau,ttm,drm_kms_helper
agpgart 42953 2 ttm,drm
i2c_algo_bit 6696 1 nouveau
af_packet 23133 8
fuse 77053 3
loop 18239 0
dm_mod 86435 0
snd_hda_codec_nvhdmi 15727 4
arc4 1601 2
firewire_ohci 26970 0
ecb 2495 2
firewire_core 61402 1 firewire_ohci
snd_hda_intel 29133 2
crc_itu_t 1747 1 firewire_core
snd_hda_codec 112731 2 snd_hda_codec_nvhdmi,snd_hda_intel
iwlagn 238807 0
uvcvideo 67755 0
iwlcore 299287 1 iwlagn
sdhci_pci 8668 0
snd_hwdep 7708 1 snd_hda_codec
iTCO_wdt 12406 0
mac80211 283755 2 iwlagn,iwlcore
ohci1394 33510 0
videodev 43764 1 uvcvideo
v4l1_compat 16833 2 uvcvideo,videodev
8250_pci 25671 0
snd_pcm 107675 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
btusb 18511 2
sdhci 23126 1 sdhci_pci
v4l2_compat_ioctl32 11225 1 videodev
8250 31155 1 8250_pci
video 25192 0
snd_timer 27486 2 snd_seq,snd_pcm
sr_mod 16396 0
e1000e 152237 0
bluetooth 108637 9 rfcomm,sco,bnep,l2cap,btusb
sg 32951 0
mmc_core 83419 1 sdhci
iTCO_vendor_support 3150 1 iTCO_wdt
pcspkr 2222 0
tpm_tis 13134 0
thinkpad_acpi 83412 0
xhci_hcd 98228 0
cfg80211 182345 3 iwlagn,iwlcore,mac80211
i2c_i801 11881 0
ieee1394 104278 1 ohci1394
i2c_core 32104 6
nouveau,drm_kms_helper,drm,i2c_algo_bit,videodev,i2c_i801
serial_core 25223 1 8250
output 2727 1 video
tpm 17388 1 tpm_tis
rfkill 21959 4 bluetooth,thinkpad_acpi,cfg80211
snd 83486 15
snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_codec_nvhdmi,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer,thinkpad_acpi
snd_page_alloc 9473 2 snd_hda_intel,snd_pcm
wmi 8750 0
battery 12270 0
soundcore 8757 1 snd
ac 4023 0
tpm_bios 6652 1 tpm
button 6925 1 nouveau
joydev 12230 0
ext4 395274 1
jbd2 98208 1 ext4
crc16 1715 2 l2cap,ext4
sd_mod 41170 3
ehci_hcd 60206 0
usbcore 233034 6 usbbk,uvcvideo,btusb,xhci_hcd,ehci_hcd
xenblk 26162 0
cdrom 43083 2 sr_mod,xenblk
xennet 37763 0
fan 4527 0
processor 42918 0
ahci 42648 2
libata 211362 1 ahci
scsi_mod 191176 4 sr_mod,sg,sd_mod,libata
thermal 20593 0
thermal_sys 18006 4 video,fan,processor,thermal
hwmon 2712 2 thinkpad_acpi,thermal_sys
linux-oit2:/etc/xen # lspci
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root
Port 1 (rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System
Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore
and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System
Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor
Miscellaneous Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link
(rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing
and Protocol Registers (rev 11)
00:16.0 Communication controller: Intel Corporation 5 Series/3400
Series Chipset HECI Controller (rev 06)
00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series
Chipset KT Controller (rev 06)
00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network
Connection (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset
High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 2 (rev 06)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 4 (rev 06)
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 5 (rev 06)
00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 7 (rev 06)
00:1c.7 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 8 (rev 06)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC
Interface Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset
6 port SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus
Controller (rev 06)
01:00.0 VGA compatible controller: nVidia Corporation GT216 [Quadro FX
880M] (rev a2)
01:00.1 Audio device: nVidia Corporation High Definition Audio
Controller (rev a1)
03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300
(rev 35)
0d:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01)
0d:00.1 System peripheral: Ricoh Co Ltd Device e230 (rev 01)
0f:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host
Controller (rev 03)
17:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01)
17:00.3 FireWire (IEEE 1394): Ricoh Co Ltd Device e832 (rev 01)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath
Architecture Generic Non-Core Registers (rev 04)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath
Architecture System Address Decoder (rev 04)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev
04)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0
(rev 04)
ff:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller (rev 04)
ff:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Target Address Decoder (rev 04)
ff:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Test Registers (rev 04)
ff:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Control Registers (rev 04)
ff:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Address Registers (rev 04)
ff:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Rank Registers (rev 04)
ff:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Thermal Control Registers (rev 04)
ff:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Control Registers (rev 04)
ff:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Address Registers (rev 04)
ff:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Rank Registers (rev 04)
ff:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Thermal Control Registers (rev 04)
--- On Sun, 6/6/10, Mark Pryor <tlviewer@yahoo.com>
wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 9:48 PM
Mike,
Let me give you a broad checklist of things that may be important.
I just did a search of the lists.xensource.com/xen-users list and there
are no posts about
your hardware.
The Thinkpad w510 Notebook.
------------
many times a notebook like this will have a stealth bios, or a
limited bios. Are you
sure that HVM is enabled?
Your choice of suse 11.3 is good and should make it much easier to get
Xen 4.0 working. I like the way your Network looks, but I didn''t see
any IP address for your
br0- why not? This should work with a non-xen kernel too.
Your first domU is Winxp sp3. This might be a problem if your HD needs
AHCI or strange raid/SATA drivers not included with Winxp.
I think a better domU would be the same source you used for dom0. This
should work PV and won''t depend if your bios supports HVM.
Oh, can you post your
#xm info
#lsmod
#lspci
for dom0
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com>
wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: "Mark Pryor" <tlviewer@yahoo.com>
Date: Sunday, June 6, 2010, 3:40 PM
Yes, I tried this, and hte same error. I then
removed
the vif altogether and the similiar hotplugin error appeared for the
harddrive. Following that, found the MAKEDEV issue but I''m not sure
what needs to be done there.
--- On Sun, 6/6/10, Mark Pryor <tlviewer@yahoo.com>
wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 5:57 PM
Mike,
Manual bridge is br0/br1.
In your HVM guest config, you should have
vif = [ ''bridge=br0'' ]
if you put xenbr0 above that would explain the problem too.
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com>
wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Date: Sunday, June 6, 2010, 2:34 PM
Thanks
for
the suggestion, I assume I should keep the br0/br1... but trying
your suggestion I still see the same error. If I comment out the vif
in the HVM config file, I get a similar error hotplug script but for
the disk.
After mucking about with this some more I think the HVM should boot
(and not timeout) even if I have the wrong bridges/network scripts.
I''m not at the stage yet where I have no connectivity... the VM
doesn''t'' stay up long enough because of these hotplugin script
timeout/crash.
Hence my ramblings towards the end of the bug about finding postings on
MAKEDEV and missing /dev/ entries but haven''t managed to add these as
MAKEDEV doesn''t seem to exist on my vanilla installation and
I''ve not
had to do this on say a Centos XEN environment but that doens''t work
for other reasons (hw support) on my newer laptop.
--- On Sun,
6/6/10,
Mark Pryor <tlviewer@yahoo.com>
wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 5:04 PM
Mike,
In your Xen config: xend-config.sxp
try to comment out
#(network-script network-bridge)
and uncomment
(network-script network-dummy)
and restart xend.
once you have a manual bridge, there is no need for Xen''s
network-bridge script.
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com>
wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: [Xen-users] Hotplug scripts not working - Networking woes on
opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Date: Sunday, June 6, 2010, 12:52 PM
Anyone can
help me with this problem I''ve described here:
https://bugzilla.novell.com/show_bug.cgi?id=612006
I''ve had XEN4.0 working on CentOS 5.4 platform without these problems.
I''m trying to do the same now with a newer laptop and CentOS
didn''t
recognise half hte drivers. The latest opensuse 11.3 does have these
drivers and specifically nouveau integration and XEN which has got me
98% of the way there... I''m presently stuck on the networking part
which looks different/problematic compared my experience on CentOS
machine.
Now the VMs launch but I see various Hotplug scripts not working
messages and the VM instantly stops running.
Thanks in advance,
Mike
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Tapas Mishra
2010-Jun-10 16:06 UTC
Re: [Xen-users] Hotplug scripts not working - (opensuse 11.3 m7 with XEN4 on W510 Thinkpad)
On Thu, Jun 10, 2010 at 7:43 PM, Michael Cook <michaelcook_mjc@yahoo.com>wrote:> If I use Virt-Manager 0.8 there just doesn''t seem to be enough options to > build a XEN domU from installation or DVD. There seems to be some steps > missing to define these things and the summary of the machine to be created > is present, hit next and it complains either the DVD is missing or existing > image file. >What is your Dom0 Sorry I did not read the complete thread.> --Tapas http://mightydreams.blogspot.com http://wiki.xensource.com/xenwiki/Xen_on_4_app_servers _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Michael Cook
2010-Jun-18 14:51 UTC
Re: [Xen-users] Hotplug scripts not working - (opensuse 11.3 RC1 with XEN4 on W510 Thinkpad)
11.3 RC1 Fresh Install
- dom0 launching a domU has exactly the same behaviour with fresh install
(hotplugin scripts not working).
- xm create still has a crash wrt vif configuration
- general networking manager seems more stable and automatic
Giving up. Moving to some other virtualisation technology on Ubuntu.
--- On Thu, 6/10/10, Michael Cook <michaelcook_mjc@yahoo.com> wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - (opensuse 11.3 m7 with
XEN4 on W510 Thinkpad)
To: "xen-users mailing list" <xen-users@lists.xensource.com>
Received: Thursday, June 10, 2010, 10:13 AM
If I use Virt-Manager 0.8 there just doesn''t seem to be enough options
to build a XEN domU from installation or DVD. There seems to be some steps
missing to define these things and the summary of the machine to be created is
present, hit next and it complains either the DVD is missing or existing image
file.
Maybe I''m missing something but on the CentOS5.4 with XEN3.4 and
Virtual Manager 0.8 I get many more options to properly build a guest domU VM
(and it works).
Mike.
--- On Tue, 6/8/10, Michael Cook <michaelcook_mjc@yahoo.com> wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working -
(opensuse 11.3 m7 with XEN4 on W510 Thinkpad)
To: "xen-users mailing list" <xen-users@lists.xensource.com>
Received: Tuesday, June 8, 2010, 10:27 AM
NULL ptr work in progress:
http://lists.xensource.com/archives/html/xen-devel/2010-05/msg01590.html
FWIW if I comment out the "vif =" line this oops goes away, but the
hotscripts
plugin still persists. No dmesg/oops/xend-debug output this time ;o(
--- On Tue, 6/8/10, Michael Cook <michaelcook_mjc@yahoo.com> wrote:
From: Michael Cook
<michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - netback_uevent+0x73/0x100
NULL ptr deref (opensuse 11.3 m7 with XEN4 on W510 Thinkpad)
To: "xen-users mailing list" <xen-users@lists.xensource.com>,
"Helmut Wieser" <helmut.wieser@ieee.org>
Received: Tuesday, June 8, 2010, 9:38 AM
Looking a bit further at this the XEND is actually de-referencing a null ptr
when starting up the VM. I''ve added the traceback to the opensuse
bugzilla report:
https://bugzilla.novell.com/show_bug.cgi?id=612006
[ 693.222999] BUG: unable to handle kernel NULL pointer dereference at
0000000000000150
[ 693.223015] IP: [<ffffffffa0889a63>] netback_uevent+0x73/0x100 [netbk]
[ 693.223038] PGD 189cef067 PUD 189d30067 PMD 0
[ 693.223052] Oops: 0000 [#1] SMP
[ 693.223061] last sysfs file:
/sys/devices/xen-backend/vif-1-0/uevent
[ 693.223068] CPU 2
I''ve yet to look at netback_uevent (and dont really have the time to
;o( right
now.
Mike.
--- On Tue, 6/8/10, Michael Cook <michaelcook_mjc@yahoo.com> wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - (opensuse 11.3 m7 with
XEN4 on W510 Thinkpad)
To: "xen-users mailing list" <xen-users@lists.xensource.com>,
"Helmut Wieser" <helmut.wieser@ieee.org>
Received: Tuesday, June 8, 2010, 8:54 AM
If I try and unpause the domUs they start booting although the WinXP starts
complaining about scandisk and wants to run through that, if I skip that, I then
get to log in, but then the ~100sec timeout hits and simply closes the domU
VM. So the behaviour seems unrelated to the content in the VM IMO but rather
something XEN environment is waiting on.
This may also suggest that networking or disk access is actually fine and the
hotplug script error message is a bit of a red-herring.
I will try building a VM from scratch to see if this makes any difference but I
have several VMs I need running which would be time consuming to say the least
to re-create from scratch. Hence my hope for a solution to this timeout error.
Mike.
--
Text/Cell: +1.613.447.7407 Email: michael@dtmc.ca
--- On Tue, 6/8/10, Helmut Wieser <helmut.wieser@ieee.org> wrote:
From: Helmut Wieser <helmut.wieser@ieee.org>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes on
opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: "xen-users mailing list" <xen-users@lists.xensource.com>
Cc: michael@dtmc.ca, "Michael Cook" <michaelcook_mjc@yahoo.com>
Received: Tuesday, June 8, 2010, 8:41 AM
Hi Mike,
Then you are definitely facing a different problem than I am. After a
dom0 reboot, my domU machines come up and stay up fine.
Did you try to unpause a domU using xm? Turn on a VNC console to track
whats going on. I suspect it''s working, and then shut down after 100
seconds.
Make sure all required modules are loaded, or built into the kernel.
Also try to add devices as you go, start with a minimum VM first, and
expand as you go.
To downgrade udev you don''t need to compile a kernel. You need to
update your initrd though. Some more info on downgrading can be found
here: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1612
regards,
Helmut
On 08.06.2010 14:22, Michael Cook wrote:
Does what not come up? The dom0 comes up everytime but the domUs start
up and then timeout, in a paused state, with hotplug scripts not
working error every time. Its very reproducable.
Was there any substance to the MAKEDEV posting circa 2006 as there are
no vnd* devices present for the psudeo-virtual-disks. I tried this (as
per opensuse bug comment I added yesterday) and MAKEDEV pumped out a
bunch of errors. To be honest I do not know what I''m doing, other than
surfing for workarounds/solutions. Hopefully someone on this list is
more experienced.
Perhaps a XEN4.0 vs XEN3.x issue? Just guessing but all of this works
fine on XEN3.x on a CentOS 5.4 machine... but CentOS5.4 has no support
for my latest laptop.
I may try the udev downgrade. Do you have any suggestions on how to do
this, is it a package downgrade or do I need to recompile the kernel.
(I''m trying to avoid recompiling/manually compiling stuff as I dont
want to diverge from maintained releases ideally).
Thx,
Mike.
--- On Tue, 6/8/10, Helmut Wieser <helmut.wieser@ieee.org>
wrote:
From: Helmut Wieser <helmut.wieser@ieee.org>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Received: Tuesday, June 8, 2010, 5:15 AM
Does it not even come up after you rebooted the dom0? Because that''s
the issue I experienced.
At first I thougt it was different module load order, or different
kernel parameters, but in the end it turned out that a dom0 reboot is
required to "fix" the hotplug scripts not working issue. Some people
say that downgrading udev to <= 151 works for them. Unfortunately
I''m not one of them.
Can you verify that?
regards,
Helmut
On 07.06.2010 05:58, Michael Cook wrote:
Hi Mark,
Thanks for your help. I will try and provide you some info. Some
background first may help. But please let me know if there are other
logs of interest.
I''ve tried many distributions from my original use of Centos5.3 with
XEN3.x. I have the following domUs which work well in CentOS but I now
wanted to move to a newer, faster host.
domUs: WinXP, Ubuntu 10.04 and RHEL5.3.
The first two are hvms, the second is a pvm, which I''ve not tried yet
and I really want the first two to work as WinXP cannot run as a PVM
from what I know.
I originally found Ubuntu 10.04 supported this W510 laptop pretty well
although they are busy writing driver fixes for USB and screen. Mostly
NVIDIA and Nouveau. Running dom0 Ubunut with NVIDIA or Nouveau doesn''t
work well at all. I think there is an mmap issue from what I''ve read
about it, circa March2010 there were hacks to get it work which have
yet to appear within the kernel drivers and manually trying to add
these to the kernel from XEN git for Ubuntu (Jeremys'') didn''t
work.
Ubuntu 10.04 (2.6.32.x) came up nicely on bare-metal. I then
thought/hoped I could find a number of guides that would get me Ubuntu
10.04 dom0. This took some work but there are a couple of guides to
recompiling and installing with XEN4.0 - then I got stuck with an
earlier kernel which didn''t seem to support any recent updates to W510
drivers (including wlan) and there was still Nouveau bug fixes for the
W510 chipset which to be honest I gave up on trying to manually fix.
I also wasn''t happy with 800x600 resolution and finally found Opensuse
11.3 milestone 7 worked as Opensuse 11.2 is 2.6.31.x and nothing worked
on the W510. CentOS5.4 on the W510 was even worse and with limited
interest & support on CentOS I figured it would be a fair time
until they support W510.
There is a wiki on the W510 which shows a lot of activity in Ubuntu to
fix up the drivers etc for W510 in Ubuntu 10.04. So I''m guessing by
U10.10 things will be sorted but I doubt XEN will be well integrated...
it seems unlikely from all the forum readings I''ve found on the
subject. I''ve added my findings so far wrt XEN to this wiki which
keeps track of the major issues for W510 (mostly in Ubuntu distro)
http://www.thinkwiki.org/wiki/Category:W510
This brought me to opensuse which I dont know very well. The
networking piece is quite different to Ubuntu and even in Ubuntu their
Network Manager drives me nuts. Opensuse seem to have a Network
Manager too through which I created br0 and br1 after reading the
comment in the xend-config.sxp file saying "Opensuse users should not
configure anything here but use the YaST Network configuration tool".
So I''ve probably not set this up properly.
None the less I was surprised as you point out that br0 didn''t have an
IP addr and doesn''t seem able to be tied to the wlan0 interface
(operation not supported message).
Further more the basic network provisioning between eth0 and wlan0
seems awkward and quirky as when eth0 is not connected it still gets an
IP addr. Oddly, it has not done this on this most recent bootup...
eth0 is now provisioned but not assigned an address. "Change Default
Route via DHCP" has always been set. So this is yet another puzzle
with YaST Network Settings. Both br0 and br1 (I tried to bridge one to
eth0 and one to wlan0) are set to DHCP but only one bridge manages to
bridge to eth0. br1 doesn''t because "operation not
supported"
(presumably from ethtool or mii) for the wlan0 driver (new chipset
support for this laptop?).
linux-oit2:/etc/xen # brctl show
bridge name bridge id STP enabled interfaces
br0 8000.00262dfac618 no eth0
br1 8000.000000000000 no
pan0 8000.000000000000 no
Anyway, I was expecting to see peth0 and xenbr0 and the scripts I''ve
run on centos5.3 which create these bridges to specific physical
devices doesn''t seem to work well at all.
Right now I dont know what to trust and obviously I''m using a
pre-release of Opensuse. I''m hoping its a simple case of
misprovisioning the native network settings along iwth the XEN
installation.
I used the example HVM file with XEN4.0 virt-manager under
/etc/xen//examples/ and simply updated the UUID, vif and harddrive
image with that of these domUs. I get the same behaviour in all of
them... timeout with some hotplug script not working.
So for the BIOS, yes, VT-d was disabled and xm info didn''t show any hvm
support. I enabled this in the W510 BIOS and then virt-manager would
allow me to create a new HVM based VM. However... it would then
complain "couldn''t find image" although it wouldn''t
let me (couldn''t
find) a place to define the name of this image. I assume only creating
an image from CD has been tested, then it complained I had no CD in the
drive.
I can try creating a VM (para-virtual for example from scratch) but my
hope was to move these three VMs which are in themselves complete
systems I dont realy want to rebuild from scratch. I also have other
RHEL5.3 VMs that cannot be easily rebuilt.
Obviously I will try and create a new VM from scratch using the
Virt-Manager wizard.
During the opensuse installation I chose partition based disk-set which
is similar ot the Ubuntu installation. The CentOS one uses LVM but I
dont think this would make any difference to running these domUs. Eg
config script which works on CentOS dom0:
name = "WinXP_sp3"
uuid = "79178fd8-d542-4c76-36ec-4791e104aad9"
maxmem = 512
memory = 512
cpus = 1
builder = "hvm"
kernel = "/usr/lib/xen/boot/hvmloader"
boot = "c"
pae = 1
acpi = 1
apic = 1
localtime = 1
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
device_model = "/usr/lib64/xen/bin/qemu-dm"
usb = 1
usbdevice = "tablet"
sdl = 0
vnc = 1
vncunused = 1
keymap = "en-us"
disk = [ "file:/var/lib/libvirt/images/XP-Pro_sp3.img,hda,w"
]
vif = [ "mac=00:16:36:f7:27:39,bridge=xenbr0,script=vif-bridge" ]
parallel = "none"
serial = "pty"
I''d be very interested in working with you to figure out this mystery
as I feel I''m very close after a couple of weeks of pulling my hair out
over kernel support for the W510 and trying to work with XEN.
Ideally, I''d rather not use another distro like opensuse but it has
been the least painful way to at least get XEN & Linux & W510
working together and fortunately the latest candidate release does do
this in a pretty stable environment. This final hurdle of hotplg
scripts is hopefully not too complicated to figure out.
lsmod, lspci and xm info follow....
linux-oit2:/etc/xen # xm info
host : linux-oit2
release : 2.6.34-8-xen
version : #1 SMP 2010-05-17 17:30:24 +0200
machine : x86_64
nr_cpus : 8
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 2
cpu_mhz : 1596
hw_caps :
bfebfbff:28100800:00000000:00001b40:0098e3fd:00000000:00000001:00000000
virt_caps : hvm hvm_directio
total_memory : 8088
free_memory : 149
free_cpus : 0
max_free_memory : 7495
max_para_memory : 7491
max_hvm_memory : 7465
node_to_cpu : node0:0-7
node_to_memory : node0:149
node_to_dma32_mem : node0:89
max_node_id : 0
xen_major : 4
xen_minor : 0
xen_extra : .0_21091_05-2.1
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : 21091
xen_commandline : vgamode=0x314 iommu=1
cc_compiler : gcc version 4.5.0 20100420 [gcc-4_5-branch
revision 158562] (SU
cc_compile_by : abuild
cc_compile_domain :
cc_compile_date : Wed May 19 19:06:40 UTC 2010
xend_config_format : 4
linux-oit2:/etc/xen # lsmod
Module Size Used by
usbbk 23911 0
gntdev 8579 0
netbk 41281 0 [permanent]
rfcomm 81560 4
blkbk 28782 0 [permanent]
blkback_pagemap 2806 1 blkbk
snd_pcm_oss 53455 0
blktap 126702 2 [permanent]
snd_mixer_oss 18817 1 snd_pcm_oss
sco 20103 2
domctl 3227 2 blkbk,blktap
bnep 18047 2
xenbus_be 3706 4 usbbk,netbk,blkbk,blktap
snd_seq 67923 0
snd_seq_device 7834 1 snd_seq
l2cap 62034 16 rfcomm,bnep
edd 10176 0
bridge 85815 3
stp 2331 1 bridge
llc 6103 2 bridge,stp
nouveau 552206 2
ttm 68464 1 nouveau
drm_kms_helper 33008 1 nouveau
drm 220232 4 nouveau,ttm,drm_kms_helper
agpgart 42953 2 ttm,drm
i2c_algo_bit 6696 1 nouveau
af_packet 23133 8
fuse 77053 3
loop 18239 0
dm_mod 86435 0
snd_hda_codec_nvhdmi 15727 4
arc4 1601 2
firewire_ohci 26970 0
ecb 2495 2
firewire_core 61402 1 firewire_ohci
snd_hda_intel 29133 2
crc_itu_t 1747 1 firewire_core
snd_hda_codec 112731 2 snd_hda_codec_nvhdmi,snd_hda_intel
iwlagn 238807 0
uvcvideo 67755 0
iwlcore 299287 1 iwlagn
sdhci_pci 8668 0
snd_hwdep 7708 1 snd_hda_codec
iTCO_wdt 12406 0
mac80211 283755 2 iwlagn,iwlcore
ohci1394 33510 0
videodev 43764 1 uvcvideo
v4l1_compat 16833 2 uvcvideo,videodev
8250_pci 25671 0
snd_pcm 107675 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
btusb 18511 2
sdhci 23126 1 sdhci_pci
v4l2_compat_ioctl32 11225 1 videodev
8250 31155 1 8250_pci
video 25192 0
snd_timer 27486 2 snd_seq,snd_pcm
sr_mod 16396 0
e1000e 152237 0
bluetooth 108637 9 rfcomm,sco,bnep,l2cap,btusb
sg 32951 0
mmc_core 83419 1 sdhci
iTCO_vendor_support 3150 1 iTCO_wdt
pcspkr 2222 0
tpm_tis 13134 0
thinkpad_acpi 83412 0
xhci_hcd 98228 0
cfg80211 182345 3 iwlagn,iwlcore,mac80211
i2c_i801 11881 0
ieee1394 104278 1 ohci1394
i2c_core 32104 6
nouveau,drm_kms_helper,drm,i2c_algo_bit,videodev,i2c_i801
serial_core 25223 1 8250
output 2727 1 video
tpm 17388 1 tpm_tis
rfkill 21959 4 bluetooth,thinkpad_acpi,cfg80211
snd 83486 15
snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_codec_nvhdmi,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer,thinkpad_acpi
snd_page_alloc 9473 2 snd_hda_intel,snd_pcm
wmi 8750 0
battery 12270 0
soundcore 8757 1 snd
ac 4023 0
tpm_bios 6652 1 tpm
button 6925 1 nouveau
joydev 12230 0
ext4 395274 1
jbd2 98208 1 ext4
crc16 1715 2 l2cap,ext4
sd_mod 41170 3
ehci_hcd 60206 0
usbcore 233034 6 usbbk,uvcvideo,btusb,xhci_hcd,ehci_hcd
xenblk 26162 0
cdrom 43083 2 sr_mod,xenblk
xennet 37763 0
fan 4527 0
processor 42918 0
ahci 42648 2
libata 211362 1 ahci
scsi_mod 191176 4 sr_mod,sg,sd_mod,libata
thermal 20593 0
thermal_sys 18006 4 video,fan,processor,thermal
hwmon 2712 2 thinkpad_acpi,thermal_sys
linux-oit2:/etc/xen # lspci
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root
Port 1 (rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System
Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore
and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System
Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor
Miscellaneous Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link
(rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing
and Protocol Registers (rev 11)
00:16.0 Communication controller: Intel Corporation 5 Series/3400
Series Chipset HECI Controller (rev 06)
00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series
Chipset KT Controller (rev 06)
00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network
Connection (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset
High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 2 (rev 06)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 4 (rev 06)
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 5 (rev 06)
00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 7 (rev 06)
00:1c.7 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 8 (rev 06)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC
Interface Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset
6 port SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus
Controller (rev 06)
01:00.0 VGA compatible controller: nVidia Corporation GT216 [Quadro FX
880M] (rev a2)
01:00.1 Audio device: nVidia Corporation High Definition Audio
Controller (rev a1)
03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300
(rev 35)
0d:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01)
0d:00.1 System peripheral: Ricoh Co Ltd Device e230 (rev 01)
0f:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host
Controller (rev 03)
17:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01)
17:00.3 FireWire (IEEE 1394): Ricoh Co Ltd Device e832 (rev 01)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath
Architecture Generic Non-Core Registers (rev 04)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath
Architecture System Address Decoder (rev 04)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev
04)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0
(rev 04)
ff:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller (rev 04)
ff:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Target Address Decoder (rev 04)
ff:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Test Registers (rev 04)
ff:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Control Registers (rev 04)
ff:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Address Registers (rev 04)
ff:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Rank Registers (rev 04)
ff:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 0 Thermal Control Registers (rev 04)
ff:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Control Registers (rev 04)
ff:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Address Registers (rev 04)
ff:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Rank Registers (rev 04)
ff:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory
Controller Channel 1 Thermal Control Registers (rev 04)
--- On Sun, 6/6/10, Mark Pryor <tlviewer@yahoo.com>
wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 9:48 PM
Mike,
Let me give you a broad checklist of things that may be important.
I just did a search of the lists.xensource.com/xen-users list and there
are no posts about
your hardware.
The Thinkpad w510 Notebook.
------------
many times a notebook like this will have a stealth bios, or a
limited bios. Are you
sure that HVM is enabled?
Your choice of suse 11.3 is good and should make it much easier to get
Xen 4.0 working. I like the way your Network looks, but I didn''t see
any IP address for your
br0- why not? This should work with a non-xen kernel too.
Your first domU is Winxp sp3. This might be a problem if your HD needs
AHCI or strange raid/SATA drivers not included with Winxp.
I think a better domU would be the same source you used for dom0. This
should work PV and won''t depend if your bios supports HVM.
Oh, can you post your
#xm info
#lsmod
#lspci
for dom0
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com>
wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: "Mark Pryor" <tlviewer@yahoo.com>
Date: Sunday, June 6, 2010, 3:40 PM
Yes, I tried this, and hte same error. I then
removed
the vif altogether and the similiar hotplugin error appeared for the
harddrive. Following that, found the MAKEDEV issue but I''m not sure
what needs to be done there.
--- On Sun, 6/6/10, Mark Pryor <tlviewer@yahoo.com>
wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 5:57 PM
Mike,
Manual bridge is br0/br1.
In your HVM guest config, you should have
vif = [ ''bridge=br0'' ]
if you put xenbr0 above that would explain the problem too.
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com>
wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Date: Sunday, June 6, 2010, 2:34 PM
Thanks
for
the suggestion, I assume I should keep the br0/br1... but trying
your suggestion I still see the same error. If I comment out the vif
in the HVM config file, I get a similar error hotplug script but for
the disk.
After mucking about with this some more I think the HVM should boot
(and not timeout) even if I have the wrong bridges/network scripts.
I''m not at the stage yet where I have no connectivity... the VM
doesn''t'' stay up long enough because of these hotplugin script
timeout/crash.
Hence my ramblings towards the end of the bug about finding postings on
MAKEDEV and missing /dev/ entries but haven''t managed to add these as
MAKEDEV doesn''t seem to exist on my vanilla installation and
I''ve not
had to do this on say a Centos XEN environment but that doens''t work
for other reasons (hw support) on my newer laptop.
--- On Sun,
6/6/10,
Mark Pryor <tlviewer@yahoo.com>
wrote:
From: Mark Pryor <tlviewer@yahoo.com>
Subject: Re: [Xen-users] Hotplug scripts not working - Networking woes
on opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: michael@dtmc.ca
Received: Sunday, June 6, 2010, 5:04 PM
Mike,
In your Xen config: xend-config.sxp
try to comment out
#(network-script network-bridge)
and uncomment
(network-script network-dummy)
and restart xend.
once you have a manual bridge, there is no need for Xen''s
network-bridge script.
--
Mark
--- On Sun, 6/6/10, Michael Cook <michaelcook_mjc@yahoo.com>
wrote:
From: Michael Cook <michaelcook_mjc@yahoo.com>
Subject: [Xen-users] Hotplug scripts not working - Networking woes on
opensuse 11.3 m7 with XEN4 on W510 Thinkpad
To: xen-users@lists.xensource.com
Date: Sunday, June 6, 2010, 12:52 PM
Anyone can
help me with this problem I''ve described here:
https://bugzilla.novell.com/show_bug.cgi?id=612006
I''ve had XEN4.0 working on CentOS 5.4 platform without these problems.
I''m trying to do the same now with a newer laptop and CentOS
didn''t
recognise half hte drivers. The latest opensuse 11.3 does have these
drivers and specifically nouveau integration and XEN which has got me
98% of the way there... I''m presently stuck on the networking part
which looks different/problematic compared my experience on CentOS
machine.
Now the VMs launch but I see various Hotplug scripts not working
messages and the VM instantly stops running.
Thanks in advance,
Mike
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----Inline Attachment Follows-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users