kernel-packages team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is such a request.

  With the recent release of this Ubuntu release, would like to confirm
if this bug is still present. Please test again with the newer kernel
and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the
following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to
Confirmed. If the bug no longer exists, change the bug status from
Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add
a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.


** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

** Tags added: kernel-request-3.13.0-24.46

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1326705

Title:
  Precise kvmhost ends in fsck when adding to a open vswitch on a trusty
  wirth

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  How to rebuild:
  Install a fresh precise kvm host (current 12.04.4) from an iso on a trusty (14.04) host.
  Add precise host to a open vSwitch
  Start the machine
  machine is fscking forever.

  Details:
  Installation, etc works fine, until i connect the host to a open vSwitch. (does not matter if I do that befor or after installation. the installation works normally). After adding the open vSwich

  `virsh edit <hostname>`
  adding
  `<interface type='bridge'>
   <source bridge='<ovsbr-name>'/>
   <virtualport type='openvswitch' />
   <model type='virtio'/>
  </interface>
  `
  the vm cannot startup anymore; it hangs in fsck forever(see attached picture). when i delete the open vSwitch interface for the host, it will start again.

  tried the same thing with trusty hosts, which works perfectly fine
  when doing this.

  tried installation a few times (checked sha256 sums of iso!), nothing
  helped.

  It’s kinda looks like #1047531 , but I’m not sure.

  Kernel:
  Linux mars 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

  Libvirt:
  ii  libvirt-bin                         1.2.2-0ubuntu13.1                   amd64        programs for the libvirt library
  ii  libvirt0                            1.2.2-0ubuntu13.1                   amd64        library for interfacing with different virtualization systems

  kvm:
  ii  qemu-kvm                            2.0.0+dfsg-2ubuntu1                 amd64        QEMU Full virtualization on x86 hardware (transitional package)

  Log (/var/log/libvirt/qemu/<precise-host>:
  2014-06-05 08:36:42.862+0000: shutting down
  2014-06-05 08:37:40.917+0000: starting up
  LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm-spice -name ubuntutest3 -S -machine pc-i440fx-trusty,accel=kvm,usb=off -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 265b5cfb-91d1-6b30-8556-2e27c3a18834 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/ubuntutest3.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/vm/ubuntutest3/ubuntutest3.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=29,id=hostnet0,vhost=on,vhostfd=30 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:9b:15:58,bus=pci.0,addr=0x5 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:4 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4
  char device redirected to /dev/pts/5 (label charserial0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326705/+subscriptions