thr3ads.net - Xen users - [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working [May 2010]

If this information is useful, please help other people find it:
Share via:

Helmut Wieser

2010-May-28 09:41 UTC

[Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Hi All,

I''m having a similar issue as Ian Tobin some weeks ago here: 
http://lists.xensource.com/archives/html/xen-users/2010-02/msg00645.html

I''m using Debian Squeeze amd64, downloaded the experimental debian 
xen-amd64 kernel with pv_ops support.
linux-headers-2.6.32-5-common-xen_2.6.32-13_amd64.deb
linux-headers-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
linux-image-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
linux-kbuild-2.6.32_2.6.32-1_amd64.deb
xen-linux-system-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb

I downloaded and compiled Xen 4.0 as specified here: 
http://wiki.xensource.com/xenwiki/Xen4.0
I used the command
hg clone -r RELEASE-4.0.0 http://xenbits.xen.org/xen-4.0-testing.hg
to check out the sources. Compile and install went without a hitch.

Since debian squeeze uses grub2 it took me a while to find a working config.
This is my 40_custom for grub2:
menuentry "Xen 4.0.0 / Squeeze Kernel 2.6.32-3-amd64 pvops" --class 
debian --class gnu-linux --class gnu --class os {
         recordfail=1
         if [ -n ${have_grubenv} ]; then save_env recordfail; fi
         set quiet=1
         insmod ext2
         insmod ext4
         set root=''(hd1,1)''
         search --no-floppy --fs-uuid --set 
91ab2378-76a4-4ab6-9065-078307ce8268
         multiboot /boot/xen-4.0.0.gz dummy=dummy dom0_mem=512M
         module /boot/vmlinuz-2.6.32-5-xen-amd64 dummy=dummy 
root=UUID=91ab2378-76a4-4ab6-9065-078307ce8268 ro quiet
         module /boot/initrd.img-2.6.32-5-xen-amd64
}

If I use "xm create /path/to/config.cfg"  the machine is paused, and 
after 100 seconds I get "Error: Device 0 (vif) could not be connected. 
Hotplug scripts not working".
I run udevd version 154, uuid is installed.

When I start "udevadm monitor" while the xm create command runs, this
is
the output:
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[1275038753.413971] add      /devices/virtual/net/tap19.0 (net)
UDEV  [1275038753.419757] add      /devices/virtual/net/tap19.0 (net)
KERNEL[1275038854.255484] remove   /devices/virtual/net/tap19.0 (net)
UDEV  [1275038854.259336] remove   /devices/virtual/net/tap19.0 (net)

This is my virtual machine config:
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
         arch_libdir = ''lib64''
else:
         arch_libdir = ''lib''

kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory=2048
shadow_memory = 8
name = "xenwin7"
vif = [ '' bridge=eth0, mac=00:16:3e:00:12:34'' ]
acpi = 1
apic = 1
disk = [
''file:/home/hwieser/xen/domains/win01/disk.img,hda,w'',
''file:/home/hwieser/xen/domains/windows7_ultimate.iso,hdc:cdrom,r''
]
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
boot="dc"
sdl = 0
vnc = 1
vncconsole = 1
vncpasswd = ''''
serial = ''pty''
usbdevice = ''tablet''


First I thought the issue was because the netbk module is missing, but 
it''s compiled in the kernel.
Here are the relevant parts of the .config:
# fgrep -i xen /boot/config-2.6.32-5-xen-amd64
CONFIG_XEN=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=32
CONFIG_XEN_SAVE_RESTORE=y
# CONFIG_XEN_DEBUG_FS is not set
CONFIG_SWIOTLB_XEN=y
CONFIG_MICROCODE_XEN=y
CONFIG_XEN_DOM0=y
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_DOM0_PCI=y
# CONFIG_XEN_PCI_PASSTHROUGH is not set
CONFIG_PCI_XEN=y
CONFIG_XEN_PCIDEV_FRONTEND=y
CONFIG_XEN_BLKDEV_FRONTEND=m
CONFIG_NETXEN_NIC=m
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_XEN_KBDDEV_FRONTEND=y
CONFIG_HVC_XEN=y
CONFIG_XEN_FBDEV_FRONTEND=y
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=m
CONFIG_XEN_BACKEND=y
CONFIG_XEN_NETDEV_BACKEND=y
CONFIG_XEN_BLKDEV_BACKEND=y
CONFIG_XEN_BLKDEV_TAP=m
CONFIG_XEN_BLKBACK_PAGEMAP=y
CONFIG_XEN_PCIDEV_BACKEND=y
CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
# CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
# CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
# CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
# CONFIG_XEN_PCIDEV_BE_DEBUG is not set
CONFIG_XENFS=m
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y
# CONFIG_XEN_PLATFORM_PCI is not set
CONFIG_XEN_MCE=y
CONFIG_XEN_XENBUS_FRONTEND=y
CONFIG_XEN_GNTDEV=y
CONFIG_XEN_S3=y
CONFIG_ACPI_PROCESSOR_XEN=m


This is my lsmod output:
Module                  Size  Used by
virtio_net             10529  0
netxen_nic             72759  0
nls_utf8                1208  0
ufs                    56490  0
qnx4                    6194  0
hfsplus                65286  0
hfs                    37471  0
minix                  21213  0
ntfs                  162876  0
vfat                    7900  0
msdos                   6202  0
fat                    40054  2 vfat,msdos
jfs                   140163  0
xfs                   437053  0
exportfs                3170  1 xfs
reiserfs              194188  0
ext4                  285355  0
jbd2                   66951  1 ext4
crc16                   1319  1 ext4
ext2                   52985  0
blktap                 28086  0
virtio_blk              4225  0
virtio                  3309  2 virtio_net,virtio_blk
pci_hotplug            21203  0
nf_conntrack_ipv4       9833  1
nf_defrag_ipv4          1139  1 nf_conntrack_ipv4
xt_state                1303  1
nf_conntrack           46567  2 nf_conntrack_ipv4,xt_state
tun                    10828  0
xt_physdev              1508  2
iptable_filter          2258  1
ip_tables              13899  1 iptable_filter
x_tables               12845  3 xt_state,xt_physdev,ip_tables
xen_evtchn              4259  1
bridge                 39614  0
stp                     1440  1 bridge
xenfs                   9568  1
xen_blkfront            8774  0
xen_netfront           15212  0
loop                   11783  0
firewire_sbp2          11498  0
snd_hda_codec_realtek   235506  1
snd_hda_intel          19875  0
snd_hda_codec          54244  2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep               5380  1 snd_hda_codec
snd_pcm                60535  2 snd_hda_intel,snd_hda_codec
snd_timer              15582  1 snd_pcm
nouveau               353136  1
ttm                    40066  1 nouveau
drm_kms_helper         20065  1 nouveau
drm                   143585  3 nouveau,ttm,drm_kms_helper
snd                    46446  6 
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
i2c_algo_bit            4225  1 nouveau
soundcore               4598  1 snd
i2c_core               15712  4 nouveau,drm_kms_helper,drm,i2c_algo_bit
snd_page_alloc          6249  2 snd_hda_intel,snd_pcm
usbhid                 33260  0
processor              36077  0
tpm_tis                 7336  0
evdev                   7352  3
tpm                     9917  1 tpm_tis
button                  4650  1 nouveau
hid                    62841  1 usbhid
tpm_bios                4521  1 tpm
psmouse                49777  0
pcspkr                  1699  0
wmi                     4323  0
serio_raw               3752  0
acpi_processor          5087  1 processor,[permanent]
ext3                  106550  1
jbd                    37101  1 ext3
mbcache                 5050  3 ext4,ext2,ext3
usb_storage            39449  0
sg                     18760  0
sr_mod                 12602  0
sd_mod                 29777  3
cdrom                  29415  1 sr_mod
crc_t10dif              1276  1 sd_mod
firewire_ohci          19468  0
firewire_core          36752  2 firewire_sbp2,firewire_ohci
crc_itu_t               1307  1 firewire_core
uhci_hcd               18537  0
ahci                   32358  2
tg3                    95679  0
libphy                 14054  1 tg3
libata                133536  1 ahci
scsi_mod              122133  6 
firewire_sbp2,usb_storage,sg,sr_mod,sd_mod,libata
ehci_hcd               31071  0
usbcore               121991  5 usbhid,usb_storage,uhci_hcd,ehci_hcd
nls_base                6377  8 
nls_utf8,hfsplus,hfs,ntfs,vfat,fat,jfs,usbcore
floppy                 49087  0
thermal                11674  0
thermal_sys            11942  2 processor,thermal

And uname -a gives:
Linux jeatxenhw 2.6.32-5-xen-amd64 #1 SMP Mon May 17 20:24:46 UTC 2010 
x86_64 GNU/Linux

The vm is running windows 7, and I got it up and running once. I could 
VNC in and start the install.
As it wanted to reboot after the install it was botched and never worked 
again.

Assistance would be greatly appreciated.

regards,
Helmut

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

Helmut Wieser

2010-May-28 11:06 UTC

head link

[Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Hi All,

I''m having a similar issue as Ian Tobin some weeks ago here: 
http://lists.xensource.com/archives/html/xen-users/2010-02/msg00645.html

I''m using Debian Squeeze amd64, downloaded the experimental debian 
xen-amd64 kernel with pv_ops support.
linux-headers-2.6.32-5-common-xen_2.6.32-13_amd64.deb
linux-headers-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
linux-image-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
linux-kbuild-2.6.32_2.6.32-1_amd64.deb
xen-linux-system-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb

I downloaded and compiled Xen 4.0 as specified here: 
http://wiki.xensource.com/xenwiki/Xen4.0
I used the command
hg clone -r RELEASE-4.0.0 http://xenbits.xen.org/xen-4.0-testing.hg
to check out the sources. Compile and install went without a hitch.

Since debian squeeze uses grub2 it took me a while to find a working config.
This is my 40_custom for grub2:
menuentry "Xen 4.0.0 / Squeeze Kernel 2.6.32-3-amd64 pvops" --class 
debian --class gnu-linux --class gnu --class os {
         recordfail=1
         if [ -n ${have_grubenv} ]; then save_env recordfail; fi
         set quiet=1
         insmod ext2
         insmod ext4
         set root=''(hd1,1)''
         search --no-floppy --fs-uuid --set 
91ab2378-76a4-4ab6-9065-078307ce8268
         multiboot /boot/xen-4.0.0.gz dummy=dummy dom0_mem=512M
         module /boot/vmlinuz-2.6.32-5-xen-amd64 dummy=dummy 
root=UUID=91ab2378-76a4-4ab6-9065-078307ce8268 ro quiet
         module /boot/initrd.img-2.6.32-5-xen-amd64
}

If I use "xm create /path/to/config.cfg"  the machine is paused, and 
after 100 seconds I get "Error: Device 0 (vif) could not be connected. 
Hotplug scripts not working".
I run udevd version 154, uuid is installed.

When I start "udevadm monitor" while the xm create command runs, this
is
the output:
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[1275038753.413971] add      /devices/virtual/net/tap19.0 (net)
UDEV  [1275038753.419757] add      /devices/virtual/net/tap19.0 (net)
KERNEL[1275038854.255484] remove   /devices/virtual/net/tap19.0 (net)
UDEV  [1275038854.259336] remove   /devices/virtual/net/tap19.0 (net)

This is my virtual machine config:
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
         arch_libdir = ''lib64''
else:
         arch_libdir = ''lib''

kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory=2048
shadow_memory = 8
name = "xenwin7"
vif = [ '' bridge=eth0, mac=00:16:3e:00:12:34'' ]
acpi = 1
apic = 1
disk = [
''file:/home/hwieser/xen/domains/win01/disk.img,hda,w'',
''file:/home/hwieser/xen/domains/windows7_ultimate.iso,hdc:cdrom,r''
]
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
boot="dc"
sdl = 0
vnc = 1
vncconsole = 1
vncpasswd = ''''
serial = ''pty''
usbdevice = ''tablet''


First I thought the issue was because the netbk module is missing, but 
it''s compiled in the kernel.
Here are the relevant parts of the .config:
# fgrep -i xen /boot/config-2.6.32-5-xen-amd64
CONFIG_XEN=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=32
CONFIG_XEN_SAVE_RESTORE=y
# CONFIG_XEN_DEBUG_FS is not set
CONFIG_SWIOTLB_XEN=y
CONFIG_MICROCODE_XEN=y
CONFIG_XEN_DOM0=y
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_DOM0_PCI=y
# CONFIG_XEN_PCI_PASSTHROUGH is not set
CONFIG_PCI_XEN=y
CONFIG_XEN_PCIDEV_FRONTEND=y
CONFIG_XEN_BLKDEV_FRONTEND=m
CONFIG_NETXEN_NIC=m
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_XEN_KBDDEV_FRONTEND=y
CONFIG_HVC_XEN=y
CONFIG_XEN_FBDEV_FRONTEND=y
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=m
CONFIG_XEN_BACKEND=y
CONFIG_XEN_NETDEV_BACKEND=y
CONFIG_XEN_BLKDEV_BACKEND=y
CONFIG_XEN_BLKDEV_TAP=m
CONFIG_XEN_BLKBACK_PAGEMAP=y
CONFIG_XEN_PCIDEV_BACKEND=y
CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
# CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
# CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
# CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
# CONFIG_XEN_PCIDEV_BE_DEBUG is not set
CONFIG_XENFS=m
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y
# CONFIG_XEN_PLATFORM_PCI is not set
CONFIG_XEN_MCE=y
CONFIG_XEN_XENBUS_FRONTEND=y
CONFIG_XEN_GNTDEV=y
CONFIG_XEN_S3=y
CONFIG_ACPI_PROCESSOR_XEN=m


This is my lsmod output:
Module                  Size  Used by
virtio_net             10529  0
netxen_nic             72759  0
nls_utf8                1208  0
ufs                    56490  0
qnx4                    6194  0
hfsplus                65286  0
hfs                    37471  0
minix                  21213  0
ntfs                  162876  0
vfat                    7900  0
msdos                   6202  0
fat                    40054  2 vfat,msdos
jfs                   140163  0
xfs                   437053  0
exportfs                3170  1 xfs
reiserfs              194188  0
ext4                  285355  0
jbd2                   66951  1 ext4
crc16                   1319  1 ext4
ext2                   52985  0
blktap                 28086  0
virtio_blk              4225  0
virtio                  3309  2 virtio_net,virtio_blk
pci_hotplug            21203  0
nf_conntrack_ipv4       9833  1
nf_defrag_ipv4          1139  1 nf_conntrack_ipv4
xt_state                1303  1
nf_conntrack           46567  2 nf_conntrack_ipv4,xt_state
tun                    10828  0
xt_physdev              1508  2
iptable_filter          2258  1
ip_tables              13899  1 iptable_filter
x_tables               12845  3 xt_state,xt_physdev,ip_tables
xen_evtchn              4259  1
bridge                 39614  0
stp                     1440  1 bridge
xenfs                   9568  1
xen_blkfront            8774  0
xen_netfront           15212  0
loop                   11783  0
firewire_sbp2          11498  0
snd_hda_codec_realtek   235506  1
snd_hda_intel          19875  0
snd_hda_codec          54244  2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep               5380  1 snd_hda_codec
snd_pcm                60535  2 snd_hda_intel,snd_hda_codec
snd_timer              15582  1 snd_pcm
nouveau               353136  1
ttm                    40066  1 nouveau
drm_kms_helper         20065  1 nouveau
drm                   143585  3 nouveau,ttm,drm_kms_helper
snd                    46446  6 
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
i2c_algo_bit            4225  1 nouveau
soundcore               4598  1 snd
i2c_core               15712  4 nouveau,drm_kms_helper,drm,i2c_algo_bit
snd_page_alloc          6249  2 snd_hda_intel,snd_pcm
usbhid                 33260  0
processor              36077  0
tpm_tis                 7336  0
evdev                   7352  3
tpm                     9917  1 tpm_tis
button                  4650  1 nouveau
hid                    62841  1 usbhid
tpm_bios                4521  1 tpm
psmouse                49777  0
pcspkr                  1699  0
wmi                     4323  0
serio_raw               3752  0
acpi_processor          5087  1 processor,[permanent]
ext3                  106550  1
jbd                    37101  1 ext3
mbcache                 5050  3 ext4,ext2,ext3
usb_storage            39449  0
sg                     18760  0
sr_mod                 12602  0
sd_mod                 29777  3
cdrom                  29415  1 sr_mod
crc_t10dif              1276  1 sd_mod
firewire_ohci          19468  0
firewire_core          36752  2 firewire_sbp2,firewire_ohci
crc_itu_t               1307  1 firewire_core
uhci_hcd               18537  0
ahci                   32358  2
tg3                    95679  0
libphy                 14054  1 tg3
libata                133536  1 ahci
scsi_mod              122133  6 
firewire_sbp2,usb_storage,sg,sr_mod,sd_mod,libata
ehci_hcd               31071  0
usbcore               121991  5 usbhid,usb_storage,uhci_hcd,ehci_hcd
nls_base                6377  8 
nls_utf8,hfsplus,hfs,ntfs,vfat,fat,jfs,usbcore
floppy                 49087  0
thermal                11674  0
thermal_sys            11942  2 processor,thermal

And uname -a gives:
Linux jeatxenhw 2.6.32-5-xen-amd64 #1 SMP Mon May 17 20:24:46 UTC 2010 
x86_64 GNU/Linux

The vm is running windows 7, and I got it up and running once. I could 
VNC in and start the install.
As it wanted to reboot after the install it was botched and never worked 
again.

Assistance would be greatly appreciated.

regards,
Helmut

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

Helmut Wieser

2010-May-28 15:01 UTC

head link

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Here''s what I found out: a reboot of the dom0 seems to fix things.
I am able to start up the domU, and it works fine. Until I shut it down 
once, that is.



On 28.05.2010 13:06, Helmut Wieser wrote:> Hi All,
>
> I''m having a similar issue as Ian Tobin some weeks ago here: 
> http://lists.xensource.com/archives/html/xen-users/2010-02/msg00645.html
>
> I''m using Debian Squeeze amd64, downloaded the experimental debian
> xen-amd64 kernel with pv_ops support.
> linux-headers-2.6.32-5-common-xen_2.6.32-13_amd64.deb
> linux-headers-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
> linux-image-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
> linux-kbuild-2.6.32_2.6.32-1_amd64.deb
> xen-linux-system-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
>
> I downloaded and compiled Xen 4.0 as specified here: 
> http://wiki.xensource.com/xenwiki/Xen4.0
> I used the command
> hg clone -r RELEASE-4.0.0 http://xenbits.xen.org/xen-4.0-testing.hg
> to check out the sources. Compile and install went without a hitch.
>
> Since debian squeeze uses grub2 it took me a while to find a working 
> config.
> This is my 40_custom for grub2:
> menuentry "Xen 4.0.0 / Squeeze Kernel 2.6.32-3-amd64 pvops"
--class
> debian --class gnu-linux --class gnu --class os {
>         recordfail=1
>         if [ -n ${have_grubenv} ]; then save_env recordfail; fi
>         set quiet=1
>         insmod ext2
>         insmod ext4
>         set root=''(hd1,1)''
>         search --no-floppy --fs-uuid --set 
> 91ab2378-76a4-4ab6-9065-078307ce8268
>         multiboot /boot/xen-4.0.0.gz dummy=dummy dom0_mem=512M
>         module /boot/vmlinuz-2.6.32-5-xen-amd64 dummy=dummy 
> root=UUID=91ab2378-76a4-4ab6-9065-078307ce8268 ro quiet
>         module /boot/initrd.img-2.6.32-5-xen-amd64
> }
>
> If I use "xm create /path/to/config.cfg"  the machine is paused,
and
> after 100 seconds I get "Error: Device 0 (vif) could not be connected.
> Hotplug scripts not working".
> I run udevd version 154, uuid is installed.
>
> When I start "udevadm monitor" while the xm create command runs,
this
> is the output:
> monitor will print the received events for:
> UDEV - the event which udev sends out after rule processing
> KERNEL - the kernel uevent
>
> KERNEL[1275038753.413971] add      /devices/virtual/net/tap19.0 (net)
> UDEV  [1275038753.419757] add      /devices/virtual/net/tap19.0 (net)
> KERNEL[1275038854.255484] remove   /devices/virtual/net/tap19.0 (net)
> UDEV  [1275038854.259336] remove   /devices/virtual/net/tap19.0 (net)
>
> This is my virtual machine config:
> import os, re
> arch = os.uname()[4]
> if re.search(''64'', arch):
>         arch_libdir = ''lib64''
> else:
>         arch_libdir = ''lib''
>
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder=''hvm''
> memory=2048
> shadow_memory = 8
> name = "xenwin7"
> vif = [ '' bridge=eth0, mac=00:16:3e:00:12:34'' ]
> acpi = 1
> apic = 1
> disk = [
''file:/home/hwieser/xen/domains/win01/disk.img,hda,w'',
>
''file:/home/hwieser/xen/domains/windows7_ultimate.iso,hdc:cdrom,r''
]
> device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
> boot="dc"
> sdl = 0
> vnc = 1
> vncconsole = 1
> vncpasswd = ''''
> serial = ''pty''
> usbdevice = ''tablet''
>
>
> First I thought the issue was because the netbk module is missing, but 
> it''s compiled in the kernel.
> Here are the relevant parts of the .config:
> # fgrep -i xen /boot/config-2.6.32-5-xen-amd64
> CONFIG_XEN=y
> CONFIG_XEN_MAX_DOMAIN_MEMORY=32
> CONFIG_XEN_SAVE_RESTORE=y
> # CONFIG_XEN_DEBUG_FS is not set
> CONFIG_SWIOTLB_XEN=y
> CONFIG_MICROCODE_XEN=y
> CONFIG_XEN_DOM0=y
> CONFIG_XEN_PRIVILEGED_GUEST=y
> CONFIG_XEN_DOM0_PCI=y
> # CONFIG_XEN_PCI_PASSTHROUGH is not set
> CONFIG_PCI_XEN=y
> CONFIG_XEN_PCIDEV_FRONTEND=y
> CONFIG_XEN_BLKDEV_FRONTEND=m
> CONFIG_NETXEN_NIC=m
> CONFIG_XEN_NETDEV_FRONTEND=m
> CONFIG_XEN_KBDDEV_FRONTEND=y
> CONFIG_HVC_XEN=y
> CONFIG_XEN_FBDEV_FRONTEND=y
> CONFIG_XEN_BALLOON=y
> CONFIG_XEN_SCRUB_PAGES=y
> CONFIG_XEN_DEV_EVTCHN=m
> CONFIG_XEN_BACKEND=y
> CONFIG_XEN_NETDEV_BACKEND=y
> CONFIG_XEN_BLKDEV_BACKEND=y
> CONFIG_XEN_BLKDEV_TAP=m
> CONFIG_XEN_BLKBACK_PAGEMAP=y
> CONFIG_XEN_PCIDEV_BACKEND=y
> CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
> # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
> # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
> # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
> # CONFIG_XEN_PCIDEV_BE_DEBUG is not set
> CONFIG_XENFS=m
> CONFIG_XEN_COMPAT_XENFS=y
> CONFIG_XEN_SYS_HYPERVISOR=y
> # CONFIG_XEN_PLATFORM_PCI is not set
> CONFIG_XEN_MCE=y
> CONFIG_XEN_XENBUS_FRONTEND=y
> CONFIG_XEN_GNTDEV=y
> CONFIG_XEN_S3=y
> CONFIG_ACPI_PROCESSOR_XEN=m
>
>
> This is my lsmod output:
> Module                  Size  Used by
> virtio_net             10529  0
> netxen_nic             72759  0
> nls_utf8                1208  0
> ufs                    56490  0
> qnx4                    6194  0
> hfsplus                65286  0
> hfs                    37471  0
> minix                  21213  0
> ntfs                  162876  0
> vfat                    7900  0
> msdos                   6202  0
> fat                    40054  2 vfat,msdos
> jfs                   140163  0
> xfs                   437053  0
> exportfs                3170  1 xfs
> reiserfs              194188  0
> ext4                  285355  0
> jbd2                   66951  1 ext4
> crc16                   1319  1 ext4
> ext2                   52985  0
> blktap                 28086  0
> virtio_blk              4225  0
> virtio                  3309  2 virtio_net,virtio_blk
> pci_hotplug            21203  0
> nf_conntrack_ipv4       9833  1
> nf_defrag_ipv4          1139  1 nf_conntrack_ipv4
> xt_state                1303  1
> nf_conntrack           46567  2 nf_conntrack_ipv4,xt_state
> tun                    10828  0
> xt_physdev              1508  2
> iptable_filter          2258  1
> ip_tables              13899  1 iptable_filter
> x_tables               12845  3 xt_state,xt_physdev,ip_tables
> xen_evtchn              4259  1
> bridge                 39614  0
> stp                     1440  1 bridge
> xenfs                   9568  1
> xen_blkfront            8774  0
> xen_netfront           15212  0
> loop                   11783  0
> firewire_sbp2          11498  0
> snd_hda_codec_realtek   235506  1
> snd_hda_intel          19875  0
> snd_hda_codec          54244  2 snd_hda_codec_realtek,snd_hda_intel
> snd_hwdep               5380  1 snd_hda_codec
> snd_pcm                60535  2 snd_hda_intel,snd_hda_codec
> snd_timer              15582  1 snd_pcm
> nouveau               353136  1
> ttm                    40066  1 nouveau
> drm_kms_helper         20065  1 nouveau
> drm                   143585  3 nouveau,ttm,drm_kms_helper
> snd                    46446  6 
>
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
>
> i2c_algo_bit            4225  1 nouveau
> soundcore               4598  1 snd
> i2c_core               15712  4 nouveau,drm_kms_helper,drm,i2c_algo_bit
> snd_page_alloc          6249  2 snd_hda_intel,snd_pcm
> usbhid                 33260  0
> processor              36077  0
> tpm_tis                 7336  0
> evdev                   7352  3
> tpm                     9917  1 tpm_tis
> button                  4650  1 nouveau
> hid                    62841  1 usbhid
> tpm_bios                4521  1 tpm
> psmouse                49777  0
> pcspkr                  1699  0
> wmi                     4323  0
> serio_raw               3752  0
> acpi_processor          5087  1 processor,[permanent]
> ext3                  106550  1
> jbd                    37101  1 ext3
> mbcache                 5050  3 ext4,ext2,ext3
> usb_storage            39449  0
> sg                     18760  0
> sr_mod                 12602  0
> sd_mod                 29777  3
> cdrom                  29415  1 sr_mod
> crc_t10dif              1276  1 sd_mod
> firewire_ohci          19468  0
> firewire_core          36752  2 firewire_sbp2,firewire_ohci
> crc_itu_t               1307  1 firewire_core
> uhci_hcd               18537  0
> ahci                   32358  2
> tg3                    95679  0
> libphy                 14054  1 tg3
> libata                133536  1 ahci
> scsi_mod              122133  6 
> firewire_sbp2,usb_storage,sg,sr_mod,sd_mod,libata
> ehci_hcd               31071  0
> usbcore               121991  5 usbhid,usb_storage,uhci_hcd,ehci_hcd
> nls_base                6377  8 
> nls_utf8,hfsplus,hfs,ntfs,vfat,fat,jfs,usbcore
> floppy                 49087  0
> thermal                11674  0
> thermal_sys            11942  2 processor,thermal
>
> And uname -a gives:
> Linux jeatxenhw 2.6.32-5-xen-amd64 #1 SMP Mon May 17 20:24:46 UTC 2010 
> x86_64 GNU/Linux
>
> The vm is running windows 7, and I got it up and running once. I could 
> VNC in and start the install.
> As it wanted to reboot after the install it was botched and never 
> worked again.
>
> Assistance would be greatly appreciated.
>
> regards,
> Helmut
>
> _______________________________________________
> 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-May-28 15:09 UTC

head link

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

On web many places I came across xend status is corrupted in such
cases and corrupt xml files in /var/lib/xend/
directories are the reason

I also got error message Hotplug scripts not working.So I removed them
and kept them back check the files in the directory above I mentioned
if any one of them is blank then it is corrupt.Do not delete move them
to some other places in a directory reboot/restart see if the error
persists.
You will have to see which is corrupt file.Though it may not help
directly but I had same problem and this was what worked for me.


On Fri, May 28, 2010 at 8:31 PM, Helmut Wieser <helmut.wieser@ieee.org>
wrote:> Here''s what I found out: a reboot of the dom0 seems to fix things.
> I am able to start up the domU, and it works fine. Until I shut it down
> once, that is.
>
>
>
> On 28.05.2010 13:06, Helmut Wieser wrote:
>>
>> Hi All,
>>
>> I''m having a similar issue as Ian Tobin some weeks ago here:
>>
http://lists.xensource.com/archives/html/xen-users/2010-02/msg00645.html
>>
>> I''m using Debian Squeeze amd64, downloaded the experimental
debian
>> xen-amd64 kernel with pv_ops support.
>> linux-headers-2.6.32-5-common-xen_2.6.32-13_amd64.deb
>> linux-headers-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
>> linux-image-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
>> linux-kbuild-2.6.32_2.6.32-1_amd64.deb
>> xen-linux-system-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
>>
>> I downloaded and compiled Xen 4.0 as specified here:
>> http://wiki.xensource.com/xenwiki/Xen4.0
>> I used the command
>> hg clone -r RELEASE-4.0.0 http://xenbits.xen.org/xen-4.0-testing.hg
>> to check out the sources. Compile and install went without a hitch.
>>
>> Since debian squeeze uses grub2 it took me a while to find a working
>> config.
>> This is my 40_custom for grub2:
>> menuentry "Xen 4.0.0 / Squeeze Kernel 2.6.32-3-amd64 pvops"
--class debian
>> --class gnu-linux --class gnu --class os {
>>        recordfail=1
>>        if [ -n ${have_grubenv} ]; then save_env recordfail; fi
>>        set quiet=1
>>        insmod ext2
>>        insmod ext4
>>        set root=''(hd1,1)''
>>        search --no-floppy --fs-uuid --set
>> 91ab2378-76a4-4ab6-9065-078307ce8268
>>        multiboot /boot/xen-4.0.0.gz dummy=dummy dom0_mem=512M
>>        module /boot/vmlinuz-2.6.32-5-xen-amd64 dummy=dummy
>> root=UUID=91ab2378-76a4-4ab6-9065-078307ce8268 ro quiet
>>        module /boot/initrd.img-2.6.32-5-xen-amd64
>> }
>>
>> If I use "xm create /path/to/config.cfg"  the machine is
paused, and after
>> 100 seconds I get "Error: Device 0 (vif) could not be connected.
Hotplug
>> scripts not working".
>> I run udevd version 154, uuid is installed.
>>
>> When I start "udevadm monitor" while the xm create command
runs, this is
>> the output:
>> monitor will print the received events for:
>> UDEV - the event which udev sends out after rule processing
>> KERNEL - the kernel uevent
>>
>> KERNEL[1275038753.413971] add      /devices/virtual/net/tap19.0 (net)
>> UDEV  [1275038753.419757] add      /devices/virtual/net/tap19.0 (net)
>> KERNEL[1275038854.255484] remove   /devices/virtual/net/tap19.0 (net)
>> UDEV  [1275038854.259336] remove   /devices/virtual/net/tap19.0 (net)
>>
>> This is my virtual machine config:
>> import os, re
>> arch = os.uname()[4]
>> if re.search(''64'', arch):
>>        arch_libdir = ''lib64''
>> else:
>>        arch_libdir = ''lib''
>>
>> kernel = "/usr/lib/xen/boot/hvmloader"
>> builder=''hvm''
>> memory=2048
>> shadow_memory = 8
>> name = "xenwin7"
>> vif = [ '' bridge=eth0, mac=00:16:3e:00:12:34'' ]
>> acpi = 1
>> apic = 1
>> disk = [
''file:/home/hwieser/xen/domains/win01/disk.img,hda,w'',
>>
''file:/home/hwieser/xen/domains/windows7_ultimate.iso,hdc:cdrom,r''
]
>> device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
>> boot="dc"
>> sdl = 0
>> vnc = 1
>> vncconsole = 1
>> vncpasswd = ''''
>> serial = ''pty''
>> usbdevice = ''tablet''
>>
>>
>> First I thought the issue was because the netbk module is missing, but
>> it''s compiled in the kernel.
>> Here are the relevant parts of the .config:
>> # fgrep -i xen /boot/config-2.6.32-5-xen-amd64
>> CONFIG_XEN=y
>> CONFIG_XEN_MAX_DOMAIN_MEMORY=32
>> CONFIG_XEN_SAVE_RESTORE=y
>> # CONFIG_XEN_DEBUG_FS is not set
>> CONFIG_SWIOTLB_XEN=y
>> CONFIG_MICROCODE_XEN=y
>> CONFIG_XEN_DOM0=y
>> CONFIG_XEN_PRIVILEGED_GUEST=y
>> CONFIG_XEN_DOM0_PCI=y
>> # CONFIG_XEN_PCI_PASSTHROUGH is not set
>> CONFIG_PCI_XEN=y
>> CONFIG_XEN_PCIDEV_FRONTEND=y
>> CONFIG_XEN_BLKDEV_FRONTEND=m
>> CONFIG_NETXEN_NIC=m
>> CONFIG_XEN_NETDEV_FRONTEND=m
>> CONFIG_XEN_KBDDEV_FRONTEND=y
>> CONFIG_HVC_XEN=y
>> CONFIG_XEN_FBDEV_FRONTEND=y
>> CONFIG_XEN_BALLOON=y
>> CONFIG_XEN_SCRUB_PAGES=y
>> CONFIG_XEN_DEV_EVTCHN=m
>> CONFIG_XEN_BACKEND=y
>> CONFIG_XEN_NETDEV_BACKEND=y
>> CONFIG_XEN_BLKDEV_BACKEND=y
>> CONFIG_XEN_BLKDEV_TAP=m
>> CONFIG_XEN_BLKBACK_PAGEMAP=y
>> CONFIG_XEN_PCIDEV_BACKEND=y
>> CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
>> # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
>> # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
>> # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
>> # CONFIG_XEN_PCIDEV_BE_DEBUG is not set
>> CONFIG_XENFS=m
>> CONFIG_XEN_COMPAT_XENFS=y
>> CONFIG_XEN_SYS_HYPERVISOR=y
>> # CONFIG_XEN_PLATFORM_PCI is not set
>> CONFIG_XEN_MCE=y
>> CONFIG_XEN_XENBUS_FRONTEND=y
>> CONFIG_XEN_GNTDEV=y
>> CONFIG_XEN_S3=y
>> CONFIG_ACPI_PROCESSOR_XEN=m
>>
>>
>> This is my lsmod output:
>> Module                  Size  Used by
>> virtio_net             10529  0
>> netxen_nic             72759  0
>> nls_utf8                1208  0
>> ufs                    56490  0
>> qnx4                    6194  0
>> hfsplus                65286  0
>> hfs                    37471  0
>> minix                  21213  0
>> ntfs                  162876  0
>> vfat                    7900  0
>> msdos                   6202  0
>> fat                    40054  2 vfat,msdos
>> jfs                   140163  0
>> xfs                   437053  0
>> exportfs                3170  1 xfs
>> reiserfs              194188  0
>> ext4                  285355  0
>> jbd2                   66951  1 ext4
>> crc16                   1319  1 ext4
>> ext2                   52985  0
>> blktap                 28086  0
>> virtio_blk              4225  0
>> virtio                  3309  2 virtio_net,virtio_blk
>> pci_hotplug            21203  0
>> nf_conntrack_ipv4       9833  1
>> nf_defrag_ipv4          1139  1 nf_conntrack_ipv4
>> xt_state                1303  1
>> nf_conntrack           46567  2 nf_conntrack_ipv4,xt_state
>> tun                    10828  0
>> xt_physdev              1508  2
>> iptable_filter          2258  1
>> ip_tables              13899  1 iptable_filter
>> x_tables               12845  3 xt_state,xt_physdev,ip_tables
>> xen_evtchn              4259  1
>> bridge                 39614  0
>> stp                     1440  1 bridge
>> xenfs                   9568  1
>> xen_blkfront            8774  0
>> xen_netfront           15212  0
>> loop                   11783  0
>> firewire_sbp2          11498  0
>> snd_hda_codec_realtek   235506  1
>> snd_hda_intel          19875  0
>> snd_hda_codec          54244  2 snd_hda_codec_realtek,snd_hda_intel
>> snd_hwdep               5380  1 snd_hda_codec
>> snd_pcm                60535  2 snd_hda_intel,snd_hda_codec
>> snd_timer              15582  1 snd_pcm
>> nouveau               353136  1
>> ttm                    40066  1 nouveau
>> drm_kms_helper         20065  1 nouveau
>> drm                   143585  3 nouveau,ttm,drm_kms_helper
>> snd                    46446  6
>>
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
>> i2c_algo_bit            4225  1 nouveau
>> soundcore               4598  1 snd
>> i2c_core               15712  4 nouveau,drm_kms_helper,drm,i2c_algo_bit
>> snd_page_alloc          6249  2 snd_hda_intel,snd_pcm
>> usbhid                 33260  0
>> processor              36077  0
>> tpm_tis                 7336  0
>> evdev                   7352  3
>> tpm                     9917  1 tpm_tis
>> button                  4650  1 nouveau
>> hid                    62841  1 usbhid
>> tpm_bios                4521  1 tpm
>> psmouse                49777  0
>> pcspkr                  1699  0
>> wmi                     4323  0
>> serio_raw               3752  0
>> acpi_processor          5087  1 processor,[permanent]
>> ext3                  106550  1
>> jbd                    37101  1 ext3
>> mbcache                 5050  3 ext4,ext2,ext3
>> usb_storage            39449  0
>> sg                     18760  0
>> sr_mod                 12602  0
>> sd_mod                 29777  3
>> cdrom                  29415  1 sr_mod
>> crc_t10dif              1276  1 sd_mod
>> firewire_ohci          19468  0
>> firewire_core          36752  2 firewire_sbp2,firewire_ohci
>> crc_itu_t               1307  1 firewire_core
>> uhci_hcd               18537  0
>> ahci                   32358  2
>> tg3                    95679  0
>> libphy                 14054  1 tg3
>> libata                133536  1 ahci
>> scsi_mod              122133  6
>> firewire_sbp2,usb_storage,sg,sr_mod,sd_mod,libata
>> ehci_hcd               31071  0
>> usbcore               121991  5 usbhid,usb_storage,uhci_hcd,ehci_hcd
>> nls_base                6377  8
>> nls_utf8,hfsplus,hfs,ntfs,vfat,fat,jfs,usbcore
>> floppy                 49087  0
>> thermal                11674  0
>> thermal_sys            11942  2 processor,thermal
>>
>> And uname -a gives:
>> Linux jeatxenhw 2.6.32-5-xen-amd64 #1 SMP Mon May 17 20:24:46 UTC 2010
>> x86_64 GNU/Linux
>>
>> The vm is running windows 7, and I got it up and running once. I could
VNC
>> in and start the install.
>> As it wanted to reboot after the install it was botched and never
worked
>> again.
>>
>> Assistance would be greatly appreciated.
>>
>> regards,
>> Helmut
>>
>> _______________________________________________
>> 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

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

Joseph M. Deming

2010-May-28 15:32 UTC

head link

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Take a look at this ongoing bug I am working on with a few people.
Sounds like a very similar scenario, except we are all seeing
kernel-oops alongside the similar behavior.  I can start a dom0, start a
machine, even start multiple machines, each creating a fault, but still
functioning apparently normally.  But as soon as you take one of the
live machines down, no new ones will start, and the same machine cannot
be restarted.

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1612

On Fri, 2010-05-28 at 20:39 +0530, Tapas Mishra wrote:> On web many places I came across xend status is corrupted in such
> cases and corrupt xml files in /var/lib/xend/
> directories are the reason
> 
> I also got error message Hotplug scripts not working.So I removed them
> and kept them back check the files in the directory above I mentioned
> if any one of them is blank then it is corrupt.Do not delete move them
> to some other places in a directory reboot/restart see if the error
> persists.
> You will have to see which is corrupt file.Though it may not help
> directly but I had same problem and this was what worked for me.
> 
> 
> On Fri, May 28, 2010 at 8:31 PM, Helmut Wieser
<helmut.wieser@ieee.org> wrote:
> > Here''s what I found out: a reboot of the dom0 seems to fix
things.
> > I am able to start up the domU, and it works fine. Until I shut it
down
> > once, that is.
> >
> >
> >
> > On 28.05.2010 13:06, Helmut Wieser wrote:
> >>
> >> Hi All,
> >>
> >> I''m having a similar issue as Ian Tobin some weeks ago
here:
> >>
http://lists.xensource.com/archives/html/xen-users/2010-02/msg00645.html
> >>
> >> I''m using Debian Squeeze amd64, downloaded the
experimental debian
> >> xen-amd64 kernel with pv_ops support.
> >> linux-headers-2.6.32-5-common-xen_2.6.32-13_amd64.deb
> >> linux-headers-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
> >> linux-image-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
> >> linux-kbuild-2.6.32_2.6.32-1_amd64.deb
> >> xen-linux-system-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
> >>
> >> I downloaded and compiled Xen 4.0 as specified here:
> >> http://wiki.xensource.com/xenwiki/Xen4.0
> >> I used the command
> >> hg clone -r RELEASE-4.0.0
http://xenbits.xen.org/xen-4.0-testing.hg
> >> to check out the sources. Compile and install went without a
hitch.
> >>
> >> Since debian squeeze uses grub2 it took me a while to find a
working
> >> config.
> >> This is my 40_custom for grub2:
> >> menuentry "Xen 4.0.0 / Squeeze Kernel 2.6.32-3-amd64
pvops" --class debian
> >> --class gnu-linux --class gnu --class os {
> >>        recordfail=1
> >>        if [ -n ${have_grubenv} ]; then save_env recordfail; fi
> >>        set quiet=1
> >>        insmod ext2
> >>        insmod ext4
> >>        set root=''(hd1,1)''
> >>        search --no-floppy --fs-uuid --set
> >> 91ab2378-76a4-4ab6-9065-078307ce8268
> >>        multiboot /boot/xen-4.0.0.gz dummy=dummy dom0_mem=512M
> >>        module /boot/vmlinuz-2.6.32-5-xen-amd64 dummy=dummy
> >> root=UUID=91ab2378-76a4-4ab6-9065-078307ce8268 ro quiet
> >>        module /boot/initrd.img-2.6.32-5-xen-amd64
> >> }
> >>
> >> If I use "xm create /path/to/config.cfg"  the machine is
paused, and after
> >> 100 seconds I get "Error: Device 0 (vif) could not be
connected. Hotplug
> >> scripts not working".
> >> I run udevd version 154, uuid is installed.
> >>
> >> When I start "udevadm monitor" while the xm create
command runs, this is
> >> the output:
> >> monitor will print the received events for:
> >> UDEV - the event which udev sends out after rule processing
> >> KERNEL - the kernel uevent
> >>
> >> KERNEL[1275038753.413971] add      /devices/virtual/net/tap19.0
(net)
> >> UDEV  [1275038753.419757] add      /devices/virtual/net/tap19.0
(net)
> >> KERNEL[1275038854.255484] remove   /devices/virtual/net/tap19.0
(net)
> >> UDEV  [1275038854.259336] remove   /devices/virtual/net/tap19.0
(net)
> >>
> >> This is my virtual machine config:
> >> import os, re
> >> arch = os.uname()[4]
> >> if re.search(''64'', arch):
> >>        arch_libdir = ''lib64''
> >> else:
> >>        arch_libdir = ''lib''
> >>
> >> kernel = "/usr/lib/xen/boot/hvmloader"
> >> builder=''hvm''
> >> memory=2048
> >> shadow_memory = 8
> >> name = "xenwin7"
> >> vif = [ '' bridge=eth0, mac=00:16:3e:00:12:34'' ]
> >> acpi = 1
> >> apic = 1
> >> disk = [
''file:/home/hwieser/xen/domains/win01/disk.img,hda,w'',
> >>
''file:/home/hwieser/xen/domains/windows7_ultimate.iso,hdc:cdrom,r''
]
> >> device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
> >> boot="dc"
> >> sdl = 0
> >> vnc = 1
> >> vncconsole = 1
> >> vncpasswd = ''''
> >> serial = ''pty''
> >> usbdevice = ''tablet''
> >>
> >>
> >> First I thought the issue was because the netbk module is missing,
but
> >> it''s compiled in the kernel.
> >> Here are the relevant parts of the .config:
> >> # fgrep -i xen /boot/config-2.6.32-5-xen-amd64
> >> CONFIG_XEN=y
> >> CONFIG_XEN_MAX_DOMAIN_MEMORY=32
> >> CONFIG_XEN_SAVE_RESTORE=y
> >> # CONFIG_XEN_DEBUG_FS is not set
> >> CONFIG_SWIOTLB_XEN=y
> >> CONFIG_MICROCODE_XEN=y
> >> CONFIG_XEN_DOM0=y
> >> CONFIG_XEN_PRIVILEGED_GUEST=y
> >> CONFIG_XEN_DOM0_PCI=y
> >> # CONFIG_XEN_PCI_PASSTHROUGH is not set
> >> CONFIG_PCI_XEN=y
> >> CONFIG_XEN_PCIDEV_FRONTEND=y
> >> CONFIG_XEN_BLKDEV_FRONTEND=m
> >> CONFIG_NETXEN_NIC=m
> >> CONFIG_XEN_NETDEV_FRONTEND=m
> >> CONFIG_XEN_KBDDEV_FRONTEND=y
> >> CONFIG_HVC_XEN=y
> >> CONFIG_XEN_FBDEV_FRONTEND=y
> >> CONFIG_XEN_BALLOON=y
> >> CONFIG_XEN_SCRUB_PAGES=y
> >> CONFIG_XEN_DEV_EVTCHN=m
> >> CONFIG_XEN_BACKEND=y
> >> CONFIG_XEN_NETDEV_BACKEND=y
> >> CONFIG_XEN_BLKDEV_BACKEND=y
> >> CONFIG_XEN_BLKDEV_TAP=m
> >> CONFIG_XEN_BLKBACK_PAGEMAP=y
> >> CONFIG_XEN_PCIDEV_BACKEND=y
> >> CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
> >> # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
> >> # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
> >> # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
> >> # CONFIG_XEN_PCIDEV_BE_DEBUG is not set
> >> CONFIG_XENFS=m
> >> CONFIG_XEN_COMPAT_XENFS=y
> >> CONFIG_XEN_SYS_HYPERVISOR=y
> >> # CONFIG_XEN_PLATFORM_PCI is not set
> >> CONFIG_XEN_MCE=y
> >> CONFIG_XEN_XENBUS_FRONTEND=y
> >> CONFIG_XEN_GNTDEV=y
> >> CONFIG_XEN_S3=y
> >> CONFIG_ACPI_PROCESSOR_XEN=m
> >>
> >>
> >> This is my lsmod output:
> >> Module                  Size  Used by
> >> virtio_net             10529  0
> >> netxen_nic             72759  0
> >> nls_utf8                1208  0
> >> ufs                    56490  0
> >> qnx4                    6194  0
> >> hfsplus                65286  0
> >> hfs                    37471  0
> >> minix                  21213  0
> >> ntfs                  162876  0
> >> vfat                    7900  0
> >> msdos                   6202  0
> >> fat                    40054  2 vfat,msdos
> >> jfs                   140163  0
> >> xfs                   437053  0
> >> exportfs                3170  1 xfs
> >> reiserfs              194188  0
> >> ext4                  285355  0
> >> jbd2                   66951  1 ext4
> >> crc16                   1319  1 ext4
> >> ext2                   52985  0
> >> blktap                 28086  0
> >> virtio_blk              4225  0
> >> virtio                  3309  2 virtio_net,virtio_blk
> >> pci_hotplug            21203  0
> >> nf_conntrack_ipv4       9833  1
> >> nf_defrag_ipv4          1139  1 nf_conntrack_ipv4
> >> xt_state                1303  1
> >> nf_conntrack           46567  2 nf_conntrack_ipv4,xt_state
> >> tun                    10828  0
> >> xt_physdev              1508  2
> >> iptable_filter          2258  1
> >> ip_tables              13899  1 iptable_filter
> >> x_tables               12845  3 xt_state,xt_physdev,ip_tables
> >> xen_evtchn              4259  1
> >> bridge                 39614  0
> >> stp                     1440  1 bridge
> >> xenfs                   9568  1
> >> xen_blkfront            8774  0
> >> xen_netfront           15212  0
> >> loop                   11783  0
> >> firewire_sbp2          11498  0
> >> snd_hda_codec_realtek   235506  1
> >> snd_hda_intel          19875  0
> >> snd_hda_codec          54244  2
snd_hda_codec_realtek,snd_hda_intel
> >> snd_hwdep               5380  1 snd_hda_codec
> >> snd_pcm                60535  2 snd_hda_intel,snd_hda_codec
> >> snd_timer              15582  1 snd_pcm
> >> nouveau               353136  1
> >> ttm                    40066  1 nouveau
> >> drm_kms_helper         20065  1 nouveau
> >> drm                   143585  3 nouveau,ttm,drm_kms_helper
> >> snd                    46446  6
> >>
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
> >> i2c_algo_bit            4225  1 nouveau
> >> soundcore               4598  1 snd
> >> i2c_core               15712  4
nouveau,drm_kms_helper,drm,i2c_algo_bit
> >> snd_page_alloc          6249  2 snd_hda_intel,snd_pcm
> >> usbhid                 33260  0
> >> processor              36077  0
> >> tpm_tis                 7336  0
> >> evdev                   7352  3
> >> tpm                     9917  1 tpm_tis
> >> button                  4650  1 nouveau
> >> hid                    62841  1 usbhid
> >> tpm_bios                4521  1 tpm
> >> psmouse                49777  0
> >> pcspkr                  1699  0
> >> wmi                     4323  0
> >> serio_raw               3752  0
> >> acpi_processor          5087  1 processor,[permanent]
> >> ext3                  106550  1
> >> jbd                    37101  1 ext3
> >> mbcache                 5050  3 ext4,ext2,ext3
> >> usb_storage            39449  0
> >> sg                     18760  0
> >> sr_mod                 12602  0
> >> sd_mod                 29777  3
> >> cdrom                  29415  1 sr_mod
> >> crc_t10dif              1276  1 sd_mod
> >> firewire_ohci          19468  0
> >> firewire_core          36752  2 firewire_sbp2,firewire_ohci
> >> crc_itu_t               1307  1 firewire_core
> >> uhci_hcd               18537  0
> >> ahci                   32358  2
> >> tg3                    95679  0
> >> libphy                 14054  1 tg3
> >> libata                133536  1 ahci
> >> scsi_mod              122133  6
> >> firewire_sbp2,usb_storage,sg,sr_mod,sd_mod,libata
> >> ehci_hcd               31071  0
> >> usbcore               121991  5
usbhid,usb_storage,uhci_hcd,ehci_hcd
> >> nls_base                6377  8
> >> nls_utf8,hfsplus,hfs,ntfs,vfat,fat,jfs,usbcore
> >> floppy                 49087  0
> >> thermal                11674  0
> >> thermal_sys            11942  2 processor,thermal
> >>
> >> And uname -a gives:
> >> Linux jeatxenhw 2.6.32-5-xen-amd64 #1 SMP Mon May 17 20:24:46 UTC
2010
> >> x86_64 GNU/Linux
> >>
> >> The vm is running windows 7, and I got it up and running once. I
could VNC
> >> in and start the install.
> >> As it wanted to reboot after the install it was botched and never
worked
> >> again.
> >>
> >> Assistance would be greatly appreciated.
> >>
> >> regards,
> >> Helmut
> >>
> >> _______________________________________________
> >> 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

Helmut Wieser

2010-May-31 07:59 UTC

head link

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

I tried looking at the scripts and found pbd.xml, pscsi_HBA.xml and 
pscsi.xml empty. I removed them and after a restart of xend they were 
present again. So I rebooted, started xend, removed the scripts and 
tried to reboot the VM. No joy.
I couldn''t find any hints in the xend init-script that recovers the 
scripts, so it must be done by xend itself.

I read about bug 1612 before I posted this, but I don''t think
it''s
related. I downgraded udev to 151 and the problem persists.

Also, here''s the part of my xend.log when (re)starting the VM fails:

[2010-05-31 09:46:09 1733] DEBUG (DevController:139) Waiting for devices 
vif2.
[2010-05-31 09:46:09 1733] DEBUG (DevController:139) Waiting for devices 
vif.
[2010-05-31 09:46:09 1733] DEBUG (DevController:144) Waiting for 0.
[2010-05-31 09:46:09 1733] DEBUG (XendDomainInfo:1891) 
XendDomainInfo.handleShutdownWatch
[2010-05-31 09:46:09 1733] DEBUG (DevController:628) 
hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status.
[2010-05-31 09:47:49 1733] DEBUG (XendDomainInfo:3053) 
XendDomainInfo.destroy: domid=2
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2411) Destroying device 
model
[2010-05-31 09:47:50 1733] INFO (image:615) xenwin7 device model terminated
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2418) Releasing devices
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vif/0
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286) 
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vbd/768
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286) 
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vbd/5632
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286) 
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/5632
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vfb/0
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286) 
XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing console/0
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286) 
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2416) No device model
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2418) Releasing devices
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vif/0
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286) 
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vbd/768
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286) 
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vbd/5632
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286) 
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/5632
[2010-05-31 09:47:50 1733] ERROR (XendDomainInfo:2244) Failed to restart 
domain 1.
Traceback (most recent call last):
   File "usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", 
line 2230, in _restart
     new_dom.waitForDevices()
   File "usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", 
line 1247, in waitForDevices
     self.getDeviceController(devclass).waitForDevices()
   File 
"usr/lib/python2.5/site-packages/xen/xend/server/DevController.py",
line
140, in waitForDevices
     return map(self.waitForDevice, self.deviceIDs())
   File 
"usr/lib/python2.5/site-packages/xen/xend/server/DevController.py",
line
155, in waitForDevice
     (devid, self.deviceClass))
VmError: Device 0 (vif) could not be connected. Hotplug scripts not working.



On 28.05.2010 17:32, Joseph M. Deming wrote:> Take a look at this ongoing bug I am working on with a few people.
> Sounds like a very similar scenario, except we are all seeing
> kernel-oops alongside the similar behavior.  I can start a dom0, start a
> machine, even start multiple machines, each creating a fault, but still
> functioning apparently normally.  But as soon as you take one of the
> live machines down, no new ones will start, and the same machine cannot
> be restarted.
>
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1612
>
> On Fri, 2010-05-28 at 20:39 +0530, Tapas Mishra wrote:
>    
>> On web many places I came across xend status is corrupted in such
>> cases and corrupt xml files in /var/lib/xend/
>> directories are the reason
>>
>> I also got error message Hotplug scripts not working.So I removed them
>> and kept them back check the files in the directory above I mentioned
>> if any one of them is blank then it is corrupt.Do not delete move them
>> to some other places in a directory reboot/restart see if the error
>> persists.
>> You will have to see which is corrupt file.Though it may not help
>> directly but I had same problem and this was what worked for me.
>>
>>
>> On Fri, May 28, 2010 at 8:31 PM, Helmut
Wieser<helmut.wieser@ieee.org>  wrote:
>>      
>>> Here''s what I found out: a reboot of the dom0 seems to fix
things.
>>> I am able to start up the domU, and it works fine. Until I shut it
down
>>> once, that is.
>>>
>>>
>>>
>>> On 28.05.2010 13:06, Helmut Wieser wrote:
>>>        
>>>> Hi All,
>>>>
>>>> I''m having a similar issue as Ian Tobin some weeks ago
here:
>>>>
http://lists.xensource.com/archives/html/xen-users/2010-02/msg00645.html
>>>>
>>>> I''m using Debian Squeeze amd64, downloaded the
experimental debian
>>>> xen-amd64 kernel with pv_ops support.
>>>> linux-headers-2.6.32-5-common-xen_2.6.32-13_amd64.deb
>>>> linux-headers-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
>>>> linux-image-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
>>>> linux-kbuild-2.6.32_2.6.32-1_amd64.deb
>>>> xen-linux-system-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
>>>>
>>>> I downloaded and compiled Xen 4.0 as specified here:
>>>> http://wiki.xensource.com/xenwiki/Xen4.0
>>>> I used the command
>>>> hg clone -r RELEASE-4.0.0
http://xenbits.xen.org/xen-4.0-testing.hg
>>>> to check out the sources. Compile and install went without a
hitch.
>>>>
>>>> Since debian squeeze uses grub2 it took me a while to find a
working
>>>> config.
>>>> This is my 40_custom for grub2:
>>>> menuentry "Xen 4.0.0 / Squeeze Kernel 2.6.32-3-amd64
pvops" --class debian
>>>> --class gnu-linux --class gnu --class os {
>>>>         recordfail=1
>>>>         if [ -n ${have_grubenv} ]; then save_env recordfail; fi
>>>>         set quiet=1
>>>>         insmod ext2
>>>>         insmod ext4
>>>>         set root=''(hd1,1)''
>>>>         search --no-floppy --fs-uuid --set
>>>> 91ab2378-76a4-4ab6-9065-078307ce8268
>>>>         multiboot /boot/xen-4.0.0.gz dummy=dummy dom0_mem=512M
>>>>         module /boot/vmlinuz-2.6.32-5-xen-amd64 dummy=dummy
>>>> root=UUID=91ab2378-76a4-4ab6-9065-078307ce8268 ro quiet
>>>>         module /boot/initrd.img-2.6.32-5-xen-amd64
>>>> }
>>>>
>>>> If I use "xm create /path/to/config.cfg"  the machine
is paused, and after
>>>> 100 seconds I get "Error: Device 0 (vif) could not be
connected. Hotplug
>>>> scripts not working".
>>>> I run udevd version 154, uuid is installed.
>>>>
>>>> When I start "udevadm monitor" while the xm create
command runs, this is
>>>> the output:
>>>> monitor will print the received events for:
>>>> UDEV - the event which udev sends out after rule processing
>>>> KERNEL - the kernel uevent
>>>>
>>>> KERNEL[1275038753.413971] add      /devices/virtual/net/tap19.0
(net)
>>>> UDEV  [1275038753.419757] add      /devices/virtual/net/tap19.0
(net)
>>>> KERNEL[1275038854.255484] remove   /devices/virtual/net/tap19.0
(net)
>>>> UDEV  [1275038854.259336] remove   /devices/virtual/net/tap19.0
(net)
>>>>
>>>> This is my virtual machine config:
>>>> import os, re
>>>> arch = os.uname()[4]
>>>> if re.search(''64'', arch):
>>>>         arch_libdir = ''lib64''
>>>> else:
>>>>         arch_libdir = ''lib''
>>>>
>>>> kernel = "/usr/lib/xen/boot/hvmloader"
>>>> builder=''hvm''
>>>> memory=2048
>>>> shadow_memory = 8
>>>> name = "xenwin7"
>>>> vif = [ '' bridge=eth0, mac=00:16:3e:00:12:34''
]
>>>> acpi = 1
>>>> apic = 1
>>>> disk = [
''file:/home/hwieser/xen/domains/win01/disk.img,hda,w'',
>>>>
''file:/home/hwieser/xen/domains/windows7_ultimate.iso,hdc:cdrom,r''
]
>>>> device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
>>>> boot="dc"
>>>> sdl = 0
>>>> vnc = 1
>>>> vncconsole = 1
>>>> vncpasswd = ''''
>>>> serial = ''pty''
>>>> usbdevice = ''tablet''
>>>>
>>>>
>>>> First I thought the issue was because the netbk module is
missing, but
>>>> it''s compiled in the kernel.
>>>> Here are the relevant parts of the .config:
>>>> # fgrep -i xen /boot/config-2.6.32-5-xen-amd64
>>>> CONFIG_XEN=y
>>>> CONFIG_XEN_MAX_DOMAIN_MEMORY=32
>>>> CONFIG_XEN_SAVE_RESTORE=y
>>>> # CONFIG_XEN_DEBUG_FS is not set
>>>> CONFIG_SWIOTLB_XEN=y
>>>> CONFIG_MICROCODE_XEN=y
>>>> CONFIG_XEN_DOM0=y
>>>> CONFIG_XEN_PRIVILEGED_GUEST=y
>>>> CONFIG_XEN_DOM0_PCI=y
>>>> # CONFIG_XEN_PCI_PASSTHROUGH is not set
>>>> CONFIG_PCI_XEN=y
>>>> CONFIG_XEN_PCIDEV_FRONTEND=y
>>>> CONFIG_XEN_BLKDEV_FRONTEND=m
>>>> CONFIG_NETXEN_NIC=m
>>>> CONFIG_XEN_NETDEV_FRONTEND=m
>>>> CONFIG_XEN_KBDDEV_FRONTEND=y
>>>> CONFIG_HVC_XEN=y
>>>> CONFIG_XEN_FBDEV_FRONTEND=y
>>>> CONFIG_XEN_BALLOON=y
>>>> CONFIG_XEN_SCRUB_PAGES=y
>>>> CONFIG_XEN_DEV_EVTCHN=m
>>>> CONFIG_XEN_BACKEND=y
>>>> CONFIG_XEN_NETDEV_BACKEND=y
>>>> CONFIG_XEN_BLKDEV_BACKEND=y
>>>> CONFIG_XEN_BLKDEV_TAP=m
>>>> CONFIG_XEN_BLKBACK_PAGEMAP=y
>>>> CONFIG_XEN_PCIDEV_BACKEND=y
>>>> CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
>>>> # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
>>>> # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
>>>> # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
>>>> # CONFIG_XEN_PCIDEV_BE_DEBUG is not set
>>>> CONFIG_XENFS=m
>>>> CONFIG_XEN_COMPAT_XENFS=y
>>>> CONFIG_XEN_SYS_HYPERVISOR=y
>>>> # CONFIG_XEN_PLATFORM_PCI is not set
>>>> CONFIG_XEN_MCE=y
>>>> CONFIG_XEN_XENBUS_FRONTEND=y
>>>> CONFIG_XEN_GNTDEV=y
>>>> CONFIG_XEN_S3=y
>>>> CONFIG_ACPI_PROCESSOR_XEN=m
>>>>
>>>>
>>>> This is my lsmod output:
>>>> Module                  Size  Used by
>>>> virtio_net             10529  0
>>>> netxen_nic             72759  0
>>>> nls_utf8                1208  0
>>>> ufs                    56490  0
>>>> qnx4                    6194  0
>>>> hfsplus                65286  0
>>>> hfs                    37471  0
>>>> minix                  21213  0
>>>> ntfs                  162876  0
>>>> vfat                    7900  0
>>>> msdos                   6202  0
>>>> fat                    40054  2 vfat,msdos
>>>> jfs                   140163  0
>>>> xfs                   437053  0
>>>> exportfs                3170  1 xfs
>>>> reiserfs              194188  0
>>>> ext4                  285355  0
>>>> jbd2                   66951  1 ext4
>>>> crc16                   1319  1 ext4
>>>> ext2                   52985  0
>>>> blktap                 28086  0
>>>> virtio_blk              4225  0
>>>> virtio                  3309  2 virtio_net,virtio_blk
>>>> pci_hotplug            21203  0
>>>> nf_conntrack_ipv4       9833  1
>>>> nf_defrag_ipv4          1139  1 nf_conntrack_ipv4
>>>> xt_state                1303  1
>>>> nf_conntrack           46567  2 nf_conntrack_ipv4,xt_state
>>>> tun                    10828  0
>>>> xt_physdev              1508  2
>>>> iptable_filter          2258  1
>>>> ip_tables              13899  1 iptable_filter
>>>> x_tables               12845  3 xt_state,xt_physdev,ip_tables
>>>> xen_evtchn              4259  1
>>>> bridge                 39614  0
>>>> stp                     1440  1 bridge
>>>> xenfs                   9568  1
>>>> xen_blkfront            8774  0
>>>> xen_netfront           15212  0
>>>> loop                   11783  0
>>>> firewire_sbp2          11498  0
>>>> snd_hda_codec_realtek   235506  1
>>>> snd_hda_intel          19875  0
>>>> snd_hda_codec          54244  2
snd_hda_codec_realtek,snd_hda_intel
>>>> snd_hwdep               5380  1 snd_hda_codec
>>>> snd_pcm                60535  2 snd_hda_intel,snd_hda_codec
>>>> snd_timer              15582  1 snd_pcm
>>>> nouveau               353136  1
>>>> ttm                    40066  1 nouveau
>>>> drm_kms_helper         20065  1 nouveau
>>>> drm                   143585  3 nouveau,ttm,drm_kms_helper
>>>> snd                    46446  6
>>>>
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
>>>> i2c_algo_bit            4225  1 nouveau
>>>> soundcore               4598  1 snd
>>>> i2c_core               15712  4
nouveau,drm_kms_helper,drm,i2c_algo_bit
>>>> snd_page_alloc          6249  2 snd_hda_intel,snd_pcm
>>>> usbhid                 33260  0
>>>> processor              36077  0
>>>> tpm_tis                 7336  0
>>>> evdev                   7352  3
>>>> tpm                     9917  1 tpm_tis
>>>> button                  4650  1 nouveau
>>>> hid                    62841  1 usbhid
>>>> tpm_bios                4521  1 tpm
>>>> psmouse                49777  0
>>>> pcspkr                  1699  0
>>>> wmi                     4323  0
>>>> serio_raw               3752  0
>>>> acpi_processor          5087  1 processor,[permanent]
>>>> ext3                  106550  1
>>>> jbd                    37101  1 ext3
>>>> mbcache                 5050  3 ext4,ext2,ext3
>>>> usb_storage            39449  0
>>>> sg                     18760  0
>>>> sr_mod                 12602  0
>>>> sd_mod                 29777  3
>>>> cdrom                  29415  1 sr_mod
>>>> crc_t10dif              1276  1 sd_mod
>>>> firewire_ohci          19468  0
>>>> firewire_core          36752  2 firewire_sbp2,firewire_ohci
>>>> crc_itu_t               1307  1 firewire_core
>>>> uhci_hcd               18537  0
>>>> ahci                   32358  2
>>>> tg3                    95679  0
>>>> libphy                 14054  1 tg3
>>>> libata                133536  1 ahci
>>>> scsi_mod              122133  6
>>>> firewire_sbp2,usb_storage,sg,sr_mod,sd_mod,libata
>>>> ehci_hcd               31071  0
>>>> usbcore               121991  5
usbhid,usb_storage,uhci_hcd,ehci_hcd
>>>> nls_base                6377  8
>>>> nls_utf8,hfsplus,hfs,ntfs,vfat,fat,jfs,usbcore
>>>> floppy                 49087  0
>>>> thermal                11674  0
>>>> thermal_sys            11942  2 processor,thermal
>>>>
>>>> And uname -a gives:
>>>> Linux jeatxenhw 2.6.32-5-xen-amd64 #1 SMP Mon May 17 20:24:46
UTC 2010
>>>> x86_64 GNU/Linux
>>>>
>>>> The vm is running windows 7, and I got it up and running once.
I could VNC
>>>> in and start the install.
>>>> As it wanted to reboot after the install it was botched and
never worked
>>>> again.
>>>>
>>>> Assistance would be greatly appreciated.
>>>>
>>>> regards,
>>>> Helmut
>>>>
>>>> _______________________________________________
>>>> 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
>
>    
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Helmut Wieser

2010-May-31 11:00 UTC

head link

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

I tried looking at the scripts and found pbd.xml, pscsi_HBA.xml and 
pscsi.xml empty. I removed them and after a restart of xend they were 
present again. So I rebooted, started xend, removed the scripts and 
tried to reboot the VM. No joy.
I couldn''t find any hints in the xend init-script that recovers the 
scripts, so it must be done by xend itself.

I read about bug 1612 before I posted this, but I don''t think
it''s
related. I downgraded udev to 151 and the problem persists.

Also, here''s the part of my xend.log when (re)starting the VM fails:

[2010-05-31 09:46:09 1733] DEBUG (DevController:139) Waiting for devices 
vif2.
[2010-05-31 09:46:09 1733] DEBUG (DevController:139) Waiting for devices 
vif.
[2010-05-31 09:46:09 1733] DEBUG (DevController:144) Waiting for 0.
[2010-05-31 09:46:09 1733] DEBUG (XendDomainInfo:1891) 
XendDomainInfo.handleShutdownWatch
[2010-05-31 09:46:09 1733] DEBUG (DevController:628) 
hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status.
[2010-05-31 09:47:49 1733] DEBUG (XendDomainInfo:3053) 
XendDomainInfo.destroy: domid=2
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2411) Destroying device 
model
[2010-05-31 09:47:50 1733] INFO (image:615) xenwin7 device model terminated
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2418) Releasing devices
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vif/0
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286) 
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vbd/768
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286) 
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vbd/5632
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286) 
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/5632
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vfb/0
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286) 
XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing console/0
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286) 
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2416) No device model
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2418) Releasing devices
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vif/0
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286) 
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vbd/768
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286) 
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vbd/5632
[2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286) 
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/5632
[2010-05-31 09:47:50 1733] ERROR (XendDomainInfo:2244) Failed to restart 
domain 1.
Traceback (most recent call last):
   File "usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", 
