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@xxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
> >> http://lists.xensource.com/xen-users
> >>
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> >
>
>
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home