Hi, Ian Campbell <[email protected]> writes: > Which dom0 kernel is this?
$ cat /proc/version Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-35) ([email protected]) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Jun 14 12:46:30 UTC 2011 in both working and broken case. > Assuming 2.6.32 (squeeze) based do you have the xen-blkback/blktap > modules (and any other backend modules) loaded? squeeze has CONFIG_XEN_BLKDEV_BACKEND=y blktap is not loaded on the working system either. I tried modprobing it now but it does not seem to change the behavior. Just for completeness here's also lsmod from broken system: Module Size Used by loop 11799 0 r8169 29311 0 via 32847 0 btrfs 375805 0 zlib_deflate 17746 1 btrfs crc32c 2560 1 libcrc32c 1074 1 btrfs ufs 56458 0 qnx4 6194 0 hfsplus 65270 0 hfs 37455 0 minix 21197 0 ntfs 162780 0 vfat 7884 0 msdos 6202 0 fat 40038 2 vfat,msdos jfs 140089 0 xfs 435383 0 reiserfs 194140 0 ext4 288318 0 jbd2 67015 1 ext4 ext2 52905 0 xt_multiport 2267 1 iptable_filter 2258 1 ip_tables 13915 1 iptable_filter x_tables 12845 2 xt_multiport,ip_tables binfmt_misc 6431 1 nfsd 254782 11 lockd 57603 1 nfsd nfs_acl 2031 1 nfsd auth_rpcgss 33476 1 nfsd sunrpc 161525 10 nfsd,lockd,nfs_acl,auth_rpcgss exportfs 3170 2 xfs,nfsd parport_pc 18855 0 ppdev 5030 0 lp 7462 0 parport 27954 3 parport_pc,ppdev,lp sco 7225 0 bnep 9459 0 rfcomm 29613 0 l2cap 24736 4 bnep,rfcomm crc16 1319 2 ext4,l2cap bluetooth 41827 4 sco,bnep,rfcomm,l2cap rfkill 13028 1 bluetooth bridge 39662 0 stp 1440 1 bridge xen_evtchn 4339 1 xenfs 9600 1 cpufreq_userspace 1992 0 cpufreq_conservative 5162 0 cpufreq_stats 2659 0 cpufreq_powersave 902 0 fuse 50908 1 kvm 214248 0 f71882fg 26406 0 coretemp 4325 0 snd_hda_codec_realtek 235602 1 snd_hda_intel 20035 2 snd_hda_codec 54244 2 snd_hda_codec_realtek,snd_hda_intel snd_hwdep 5380 1 snd_hda_codec snd_pcm_oss 32591 0 snd_mixer_oss 12606 1 snd_pcm_oss snd_pcm 60551 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_seq_midi 4400 0 snd_rawmidi 15515 1 snd_seq_midi snd_seq_midi_event 4628 1 snd_seq_midi snd_seq 42881 2 snd_seq_midi,snd_seq_midi_event i915 255710 2 drm_kms_helper 20369 1 i915 snd_timer 15582 2 snd_pcm,snd_seq drm 143329 4 via,i915,drm_kms_helper i2c_i801 7830 0 snd_seq_device 4493 3 snd_seq_midi,snd_rawmidi,snd_seq i2c_algo_bit 4225 1 i915 i2c_core 15819 5 i915,drm_kms_helper,drm,i2c_i801,i2c_algo_bit video 17445 1 i915 snd 46526 15 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device output 1692 1 video soundcore 4598 1 snd snd_page_alloc 6249 2 snd_hda_intel,snd_pcm pcspkr 1699 0 evdev 7352 6 asix 12749 0 cdc_acm 15126 0 processor 35941 0 usbnet 11811 1 asix acpi_processor 5087 1 processor,[permanent] button 4650 1 i915 ext3 106630 2 jbd 37085 1 ext3 mbcache 5050 3 ext4,ext2,ext3 dm_mod 53706 0 sg 24069 0 usbhid 33276 0 hid 63257 1 usbhid sr_mod 12602 0 sd_mod 29905 4 crc_t10dif 1276 1 sd_mod cdrom 29415 1 sr_mod usb_storage 39961 0 ahci 32534 3 libata 133744 1 ahci firewire_ohci 19660 0 firewire_core 36848 1 firewire_ohci crc_itu_t 1307 1 firewire_core scsi_mod 126501 5 sg,sr_mod,sd_mod,usb_storage,libata uhci_hcd 18521 0 ehci_hcd 32065 0 mii 3210 3 r8169,asix,usbnet thermal 11674 0 usbcore 122482 8 asix,cdc_acm,usbnet,usbhid,usb_storage,uhci_hcd,ehci_hcd nls_base 6377 7 hfsplus,hfs,ntfs,vfat,fat,jfs,usbcore thermal_sys 11942 3 video,processor,thermal and working one: Module Size Used by tun 10908 0 iptable_nat 4299 0 nf_nat 13372 1 iptable_nat nf_conntrack_ipv4 9833 6 iptable_nat,nf_nat nf_defrag_ipv4 1139 1 nf_conntrack_ipv4 xt_state 1303 3 nf_conntrack 46519 4 iptable_nat,nf_nat,nf_conntrack_ipv4,xt_state xt_physdev 1508 6 iptable_filter 2258 1 ip_tables 13915 2 iptable_nat,iptable_filter x_tables 12845 4 iptable_nat,xt_state,xt_physdev,ip_tables bridge 39662 0 stp 1440 1 bridge xen_evtchn 4339 4 xenfs 9600 1 nfs 241226 2 lockd 57603 1 nfs fscache 29834 1 nfs nfs_acl 2031 1 nfs auth_rpcgss 33476 1 nfs sunrpc 161525 15 nfs,lockd,nfs_acl,auth_rpcgss loop 11799 12 edac_core 29261 0 edac_mce_amd 6433 0 snd_pcm 60551 0 snd_timer 15582 1 snd_pcm snd 46526 2 snd_pcm,snd_timer evdev 7352 3 soundcore 4598 1 snd snd_page_alloc 6249 1 snd_pcm i2c_piix4 8328 0 pcspkr 1699 0 i2c_core 15819 1 i2c_piix4 k10temp 2715 0 asus_atk0110 7686 0 processor 35941 0 acpi_processor 5087 1 processor,[permanent] button 4650 0 ext3 106630 3 jbd 37085 1 ext3 mbcache 5050 1 ext3 raid1 18431 7 raid0 5517 3 md_mod 73872 12 raid1,raid0 ata_generic 3239 0 sd_mod 29905 20 crc_t10dif 1276 1 sd_mod ohci_hcd 19327 0 pata_jmicron 2280 0 xhci 33705 0 ehci_hcd 32065 0 ahci 32534 16 usbcore 122482 4 ohci_hcd,xhci,ehci_hcd nls_base 6377 1 usbcore libata 133744 3 ata_generic,pata_jmicron,ahci scsi_mod 126501 2 sd_mod,libata sky2 40803 0 thermal 11674 0 thermal_sys 11942 2 processor,thermal > What udev rules do you have? What is present in /etc/xen/scripts? There are some custom rules: # tree /etc/udev/ |-- hdparm.rules |-- libmtp7.rules |-- links.conf |-- logitechmouse.rules |-- rules.d | |-- 025_logitechmouse.rules -> ../logitechmouse.rules | |-- 55_avr_remote_power.rules | |-- 56_arduino.rules | |-- 70-persistent-cd.rules | |-- 70-persistent-net.rules | |-- 81_download_photos.rules | |-- 81_upload_photos.rules | |-- 81_upload_photos.rules~ | |-- z60_hdparm.rules -> ../hdparm.rules | `-- z60_xserver-xorg-input-wacom.rules `-- udev.conf # tree /etc/xen/scripts /etc/xen/scripts |-- blktap |-- block |-- block-common.sh |-- block-enbd |-- block-nbd |-- external-device-migrate |-- locking.sh |-- logging.sh |-- network-bridge |-- network-nat |-- network-route |-- qemu-ifup |-- vif-bridge |-- vif-common.sh |-- vif-nat |-- vif-route |-- vif2 |-- vscsi |-- vtpm |-- vtpm-common.sh |-- vtpm-delete |-- vtpm-hotplug-common.sh |-- vtpm-impl |-- vtpm-migration.sh |-- xen-hotplug-cleanup |-- xen-hotplug-common.sh |-- xen-network-common.sh `-- xen-script-common.sh > There's usually a logfile called xen-hotplug or something along those > lines -- does that show anything? It does not get created at all. If there are no udev events then clearly no udev scripts ever get executed? > Does xenstore-ls show the backends under /local/domain/0/backend and the > frontends under /local/domain/<domid>/device? See my next email, it has xenstore contents. > Did this work previously on this machine (i.e. is this an new issue > after an upgrade or a fresh install etc). No, I just installed xen and booted to it. > May or may not relate to this issue (probably not) but I'd normally > recommend not using network-script at all and rather configuring > your /etc/network/interfaces as per > http://wiki.xen.org/xenwiki/HostConfiguration/Networking I don't think it is related indeed since the problem occurs even after I've removed the vif= line. -Timo -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
