I have problem to start domU with errors: # xm create -c x335-hien1-vm4.cfg Using config file "x335-hien1-vm4.cfg". Error: Device 0 (vif) could not be connected. Hotplug scripts not working in changeset: changeset: 7700:98bcd8fbd5e36662c10becdcd0222a22161bb2b6 tag: tip user: kaf24@firebug.cl.cam.ac.uk date: Tue Nov 8 09:48:42 2005 summary: Fix alloc_skb() to ensure data is always physically contiguous. ============I used route network. Here what I used in xend-config.sxp: (network-script network-route) (vif-script vif-route) Anybody has any ideas ? Regards, Hien Nguyen Linux Technology Center AUSTIN Phone: (512) 838-4140 Tie Line: 678-4140 e-mail: hien1@us.ibm.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I saw the script "xen-network-common.sh" that used `/sbin/getcfg -d /etc/sysconfig/network/ -f ifcfg- -- $1` to get info of netwoerk config. That is specific to SLES9 systems. For RHEL4 or FC3/4 they don''t have /sbin/getcfg and /etc/sysconfig/network/ dir. That''s why the script exited with RC=1. ========I have problem to start domU with errors: # xm create -c x335-hien1-vm4.cfg Using config file "x335-hien1-vm4.cfg". Error: Device 0 (vif) could not be connected. Hotplug scripts not working in changeset: changeset: 7700:98bcd8fbd5e36662c10becdcd0222a22161bb2b6 tag: tip user: kaf24@firebug.cl.cam.ac.uk date: Tue Nov 8 09:48:42 2005 summary: Fix alloc_skb() to ensure data is always physically contiguous. ============I used route network. Here what I used in xend-config.sxp: (network-script network-route) (vif-script vif-route) Anybody has any ideas ? Regards, Hien Nguyen Linux Technology Center AUSTIN Phone: (512) 838-4140 Tie Line: 678-4140 e-mail: hien1@us.ibm.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Tue, Nov 08, 2005 at 05:49:47PM -0600, Hien Nguyen wrote:> I saw the script "xen-network-common.sh" that used `/sbin/getcfg -d > /etc/sysconfig/network/ -f ifcfg- -- $1` to get info of netwoerk config. > That is specific to SLES9 systems. For RHEL4 or FC3/4 they don''t have > /sbin/getcfg and /etc/sysconfig/network/ dir. That''s why the script exited > with RC=1.That line is protected with "if [ -e /etc/SuSE-release ]". If you are using Redhat then that file should not exist, and that code should not be run. Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I did xend stop, then xend start, and recreate domU. The same error
occurred;
Device 0 (vif) could not be connected. Hotplug scripts not working.
I turned set -x on the following scripts: network-route, vif-route. But
nothing showed on xend-debug.log. It seemed that some scripts didn''t
run
or exited with errors. /var/log/xend.log showed:
[2005-11-09 09:30:42 xend] INFO (SrvDaemon:268) Xend Daemon started
[2005-11-09 09:30:42 xend] INFO (SrvDaemon:272) Xend changeset: Tue Nov 8
09:48:42 2005 7700:98bcd8fbd5e36662c10becdcd0222a221.
[2005-11-09 09:30:42 xend.XendDomainInfo] DEBUG (XendDomainInfo:170)
XendDomainInfo.recreate({''paused'': 0,
''cpu_time'': 540337970398L,
''ssidref'': 0, ''handle'': [0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0],
''shutdown_reason'': 0, ''dying'': 0,
''dom'': 0, ''mem_kb'': 524288,
''maxmem_kb'':
-4, ''max_vcpu_id'': 3, ''crashed'': 0,
''running'': 1, ''shutdown'': 0,
''online_vcpus'': 4, ''blocked'': 0})
[2005-11-09 09:30:42 xend.XendDomainInfo] INFO (XendDomainInfo:182)
Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000.
[2005-11-09 09:30:42 xend] DEBUG (XendDomain:140) number of vcpus to use
is 0
[2005-11-09 09:30:42 xend] INFO (SrvServer:112) unix
path=/var/lib/xend/xend-socket
[2005-11-09 09:30:57 xend.XendDomainInfo] DEBUG (XendDomainInfo:149)
XendDomainInfo.create([''vm'', [''name'',
''x335-hien1-vm4''], [''memory'',
''1024''], [''image'',
[''linux'', [''kernel'',
''/boot/vmlinuz-2.6-xenU''],
[''ramdisk'', ''/boot/initrd-2.6.12-xenU''],
[''root'', ''/dev/sdb1 ro''],
[''args'', ''ro selinux=0 3''],
[''vcpus'', ''1''], [''vcpus'',
''1''], [''boot'', ''c''],
[''display'', ''localhost:10.0'']]],
[''device'', [''vbd'',
[''uname'',
''file:/FC4-FILEVBD4/FC4-32-filevbd4''],
[''dev'', ''sdb1''], [''mode'',
''w'']]],
[''device'', [''vbd'',
[''uname'', ''phy:sdc''],
[''dev'', ''sdc''], [''mode'',
''w'']]],
[''device'', [''vbd'',
[''uname'', ''phy:sdd''],
[''dev'', ''sdd''], [''mode'',
''w'']]],
[''device'',
[''vif'', [''mac'',
''AA:00:00:17:12:6A''], [''ip'',
''10.8.1.2'']]]])
[2005-11-09 09:30:57 xend.XendDomainInfo] DEBUG (XendDomainInfo:252)
parseConfig: config is [''vm'', [''name'',
''x335-hien1-vm4''], [''memory'',
''1024''], [''image'',
[''linux'', [''kernel'',
''/boot/vmlinuz-2.6-xenU''],
[''ramdisk'', ''/boot/initrd-2.6.12-xenU''],
[''root'', ''/dev/sdb1 ro''],
[''args'', ''ro selinux=0 3''],
[''vcpus'', ''1''], [''vcpus'',
''1''], [''boot'', ''c''],
[''display'', ''localhost:10.0'']]],
[''device'', [''vbd'',
[''uname'',
''file:/FC4-FILEVBD4/FC4-32-filevbd4''],
[''dev'', ''sdb1''], [''mode'',
''w'']]],
[''device'', [''vbd'',
[''uname'', ''phy:sdc''],
[''dev'', ''sdc''], [''mode'',
''w'']]],
[''device'', [''vbd'',
[''uname'', ''phy:sdd''],
[''dev'', ''sdd''], [''mode'',
''w'']]],
[''device'', [''vif'', [''mac'',
''AA:00:00:17:12:6A''], [''ip'',
''10.8.1.2'']]]]
[2005-11-09 09:30:57 xend.XendDomainInfo] DEBUG (XendDomainInfo:310)
parseConfig: result is {''ssidref'': None,
''name'': ''x335-hien1-vm4'',
''on_reboot'': None, ''maxmem'': None,
''on_poweroff'': None, ''mem_kb'': None,
''maxmem_kb'': None, ''on_crash'': None,
''backend'': [], ''vcpus'': 1,
''cpu_weight'': None, ''vcpu_avail'': None,
''memory'': 1024, ''device'':
[(''vbd'',
[''vbd'', [''uname'',
''file:/FC4-FILEVBD4/FC4-32-filevbd4''],
[''dev'', ''sdb1''],
[''mode'', ''w'']]), (''vbd'',
[''vbd'', [''uname'',
''phy:sdc''], [''dev'',
''sdc''],
[''mode'', ''w'']]), (''vbd'',
[''vbd'', [''uname'',
''phy:sdd''], [''dev'',
''sdd''],
[''mode'', ''w'']]), (''vif'',
[''vif'', [''mac'',
''AA:00:00:17:12:6A''], [''ip'',
''10.8.1.2'']])], ''bootloader'': None,
''image'': [''linux'',
[''kernel'',
''/boot/vmlinuz-2.6-xenU''], [''ramdisk'',
''/boot/initrd-2.6.12-xenU''],
[''root'', ''/dev/sdb1 ro''],
[''args'', ''ro selinux=0 3''],
[''vcpus'', ''1''],
[''vcpus'', ''1''], [''boot'',
''c''], [''display'',
''localhost:10.0'']], ''cpu'': None,
''uuid'': None}
[2005-11-09 09:30:57 xend.XendDomainInfo] DEBUG (XendDomainInfo:1059)
XendDomainInfo.construct: None 0
[2005-11-09 09:30:57 xend.XendDomainInfo] DEBUG (XendDomainInfo:1092)
XendDomainInfo.initDomain: 5 1048576 1.0
[2005-11-09 09:30:57 xend] INFO (image:132) buildDomain os=linux dom=5
vcpus=1
[2005-11-09 09:30:57 xend] DEBUG (image:170) dom = 5
[2005-11-09 09:30:57 xend] DEBUG (image:171) image =
/boot/vmlinuz-2.6-xenU
[2005-11-09 09:30:57 xend] DEBUG (image:172) store_evtchn = 1
[2005-11-09 09:30:57 xend] DEBUG (image:173) console_evtchn = 2
[2005-11-09 09:30:57 xend] DEBUG (image:174) cmdline =
root=/dev/sdb1 ro ro selinux=0 3
[2005-11-09 09:30:57 xend] DEBUG (image:175) ramdisk =
/boot/initrd-2.6.12-xenU
[2005-11-09 09:30:57 xend] DEBUG (image:176) vcpus = 1
[2005-11-09 09:30:57 xend] DEBUG (DevController:275) DevController:
writing {''virtual-device'': ''2065'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/vbd/5/2065''} to
/local/domain/5/device/vbd/2065.
[2005-11-09 09:30:57 xend] DEBUG (DevController:277) DevController:
writing {''domain'': ''x335-hien1-vm4'',
''params'':
''/FC4-FILEVBD4/FC4-32-filevbd4'',
''frontend-id'': ''5'',
''type'': ''file'',
''dev'': ''sdb1'', ''frontend'':
''/local/domain/5/device/vbd/2065''} to
/local/domain/0/backend/vbd/5/2065.
[2005-11-09 09:30:57 xend] DEBUG (DevController:275) DevController:
writing {''virtual-device'': ''2080'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/vbd/5/2080''} to
/local/domain/5/device/vbd/2080.
[2005-11-09 09:30:57 xend] DEBUG (DevController:277) DevController:
writing {''domain'': ''x335-hien1-vm4'',
''params'': ''sdc'',
''frontend-id'': ''5'',
''type'': ''phy'', ''dev'':
''sdc'', ''frontend'':
''/local/domain/5/device/vbd/2080''} to
/local/domain/0/backend/vbd/5/2080.
[2005-11-09 09:30:57 xend] DEBUG (DevController:275) DevController:
writing {''virtual-device'': ''2096'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/vbd/5/2096''} to
/local/domain/5/device/vbd/2096.
[2005-11-09 09:30:57 xend] DEBUG (DevController:277) DevController:
writing {''domain'': ''x335-hien1-vm4'',
''params'': ''sdd'',
''frontend-id'': ''5'',
''type'': ''phy'', ''dev'':
''sdd'', ''frontend'':
''/local/domain/5/device/vbd/2096''} to
/local/domain/0/backend/vbd/5/2096.
[2005-11-09 09:30:57 xend] DEBUG (DevController:275) DevController:
writing {''backend-id'': ''0'',
''mac'': ''AA:00:00:17:12:6A'',
''handle'': ''0'',
''backend'':
''/local/domain/0/backend/vif/5/0''} to
/local/domain/5/device/vif/0.
[2005-11-09 09:30:57 xend] DEBUG (DevController:277) DevController:
writing {''frontend-id'': ''5'',
''mac'': ''AA:00:00:17:12:6A'',
''handle'': ''0'',
''script'': ''/etc/xen/scripts/vif-route'',
''ip'': ''10.8.1.2'',
''domain'':
''x335-hien1-vm4'', ''frontend'':
''/local/domain/5/device/vif/0''} to
/local/domain/0/backend/vif/5/0.
[2005-11-09 09:30:57 xend.XendDomainInfo] DEBUG (XendDomainInfo:593)
Storing VM
details: {''ssidref'': ''0'',
''uuid'':
''653308f2-c5af-698c-95a6-1c5e1410378e'',
''on_reboot'': ''restart'',
''image'': "(linux (kernel /boot/vmlinuz-2.6-xenU)
(ramdisk /boot/initrd-2.6.12-xenU) (root ''/dev/sdb1 ro'') (args
''ro
selinux=0 3'') (vcpus 1) (vcpus 1) (boot c) (display
localhost:10.0))",
''on_poweroff'': ''destroy'',
''vcpus'':
''1'', ''on_crash'':
''restart'', ''memory/target'':
''1048576'', ''vcpu_avail'':
''1'',
''name'': ''x335-hien1-vm4''}
[2005-11-09 09:30:57 xend.XendDomainInfo] DEBUG (XendDomainInfo:618)
Storing domain details: {''console/ring-ref'':
''386208'', ''console/port'':
''2'', ''name'':
''x335-hien1-vm4'', ''console/limit'':
''1048576'', ''vm'':
''/vm/653308f2-c5af-698c-95a6-1c5e1410378e'',
''domid'': ''5'',
''cpu/0/availability'': ''online'',
''memory/target'': ''1048576'',
''store/ring-ref'': ''386209'',
''store/port'': ''1''}
[2005-11-09 09:30:57 xend] DEBUG (DevController:69) Waiting for devices
vif.
[2005-11-09 09:30:57 xend] DEBUG (DevController:75) Waiting for 0.
[2005-11-09 09:32:57 xend] ERROR (SrvBase:87) Request wait_for_devices
failed.
Traceback (most recent call last):
File "/usr/lib/python/xen/web/SrvBase.py", line 85, in perform
return op_method(op, req)
File "/usr/lib/python/xen/xend/server/SrvDomain.py", line 68, in
op_wait_for_devices
return self.dom.waitForDevices()
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1249, in
waitForDevices
self.waitForDevices_(c)
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 901, in
waitForDevices_
return self.getDeviceController(deviceClass).waitForDevices()
File "/usr/lib/python/xen/xend/server/DevController.py", line 71, in
waitForDevices
return map(self.waitForDevice, self.deviceIDs())
File "/usr/lib/python/xen/xend/server/DevController.py", line 80, in
waitForDevice
raise VmError( ("Device %s (%s) could not be connected. "
VmError: Device 0 (vif) could not be connected. Hotplug scripts not
working
Regards,
Hien Nguyen
Linux Technology Center AUSTIN
Phone: (512) 838-4140 Tie Line: 678-4140
e-mail: hien1@us.ibm.com
Ewan Mellor <ewan@xensource.com>
11/09/2005 05:24 AM
To
Hien Nguyen/Austin/IBM@IBMUS
cc
xen-devel@lists.xensource.com
Subject
Re: [Xen-devel] Hotplug script not working
On Tue, Nov 08, 2005 at 05:49:47PM -0600, Hien Nguyen wrote:
> I saw the script "xen-network-common.sh" that used `/sbin/getcfg
-d
> /etc/sysconfig/network/ -f ifcfg- -- $1` to get info of netwoerk config.
> That is specific to SLES9 systems. For RHEL4 or FC3/4 they don''t
have
> /sbin/getcfg and /etc/sysconfig/network/ dir. That''s why the
script
exited > with RC=1.
That line is protected with "if [ -e /etc/SuSE-release ]". If you are
using
Redhat then that file should not exist, and that code should not be run.
Ewan.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
On Wed, Nov 09, 2005 at 10:03:35AM -0600, Hien Nguyen wrote:> I did xend stop, then xend start, and recreate domU. The same error > occurred; > > Device 0 (vif) could not be connected. Hotplug scripts not working. > > I turned set -x on the following scripts: network-route, vif-route. But > nothing showed on xend-debug.log. It seemed that some scripts didn''t run > or exited with errors.Do you get anything in /var/log/{debug,messages,syslog}? Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ewan Mellor wrote:> On Wed, Nov 09, 2005 at 10:03:35AM -0600, Hien Nguyen wrote: > >> I did xend stop, then xend start, and recreate domU. The same error >> occurred; >> >> Device 0 (vif) could not be connected. Hotplug scripts not working. >> >> I turned set -x on the following scripts: network-route, vif-route. But >> nothing showed on xend-debug.log. It seemed that some scripts didn''t run >> or exited with errors. > > Do you get anything in /var/log/{debug,messages,syslog}? >I have this same problem under CentOS 4 and Fedora Core 4. I am doing my own investigations, but I just wanted to verify this is not an isolated case. Thank you, Matt Ayres _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Mine is Fedora Core 4 that running on x335 system. Changeset is 7700. Regards, Hien Nguyen Linux Technology Center AUSTIN Phone: (512) 838-4140 Tie Line: 678-4140 e-mail: hien1@us.ibm.com Matt Ayres <matta@tektonic.net> 11/09/2005 10:26 AM To Ewan Mellor <ewan@xensource.com> cc Hien Nguyen/Austin/IBM@IBMUS, xen-devel@lists.xensource.com Subject Re: [Xen-devel] Hotplug script not working Ewan Mellor wrote:> On Wed, Nov 09, 2005 at 10:03:35AM -0600, Hien Nguyen wrote: > >> I did xend stop, then xend start, and recreate domU. The same error >> occurred; >> >> Device 0 (vif) could not be connected. Hotplug scripts not working. >> >> I turned set -x on the following scripts: network-route, vif-route. But>> nothing showed on xend-debug.log. It seemed that some scripts didn''trun>> or exited with errors. > > Do you get anything in /var/log/{debug,messages,syslog}? >I have this same problem under CentOS 4 and Fedora Core 4. I am doing my own investigations, but I just wanted to verify this is not an isolated case. Thank you, Matt Ayres _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I openned bug#392 on bugzilla and post more details on there. Regards, Hien Nguyen Linux Technology Center AUSTIN Phone: (512) 838-4140 Tie Line: 678-4140 e-mail: hien1@us.ibm.com Ewan Mellor <ewan@xensource.com> 11/09/2005 10:08 AM To Hien Nguyen/Austin/IBM@IBMUS cc xen-devel@lists.xensource.com Subject Re: [Xen-devel] Hotplug script not working On Wed, Nov 09, 2005 at 10:03:35AM -0600, Hien Nguyen wrote:> I did xend stop, then xend start, and recreate domU. The same error > occurred; > > Device 0 (vif) could not be connected. Hotplug scripts not working. > > I turned set -x on the following scripts: network-route, vif-route. But > nothing showed on xend-debug.log. It seemed that some scripts didn''t run> or exited with errors.Do you get anything in /var/log/{debug,messages,syslog}? Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
----- Original Message ----- From: "Matt Ayres" <matta@tektonic.net> Sent: Thursday, November 10, 2005 5:26 AM Subject: Re: [Xen-devel] Hotplug script not working> I have this same problem under CentOS 4 and Fedora Core 4. I am doing my > own investigations, but I just wanted to verify this is not an isolated > case.I seem to be going backwards with the xen networking and FC4 (bridge/vlan/bonding). I don''t as yet know what my problem is, and I can''t get vif0.0 and veth0 operating reliably (I have it working well on one machine with code from the 22nd Oct, but not on others - newer code doesn''t seem to help). I have noticed that on machines where I am having good success, that there is a "Dynamic-irq blkif-backend" entry in /proc/interrupts. ICMP pings work reliabily, but other traffic seems to hit the bit bucket. I don''t understand how hotplug would work on FC4, as FC4 uses udev (sysctl kernel.hotplug -> "kernel.hotplug = /sbin/udevsend", and udevd is running), but there is a limitation that xen only uses udev for udev 059 and greater (''check_hotplug'' script); but FC4 reports `udev- V` -> 058. How are other people getting this to work on FC4? Why does the check_hotplug script require udev >= 059? Greg. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, Nov 10, 2005 at 11:43:02PM +1300, Greg Brackley wrote:> I don''t understand how hotplug would work on FC4, as FC4 uses udev (sysctl > kernel.hotplug -> "kernel.hotplug = /sbin/udevsend", and udevd is running), > but there is a limitation that xen only uses udev for udev 059 and greater > (''check_hotplug'' script); but FC4 reports `udev- V` -> 058. How are other > people getting this to work on FC4? Why does the check_hotplug script > require udev >= 059?udev 059 introduced new rule syntax and semantics, which we use. If you don''t have udev 059, you need to use the older hotplug stuff. Do you have an /sbin/hotplug? If so, you could try echo "/sbin/hotplug" >/proc/sys/kernel/hotplug and see if that helps. Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
From: "Ewan Mellor" <ewan@xensource.com>> On Thu, Nov 10, 2005 at 11:43:02PM +1300, Greg Brackley wrote: > >> I don''t understand how hotplug would work on FC4, as FC4 uses udev >> (sysctl >> kernel.hotplug -> "kernel.hotplug = /sbin/udevsend", and udevd is >> running), >> but there is a limitation that xen only uses udev for udev 059 and >> greater >> (''check_hotplug'' script); but FC4 reports `udev- V` -> 058. How are other >> people getting this to work on FC4? Why does the check_hotplug script >> require udev >= 059? > > udev 059 introduced new rule syntax and semantics, which we use. > > If you don''t have udev 059, you need to use the older hotplug stuff. Do > you > have an /sbin/hotplug?I have worked around this with a very simple set of rules [1]. This immediately allowed me to get domU images running. I''m unsure as to what the effect of discarding all the other parameters has had. I notice that 8 vif0/veth interfaces are created in dom0. I believe providing a parameter to the driver would overcome this (if it worried me). What concerned me slightly was a spurious vif5.0 appearing in dom0 (before ANY domU''s had been created). I am now back to working out why I can get ICMP traffic working, but getting other traffic forwarding is eluding me. It seems to relate to my VLAN/bridge/vif configuration. I''ve looked at ecn, MAC addresses, arp_filter, rp_filter, log_martians, bridge stp settings, vlan configs, ethtool settings, and googled late into the night. I would still be VERY keen to hear from anyone on successes (or failures) with VLANs and xen. Possible areas to look at would be great. Strange thing is, I have one machine (with a single VLAN) working ok [but I''m reluctant to touch it, because I don''t know why it works when the other machines don''t]. Greg :-) [1] /etc/udev/rules.d/10-xen-backend.rules KERNEL=="vif*" KERNEL=="veth*" _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel