Xen users - Aug 2010 - Xen 4.0.1-rc5 w/ 2.6.32.16 dom0, DomU''s start paused

I run my production DomU''s using Xen 3.4.1 at the moment with the old 
2.6.18.x dom0 kernel.  I just built a new Xen version (4.0.1-rc5) with 
jemerys git repo of 2.6.32.16 dom0 pvops kernel.   When starting domains 
the go instantly into a paused state and eventually i see this error on 
the command line.

[root@host test1]# xm create -c vps.config
Using config file "./vps.config".
[root@uk1 ndctest1]# Error: Device 0 (vif) could not be connected. 
Hotplug scripts not working.


If i remove the vif line from the domU config the guest starts up fine. 
  Anybody know what might be going on?


[root@uk1 scripts]# ls -l /etc/xen/scripts/
total 260
-rwxr-xr-x 1 root root  2260 Aug  3 10:37 blktap
-rwxr-xr-x 1 root root  7698 Aug  3 10:37 block
-rw-r--r-- 1 root root  3164 Aug  3 10:37 block-common.sh
-rwxr-xr-x 1 root root   498 Aug  3 10:37 block-enbd
-rwxr-xr-x 1 root root   498 Aug  3 10:37 block-nbd
-rwxr-xr-x 1 root root  2896 Aug  3 10:37 external-device-migrate
-rwxr-xr-x 1 root root   238 Aug  3 13:31 hotplugpath.sh
-rw-r--r-- 1 root root  2065 Aug  3 10:37 locking.sh
-rw-r--r-- 1 root root   804 Aug  3 10:37 logging.sh
-rwxr-xr-x 1 root root  8249 Aug  3 10:37 network-bridge
-rwxr-xr-x 1 root root  2802 Aug  3 10:37 network-nat
-rwxr-xr-x 1 root root   774 Aug  3 10:37 network-route
-rwxr-xr-x 1 root root   840 Aug  3 13:30 qemu-ifup
-rwxr-xr-x 1 root root   842 Aug  3 10:37 vif2
-rwxr-xr-x 1 root root  2661 Aug  3 10:37 vif-bridge
-rw-r--r-- 1 root root  4022 Aug  3 10:37 vif-common.sh
-rwxr-xr-x 1 root root  4859 Aug  3 10:37 vif-nat
-rwxr-xr-x 1 root root  1605 Aug  3 10:37 vif-route
-rwxr-xr-x 1 root root   243 Aug  3 10:37 vscsi
-rwxr-xr-x 1 root root   351 Aug  3 10:37 vtpm
-rw-r--r-- 1 root root 11070 Aug  3 10:37 vtpm-common.sh
-rwxr-xr-x 1 root root   346 Aug  3 10:37 vtpm-delete
-rw-r--r-- 1 root root  1054 Aug  3 10:37 vtpm-hotplug-common.sh
-rw-r--r-- 1 root root  5903 Aug  3 10:37 vtpm-impl
-rw-r--r-- 1 root root   750 Aug  3 10:37 vtpm-migration.sh
-rwxr-xr-x 1 root root  1441 Aug  3 10:37 xen-hotplug-cleanup
-rw-r--r-- 1 root root  2286 Aug  3 10:37 xen-hotplug-common.sh
-rw-r--r-- 1 root root  2414 Aug  3 10:37 xen-network-common.sh
-rw-r--r-- 1 root root   993 Aug  3 10:37 xen-script-common.sh



[root@host test1]# cat vps.config
name = "ndctest1"
kernel = "/usr/local/vpshost/kernels/vmlinux-2.6.34-1"
vcpus = 8
memory = 1024
vif = [ ''mac=FE:FD:55:5C:59:14'' ]
dhcp = "off"
disk = [
''phy:vg/fs_9593,xvda,w'',''phy:vg/fs_9594,xvdb,w'',
]
extra = "root=/dev/xvda ro xencons=tty console=tty1 console=hvc0 "


My dom0 kernel config --> http://pastebin.com/K8ABm63B


Thanks,

~Shaun





_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Your mac address is imcompatible with the xen-netfront device
00:16:ww:xx:yy:zz