line 2230, in _restart
     new_dom.waitForDevices()
   File "usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", 
line 1247, in waitForDevices
     self.getDeviceController(devclass).waitForDevices()
   File 
"usr/lib/python2.5/site-packages/xen/xend/server/DevController.py",
line
140, in waitForDevices
     return map(self.waitForDevice, self.deviceIDs())
   File 
"usr/lib/python2.5/site-packages/xen/xend/server/DevController.py",
line
155, in waitForDevice
     (devid, self.deviceClass))
VmError: Device 0 (vif) could not be connected. Hotplug scripts not working.


On 28.05.2010 17:32, Joseph M. Deming wrote:> Take a look at this ongoing bug I am working on with a few people.
> Sounds like a very similar scenario, except we are all seeing
> kernel-oops alongside the similar behavior.  I can start a dom0, start a
> machine, even start multiple machines, each creating a fault, but still
> functioning apparently normally.  But as soon as you take one of the
> live machines down, no new ones will start, and the same machine cannot
> be restarted.
>
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1612
>
> On Fri, 2010-05-28 at 20:39 +0530, Tapas Mishra wrote:
>    
>> On web many places I came across xend status is corrupted in such
>> cases and corrupt xml files in /var/lib/xend/
>> directories are the reason
>>
>> I also got error message Hotplug scripts not working.So I removed them
>> and kept them back check the files in the directory above I mentioned
>> if any one of them is blank then it is corrupt.Do not delete move them
>> to some other places in a directory reboot/restart see if the error
>> persists.
>> You will have to see which is corrupt file.Though it may not help
>> directly but I had same problem and this was what worked for me.
>>
>>
>> On Fri, May 28, 2010 at 8:31 PM, Helmut
Wieser<helmut.wieser@ieee.org>  wrote:
>>      
>>> Here''s what I found out: a reboot of the dom0 seems to fix
things.
>>> I am able to start up the domU, and it works fine. Until I shut it
down
>>> once, that is.
>>>
>>>
>>>
>>> On 28.05.2010 13:06, Helmut Wieser wrote:
>>>        
>>>> Hi All,
>>>>
>>>> I''m having a similar issue as Ian Tobin some weeks ago
here:
>>>>
http://lists.xensource.com/archives/html/xen-users/2010-02/msg00645.html
>>>>
>>>> I''m using Debian Squeeze amd64, downloaded the
experimental debian
>>>> xen-amd64 kernel with pv_ops support.
>>>> linux-headers-2.6.32-5-common-xen_2.6.32-13_amd64.deb
>>>> linux-headers-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
>>>> linux-image-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
>>>> linux-kbuild-2.6.32_2.6.32-1_amd64.deb
>>>> xen-linux-system-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
>>>>
>>>> I downloaded and compiled Xen 4.0 as specified here:
>>>> http://wiki.xensource.com/xenwiki/Xen4.0
>>>> I used the command
>>>> hg clone -r RELEASE-4.0.0
http://xenbits.xen.org/xen-4.0-testing.hg
>>>> to check out the sources. Compile and install went without a
hitch.
>>>>
>>>> Since debian squeeze uses grub2 it took me a while to find a
working
>>>> config.
>>>> This is my 40_custom for grub2:
>>>> menuentry "Xen 4.0.0 / Squeeze Kernel 2.6.32-3-amd64
pvops" --class debian
>>>> --class gnu-linux --class gnu --class os {
>>>>         recordfail=1
>>>>         if [ -n ${have_grubenv} ]; then save_env recordfail; fi
>>>>         set quiet=1
>>>>         insmod ext2
>>>>         insmod ext4
>>>>         set root=''(hd1,1)''
>>>>         search --no-floppy --fs-uuid --set
>>>> 91ab2378-76a4-4ab6-9065-078307ce8268
>>>>         multiboot /boot/xen-4.0.0.gz dummy=dummy dom0_mem=512M
>>>>         module /boot/vmlinuz-2.6.32-5-xen-amd64 dummy=dummy
>>>> root=UUID=91ab2378-76a4-4ab6-9065-078307ce8268 ro quiet
>>>>         module /boot/initrd.img-2.6.32-5-xen-amd64
>>>> }
>>>>
>>>> If I use "xm create /path/to/config.cfg"  the machine
is paused, and after
>>>> 100 seconds I get "Error: Device 0 (vif) could not be
connected. Hotplug
>>>> scripts not working".
>>>> I run udevd version 154, uuid is installed.
>>>>
>>>> When I start "udevadm monitor" while the xm create
command runs, this is
>>>> the output:
>>>> monitor will print the received events for:
>>>> UDEV - the event which udev sends out after rule processing
>>>> KERNEL - the kernel uevent
>>>>
>>>> KERNEL[1275038753.413971] add      /devices/virtual/net/tap19.0
(net)
>>>> UDEV  [1275038753.419757] add      /devices/virtual/net/tap19.0
(net)
>>>> KERNEL[1275038854.255484] remove   /devices/virtual/net/tap19.0
(net)
>>>> UDEV  [1275038854.259336] remove   /devices/virtual/net/tap19.0
(net)
>>>>
>>>> This is my virtual machine config:
>>>> import os, re
>>>> arch = os.uname()[4]
>>>> if re.search(''64'', arch):
>>>>         arch_libdir = ''lib64''
>>>> else:
>>>>         arch_libdir = ''lib''
>>>>
>>>> kernel = "/usr/lib/xen/boot/hvmloader"
>>>> builder=''hvm''
>>>> memory=2048
>>>> shadow_memory = 8
>>>> name = "xenwin7"
>>>> vif = [ '' bridge=eth0, mac=00:16:3e:00:12:34''
]
>>>> acpi = 1
>>>> apic = 1
>>>> disk = [
''file:/home/hwieser/xen/domains/win01/disk.img,hda,w'',
>>>>
''file:/home/hwieser/xen/domains/windows7_ultimate.iso,hdc:cdrom,r''
]
>>>> device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
>>>> boot="dc"
>>>> sdl = 0
>>>> vnc = 1
>>>> vncconsole = 1
>>>> vncpasswd = ''''
>>>> serial = ''pty''
>>>> usbdevice = ''tablet''
>>>>
>>>>
>>>> First I thought the issue was because the netbk module is
missing, but
>>>> it''s compiled in the kernel.
>>>> Here are the relevant parts of the .config:
>>>> # fgrep -i xen /boot/config-2.6.32-5-xen-amd64
>>>> CONFIG_XEN=y
>>>> CONFIG_XEN_MAX_DOMAIN_MEMORY=32
>>>> CONFIG_XEN_SAVE_RESTORE=y
>>>> # CONFIG_XEN_DEBUG_FS is not set
>>>> CONFIG_SWIOTLB_XEN=y
>>>> CONFIG_MICROCODE_XEN=y
>>>> CONFIG_XEN_DOM0=y
>>>> CONFIG_XEN_PRIVILEGED_GUEST=y
>>>> CONFIG_XEN_DOM0_PCI=y
>>>> # CONFIG_XEN_PCI_PASSTHROUGH is not set
>>>> CONFIG_PCI_XEN=y
>>>> CONFIG_XEN_PCIDEV_FRONTEND=y
>>>> CONFIG_XEN_BLKDEV_FRONTEND=m
>>>> CONFIG_NETXEN_NIC=m
>>>> CONFIG_XEN_NETDEV_FRONTEND=m
>>>> CONFIG_XEN_KBDDEV_FRONTEND=y
>>>> CONFIG_HVC_XEN=y
>>>> CONFIG_XEN_FBDEV_FRONTEND=y
>>>> CONFIG_XEN_BALLOON=y
>>>> CONFIG_XEN_SCRUB_PAGES=y
>>>> CONFIG_XEN_DEV_EVTCHN=m
>>>> CONFIG_XEN_BACKEND=y
>>>> CONFIG_XEN_NETDEV_BACKEND=y
>>>> CONFIG_XEN_BLKDEV_BACKEND=y
>>>> CONFIG_XEN_BLKDEV_TAP=m
>>>> CONFIG_XEN_BLKBACK_PAGEMAP=y
>>>> CONFIG_XEN_PCIDEV_BACKEND=y
>>>> CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
>>>> # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
>>>> # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
>>>> # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
>>>> # CONFIG_XEN_PCIDEV_BE_DEBUG is not set
>>>> CONFIG_XENFS=m
>>>> CONFIG_XEN_COMPAT_XENFS=y
>>>> CONFIG_XEN_SYS_HYPERVISOR=y
>>>> # CONFIG_XEN_PLATFORM_PCI is not set
>>>> CONFIG_XEN_MCE=y
>>>> CONFIG_XEN_XENBUS_FRONTEND=y
>>>> CONFIG_XEN_GNTDEV=y
>>>> CONFIG_XEN_S3=y
>>>> CONFIG_ACPI_PROCESSOR_XEN=m
>>>>
>>>>
>>>> This is my lsmod output:
>>>> Module                  Size  Used by
>>>> virtio_net             10529  0
>>>> netxen_nic             72759  0
>>>> nls_utf8                1208  0
>>>> ufs                    56490  0
>>>> qnx4                    6194  0
>>>> hfsplus                65286  0
>>>> hfs                    37471  0
>>>> minix                  21213  0
>>>> ntfs                  162876  0
>>>> vfat                    7900  0
>>>> msdos                   6202  0
>>>> fat                    40054  2 vfat,msdos
>>>> jfs                   140163  0
>>>> xfs                   437053  0
>>>> exportfs                3170  1 xfs
>>>> reiserfs              194188  0
>>>> ext4                  285355  0
>>>> jbd2                   66951  1 ext4
>>>> crc16                   1319  1 ext4
>>>> ext2                   52985  0
>>>> blktap                 28086  0
>>>> virtio_blk              4225  0
>>>> virtio                  3309  2 virtio_net,virtio_blk
>>>> pci_hotplug            21203  0
>>>> nf_conntrack_ipv4       9833  1
>>>> nf_defrag_ipv4          1139  1 nf_conntrack_ipv4
>>>> xt_state                1303  1
>>>> nf_conntrack           46567  2 nf_conntrack_ipv4,xt_state
>>>> tun                    10828  0
>>>> xt_physdev              1508  2
>>>> iptable_filter          2258  1
>>>> ip_tables              13899  1 iptable_filter
>>>> x_tables               12845  3 xt_state,xt_physdev,ip_tables
>>>> xen_evtchn              4259  1
>>>> bridge                 39614  0
>>>> stp                     1440  1 bridge
>>>> xenfs                   9568  1
>>>> xen_blkfront            8774  0
>>>> xen_netfront           15212  0
>>>> loop                   11783  0
>>>> firewire_sbp2          11498  0
>>>> snd_hda_codec_realtek   235506  1
>>>> snd_hda_intel          19875  0
>>>> snd_hda_codec          54244  2
snd_hda_codec_realtek,snd_hda_intel
>>>> snd_hwdep               5380  1 snd_hda_codec
>>>> snd_pcm                60535  2 snd_hda_intel,snd_hda_codec
>>>> snd_timer              15582  1 snd_pcm
>>>> nouveau               353136  1
>>>> ttm                    40066  1 nouveau
>>>> drm_kms_helper         20065  1 nouveau
>>>> drm                   143585  3 nouveau,ttm,drm_kms_helper
>>>> snd                    46446  6
>>>>
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
>>>> i2c_algo_bit            4225  1 nouveau
>>>> soundcore               4598  1 snd
>>>> i2c_core               15712  4
nouveau,drm_kms_helper,drm,i2c_algo_bit
>>>> snd_page_alloc          6249  2 snd_hda_intel,snd_pcm
>>>> usbhid                 33260  0
>>>> processor              36077  0
>>>> tpm_tis                 7336  0
>>>> evdev                   7352  3
>>>> tpm                     9917  1 tpm_tis
>>>> button                  4650  1 nouveau
>>>> hid                    62841  1 usbhid
>>>> tpm_bios                4521  1 tpm
>>>> psmouse                49777  0
>>>> pcspkr                  1699  0
>>>> wmi                     4323  0
>>>> serio_raw               3752  0
>>>> acpi_processor          5087  1 processor,[permanent]
>>>> ext3                  106550  1
>>>> jbd                    37101  1 ext3
>>>> mbcache                 5050  3 ext4,ext2,ext3
>>>> usb_storage            39449  0
>>>> sg                     18760  0
>>>> sr_mod                 12602  0
>>>> sd_mod                 29777  3
>>>> cdrom                  29415  1 sr_mod
>>>> crc_t10dif              1276  1 sd_mod
>>>> firewire_ohci          19468  0
>>>> firewire_core          36752  2 firewire_sbp2,firewire_ohci
>>>> crc_itu_t               1307  1 firewire_core
>>>> uhci_hcd               18537  0
>>>> ahci                   32358  2
>>>> tg3                    95679  0
>>>> libphy                 14054  1 tg3
>>>> libata                133536  1 ahci
>>>> scsi_mod              122133  6
>>>> firewire_sbp2,usb_storage,sg,sr_mod,sd_mod,libata
>>>> ehci_hcd               31071  0
>>>> usbcore               121991  5
usbhid,usb_storage,uhci_hcd,ehci_hcd
>>>> nls_base                6377  8
>>>> nls_utf8,hfsplus,hfs,ntfs,vfat,fat,jfs,usbcore
>>>> floppy                 49087  0
>>>> thermal                11674  0
>>>> thermal_sys            11942  2 processor,thermal
>>>>
>>>> And uname -a gives:
>>>> Linux jeatxenhw 2.6.32-5-xen-amd64 #1 SMP Mon May 17 20:24:46
UTC 2010
>>>> x86_64 GNU/Linux
>>>>
>>>> The vm is running windows 7, and I got it up and running once.
I could VNC
>>>> in and start the install.
>>>> As it wanted to reboot after the install it was botched and
never worked
>>>> again.
>>>>
>>>> Assistance would be greatly appreciated.
>>>>
>>>> regards,
>>>> Helmut
>>>>
>>>> _______________________________________________
>>>> 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
>
>    
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Tapas Mishra

2010-May-31 13:31 UTC

head link

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Check if this works
http://lists.xensource.com/archives/html/xen-users/2007-10/msg00799.html

On Mon, May 31, 2010 at 4:30 PM, Helmut Wieser <helmut.wieser@ieee.org>
wrote:> I tried looking at the scripts and found pbd.xml, pscsi_HBA.xml and
> pscsi.xml empty. I removed them and after a restart of xend they were
> present again. So I rebooted, started xend, removed the scripts and tried
to
> reboot the VM. No joy.
> I couldn''t find any hints in the xend init-script that recovers
the scripts,
> so it must be done by xend itself.
>
> I read about bug 1612 before I posted this, but I don''t think
it''s related.
> I downgraded udev to 151 and the problem persists.
>
> Also, here''s the part of my xend.log when (re)starting the VM
fails:
>
> [2010-05-31 09:46:09 1733] DEBUG (DevController:139) Waiting for devices
> vif2.
> [2010-05-31 09:46:09 1733] DEBUG (DevController:139) Waiting for devices
> vif.
> [2010-05-31 09:46:09 1733] DEBUG (DevController:144) Waiting for 0.
> [2010-05-31 09:46:09 1733] DEBUG (XendDomainInfo:1891)
> XendDomainInfo.handleShutdownWatch
> [2010-05-31 09:46:09 1733] DEBUG (DevController:628) hotplugStatusCallback
> /local/domain/0/backend/vif/2/0/hotplug-status.
> [2010-05-31 09:47:49 1733] DEBUG (XendDomainInfo:3053)
> XendDomainInfo.destroy: domid=2
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2411) Destroying device
> model
> [2010-05-31 09:47:50 1733] INFO (image:615) xenwin7 device model terminated
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2418) Releasing devices
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vif/0
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286)
> XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vbd/768
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286)
> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vbd/5632
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286)
> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/5632
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vfb/0
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286)
> XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing console/0
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286)
> XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2416) No device model
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2418) Releasing devices
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vif/0
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286)
> XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vbd/768
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286)
> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vbd/5632
> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286)
> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/5632
> [2010-05-31 09:47:50 1733] ERROR (XendDomainInfo:2244) Failed to restart
> domain 1.
> Traceback (most recent call last):
>  File
"usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", line
> 2230, in _restart
>    new_dom.waitForDevices()
>  File
"usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", line
> 1247, in waitForDevices
>    self.getDeviceController(devclass).waitForDevices()
>  File
"usr/lib/python2.5/site-packages/xen/xend/server/DevController.py",
> line 140, in waitForDevices
>    return map(self.waitForDevice, self.deviceIDs())
>  File
"usr/lib/python2.5/site-packages/xen/xend/server/DevController.py",
> line 155, in waitForDevice
>    (devid, self.deviceClass))
> VmError: Device 0 (vif) could not be connected. Hotplug scripts not
working.
>
>
> On 28.05.2010 17:32, Joseph M. Deming wrote:
>>
>> Take a look at this ongoing bug I am working on with a few people.
>> Sounds like a very similar scenario, except we are all seeing
>> kernel-oops alongside the similar behavior.  I can start a dom0, start
a
>> machine, even start multiple machines, each creating a fault, but still
>> functioning apparently normally.  But as soon as you take one of the
>> live machines down, no new ones will start, and the same machine cannot
>> be restarted.
>>
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1612
>>
>> On Fri, 2010-05-28 at 20:39 +0530, Tapas Mishra wrote:
>>
>>>
>>> On web many places I came across xend status is corrupted in such
>>> cases and corrupt xml files in /var/lib/xend/
>>> directories are the reason
>>>
>>> I also got error message Hotplug scripts not working.So I removed
them
>>> and kept them back check the files in the directory above I
mentioned
>>> if any one of them is blank then it is corrupt.Do not delete move
them
>>> to some other places in a directory reboot/restart see if the error
>>> persists.
>>> You will have to see which is corrupt file.Though it may not help
>>> directly but I had same problem and this was what worked for me.
>>>
>>>
>>> On Fri, May 28, 2010 at 8:31 PM, Helmut
Wieser<helmut.wieser@ieee.org>
>>>  wrote:
>>>
>>>>
>>>> Here''s what I found out: a reboot of the dom0 seems to
fix things.
>>>> I am able to start up the domU, and it works fine. Until I shut
it down
>>>> once, that is.
>>>>
>>>>
>>>>
>>>> On 28.05.2010 13:06, Helmut Wieser wrote:
>>>>
>>>>>
>>>>> Hi All,
>>>>>
>>>>> I''m having a similar issue as Ian Tobin some weeks
ago here:
>>>>>
>>>>>
http://lists.xensource.com/archives/html/xen-users/2010-02/msg00645.html
>>>>>
>>>>> I''m using Debian Squeeze amd64, downloaded the
experimental debian
>>>>> xen-amd64 kernel with pv_ops support.
>>>>> linux-headers-2.6.32-5-common-xen_2.6.32-13_amd64.deb
>>>>> linux-headers-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
>>>>> linux-image-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
>>>>> linux-kbuild-2.6.32_2.6.32-1_amd64.deb
>>>>> xen-linux-system-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
>>>>>
>>>>> I downloaded and compiled Xen 4.0 as specified here:
>>>>> http://wiki.xensource.com/xenwiki/Xen4.0
>>>>> I used the command
>>>>> hg clone -r RELEASE-4.0.0
http://xenbits.xen.org/xen-4.0-testing.hg
>>>>> to check out the sources. Compile and install went without
a hitch.
>>>>>
>>>>> Since debian squeeze uses grub2 it took me a while to find
a working
>>>>> config.
>>>>> This is my 40_custom for grub2:
>>>>> menuentry "Xen 4.0.0 / Squeeze Kernel 2.6.32-3-amd64
pvops" --class
>>>>> debian
>>>>> --class gnu-linux --class gnu --class os {
>>>>>        recordfail=1
>>>>>        if [ -n ${have_grubenv} ]; then save_env recordfail;
fi
>>>>>        set quiet=1
>>>>>        insmod ext2
>>>>>        insmod ext4
>>>>>        set root=''(hd1,1)''
>>>>>        search --no-floppy --fs-uuid --set
>>>>> 91ab2378-76a4-4ab6-9065-078307ce8268
>>>>>        multiboot /boot/xen-4.0.0.gz dummy=dummy
dom0_mem=512M
>>>>>        module /boot/vmlinuz-2.6.32-5-xen-amd64 dummy=dummy
>>>>> root=UUID=91ab2378-76a4-4ab6-9065-078307ce8268 ro quiet
>>>>>        module /boot/initrd.img-2.6.32-5-xen-amd64
>>>>> }
>>>>>
>>>>> If I use "xm create /path/to/config.cfg"  the
machine is paused, and
>>>>> after
>>>>> 100 seconds I get "Error: Device 0 (vif) could not be
connected.
>>>>> Hotplug
>>>>> scripts not working".
>>>>> I run udevd version 154, uuid is installed.
>>>>>
>>>>> When I start "udevadm monitor" while the xm
create command runs, this
>>>>> is
>>>>> the output:
>>>>> monitor will print the received events for:
>>>>> UDEV - the event which udev sends out after rule processing
>>>>> KERNEL - the kernel uevent
>>>>>
>>>>> KERNEL[1275038753.413971] add    
 /devices/virtual/net/tap19.0 (net)
>>>>> UDEV  [1275038753.419757] add    
 /devices/virtual/net/tap19.0 (net)
>>>>> KERNEL[1275038854.255484] remove  
/devices/virtual/net/tap19.0 (net)
>>>>> UDEV  [1275038854.259336] remove  
/devices/virtual/net/tap19.0 (net)
>>>>>
>>>>> This is my virtual machine config:
>>>>> import os, re
>>>>> arch = os.uname()[4]
>>>>> if re.search(''64'', arch):
>>>>>        arch_libdir = ''lib64''
>>>>> else:
>>>>>        arch_libdir = ''lib''
>>>>>
>>>>> kernel = "/usr/lib/xen/boot/hvmloader"
>>>>> builder=''hvm''
>>>>> memory=2048
>>>>> shadow_memory = 8
>>>>> name = "xenwin7"
>>>>> vif = [ '' bridge=eth0,
mac=00:16:3e:00:12:34'' ]
>>>>> acpi = 1
>>>>> apic = 1
>>>>> disk = [
''file:/home/hwieser/xen/domains/win01/disk.img,hda,w'',
>>>>>
''file:/home/hwieser/xen/domains/windows7_ultimate.iso,hdc:cdrom,r''
]
>>>>> device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
>>>>> boot="dc"
>>>>> sdl = 0
>>>>> vnc = 1
>>>>> vncconsole = 1
>>>>> vncpasswd = ''''
>>>>> serial = ''pty''
>>>>> usbdevice = ''tablet''
>>>>>
>>>>>
>>>>> First I thought the issue was because the netbk module is
missing, but
>>>>> it''s compiled in the kernel.
>>>>> Here are the relevant parts of the .config:
>>>>> # fgrep -i xen /boot/config-2.6.32-5-xen-amd64
>>>>> CONFIG_XEN=y
>>>>> CONFIG_XEN_MAX_DOMAIN_MEMORY=32
>>>>> CONFIG_XEN_SAVE_RESTORE=y
>>>>> # CONFIG_XEN_DEBUG_FS is not set
>>>>> CONFIG_SWIOTLB_XEN=y
>>>>> CONFIG_MICROCODE_XEN=y
>>>>> CONFIG_XEN_DOM0=y
>>>>> CONFIG_XEN_PRIVILEGED_GUEST=y
>>>>> CONFIG_XEN_DOM0_PCI=y
>>>>> # CONFIG_XEN_PCI_PASSTHROUGH is not set
>>>>> CONFIG_PCI_XEN=y
>>>>> CONFIG_XEN_PCIDEV_FRONTEND=y
>>>>> CONFIG_XEN_BLKDEV_FRONTEND=m
>>>>> CONFIG_NETXEN_NIC=m
>>>>> CONFIG_XEN_NETDEV_FRONTEND=m
>>>>> CONFIG_XEN_KBDDEV_FRONTEND=y
>>>>> CONFIG_HVC_XEN=y
>>>>> CONFIG_XEN_FBDEV_FRONTEND=y
>>>>> CONFIG_XEN_BALLOON=y
>>>>> CONFIG_XEN_SCRUB_PAGES=y
>>>>> CONFIG_XEN_DEV_EVTCHN=m
>>>>> CONFIG_XEN_BACKEND=y
>>>>> CONFIG_XEN_NETDEV_BACKEND=y
>>>>> CONFIG_XEN_BLKDEV_BACKEND=y
>>>>> CONFIG_XEN_BLKDEV_TAP=m
>>>>> CONFIG_XEN_BLKBACK_PAGEMAP=y
>>>>> CONFIG_XEN_PCIDEV_BACKEND=y
>>>>> CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
>>>>> # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
>>>>> # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
>>>>> # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
>>>>> # CONFIG_XEN_PCIDEV_BE_DEBUG is not set
>>>>> CONFIG_XENFS=m
>>>>> CONFIG_XEN_COMPAT_XENFS=y
>>>>> CONFIG_XEN_SYS_HYPERVISOR=y
>>>>> # CONFIG_XEN_PLATFORM_PCI is not set
>>>>> CONFIG_XEN_MCE=y
>>>>> CONFIG_XEN_XENBUS_FRONTEND=y
>>>>> CONFIG_XEN_GNTDEV=y
>>>>> CONFIG_XEN_S3=y
>>>>> CONFIG_ACPI_PROCESSOR_XEN=m
>>>>>
>>>>>
>>>>> This is my lsmod output:
>>>>> Module                  Size  Used by
>>>>> virtio_net             10529  0
>>>>> netxen_nic             72759  0
>>>>> nls_utf8                1208  0
>>>>> ufs                    56490  0
>>>>> qnx4                    6194  0
>>>>> hfsplus                65286  0
>>>>> hfs                    37471  0
>>>>> minix                  21213  0
>>>>> ntfs                  162876  0
>>>>> vfat                    7900  0
>>>>> msdos                   6202  0
>>>>> fat                    40054  2 vfat,msdos
>>>>> jfs                   140163  0
>>>>> xfs                   437053  0
>>>>> exportfs                3170  1 xfs
>>>>> reiserfs              194188  0
>>>>> ext4                  285355  0
>>>>> jbd2                   66951  1 ext4
>>>>> crc16                   1319  1 ext4
>>>>> ext2                   52985  0
>>>>> blktap                 28086  0
>>>>> virtio_blk              4225  0
>>>>> virtio                  3309  2 virtio_net,virtio_blk
>>>>> pci_hotplug            21203  0
>>>>> nf_conntrack_ipv4       9833  1
>>>>> nf_defrag_ipv4          1139  1 nf_conntrack_ipv4
>>>>> xt_state                1303  1
>>>>> nf_conntrack           46567  2 nf_conntrack_ipv4,xt_state
>>>>> tun                    10828  0
>>>>> xt_physdev              1508  2
>>>>> iptable_filter          2258  1
>>>>> ip_tables              13899  1 iptable_filter
>>>>> x_tables               12845  3
xt_state,xt_physdev,ip_tables
>>>>> xen_evtchn              4259  1
>>>>> bridge                 39614  0
>>>>> stp                     1440  1 bridge
>>>>> xenfs                   9568  1
>>>>> xen_blkfront            8774  0
>>>>> xen_netfront           15212  0
>>>>> loop                   11783  0
>>>>> firewire_sbp2          11498  0
>>>>> snd_hda_codec_realtek   235506  1
>>>>> snd_hda_intel          19875  0
>>>>> snd_hda_codec          54244  2
snd_hda_codec_realtek,snd_hda_intel
>>>>> snd_hwdep               5380  1 snd_hda_codec
>>>>> snd_pcm                60535  2 snd_hda_intel,snd_hda_codec
>>>>> snd_timer              15582  1 snd_pcm
>>>>> nouveau               353136  1
>>>>> ttm                    40066  1 nouveau
>>>>> drm_kms_helper         20065  1 nouveau
>>>>> drm                   143585  3 nouveau,ttm,drm_kms_helper
>>>>> snd                    46446  6
>>>>>
>>>>>
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
>>>>> i2c_algo_bit            4225  1 nouveau
>>>>> soundcore               4598  1 snd
>>>>> i2c_core               15712  4
nouveau,drm_kms_helper,drm,i2c_algo_bit
>>>>> snd_page_alloc          6249  2 snd_hda_intel,snd_pcm
>>>>> usbhid                 33260  0
>>>>> processor              36077  0
>>>>> tpm_tis                 7336  0
>>>>> evdev                   7352  3
>>>>> tpm                     9917  1 tpm_tis
>>>>> button                  4650  1 nouveau
>>>>> hid                    62841  1 usbhid
>>>>> tpm_bios                4521  1 tpm
>>>>> psmouse                49777  0
>>>>> pcspkr                  1699  0
>>>>> wmi                     4323  0
>>>>> serio_raw               3752  0
>>>>> acpi_processor          5087  1 processor,[permanent]
>>>>> ext3                  106550  1
>>>>> jbd                    37101  1 ext3
>>>>> mbcache                 5050  3 ext4,ext2,ext3
>>>>> usb_storage            39449  0
>>>>> sg                     18760  0
>>>>> sr_mod                 12602  0
>>>>> sd_mod                 29777  3
>>>>> cdrom                  29415  1 sr_mod
>>>>> crc_t10dif              1276  1 sd_mod
>>>>> firewire_ohci          19468  0
>>>>> firewire_core          36752  2 firewire_sbp2,firewire_ohci
>>>>> crc_itu_t               1307  1 firewire_core
>>>>> uhci_hcd               18537  0
>>>>> ahci                   32358  2
>>>>> tg3                    95679  0
>>>>> libphy                 14054  1 tg3
>>>>> libata                133536  1 ahci
>>>>> scsi_mod              122133  6
>>>>> firewire_sbp2,usb_storage,sg,sr_mod,sd_mod,libata
>>>>> ehci_hcd               31071  0
>>>>> usbcore               121991  5
usbhid,usb_storage,uhci_hcd,ehci_hcd
>>>>> nls_base                6377  8
>>>>> nls_utf8,hfsplus,hfs,ntfs,vfat,fat,jfs,usbcore
>>>>> floppy                 49087  0
>>>>> thermal                11674  0
>>>>> thermal_sys            11942  2 processor,thermal
>>>>>
>>>>> And uname -a gives:
>>>>> Linux jeatxenhw 2.6.32-5-xen-amd64 #1 SMP Mon May 17
20:24:46 UTC 2010
>>>>> x86_64 GNU/Linux
>>>>>
>>>>> The vm is running windows 7, and I got it up and running
once. I could
>>>>> VNC
>>>>> in and start the install.
>>>>> As it wanted to reboot after the install it was botched and
never
>>>>> worked
>>>>> again.
>>>>>
>>>>> Assistance would be greatly appreciated.
>>>>>
>>>>> regards,
>>>>> Helmut
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>
>>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>