--- On Wed, 8/4/10, ShaunR <mailinglists@unix-scripts.com> wrote:
> From: ShaunR <mailinglists@unix-scripts.com>
> Subject: [Xen-users] Xen 4.0.1-rc5 w/ 2.6.32.16 dom0, DomU''s start
paused
> To: xen-users@lists.xensource.com
> Date: Wednesday, August 4, 2010, 9:02 AM
> I run my production DomU''s using Xen
> 3.4.1 at the moment with the old 2.6.18.x dom0 kernel. 
> I just built a new Xen version (4.0.1-rc5) with jemerys git
> repo of 2.6.32.16 dom0 pvops kernel.   When
> starting domains the go instantly into a paused state and
> eventually i see this error on the command line.
> 
> [root@host test1]# xm create -c vps.config
> Using config file "./vps.config".
> [root@uk1 ndctest1]# Error: Device 0 (vif) could not be
> connected. Hotplug scripts not working.
> 
> 
> If i remove the vif line from the domU config the guest
> starts up fine.  Anybody know what might be going on?
> 
<snip>
> 
> [root@host test1]# cat vps.config
> name = "ndctest1"
> kernel = "/usr/local/vpshost/kernels/vmlinux-2.6.34-1"
> vcpus = 8
> memory = 1024
> vif = [ ''mac=FE:FD:55:5C:59:14'' ]
this mac address is incompatible. Run with vif = [], then see what mac it uses.
> dhcp = "off"
> disk = [
''phy:vg/fs_9593,xvda,w'',''phy:vg/fs_9594,xvdb,w'',
> ]
> extra = "root=/dev/xvda ro xencons=tty console=tty1
> console=hvc0 "
-- 
Marl


      

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

When did this start?  I''ve always just converted the ip address into a 
MAC.  Also why does it also pause when i remove that and just set vif = 
[ '''' ]?

~Shaun


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

BTW, This didnt solve my problem.  Still happening.

~Shaun


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi.

I''m trying to start xend on a Debian Lenny, Xen 4.0.

I''m absolutely sure blkdev_tap is enabled in the running kernel.

But if I try to start xend I get the following error and xend doesn''t
start.

Any clue?


Aug  4 18:35:21 master BLKTAPCTRL[3057]: blktapctrl.c:790: blktapctrl:
v1.0.0
Aug  4 18:35:21 master BLKTAPCTRL[3057]: blktapctrl.c:792: Found driver:
[raw image (aio)]
Aug  4 18:35:21 master BLKTAPCTRL[3057]: blktapctrl.c:792: Found driver:
[raw image (sync)]
Aug  4 18:35:21 master BLKTAPCTRL[3057]: blktapctrl.c:792: Found driver:
[vmware image (vmdk)]
Aug  4 18:35:21 master BLKTAPCTRL[3057]: blktapctrl.c:792: Found driver:
[ramdisk image (ram)]
Aug  4 18:35:21 master BLKTAPCTRL[3057]: blktapctrl.c:792: Found driver:
[qcow disk (qcow)]
Aug  4 18:35:21 master BLKTAPCTRL[3057]: blktapctrl.c:792: Found driver:
[qcow2 disk (qcow2)]
Aug  4 18:35:21 master BLKTAPCTRL[3057]: blktapctrl_linux.c:92:
couldn''t
find device number for ''blktap0''
Aug  4 18:35:21 master BLKTAPCTRL[3057]: blktapctrl.c:859: couldn''t
open
blktap interface
Aug  4 18:35:21 master BLKTAPCTRL[3057]: blktapctrl.c:922: Unable to start
blktapctrl


By the way, my cpuinfo:

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 13
model name      : Intel(R) Celeron(R) M processor          900MHz
stepping        : 8
cpu MHz         : 630.065
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu de tsc msr pae mce cx8 apic mtrr mca cmov clflush
acpi mmx fxsr sse sse2 ss nx up hypervisor
bogomips        : 1260.13
clflush size    : 64
power management:

[]s
Alexander
Brazil

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Thu, Aug 5, 2010 at 5:48 AM, <alexander@nautae.eti.br>
wrote:
>
> Hi.
>
> I''m trying to start xend on a Debian Lenny, Xen 4.0.
How do you install Xen and the kernel?
>
> I''m absolutely sure blkdev_tap is enabled in the running kernel.
>
> But if I try to start xend I get the following error and xend
doesn''t
> start.

I lost track of what combination of Xen and pv_ops kernel worked or
not. If you use pv_ops kernel, Boris usually has a good tutorial, like
http://bderzhavets.wordpress.com/2010/07/08/set-up-xen-4-1-unstable-2-6-32-16-pvops-dom0-on-top-of-ubuntu-10-04-server/

Personally I stick with Xen 4.0 and kernel 2.6.34 + Andrew Lyon''s
version of Suse xen kernel patch :
http://code.google.com/p/gentoo-xen-kernel/downloads/list , which has
worked fine for me.

--
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

try to deactivate (add ''#'' at front of the line):

line 20
import xen.lowlevel.xc

line 591-621
the whole funktion def sniff_solaris(fs, cfg):

line 709
chosencfg = sniff_solaris(fs, incfg)

Am 05.08.2010 00:35, schrieb ShaunR:
> BTW, This didnt solve my problem.  Still happening.
>
> ~Shaun
>
Greetz

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On 08/04/10 18:02, ShaunR wrote:
> I run my production DomU''s using Xen 3.4.1 at the moment with the
old
> 2.6.18.x dom0 kernel. I just built a new Xen version (4.0.1-rc5) with
> jemerys git repo of 2.6.32.16 dom0 pvops kernel. When starting domains
> the go instantly into a paused state and eventually i see this error on
> the command line.
>
> [root@host test1]# xm create -c vps.config
> Using config file "./vps.config".
> [root@uk1 ndctest1]# Error: Device 0 (vif) could not be connected.
> Hotplug scripts not working.
first of all, in this case, the error message pointed me where to look 
for the error... that and the fact, that without vif-line in 
xmdomain.cfg the vm boots seemlessly.
> If i remove the vif line from the domU config the guest starts up fine.
> Anybody know what might be going on?
Yes, I solved your problem.

 >
 > My dom0 kernel config --> http://pastebin.com/K8ABm63B
 >

I boiled down your problem to the kernel config. I took a working test 
system and booted with your kernel, it booted and (suprisingly) my 
guests paused and crashed after a timeout with the very same error 
message. So i dug into the hotplug scripts responsible for the networking.
> [root@uk1 scripts]# ls -l /etc/xen/scripts/
> total 260
> -rwxr-xr-x 1 root root 2260 Aug 3 10:37 blktap
> -rwxr-xr-x 1 root root 7698 Aug 3 10:37 block
> -rw-r--r-- 1 root root 3164 Aug 3 10:37 block-common.sh
> -rwxr-xr-x 1 root root 498 Aug 3 10:37 block-enbd
> -rwxr-xr-x 1 root root 498 Aug 3 10:37 block-nbd
> -rwxr-xr-x 1 root root 2896 Aug 3 10:37 external-device-migrate
> -rwxr-xr-x 1 root root 238 Aug 3 13:31 hotplugpath.sh
> -rw-r--r-- 1 root root 2065 Aug 3 10:37 locking.sh
> -rw-r--r-- 1 root root 804 Aug 3 10:37 logging.sh
> -rwxr-xr-x 1 root root 8249 Aug 3 10:37 network-bridge
> -rwxr-xr-x 1 root root 2802 Aug 3 10:37 network-nat
> -rwxr-xr-x 1 root root 774 Aug 3 10:37 network-route
> -rwxr-xr-x 1 root root 840 Aug 3 13:30 qemu-ifup
> -rwxr-xr-x 1 root root 842 Aug 3 10:37 vif2
> -rwxr-xr-x 1 root root 2661 Aug 3 10:37 vif-bridge
> -rw-r--r-- 1 root root 4022 Aug 3 10:37 vif-common.sh
> -rwxr-xr-x 1 root root 4859 Aug 3 10:37 vif-nat
> -rwxr-xr-x 1 root root 1605 Aug 3 10:37 vif-route
> -rwxr-xr-x 1 root root 243 Aug 3 10:37 vscsi
> -rwxr-xr-x 1 root root 351 Aug 3 10:37 vtpm
> -rw-r--r-- 1 root root 11070 Aug 3 10:37 vtpm-common.sh
> -rwxr-xr-x 1 root root 346 Aug 3 10:37 vtpm-delete
> -rw-r--r-- 1 root root 1054 Aug 3 10:37 vtpm-hotplug-common.sh
> -rw-r--r-- 1 root root 5903 Aug 3 10:37 vtpm-impl
> -rw-r--r-- 1 root root 750 Aug 3 10:37 vtpm-migration.sh
> -rwxr-xr-x 1 root root 1441 Aug 3 10:37 xen-hotplug-cleanup
> -rw-r--r-- 1 root root 2286 Aug 3 10:37 xen-hotplug-common.sh
> -rw-r--r-- 1 root root 2414 Aug 3 10:37 xen-network-common.sh
> -rw-r--r-- 1 root root 993 Aug 3 10:37 xen-script-common.sh
according to how your xend is configured to setup network (dummy, 
bridge, nat, routing) and more important, how it is configured to attach 
the networking for your guests, you need iptables (among other tools). 
iptables itself relies on some kernel components... you will need state 
matches, for nat you will need nat table of iptables and masquerading 
targets and perhaps connection tracking support...

iptables connection tracking and nat support, masqerading, and (finally) 
the match target was missing in your kernel config. So was the grant 
table support...

See my modified kernel config http://gist.github.com/509754

I will poke you on IRC this evening.

Sincerly
Nicolas

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users