-- 
Tapas

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

Helmut Wieser

2010-May-31 14:13 UTC

head link

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

No, this doesn''t help.
I''m currently trying to ditch the debian kernel and compiling one of 
jeremy''s kernels with a config close to the one from debian.

On 31.05.2010 15:31, Tapas Mishra wrote:> Check if this works
> http://lists.xensource.com/archives/html/xen-users/2007-10/msg00799.html
>
> On Mon, May 31, 2010 at 4:30 PM, Helmut
Wieser<helmut.wieser@ieee.org>  wrote:
>    
>> I tried looking at the scripts and found pbd.xml, pscsi_HBA.xml and
>> pscsi.xml empty. I removed them and after a restart of xend they were
>> present again. So I rebooted, started xend, removed the scripts and
tried to
>> reboot the VM. No joy.
>> I couldn''t find any hints in the xend init-script that
recovers the scripts,
>> so it must be done by xend itself.
>>
>> I read about bug 1612 before I posted this, but I don''t think
it''s related.
>> I downgraded udev to 151 and the problem persists.
>>
>> Also, here''s the part of my xend.log when (re)starting the VM
fails:
>>
>> [2010-05-31 09:46:09 1733] DEBUG (DevController:139) Waiting for
devices
>> vif2.
>> [2010-05-31 09:46:09 1733] DEBUG (DevController:139) Waiting for
devices
>> vif.
>> [2010-05-31 09:46:09 1733] DEBUG (DevController:144) Waiting for 0.
>> [2010-05-31 09:46:09 1733] DEBUG (XendDomainInfo:1891)
>> XendDomainInfo.handleShutdownWatch
>> [2010-05-31 09:46:09 1733] DEBUG (DevController:628)
hotplugStatusCallback
>> /local/domain/0/backend/vif/2/0/hotplug-status.
>> [2010-05-31 09:47:49 1733] DEBUG (XendDomainInfo:3053)
>> XendDomainInfo.destroy: domid=2
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2411) Destroying
device
>> model
>> [2010-05-31 09:47:50 1733] INFO (image:615) xenwin7 device model
terminated
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2418) Releasing
devices
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vif/0
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286)
>> XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vbd/768
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286)
>> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing
vbd/5632
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286)
>> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/5632
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vfb/0
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286)
>> XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing
console/0
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286)
>> XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2416) No device model
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2418) Releasing
devices
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vif/0
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286)
>> XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing vbd/768
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286)
>> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:2424) Removing
vbd/5632
>> [2010-05-31 09:47:50 1733] DEBUG (XendDomainInfo:1286)
>> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/5632
>> [2010-05-31 09:47:50 1733] ERROR (XendDomainInfo:2244) Failed to
restart
>> domain 1.
>> Traceback (most recent call last):
>>   File
"usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", line
>> 2230, in _restart
>>     new_dom.waitForDevices()
>>   File
"usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py", line
>> 1247, in waitForDevices
>>     self.getDeviceController(devclass).waitForDevices()
>>   File
"usr/lib/python2.5/site-packages/xen/xend/server/DevController.py",
>> line 140, in waitForDevices
>>     return map(self.waitForDevice, self.deviceIDs())
>>   File
"usr/lib/python2.5/site-packages/xen/xend/server/DevController.py",
>> line 155, in waitForDevice
>>     (devid, self.deviceClass))
>> VmError: Device 0 (vif) could not be connected. Hotplug scripts not
working.
>>
>>
>> On 28.05.2010 17:32, Joseph M. Deming wrote:
>>      
>>> Take a look at this ongoing bug I am working on with a few people.
>>> Sounds like a very similar scenario, except we are all seeing
>>> kernel-oops alongside the similar behavior.  I can start a dom0,
start a
>>> machine, even start multiple machines, each creating a fault, but
still
>>> functioning apparently normally.  But as soon as you take one of
the
>>> live machines down, no new ones will start, and the same machine
cannot
>>> be restarted.
>>>
>>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1612
>>>
>>> On Fri, 2010-05-28 at 20:39 +0530, Tapas Mishra wrote:
>>>
>>>        
>>>> On web many places I came across xend status is corrupted in
such
>>>> cases and corrupt xml files in /var/lib/xend/
>>>> directories are the reason
>>>>
>>>> I also got error message Hotplug scripts not working.So I
removed them
>>>> and kept them back check the files in the directory above I
mentioned
>>>> if any one of them is blank then it is corrupt.Do not delete
move them
>>>> to some other places in a directory reboot/restart see if the
error
>>>> persists.
>>>> You will have to see which is corrupt file.Though it may not
help
>>>> directly but I had same problem and this was what worked for
me.
>>>>
>>>>
>>>> On Fri, May 28, 2010 at 8:31 PM, Helmut
Wieser<helmut.wieser@ieee.org>
>>>>   wrote:
>>>>
>>>>          
>>>>> Here''s what I found out: a reboot of the dom0
seems to fix things.
>>>>> I am able to start up the domU, and it works fine. Until I
shut it down
>>>>> once, that is.
>>>>>
>>>>>
>>>>>
>>>>> On 28.05.2010 13:06, Helmut Wieser wrote:
>>>>>
>>>>>            
>>>>>> Hi All,
>>>>>>
>>>>>> I''m having a similar issue as Ian Tobin some
weeks ago here:
>>>>>>
>>>>>>
http://lists.xensource.com/archives/html/xen-users/2010-02/msg00645.html
>>>>>>
>>>>>> I''m using Debian Squeeze amd64, downloaded the
experimental debian
>>>>>> xen-amd64 kernel with pv_ops support.
>>>>>> linux-headers-2.6.32-5-common-xen_2.6.32-13_amd64.deb
>>>>>> linux-headers-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
>>>>>> linux-image-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
>>>>>> linux-kbuild-2.6.32_2.6.32-1_amd64.deb
>>>>>> xen-linux-system-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb
>>>>>>
>>>>>> I downloaded and compiled Xen 4.0 as specified here:
>>>>>> http://wiki.xensource.com/xenwiki/Xen4.0
>>>>>> I used the command
>>>>>> hg clone -r RELEASE-4.0.0
http://xenbits.xen.org/xen-4.0-testing.hg
>>>>>> to check out the sources. Compile and install went
without a hitch.
>>>>>>
>>>>>> Since debian squeeze uses grub2 it took me a while to
find a working
>>>>>> config.
>>>>>> This is my 40_custom for grub2:
>>>>>> menuentry "Xen 4.0.0 / Squeeze Kernel
2.6.32-3-amd64 pvops" --class
>>>>>> debian
>>>>>> --class gnu-linux --class gnu --class os {
>>>>>>         recordfail=1
>>>>>>         if [ -n ${have_grubenv} ]; then save_env
recordfail; fi
>>>>>>         set quiet=1
>>>>>>         insmod ext2
>>>>>>         insmod ext4
>>>>>>         set root=''(hd1,1)''
>>>>>>         search --no-floppy --fs-uuid --set
>>>>>> 91ab2378-76a4-4ab6-9065-078307ce8268
>>>>>>         multiboot /boot/xen-4.0.0.gz dummy=dummy
dom0_mem=512M
>>>>>>         module /boot/vmlinuz-2.6.32-5-xen-amd64
dummy=dummy
>>>>>> root=UUID=91ab2378-76a4-4ab6-9065-078307ce8268 ro quiet
>>>>>>         module /boot/initrd.img-2.6.32-5-xen-amd64
>>>>>> }
>>>>>>
>>>>>> If I use "xm create /path/to/config.cfg"  the
machine is paused, and
>>>>>> after
>>>>>> 100 seconds I get "Error: Device 0 (vif) could not
be connected.
>>>>>> Hotplug
>>>>>> scripts not working".
>>>>>> I run udevd version 154, uuid is installed.
>>>>>>
>>>>>> When I start "udevadm monitor" while the xm
create command runs, this
>>>>>> is
>>>>>> the output:
>>>>>> monitor will print the received events for:
>>>>>> UDEV - the event which udev sends out after rule
processing
>>>>>> KERNEL - the kernel uevent
>>>>>>
>>>>>> KERNEL[1275038753.413971] add     
/devices/virtual/net/tap19.0 (net)
>>>>>> UDEV  [1275038753.419757] add     
/devices/virtual/net/tap19.0 (net)
>>>>>> KERNEL[1275038854.255484] remove  
/devices/virtual/net/tap19.0 (net)
>>>>>> UDEV  [1275038854.259336] remove  
/devices/virtual/net/tap19.0 (net)
>>>>>>
>>>>>> This is my virtual machine config:
>>>>>> import os, re
>>>>>> arch = os.uname()[4]
>>>>>> if re.search(''64'', arch):
>>>>>>         arch_libdir = ''lib64''
>>>>>> else:
>>>>>>         arch_libdir = ''lib''
>>>>>>
>>>>>> kernel = "/usr/lib/xen/boot/hvmloader"
>>>>>> builder=''hvm''
>>>>>> memory=2048
>>>>>> shadow_memory = 8
>>>>>> name = "xenwin7"
>>>>>> vif = [ '' bridge=eth0,
mac=00:16:3e:00:12:34'' ]
>>>>>> acpi = 1
>>>>>> apic = 1
>>>>>> disk = [
''file:/home/hwieser/xen/domains/win01/disk.img,hda,w'',
>>>>>>
''file:/home/hwieser/xen/domains/windows7_ultimate.iso,hdc:cdrom,r''
]
>>>>>> device_model = ''/usr/'' + arch_libdir
+ ''/xen/bin/qemu-dm''
>>>>>> boot="dc"
>>>>>> sdl = 0
>>>>>> vnc = 1
>>>>>> vncconsole = 1
>>>>>> vncpasswd = ''''
>>>>>> serial = ''pty''
>>>>>> usbdevice = ''tablet''
>>>>>>
>>>>>>
>>>>>> First I thought the issue was because the netbk module
is missing, but
>>>>>> it''s compiled in the kernel.
>>>>>> Here are the relevant parts of the .config:
>>>>>> # fgrep -i xen /boot/config-2.6.32-5-xen-amd64
>>>>>> CONFIG_XEN=y
>>>>>> CONFIG_XEN_MAX_DOMAIN_MEMORY=32
>>>>>> CONFIG_XEN_SAVE_RESTORE=y
>>>>>> # CONFIG_XEN_DEBUG_FS is not set
>>>>>> CONFIG_SWIOTLB_XEN=y
>>>>>> CONFIG_MICROCODE_XEN=y
>>>>>> CONFIG_XEN_DOM0=y
>>>>>> CONFIG_XEN_PRIVILEGED_GUEST=y
>>>>>> CONFIG_XEN_DOM0_PCI=y
>>>>>> # CONFIG_XEN_PCI_PASSTHROUGH is not set
>>>>>> CONFIG_PCI_XEN=y
>>>>>> CONFIG_XEN_PCIDEV_FRONTEND=y
>>>>>> CONFIG_XEN_BLKDEV_FRONTEND=m
>>>>>> CONFIG_NETXEN_NIC=m
>>>>>> CONFIG_XEN_NETDEV_FRONTEND=m
>>>>>> CONFIG_XEN_KBDDEV_FRONTEND=y
>>>>>> CONFIG_HVC_XEN=y
>>>>>> CONFIG_XEN_FBDEV_FRONTEND=y
>>>>>> CONFIG_XEN_BALLOON=y
>>>>>> CONFIG_XEN_SCRUB_PAGES=y
>>>>>> CONFIG_XEN_DEV_EVTCHN=m
>>>>>> CONFIG_XEN_BACKEND=y
>>>>>> CONFIG_XEN_NETDEV_BACKEND=y
>>>>>> CONFIG_XEN_BLKDEV_BACKEND=y
>>>>>> CONFIG_XEN_BLKDEV_TAP=m
>>>>>> CONFIG_XEN_BLKBACK_PAGEMAP=y
>>>>>> CONFIG_XEN_PCIDEV_BACKEND=y
>>>>>> CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
>>>>>> # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
>>>>>> # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
>>>>>> # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
>>>>>> # CONFIG_XEN_PCIDEV_BE_DEBUG is not set
>>>>>> CONFIG_XENFS=m
>>>>>> CONFIG_XEN_COMPAT_XENFS=y
>>>>>> CONFIG_XEN_SYS_HYPERVISOR=y
>>>>>> # CONFIG_XEN_PLATFORM_PCI is not set
>>>>>> CONFIG_XEN_MCE=y
>>>>>> CONFIG_XEN_XENBUS_FRONTEND=y
>>>>>> CONFIG_XEN_GNTDEV=y
>>>>>> CONFIG_XEN_S3=y
>>>>>> CONFIG_ACPI_PROCESSOR_XEN=m
>>>>>>
>>>>>>
>>>>>> This is my lsmod output:
>>>>>> Module                  Size  Used by
>>>>>> virtio_net             10529  0
>>>>>> netxen_nic             72759  0
>>>>>> nls_utf8                1208  0
>>>>>> ufs                    56490  0
>>>>>> qnx4                    6194  0
>>>>>> hfsplus                65286  0
>>>>>> hfs                    37471  0
>>>>>> minix                  21213  0
>>>>>> ntfs                  162876  0
>>>>>> vfat                    7900  0
>>>>>> msdos                   6202  0
>>>>>> fat                    40054  2 vfat,msdos
>>>>>> jfs                   140163  0
>>>>>> xfs                   437053  0
>>>>>> exportfs                3170  1 xfs
>>>>>> reiserfs              194188  0
>>>>>> ext4                  285355  0
>>>>>> jbd2                   66951  1 ext4
>>>>>> crc16                   1319  1 ext4
>>>>>> ext2                   52985  0
>>>>>> blktap                 28086  0
>>>>>> virtio_blk              4225  0
>>>>>> virtio                  3309  2 virtio_net,virtio_blk
>>>>>> pci_hotplug            21203  0
>>>>>> nf_conntrack_ipv4       9833  1
>>>>>> nf_defrag_ipv4          1139  1 nf_conntrack_ipv4
>>>>>> xt_state                1303  1
>>>>>> nf_conntrack           46567  2
nf_conntrack_ipv4,xt_state
>>>>>> tun                    10828  0
>>>>>> xt_physdev              1508  2
>>>>>> iptable_filter          2258  1
>>>>>> ip_tables              13899  1 iptable_filter
>>>>>> x_tables               12845  3
xt_state,xt_physdev,ip_tables
>>>>>> xen_evtchn              4259  1
>>>>>> bridge                 39614  0
>>>>>> stp                     1440  1 bridge
>>>>>> xenfs                   9568  1
>>>>>> xen_blkfront            8774  0
>>>>>> xen_netfront           15212  0
>>>>>> loop                   11783  0
>>>>>> firewire_sbp2          11498  0
>>>>>> snd_hda_codec_realtek   235506  1
>>>>>> snd_hda_intel          19875  0
>>>>>> snd_hda_codec          54244  2
snd_hda_codec_realtek,snd_hda_intel
>>>>>> snd_hwdep               5380  1 snd_hda_codec
>>>>>> snd_pcm                60535  2
snd_hda_intel,snd_hda_codec
>>>>>> snd_timer              15582  1 snd_pcm
>>>>>> nouveau               353136  1
>>>>>> ttm                    40066  1 nouveau
>>>>>> drm_kms_helper         20065  1 nouveau
>>>>>> drm                   143585  3
nouveau,ttm,drm_kms_helper
>>>>>> snd                    46446  6
>>>>>>
>>>>>>
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
>>>>>> i2c_algo_bit            4225  1 nouveau
>>>>>> soundcore               4598  1 snd
>>>>>> i2c_core               15712  4
nouveau,drm_kms_helper,drm,i2c_algo_bit
>>>>>> snd_page_alloc          6249  2 snd_hda_intel,snd_pcm
>>>>>> usbhid                 33260  0
>>>>>> processor              36077  0
>>>>>> tpm_tis                 7336  0
>>>>>> evdev                   7352  3
>>>>>> tpm                     9917  1 tpm_tis
>>>>>> button                  4650  1 nouveau
>>>>>> hid                    62841  1 usbhid
>>>>>> tpm_bios                4521  1 tpm
>>>>>> psmouse                49777  0
>>>>>> pcspkr                  1699  0
>>>>>> wmi                     4323  0
>>>>>> serio_raw               3752  0
>>>>>> acpi_processor          5087  1 processor,[permanent]
>>>>>> ext3                  106550  1
>>>>>> jbd                    37101  1 ext3
>>>>>> mbcache                 5050  3 ext4,ext2,ext3
>>>>>> usb_storage            39449  0
>>>>>> sg                     18760  0
>>>>>> sr_mod                 12602  0
>>>>>> sd_mod                 29777  3
>>>>>> cdrom                  29415  1 sr_mod
>>>>>> crc_t10dif              1276  1 sd_mod
>>>>>> firewire_ohci          19468  0
>>>>>> firewire_core          36752  2
firewire_sbp2,firewire_ohci
>>>>>> crc_itu_t               1307  1 firewire_core
>>>>>> uhci_hcd               18537  0
>>>>>> ahci                   32358  2
>>>>>> tg3                    95679  0
>>>>>> libphy                 14054  1 tg3
>>>>>> libata                133536  1 ahci
>>>>>> scsi_mod              122133  6
>>>>>> firewire_sbp2,usb_storage,sg,sr_mod,sd_mod,libata
>>>>>> ehci_hcd               31071  0
>>>>>> usbcore               121991  5
usbhid,usb_storage,uhci_hcd,ehci_hcd
>>>>>> nls_base                6377  8
>>>>>> nls_utf8,hfsplus,hfs,ntfs,vfat,fat,jfs,usbcore
>>>>>> floppy                 49087  0
>>>>>> thermal                11674  0
>>>>>> thermal_sys            11942  2 processor,thermal
>>>>>>
>>>>>> And uname -a gives:
>>>>>> Linux jeatxenhw 2.6.32-5-xen-amd64 #1 SMP Mon May 17
20:24:46 UTC 2010
>>>>>> x86_64 GNU/Linux
>>>>>>
>>>>>> The vm is running windows 7, and I got it up and
running once. I could
>>>>>> VNC
>>>>>> in and start the install.
>>>>>> As it wanted to reboot after the install it was botched
and never
>>>>>> worked
>>>>>> again.
>>>>>>
>>>>>> Assistance would be greatly appreciated.
>>>>>>
>>>>>> regards,
>>>>>> Helmut
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>
>>>
>>>        
>> _______________________________________________
>> 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

Niels Dettenbach

2010-May-31 14:27 UTC

head link

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Am Montag 31 Mai 2010, 16:13:14 schrieb Helmut Wieser:> No, this doesn''t help.
> I''m currently trying to ditch the debian kernel and compiling one
of
> jeremy''s kernels with a config close to the one from debian.
...you may try this:

 1.) make shure udev is <=151 (i use 141 currently)


 2.) set in your xen kernel (if not): 

CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_WIRELESS_EXT_SYSFS=y    *
CONFIG_GPIO_SYSFS=y  *
CONFIG_VIDEO_PVRUSB2_SYSFS=y
CONFIG_RTC_INTF_SYSFS=y
CONFIG_XEN_SYSFS=y
CONFIG_SYSFS=y

(* only if applies to your hardware)

(not shure if it''s optimal but seems to work for me with 3.4x and 4.x)

=> reboot


 3.) make a
	mount -t sysfs sys /sys

=> if you still have any sysfs mounted you might try to unmount it before
this
step

I have a line
sys                     /sys            sysfs           auto 0 0

in my fstab which seems to help...

May be this is widely waste but it seems to help me - so pls don''t hit
me...
;)

Another thing is that you might have fractions of your (to new) udev config 
from before downgrading.

I''m working with gentoo which compiles things as i want so i''m
not fully in
the view what your distributor and package management might does well and what 
not with your (udev) configs...


may be this helps,


Niels.

- 

-- 

---

  Niels Dettenbach
  ---
  Syndicat IT&Internet
  http://www.syndicat.com
  T.-Muentzer.-Str. 2, 37308 Heilbad Heiligenstadt - DE
  ---
  Kryptoinfo: 
  PGP public key ID 651CA20D
  Fingerprint: 55E0 4DCD B04C 4A49 1586  88AE 54DC 4465 651C A20D
  https://syndicat.com/pub_key.asc
  ---


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

Helmut Wieser

2010-Jun-01 07:03 UTC

head link

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

No joy. I couldn''t find out what CONFIG_XEN_SYSFS does, but it
doesn''t
seem to be part of 2.6.31.13. I set all the other options apart from 
wireless that you suggested.

I''ll try to use Zhang Enming''s kernel config next.

Oh, and of course I get the infamous oops from bug 1612, I just never 
noticed it because my console doesn''t work with gfx passthru.
Here''s the output:

[  167.571125]   alloc irq_desc for 826 on node 0
[  167.571131]   alloc kstat_irqs on node 0
[  167.724755] BUG: unable to handle kernel NULL pointer dereference at 
0000000000000110
[  167.724943] IP: [<ffffffff8124ad7c>] netback_uevent+0x90/0xd5
[  167.725066] PGD 1d5e6067 PUD 1ddd2067 PMD 0
[  167.725296] Oops: 0000 [#1] SMP
[  167.725472] last sysfs file: /sys/devices/vif-1-0/uevent
[  167.725544] CPU 2
[  167.725653] Modules linked in: bridge stp xenfs blktap pci_hotplug 
xen_blkfront xen_netfront xen_evtchn loop firewire_sbp2 
snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep usbhid 
snd_pcm snd_timer snd hid wmi processor soundcore acpi_processor pcspkr 
psmouse snd_page_alloc serio_raw button evdev ext3 jbd mbcache 
usb_storage sr_mod sd_mod crc_t10dif cdrom tg3 firewire_ohci floppy 
thermal ahci firewire_core libphy libata thermal_sys crc_itu_t scsi_mod 
uhci_hcd ehci_hcd usbcore nls_base [last unloaded: scsi_wait_scan]
[  167.728264] Pid: 1955, comm: udevd Not tainted 2.6.31.13 #3 HP Z600 
Workstation
[  167.728356] RIP: e030:[<ffffffff8124ad7c>]  [<ffffffff8124ad7c>] 
netback_uevent+0x90/0xd5
[  167.728497] RSP: e02b:ffff880002095d98  EFLAGS: 00010246
[  167.728569] RAX: 0000000000000000 RBX: ffff88000231ea00 RCX: 
000000000080007c
[  167.728644] RDX: ffff88001d3ab440 RSI: 00000000a3c9a148 RDI: 
01000000000002c0
[  167.728722] RBP: ffff88000244e000 R08: 0000000000000000 R09: 
0000000000000000
[  167.728797] R10: ffffffff8100eddf R11: 00000000a3c9a148 R12: 
0000000000000000
[  167.728873] R13: ffff88001d3ab680 R14: ffff88001d5b9000 R15: 
ffffffff81502b30
[  167.728955] FS:  00007fdb8f1c5790(0000) GS:ffffc9000002e000(0000) 
knlGS:0000000000000000
[  167.729051] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[  167.729128] CR2: 0000000000000110 CR3: 000000001dcfc000 CR4: 
0000000000002660
[  167.729212] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 
0000000000000000
[  167.729303] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 
0000000000000400
[  167.729405] Process udevd (pid: 1955, threadinfo ffff880002094000, 
task ffff88001d5206c0)
[  167.729525] Stack:
[  167.729609]  ffffffff814608a6 00000000a3c9a148 0000000000000002 
ffff88000231ea40
[  167.729835] <0> ffff88000244e000 ffff88000231ea50 ffff88000231ea50 
ffffffff81283264
[  167.730179] <0> 00007fdb00000010 00000000a3c9a148 ffff880002095f50 
0000000000000000
[  167.730566] Call Trace:
[  167.730639]  [<ffffffff81283264>] ? dev_uevent+0x1a2/0x207
[  167.730714]  [<ffffffff81284725>] ? show_uevent+0x92/0xfd
[  167.730790]  [<ffffffff81282e8b>] ? dev_attr_show+0x2e/0x6b
[  167.730873]  [<ffffffff810ce1b0>] ? get_zeroed_page+0x21/0x76
[  167.730957]  [<ffffffff811647fb>] ? sysfs_read_file+0xbb/0x156
[  167.731051]  [<ffffffff8100e301>] ? xen_force_evtchn_callback+0x1d/0x37
[  167.731133]  [<ffffffff8100edf2>] ? check_events+0x12/0x20
[  167.731209]  [<ffffffff81105f91>] ? vfs_read+0xb1/0x123
[  167.731285]  [<ffffffff8100eddf>] ? xen_restore_fl_direct_end+0x0/0x1
[  167.731366]  [<ffffffff81384013>] ? _spin_unlock_irqrestore+0x24/0x3e
[  167.731445]  [<ffffffff811060eb>] ? sys_read+0x55/0x90
[  167.731527]  [<ffffffff81013e42>] ? system_call_fastpath+0x16/0x1b
[  167.731619] Code: c7 c6 33 1f 45 81 31 c0 48 89 ef e8 17 f0 f7 ff 85 
c0 74 0f 4c 89 ef bd f4 ff ff ff e8 66 3e eb ff eb 2b 4c 89 ef e8 5c 3e 
eb ff <49> 8b 94 24 10 01 00 00 48 89 ef 31 c0 48 c7 c6 3d 1f 45 81 e8
[  167.734689] RIP  [<ffffffff8124ad7c>] netback_uevent+0x90/0xd5
[  167.734818]  RSP <ffff880002095d98>
[  167.734890] CR2: 0000000000000110
[  167.734966] ---[ end trace d844f79248755c84 ]---
[  167.927689] device vif1.0 entered promiscuous mode
[  167.938021] eth0: port 2(vif1.0) entering forwarding state
[  168.100416] ip_tables: (C) 2000-2006 Netfilter Core Team
[  168.316187] nf_conntrack version 0.5.0 (4044 buckets, 16176 max)
[  168.316778] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. 
Please use
[  168.316873] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack 
module option or
[  168.316966] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[  168.427110] physdev match: using --physdev-out in the OUTPUT, FORWARD 
and POSTROUTING chains for non-bridged traffic is not supported anymore.
[  168.620471] tun: Universal TUN/TAP device driver, 1.6
[  168.620550] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[  168.668587] device tap1.0 entered promiscuous mode
[  168.668694] eth0: port 3(tap1.0) entering forwarding state
[  168.688096]   alloc irq_desc for 825 on node 0
[  168.688170]   alloc kstat_irqs on node 0

But the machine comes up for the first time and everything seems to be 
working fine.

I use udevd 151.


On 31.05.2010 16:27, Niels Dettenbach wrote:> Am Montag 31 Mai 2010, 16:13:14 schrieb Helmut Wieser:
>    
>> No, this doesn''t help.
>> I''m currently trying to ditch the debian kernel and compiling
one of
>> jeremy''s kernels with a config close to the one from debian.
>>      
> ...you may try this:
>
>   1.) make shure udev is<=151 (i use 141 currently)
>
>
>   2.) set in your xen kernel (if not):
>
> CONFIG_SYSFS_DEPRECATED=y
> CONFIG_SYSFS_DEPRECATED_V2=y
> CONFIG_ACPI_SYSFS_POWER=y
> CONFIG_WIRELESS_EXT_SYSFS=y    *
> CONFIG_GPIO_SYSFS=y  *
> CONFIG_VIDEO_PVRUSB2_SYSFS=y
> CONFIG_RTC_INTF_SYSFS=y
> CONFIG_XEN_SYSFS=y
> CONFIG_SYSFS=y
>
> (* only if applies to your hardware)
>
> (not shure if it''s optimal but seems to work for me with 3.4x and
4.x)
>
> =>  reboot
>
>
>   3.) make a
> 	mount -t sysfs sys /sys
>
> =>  if you still have any sysfs mounted you might try to unmount it
before this
> step
>
> I have a line
> sys                     /sys            sysfs           auto 0 0
>
> in my fstab which seems to help...
>
> May be this is widely waste but it seems to help me - so pls don''t
hit me...
> ;)
>
> Another thing is that you might have fractions of your (to new) udev config
> from before downgrading.
>
> I''m working with gentoo which compiles things as i want so
i''m not fully in
> the view what your distributor and package management might does well and
what
> not with your (udev) configs...
>
>
> may be this helps,
>
>
> Niels.
>
> -
>
>    
>
>
> _______________________________________________
> 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-01 09:53 UTC

head link

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Doesn''t seem to make a difference.
I even downgraded to udevd 141, no change.

I found my problem here, and applied the patch from 
http://lists.xensource.com/archives/html/xen-devel/2010-05/msg01462.html
But as it''s incomplete it didn''t help me with my
configuration.
I even tried to compile 2.6.32.14 and still have the same issue.

This is the relevant part of my drivers/xen/netback/netbus.c:
static int netback_uevent(struct xenbus_device *xdev, struct 
kobj_uevent_env *env)
{
         struct backend_info *be;
         struct xen_netif *netif;
         char *val;

         DPRINTK("netback_uevent");

         be = dev_get_drvdata(&xdev->dev);
         if (!be)
                 return 0;
         netif = be->netif;

         val = xenbus_read(XBT_NIL, xdev->nodename, "script",
NULL);
         if (IS_ERR(val)) {
                 int err = PTR_ERR(val);
                 xenbus_dev_fatal(xdev, err, "reading script");
                 return err;
         }
         else {
                 if (add_uevent_var(env, "script=%s", val)) {
                         kfree(val);
                         return -ENOMEM;
                 }
                 kfree(val);
         }

         if (add_uevent_var(env, "vif=%s", netif->dev->name))
                 return -ENOMEM;

         return 0;
}

This is the dmesg when I start a hvm domU for the first time:

BUG: unable to handle kernel NULL pointer dereference at 0000000000000110
IP: [<ffffffff8123610a>] netback_uevent+0x8e/0xbf
PGD 1e2bc067 PUD 1dd03067 PMD 0
Oops: 0000 [#1] SMP
last sysfs file: /sys/devices/vif-1-0/uevent
CPU 7
Modules linked in: bridge stp llc ipv6 xen_netfront firewire_sbp2 
snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm 
snd_timer snd tpm_tis soundcore tpm serio_raw snd_page_alloc pcspkr 
tpm_bios wmi firewire_ohci usb_storage firewire_core crc_itu_t tg3 
floppy [last unloaded: scsi_wait_scan]
Pid: 2141, comm: udevd Not tainted 2.6.32.14 #6 HP Z600 Workstation
RIP: e030:[<ffffffff8123610a>]  [<ffffffff8123610a>] 
netback_uevent+0x8e/0xbf
RSP: e02b:ffff88001d21fda8  EFLAGS: 00010246
RAX: 00200000000000c1 RBX: ffff88001cccde00 RCX: 0000000000800046
RDX: ffff88001d7e3b00 RSI: ffffea00006739a8 RDI: 00200000000002c0
RBP: ffff88001d21fdc8 R08: 0000000000000000 R09: ffffffff815c7cf0
R10: ffff88001e292904 R11: ffff88001e292154 R12: ffff88001e292000
R13: 0000000000000000 R14: ffff88001d7e3b80 R15: ffff88001e7be000
FS:  00007f7591154790(0000) GS:ffff880002ca2000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000110 CR3: 000000001d240000 CR4: 0000000000002660
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process udevd (pid: 2141, threadinfo ffff88001d21e000, task 
ffff88001e6a16e0)
Stack:
  ffff88001cccde40 ffff88001e292000 ffff88001cccde00 ffffffff815fe0e8
<0> ffff88001d21fdf8 ffffffff8122badc ffff88001cccde40 ffff88001e292000
<0> ffff88001fc49f60 ffff88001cccde50 ffff88001d21fe28 ffffffff81266772
Call Trace:
  [<ffffffff8122badc>] xenbus_uevent_backend+0x90/0xab
  [<ffffffff81266772>] dev_uevent+0x102/0x146
  [<ffffffff81267459>] show_uevent+0x81/0xd8
  [<ffffffff81266434>] dev_attr_show+0x22/0x49
  [<ffffffff810a0e41>] ? __get_free_pages+0x9/0x46
  [<ffffffff8112561c>] sysfs_read_file+0xac/0x12e
  [<ffffffff810d459f>] vfs_read+0xa6/0x103
  [<ffffffff810d46b2>] sys_read+0x45/0x69
  [<ffffffff81012a82>] system_call_fastpath+0x16/0x1b
Code: c6 79 48 53 81 31 c0 4c 89 e7 e8 ea 03 f8 ff 85 c0 74 10 4c 89 f7 
41 bc f4 ff ff ff e8 99 3e e9 ff eb 2d 4c 89 f7 e8 8f 3e e9 ff <49> 8b 
95 10 01 00 00 4c 89 e7 31 c0 48 c7 c6 83 48 53 81 41 bc
RIP  [<ffffffff8123610a>] netback_uevent+0x8e/0xbf
  RSP <ffff88001d21fda8>
CR2: 0000000000000110
---[ end trace 4f88c9bf70342ee1 ]---

I don''t get it, because the patch is supposed to prevent null pointers.
Either xdev itself is corrupt, or returning corrupt data.
I''m stumped.


On 01.06.2010 09:03, Helmut Wieser wrote:> No joy. I couldn''t find out what CONFIG_XEN_SYSFS does, but it
doesn''t
> seem to be part of 2.6.31.13. I set all the other options apart from 
> wireless that you suggested.
>
> I''ll try to use Zhang Enming''s kernel config next.
>
> Oh, and of course I get the infamous oops from bug 1612, I just never 
> noticed it because my console doesn''t work with gfx passthru.
> Here''s the output:
>
> [  167.571125]   alloc irq_desc for 826 on node 0
> [  167.571131]   alloc kstat_irqs on node 0
> [  167.724755] BUG: unable to handle kernel NULL pointer dereference 
> at 0000000000000110
> [  167.724943] IP: [<ffffffff8124ad7c>] netback_uevent+0x90/0xd5
> [  167.725066] PGD 1d5e6067 PUD 1ddd2067 PMD 0
> [  167.725296] Oops: 0000 [#1] SMP
> [  167.725472] last sysfs file: /sys/devices/vif-1-0/uevent
> [  167.725544] CPU 2
> [  167.725653] Modules linked in: bridge stp xenfs blktap pci_hotplug 
> xen_blkfront xen_netfront xen_evtchn loop firewire_sbp2 
> snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep usbhid 
> snd_pcm snd_timer snd hid wmi processor soundcore acpi_processor 
> pcspkr psmouse snd_page_alloc serio_raw button evdev ext3 jbd mbcache 
> usb_storage sr_mod sd_mod crc_t10dif cdrom tg3 firewire_ohci floppy 
> thermal ahci firewire_core libphy libata thermal_sys crc_itu_t 
> scsi_mod uhci_hcd ehci_hcd usbcore nls_base [last unloaded: 
> scsi_wait_scan]
> [  167.728264] Pid: 1955, comm: udevd Not tainted 2.6.31.13 #3 HP Z600 
> Workstation
> [  167.728356] RIP: e030:[<ffffffff8124ad7c>] 
[<ffffffff8124ad7c>]
> netback_uevent+0x90/0xd5
> [  167.728497] RSP: e02b:ffff880002095d98  EFLAGS: 00010246
> [  167.728569] RAX: 0000000000000000 RBX: ffff88000231ea00 RCX: 
> 000000000080007c
> [  167.728644] RDX: ffff88001d3ab440 RSI: 00000000a3c9a148 RDI: 
> 01000000000002c0
> [  167.728722] RBP: ffff88000244e000 R08: 0000000000000000 R09: 
> 0000000000000000
> [  167.728797] R10: ffffffff8100eddf R11: 00000000a3c9a148 R12: 
> 0000000000000000
> [  167.728873] R13: ffff88001d3ab680 R14: ffff88001d5b9000 R15: 
> ffffffff81502b30
> [  167.728955] FS:  00007fdb8f1c5790(0000) GS:ffffc9000002e000(0000) 
> knlGS:0000000000000000
> [  167.729051] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> [  167.729128] CR2: 0000000000000110 CR3: 000000001dcfc000 CR4: 
> 0000000000002660
> [  167.729212] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 
> 0000000000000000
> [  167.729303] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 
> 0000000000000400
> [  167.729405] Process udevd (pid: 1955, threadinfo ffff880002094000, 
> task ffff88001d5206c0)
> [  167.729525] Stack:
> [  167.729609]  ffffffff814608a6 00000000a3c9a148 0000000000000002 
> ffff88000231ea40
> [  167.729835] <0> ffff88000244e000 ffff88000231ea50 ffff88000231ea50
> ffffffff81283264
> [  167.730179] <0> 00007fdb00000010 00000000a3c9a148 ffff880002095f50
> 0000000000000000
> [  167.730566] Call Trace:
> [  167.730639]  [<ffffffff81283264>] ? dev_uevent+0x1a2/0x207
> [  167.730714]  [<ffffffff81284725>] ? show_uevent+0x92/0xfd
> [  167.730790]  [<ffffffff81282e8b>] ? dev_attr_show+0x2e/0x6b
> [  167.730873]  [<ffffffff810ce1b0>] ? get_zeroed_page+0x21/0x76
> [  167.730957]  [<ffffffff811647fb>] ? sysfs_read_file+0xbb/0x156
> [  167.731051]  [<ffffffff8100e301>] ?
xen_force_evtchn_callback+0x1d/0x37
> [  167.731133]  [<ffffffff8100edf2>] ? check_events+0x12/0x20
> [  167.731209]  [<ffffffff81105f91>] ? vfs_read+0xb1/0x123
> [  167.731285]  [<ffffffff8100eddf>] ?
xen_restore_fl_direct_end+0x0/0x1
> [  167.731366]  [<ffffffff81384013>] ?
_spin_unlock_irqrestore+0x24/0x3e
> [  167.731445]  [<ffffffff811060eb>] ? sys_read+0x55/0x90
> [  167.731527]  [<ffffffff81013e42>] ? system_call_fastpath+0x16/0x1b
> [  167.731619] Code: c7 c6 33 1f 45 81 31 c0 48 89 ef e8 17 f0 f7 ff 
> 85 c0 74 0f 4c 89 ef bd f4 ff ff ff e8 66 3e eb ff eb 2b 4c 89 ef e8 
> 5c 3e eb ff <49> 8b 94 24 10 01 00 00 48 89 ef 31 c0 48 c7 c6 3d 1f
45
> 81 e8
> [  167.734689] RIP  [<ffffffff8124ad7c>] netback_uevent+0x90/0xd5
> [  167.734818]  RSP <ffff880002095d98>
> [  167.734890] CR2: 0000000000000110
> [  167.734966] ---[ end trace d844f79248755c84 ]---
> [  167.927689] device vif1.0 entered promiscuous mode
> [  167.938021] eth0: port 2(vif1.0) entering forwarding state
> [  168.100416] ip_tables: (C) 2000-2006 Netfilter Core Team
> [  168.316187] nf_conntrack version 0.5.0 (4044 buckets, 16176 max)
> [  168.316778] CONFIG_NF_CT_ACCT is deprecated and will be removed 
> soon. Please use
> [  168.316873] nf_conntrack.acct=1 kernel parameter, acct=1 
> nf_conntrack module option or
> [  168.316966] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
> [  168.427110] physdev match: using --physdev-out in the OUTPUT, 
> FORWARD and POSTROUTING chains for non-bridged traffic is not 
> supported anymore.
> [  168.620471] tun: Universal TUN/TAP device driver, 1.6
> [  168.620550] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
> [  168.668587] device tap1.0 entered promiscuous mode
> [  168.668694] eth0: port 3(tap1.0) entering forwarding state
> [  168.688096]   alloc irq_desc for 825 on node 0
> [  168.688170]   alloc kstat_irqs on node 0
>
> But the machine comes up for the first time and everything seems to be 
> working fine.
>
> I use udevd 151.
>
>
> On 31.05.2010 16:27, Niels Dettenbach wrote:
>> Am Montag 31 Mai 2010, 16:13:14 schrieb Helmut Wieser:
>>    
>>> No, this doesn''t help.
>>> I''m currently trying to ditch the debian kernel and
compiling one of
>>> jeremy''s kernels with a config close to the one from
debian.
>>>      
>> ...you may try this:
>>
>>   1.) make shure udev is<=151 (i use 141 currently)
>>
>>
>>   2.) set in your xen kernel (if not):
>>
>> CONFIG_SYSFS_DEPRECATED=y
>> CONFIG_SYSFS_DEPRECATED_V2=y
>> CONFIG_ACPI_SYSFS_POWER=y
>> CONFIG_WIRELESS_EXT_SYSFS=y    *
>> CONFIG_GPIO_SYSFS=y  *
>> CONFIG_VIDEO_PVRUSB2_SYSFS=y
>> CONFIG_RTC_INTF_SYSFS=y
>> CONFIG_XEN_SYSFS=y
>> CONFIG_SYSFS=y
>>
>> (* only if applies to your hardware)
>>
>> (not shure if it''s optimal but seems to work for me with 3.4x
and 4.x)
>>
>> =>  reboot
>>
>>
>>   3.) make a
>> 	mount -t sysfs sys /sys
>>
>> =>  if you still have any sysfs mounted you might try to unmount it
before this
>> step
>>
>> I have a line
>> sys                     /sys            sysfs           auto 0 0
>>
>> in my fstab which seems to help...
>>
>> May be this is widely waste but it seems to help me - so pls
don''t hit me...
>> ;)
>>
>> Another thing is that you might have fractions of your (to new) udev
config
>> from before downgrading.
>>
>> I''m working with gentoo which compiles things as i want so
i''m not fully in
>> the view what your distributor and package management might does well
and what
>> not with your (udev) configs...
>>
>>
>> may be this helps,
>>
>>
>> Niels.
>>
>> -
>>
>>    
>>
>>
>> _______________________________________________
>> 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

Helmut Wieser

2010-Jun-02 07:29 UTC

head link

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Ok, now this is starting to get interesting. I previously had 
xen-netback statically compiled into the kernel.
It''s hard to debug static drivers, so I changed it to compile as a 
module. And lo and behold, the kernel oops disappeared.

It is not a stable solution though. Sometimes I still get the same oops, 
it seems to be a race condition.
I''m running 2.6.32.14 from Jeremy''s xen/stable-2.6.32.x


On 01.06.2010 11:53, Helmut Wieser wrote:> Doesn''t seem to make a difference.
> I even downgraded to udevd 141, no change.
>
> I found my problem here, and applied the patch from 
> http://lists.xensource.com/archives/html/xen-devel/2010-05/msg01462.html
> But as it''s incomplete it didn''t help me with my
configuration.
> I even tried to compile 2.6.32.14 and still have the same issue.
>
> This is the relevant part of my drivers/xen/netback/netbus.c:
> static int netback_uevent(struct xenbus_device *xdev, struct 
> kobj_uevent_env *env)
> {
>         struct backend_info *be;
>         struct xen_netif *netif;
>         char *val;
>
>         DPRINTK("netback_uevent");
>
>         be = dev_get_drvdata(&xdev->dev);
>         if (!be)
>                 return 0;
>         netif = be->netif;
>
>         val = xenbus_read(XBT_NIL, xdev->nodename, "script",
NULL);
>         if (IS_ERR(val)) {
>                 int err = PTR_ERR(val);
>                 xenbus_dev_fatal(xdev, err, "reading script");
>                 return err;
>         }
>         else {
>                 if (add_uevent_var(env, "script=%s", val)) {
>                         kfree(val);
>                         return -ENOMEM;
>                 }
>                 kfree(val);
>         }
>
>         if (add_uevent_var(env, "vif=%s",
netif->dev->name))
>                 return -ENOMEM;
>
>         return 0;
> }
>
> This is the dmesg when I start a hvm domU for the first time:
>
> BUG: unable to handle kernel NULL pointer dereference at 0000000000000110
> IP: [<ffffffff8123610a>] netback_uevent+0x8e/0xbf
> PGD 1e2bc067 PUD 1dd03067 PMD 0
> Oops: 0000 [#1] SMP
> last sysfs file: /sys/devices/vif-1-0/uevent
> CPU 7
> Modules linked in: bridge stp llc ipv6 xen_netfront firewire_sbp2 
> snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm 
> snd_timer snd tpm_tis soundcore tpm serio_raw snd_page_alloc pcspkr 
> tpm_bios wmi firewire_ohci usb_storage firewire_core crc_itu_t tg3 
> floppy [last unloaded: scsi_wait_scan]
> Pid: 2141, comm: udevd Not tainted 2.6.32.14 #6 HP Z600 Workstation
> RIP: e030:[<ffffffff8123610a>]  [<ffffffff8123610a>] 
> netback_uevent+0x8e/0xbf
> RSP: e02b:ffff88001d21fda8  EFLAGS: 00010246
> RAX: 00200000000000c1 RBX: ffff88001cccde00 RCX: 0000000000800046
> RDX: ffff88001d7e3b00 RSI: ffffea00006739a8 RDI: 00200000000002c0
> RBP: ffff88001d21fdc8 R08: 0000000000000000 R09: ffffffff815c7cf0
> R10: ffff88001e292904 R11: ffff88001e292154 R12: ffff88001e292000
> R13: 0000000000000000 R14: ffff88001d7e3b80 R15: ffff88001e7be000
> FS:  00007f7591154790(0000) GS:ffff880002ca2000(0000) 
> knlGS:0000000000000000
> CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 0000000000000110 CR3: 000000001d240000 CR4: 0000000000002660
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process udevd (pid: 2141, threadinfo ffff88001d21e000, task 
> ffff88001e6a16e0)
> Stack:
>  ffff88001cccde40 ffff88001e292000 ffff88001cccde00 ffffffff815fe0e8
> <0> ffff88001d21fdf8 ffffffff8122badc ffff88001cccde40
ffff88001e292000
> <0> ffff88001fc49f60 ffff88001cccde50 ffff88001d21fe28
ffffffff81266772
> Call Trace:
>  [<ffffffff8122badc>] xenbus_uevent_backend+0x90/0xab
>  [<ffffffff81266772>] dev_uevent+0x102/0x146
>  [<ffffffff81267459>] show_uevent+0x81/0xd8
>  [<ffffffff81266434>] dev_attr_show+0x22/0x49
>  [<ffffffff810a0e41>] ? __get_free_pages+0x9/0x46
>  [<ffffffff8112561c>] sysfs_read_file+0xac/0x12e
>  [<ffffffff810d459f>] vfs_read+0xa6/0x103
>  [<ffffffff810d46b2>] sys_read+0x45/0x69
>  [<ffffffff81012a82>] system_call_fastpath+0x16/0x1b
> Code: c6 79 48 53 81 31 c0 4c 89 e7 e8 ea 03 f8 ff 85 c0 74 10 4c 89 
> f7 41 bc f4 ff ff ff e8 99 3e e9 ff eb 2d 4c 89 f7 e8 8f 3e e9 ff
<49>
> 8b 95 10 01 00 00 4c 89 e7 31 c0 48 c7 c6 83 48 53 81 41 bc
> RIP  [<ffffffff8123610a>] netback_uevent+0x8e/0xbf
>  RSP <ffff88001d21fda8>
> CR2: 0000000000000110
> ---[ end trace 4f88c9bf70342ee1 ]---
>
> I don''t get it, because the patch is supposed to prevent null 
> pointers. Either xdev itself is corrupt, or returning corrupt data.
> I''m stumped.
>
>
> On 01.06.2010 09:03, Helmut Wieser wrote:
>> No joy. I couldn''t find out what CONFIG_XEN_SYSFS does, but it
>> doesn''t seem to be part of 2.6.31.13. I set all the other
options
>> apart from wireless that you suggested.
>>
>> I''ll try to use Zhang Enming''s kernel config next.
>>
>> Oh, and of course I get the infamous oops from bug 1612, I just never 
>> noticed it because my console doesn''t work with gfx passthru.
>> Here''s the output:
>>
>> [  167.571125]   alloc irq_desc for 826 on node 0
>> [  167.571131]   alloc kstat_irqs on node 0
>> [  167.724755] BUG: unable to handle kernel NULL pointer dereference 
>> at 0000000000000110
>> [  167.724943] IP: [<ffffffff8124ad7c>] netback_uevent+0x90/0xd5
>> [  167.725066] PGD 1d5e6067 PUD 1ddd2067 PMD 0
>> [  167.725296] Oops: 0000 [#1] SMP
>> [  167.725472] last sysfs file: /sys/devices/vif-1-0/uevent
>> [  167.725544] CPU 2
>> [  167.725653] Modules linked in: bridge stp xenfs blktap pci_hotplug 
>> xen_blkfront xen_netfront xen_evtchn loop firewire_sbp2 
>> snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep usbhid 
>> snd_pcm snd_timer snd hid wmi processor soundcore acpi_processor 
>> pcspkr psmouse snd_page_alloc serio_raw button evdev ext3 jbd mbcache 
>> usb_storage sr_mod sd_mod crc_t10dif cdrom tg3 firewire_ohci floppy 
>> thermal ahci firewire_core libphy libata thermal_sys crc_itu_t 
>> scsi_mod uhci_hcd ehci_hcd usbcore nls_base [last unloaded: 
>> scsi_wait_scan]
>> [  167.728264] Pid: 1955, comm: udevd Not tainted 2.6.31.13 #3 HP 
>> Z600 Workstation
>> [  167.728356] RIP: e030:[<ffffffff8124ad7c>] 
[<ffffffff8124ad7c>]
>> netback_uevent+0x90/0xd5
>> [  167.728497] RSP: e02b:ffff880002095d98  EFLAGS: 00010246
>> [  167.728569] RAX: 0000000000000000 RBX: ffff88000231ea00 RCX: 
>> 000000000080007c
>> [  167.728644] RDX: ffff88001d3ab440 RSI: 00000000a3c9a148 RDI: 
>> 01000000000002c0
>> [  167.728722] RBP: ffff88000244e000 R08: 0000000000000000 R09: 
>> 0000000000000000
>> [  167.728797] R10: ffffffff8100eddf R11: 00000000a3c9a148 R12: 
>> 0000000000000000
>> [  167.728873] R13: ffff88001d3ab680 R14: ffff88001d5b9000 R15: 
>> ffffffff81502b30
>> [  167.728955] FS:  00007fdb8f1c5790(0000) GS:ffffc9000002e000(0000) 
>> knlGS:0000000000000000
>> [  167.729051] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
>> [  167.729128] CR2: 0000000000000110 CR3: 000000001dcfc000 CR4: 
>> 0000000000002660
>> [  167.729212] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 
>> 0000000000000000
>> [  167.729303] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 
>> 0000000000000400
>> [  167.729405] Process udevd (pid: 1955, threadinfo ffff880002094000, 
>> task ffff88001d5206c0)
>> [  167.729525] Stack:
>> [  167.729609]  ffffffff814608a6 00000000a3c9a148 0000000000000002 
>> ffff88000231ea40
>> [  167.729835] <0> ffff88000244e000 ffff88000231ea50
ffff88000231ea50
>> ffffffff81283264
>> [  167.730179] <0> 00007fdb00000010 00000000a3c9a148
ffff880002095f50
>> 0000000000000000
>> [  167.730566] Call Trace:
>> [  167.730639]  [<ffffffff81283264>] ? dev_uevent+0x1a2/0x207
>> [  167.730714]  [<ffffffff81284725>] ? show_uevent+0x92/0xfd
>> [  167.730790]  [<ffffffff81282e8b>] ? dev_attr_show+0x2e/0x6b
>> [  167.730873]  [<ffffffff810ce1b0>] ? get_zeroed_page+0x21/0x76
>> [  167.730957]  [<ffffffff811647fb>] ? sysfs_read_file+0xbb/0x156
>> [  167.731051]  [<ffffffff8100e301>] ? 
>> xen_force_evtchn_callback+0x1d/0x37
>> [  167.731133]  [<ffffffff8100edf2>] ? check_events+0x12/0x20
>> [  167.731209]  [<ffffffff81105f91>] ? vfs_read+0xb1/0x123
>> [  167.731285]  [<ffffffff8100eddf>] ?
xen_restore_fl_direct_end+0x0/0x1
>> [  167.731366]  [<ffffffff81384013>] ?
_spin_unlock_irqrestore+0x24/0x3e
>> [  167.731445]  [<ffffffff811060eb>] ? sys_read+0x55/0x90
>> [  167.731527]  [<ffffffff81013e42>] ?
system_call_fastpath+0x16/0x1b
>> [  167.731619] Code: c7 c6 33 1f 45 81 31 c0 48 89 ef e8 17 f0 f7 ff 
>> 85 c0 74 0f 4c 89 ef bd f4 ff ff ff e8 66 3e eb ff eb 2b 4c 89 ef e8 
>> 5c 3e eb ff <49> 8b 94 24 10 01 00 00 48 89 ef 31 c0 48 c7 c6 3d
1f
>> 45 81 e8
>> [  167.734689] RIP  [<ffffffff8124ad7c>] netback_uevent+0x90/0xd5
>> [  167.734818]  RSP <ffff880002095d98>
>> [  167.734890] CR2: 0000000000000110
>> [  167.734966] ---[ end trace d844f79248755c84 ]---
>> [  167.927689] device vif1.0 entered promiscuous mode
>> [  167.938021] eth0: port 2(vif1.0) entering forwarding state
>> [  168.100416] ip_tables: (C) 2000-2006 Netfilter Core Team
>> [  168.316187] nf_conntrack version 0.5.0 (4044 buckets, 16176 max)
>> [  168.316778] CONFIG_NF_CT_ACCT is deprecated and will be removed 
>> soon. Please use
>> [  168.316873] nf_conntrack.acct=1 kernel parameter, acct=1 
>> nf_conntrack module option or
>> [  168.316966] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
>> [  168.427110] physdev match: using --physdev-out in the OUTPUT, 
>> FORWARD and POSTROUTING chains for non-bridged traffic is not 
>> supported anymore.
>> [  168.620471] tun: Universal TUN/TAP device driver, 1.6
>> [  168.620550] tun: (C) 1999-2004 Max Krasnyansky
<maxk@qualcomm.com>
>> [  168.668587] device tap1.0 entered promiscuous mode
>> [  168.668694] eth0: port 3(tap1.0) entering forwarding state
>> [  168.688096]   alloc irq_desc for 825 on node 0
>> [  168.688170]   alloc kstat_irqs on node 0
>>
>> But the machine comes up for the first time and everything seems to 
>> be working fine.
>>
>> I use udevd 151.
>>
>>
>> On 31.05.2010 16:27, Niels Dettenbach wrote:
>>> Am Montag 31 Mai 2010, 16:13:14 schrieb Helmut Wieser:
>>>    
>>>> No, this doesn''t help.
>>>> I''m currently trying to ditch the debian kernel and
compiling one of
>>>> jeremy''s kernels with a config close to the one from
debian.
>>>>      
>>> ...you may try this:
>>>
>>>   1.) make shure udev is<=151 (i use 141 currently)
>>>
>>>
>>>   2.) set in your xen kernel (if not):
>>>
>>> CONFIG_SYSFS_DEPRECATED=y
>>> CONFIG_SYSFS_DEPRECATED_V2=y
>>> CONFIG_ACPI_SYSFS_POWER=y
>>> CONFIG_WIRELESS_EXT_SYSFS=y    *
>>> CONFIG_GPIO_SYSFS=y  *
>>> CONFIG_VIDEO_PVRUSB2_SYSFS=y
>>> CONFIG_RTC_INTF_SYSFS=y
>>> CONFIG_XEN_SYSFS=y
>>> CONFIG_SYSFS=y
>>>
>>> (* only if applies to your hardware)
>>>
>>> (not shure if it''s optimal but seems to work for me with
3.4x and 4.x)
>>>
>>> =>  reboot
>>>
>>>
>>>   3.) make a
>>> 	mount -t sysfs sys /sys
>>>
>>> =>  if you still have any sysfs mounted you might try to unmount
it before this
>>> step
>>>
>>> I have a line
>>> sys                     /sys            sysfs           auto 0 0
>>>
>>> in my fstab which seems to help...
>>>
>>> May be this is widely waste but it seems to help me - so pls
don''t hit me...
>>> ;)
>>>
>>> Another thing is that you might have fractions of your (to new)
udev config
>>> from before downgrading.
>>>
>>> I''m working with gentoo which compiles things as i want so
i''m not fully in
>>> the view what your distributor and package management might does
well and what
>>> not with your (udev) configs...
>>>
>>>
>>> may be this helps,
>>>
>>>
>>> Niels.
>>>
>>> -
>>>
>>>    
>>>
>>>
>>> _______________________________________________
>>> 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

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

Helmut Wieser

2010-Jun-07 08:47 UTC

head link

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Also here setting viridian=1 doesn''t make a difference.

On 02.06.2010 09:29, Helmut Wieser wrote:> Ok, now this is starting to get interesting. I previously had 
> xen-netback statically compiled into the kernel.
> It''s hard to debug static drivers, so I changed it to compile as a
> module. And lo and behold, the kernel oops disappeared.
>
> It is not a stable solution though. Sometimes I still get the same 
> oops, it seems to be a race condition.
> I''m running 2.6.32.14 from Jeremy''s xen/stable-2.6.32.x
>
>
> On 01.06.2010 11:53, Helmut Wieser wrote:
>> Doesn''t seem to make a difference.
>> I even downgraded to udevd 141, no change.
>>
>> I found my problem here, and applied the patch from 
>>
http://lists.xensource.com/archives/html/xen-devel/2010-05/msg01462.html
>> But as it''s incomplete it didn''t help me with my
configuration.
>> I even tried to compile 2.6.32.14 and still have the same issue.
>>
>> This is the relevant part of my drivers/xen/netback/netbus.c:
>> static int netback_uevent(struct xenbus_device *xdev, struct 
>> kobj_uevent_env *env)
>> {
>>         struct backend_info *be;
>>         struct xen_netif *netif;
>>         char *val;
>>
>>         DPRINTK("netback_uevent");
>>
>>         be = dev_get_drvdata(&xdev->dev);
>>         if (!be)
>>                 return 0;
>>         netif = be->netif;
>>
>>         val = xenbus_read(XBT_NIL, xdev->nodename,
"script", NULL);
>>         if (IS_ERR(val)) {
>>                 int err = PTR_ERR(val);
>>                 xenbus_dev_fatal(xdev, err, "reading
script");
>>                 return err;
>>         }
>>         else {
>>                 if (add_uevent_var(env, "script=%s", val)) {
>>                         kfree(val);
>>                         return -ENOMEM;
>>                 }
>>                 kfree(val);
>>         }
>>
>>         if (add_uevent_var(env, "vif=%s",
netif->dev->name))
>>                 return -ENOMEM;
>>
>>         return 0;
>> }
>>
>> This is the dmesg when I start a hvm domU for the first time:
>>
>> BUG: unable to handle kernel NULL pointer dereference at
0000000000000110
>> IP: [<ffffffff8123610a>] netback_uevent+0x8e/0xbf
>> PGD 1e2bc067 PUD 1dd03067 PMD 0
>> Oops: 0000 [#1] SMP
>> last sysfs file: /sys/devices/vif-1-0/uevent
>> CPU 7
>> Modules linked in: bridge stp llc ipv6 xen_netfront firewire_sbp2 
>> snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm 
>> snd_timer snd tpm_tis soundcore tpm serio_raw snd_page_alloc pcspkr 
>> tpm_bios wmi firewire_ohci usb_storage firewire_core crc_itu_t tg3 
>> floppy [last unloaded: scsi_wait_scan]
>> Pid: 2141, comm: udevd Not tainted 2.6.32.14 #6 HP Z600 Workstation
>> RIP: e030:[<ffffffff8123610a>]  [<ffffffff8123610a>] 
>> netback_uevent+0x8e/0xbf
>> RSP: e02b:ffff88001d21fda8  EFLAGS: 00010246
>> RAX: 00200000000000c1 RBX: ffff88001cccde00 RCX: 0000000000800046
>> RDX: ffff88001d7e3b00 RSI: ffffea00006739a8 RDI: 00200000000002c0
>> RBP: ffff88001d21fdc8 R08: 0000000000000000 R09: ffffffff815c7cf0
>> R10: ffff88001e292904 R11: ffff88001e292154 R12: ffff88001e292000
>> R13: 0000000000000000 R14: ffff88001d7e3b80 R15: ffff88001e7be000
>> FS:  00007f7591154790(0000) GS:ffff880002ca2000(0000) 
>> knlGS:0000000000000000
>> CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
>> CR2: 0000000000000110 CR3: 000000001d240000 CR4: 0000000000002660
>> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
>> Process udevd (pid: 2141, threadinfo ffff88001d21e000, task 
>> ffff88001e6a16e0)
>> Stack:
>>  ffff88001cccde40 ffff88001e292000 ffff88001cccde00 ffffffff815fe0e8
>> <0> ffff88001d21fdf8 ffffffff8122badc ffff88001cccde40
ffff88001e292000
>> <0> ffff88001fc49f60 ffff88001cccde50 ffff88001d21fe28
ffffffff81266772
>> Call Trace:
>>  [<ffffffff8122badc>] xenbus_uevent_backend+0x90/0xab
>>  [<ffffffff81266772>] dev_uevent+0x102/0x146
>>  [<ffffffff81267459>] show_uevent+0x81/0xd8
>>  [<ffffffff81266434>] dev_attr_show+0x22/0x49
>>  [<ffffffff810a0e41>] ? __get_free_pages+0x9/0x46
>>  [<ffffffff8112561c>] sysfs_read_file+0xac/0x12e
>>  [<ffffffff810d459f>] vfs_read+0xa6/0x103
>>  [<ffffffff810d46b2>] sys_read+0x45/0x69
>>  [<ffffffff81012a82>] system_call_fastpath+0x16/0x1b
>> Code: c6 79 48 53 81 31 c0 4c 89 e7 e8 ea 03 f8 ff 85 c0 74 10 4c 89 
>> f7 41 bc f4 ff ff ff e8 99 3e e9 ff eb 2d 4c 89 f7 e8 8f 3e e9 ff 
>> <49> 8b 95 10 01 00 00 4c 89 e7 31 c0 48 c7 c6 83 48 53 81 41 bc
>> RIP  [<ffffffff8123610a>] netback_uevent+0x8e/0xbf
>>  RSP <ffff88001d21fda8>
>> CR2: 0000000000000110
>> ---[ end trace 4f88c9bf70342ee1 ]---
>>
>> I don''t get it, because the patch is supposed to prevent null 
>> pointers. Either xdev itself is corrupt, or returning corrupt data.
>> I''m stumped.
>>
>>
>> On 01.06.2010 09:03, Helmut Wieser wrote:
>>> No joy. I couldn''t find out what CONFIG_XEN_SYSFS does,
but it
>>> doesn''t seem to be part of 2.6.31.13. I set all the other
options
>>> apart from wireless that you suggested.
>>>
>>> I''ll try to use Zhang Enming''s kernel config
next.
>>>
>>> Oh, and of course I get the infamous oops from bug 1612, I just 
>>> never noticed it because my console doesn''t work with gfx
passthru.
>>> Here''s the output:
>>>
>>> [  167.571125]   alloc irq_desc for 826 on node 0
>>> [  167.571131]   alloc kstat_irqs on node 0
>>> [  167.724755] BUG: unable to handle kernel NULL pointer
dereference
>>> at 0000000000000110
>>> [  167.724943] IP: [<ffffffff8124ad7c>]
netback_uevent+0x90/0xd5
>>> [  167.725066] PGD 1d5e6067 PUD 1ddd2067 PMD 0
>>> [  167.725296] Oops: 0000 [#1] SMP
>>> [  167.725472] last sysfs file: /sys/devices/vif-1-0/uevent
>>> [  167.725544] CPU 2
>>> [  167.725653] Modules linked in: bridge stp xenfs blktap 
>>> pci_hotplug xen_blkfront xen_netfront xen_evtchn loop firewire_sbp2
>>> snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep usbhid 
>>> snd_pcm snd_timer snd hid wmi processor soundcore acpi_processor 
>>> pcspkr psmouse snd_page_alloc serio_raw button evdev ext3 jbd 
>>> mbcache usb_storage sr_mod sd_mod crc_t10dif cdrom tg3
firewire_ohci
>>> floppy thermal ahci firewire_core libphy libata thermal_sys 
>>> crc_itu_t scsi_mod uhci_hcd ehci_hcd usbcore nls_base [last 
>>> unloaded: scsi_wait_scan]
>>> [  167.728264] Pid: 1955, comm: udevd Not tainted 2.6.31.13 #3 HP 
>>> Z600 Workstation
>>> [  167.728356] RIP: e030:[<ffffffff8124ad7c>] 
[<ffffffff8124ad7c>]
>>> netback_uevent+0x90/0xd5
>>> [  167.728497] RSP: e02b:ffff880002095d98  EFLAGS: 00010246
>>> [  167.728569] RAX: 0000000000000000 RBX: ffff88000231ea00 RCX: 
>>> 000000000080007c
>>> [  167.728644] RDX: ffff88001d3ab440 RSI: 00000000a3c9a148 RDI: 
>>> 01000000000002c0
>>> [  167.728722] RBP: ffff88000244e000 R08: 0000000000000000 R09: 
>>> 0000000000000000
>>> [  167.728797] R10: ffffffff8100eddf R11: 00000000a3c9a148 R12: 
>>> 0000000000000000
>>> [  167.728873] R13: ffff88001d3ab680 R14: ffff88001d5b9000 R15: 
>>> ffffffff81502b30
>>> [  167.728955] FS:  00007fdb8f1c5790(0000)
GS:ffffc9000002e000(0000)
>>> knlGS:0000000000000000
>>> [  167.729051] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
>>> [  167.729128] CR2: 0000000000000110 CR3: 000000001dcfc000 CR4: 
>>> 0000000000002660
>>> [  167.729212] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 
>>> 0000000000000000
>>> [  167.729303] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 
>>> 0000000000000400
>>> [  167.729405] Process udevd (pid: 1955, threadinfo 
>>> ffff880002094000, task ffff88001d5206c0)
>>> [  167.729525] Stack:
>>> [  167.729609]  ffffffff814608a6 00000000a3c9a148 0000000000000002 
>>> ffff88000231ea40
>>> [  167.729835] <0> ffff88000244e000 ffff88000231ea50 
>>> ffff88000231ea50 ffffffff81283264
>>> [  167.730179] <0> 00007fdb00000010 00000000a3c9a148 
>>> ffff880002095f50 0000000000000000
>>> [  167.730566] Call Trace:
>>> [  167.730639]  [<ffffffff81283264>] ? dev_uevent+0x1a2/0x207
>>> [  167.730714]  [<ffffffff81284725>] ? show_uevent+0x92/0xfd
>>> [  167.730790]  [<ffffffff81282e8b>] ?
dev_attr_show+0x2e/0x6b
>>> [  167.730873]  [<ffffffff810ce1b0>] ?
get_zeroed_page+0x21/0x76
>>> [  167.730957]  [<ffffffff811647fb>] ?
sysfs_read_file+0xbb/0x156
>>> [  167.731051]  [<ffffffff8100e301>] ? 
>>> xen_force_evtchn_callback+0x1d/0x37
>>> [  167.731133]  [<ffffffff8100edf2>] ? check_events+0x12/0x20
>>> [  167.731209]  [<ffffffff81105f91>] ? vfs_read+0xb1/0x123
>>> [  167.731285]  [<ffffffff8100eddf>] ?
xen_restore_fl_direct_end+0x0/0x1
>>> [  167.731366]  [<ffffffff81384013>] ?
_spin_unlock_irqrestore+0x24/0x3e
>>> [  167.731445]  [<ffffffff811060eb>] ? sys_read+0x55/0x90
>>> [  167.731527]  [<ffffffff81013e42>] ?
system_call_fastpath+0x16/0x1b
>>> [  167.731619] Code: c7 c6 33 1f 45 81 31 c0 48 89 ef e8 17 f0 f7
ff
>>> 85 c0 74 0f 4c 89 ef bd f4 ff ff ff e8 66 3e eb ff eb 2b 4c 89 ef
e8
>>> 5c 3e eb ff <49> 8b 94 24 10 01 00 00 48 89 ef 31 c0 48 c7 c6
3d 1f
>>> 45 81 e8
>>> [  167.734689] RIP  [<ffffffff8124ad7c>]
netback_uevent+0x90/0xd5
>>> [  167.734818]  RSP <ffff880002095d98>
>>> [  167.734890] CR2: 0000000000000110
>>> [  167.734966] ---[ end trace d844f79248755c84 ]---
>>> [  167.927689] device vif1.0 entered promiscuous mode
>>> [  167.938021] eth0: port 2(vif1.0) entering forwarding state
>>> [  168.100416] ip_tables: (C) 2000-2006 Netfilter Core Team
>>> [  168.316187] nf_conntrack version 0.5.0 (4044 buckets, 16176 max)
>>> [  168.316778] CONFIG_NF_CT_ACCT is deprecated and will be removed 
>>> soon. Please use
>>> [  168.316873] nf_conntrack.acct=1 kernel parameter, acct=1 
>>> nf_conntrack module option or
>>> [  168.316966] sysctl net.netfilter.nf_conntrack_acct=1 to enable
it.
>>> [  168.427110] physdev match: using --physdev-out in the OUTPUT, 
>>> FORWARD and POSTROUTING chains for non-bridged traffic is not 
>>> supported anymore.
>>> [  168.620471] tun: Universal TUN/TAP device driver, 1.6
>>> [  168.620550] tun: (C) 1999-2004 Max Krasnyansky
<maxk@qualcomm.com>
>>> [  168.668587] device tap1.0 entered promiscuous mode
>>> [  168.668694] eth0: port 3(tap1.0) entering forwarding state
>>> [  168.688096]   alloc irq_desc for 825 on node 0
>>> [  168.688170]   alloc kstat_irqs on node 0
>>>
>>> But the machine comes up for the first time and everything seems to
>>> be working fine.
>>>
>>> I use udevd 151.
>>>
>>>
>>> On 31.05.2010 16:27, Niels Dettenbach wrote:
>>>> Am Montag 31 Mai 2010, 16:13:14 schrieb Helmut Wieser:
>>>>    
>>>>> No, this doesn''t help.
>>>>> I''m currently trying to ditch the debian kernel
and compiling one of
>>>>> jeremy''s kernels with a config close to the one
from debian.
>>>>>      
>>>> ...you may try this:
>>>>
>>>>   1.) make shure udev is<=151 (i use 141 currently)
>>>>
>>>>
>>>>   2.) set in your xen kernel (if not):
>>>>
>>>> CONFIG_SYSFS_DEPRECATED=y
>>>> CONFIG_SYSFS_DEPRECATED_V2=y
>>>> CONFIG_ACPI_SYSFS_POWER=y
>>>> CONFIG_WIRELESS_EXT_SYSFS=y    *
>>>> CONFIG_GPIO_SYSFS=y  *
>>>> CONFIG_VIDEO_PVRUSB2_SYSFS=y
>>>> CONFIG_RTC_INTF_SYSFS=y
>>>> CONFIG_XEN_SYSFS=y
>>>> CONFIG_SYSFS=y
>>>>
>>>> (* only if applies to your hardware)
>>>>
>>>> (not shure if it''s optimal but seems to work for me
with 3.4x and 4.x)
>>>>
>>>> =>  reboot
>>>>
>>>>
>>>>   3.) make a
>>>> 	mount -t sysfs sys /sys
>>>>
>>>> =>  if you still have any sysfs mounted you might try to
unmount it before this
>>>> step
>>>>
>>>> I have a line
>>>> sys                     /sys            sysfs           auto 0
0
>>>>
>>>> in my fstab which seems to help...
>>>>
>>>> May be this is widely waste but it seems to help me - so pls
don''t hit me...
>>>> ;)
>>>>
>>>> Another thing is that you might have fractions of your (to new)
udev config
>>>> from before downgrading.
>>>>
>>>> I''m working with gentoo which compiles things as i
want so i''m not fully in
>>>> the view what your distributor and package management might
does well and what
>>>> not with your (udev) configs...
>>>>
>>>>
>>>> may be this helps,
>>>>
>>>>
>>>> Niels.
>>>>
>>>> -
>>>>
>>>>    
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>
>
> _______________________________________________
> 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

Possibly Parallel Threads

Search for more apparently analagous threads

Xen users - May 2010 - Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

[Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

[Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Re: [Xen-users] Error: Device 0 (vif) could notbeconnected. Hotplugscripts not working

Possibly Parallel Threads