[Kernel-packages] [Bug 1307473] Re: guest hang due to missing clock interrupt

2014-07-17 Thread Jan Müller
dup of #1332409?

seems to be a 3.13 only bug.

-- 
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/1307473

Title:
  guest hang due to missing clock interrupt

Status in QEMU:
  New
Status in “linux” package in Ubuntu:
  Confirmed
Status in “qemu” package in Ubuntu:
  Confirmed

Bug description:
  
  I noticed on 2 different systems that after upgrade from precise to latest 
trusty VMs are crashing:

  - in case of Windows VMs I'm getting BSOD with error message: A clock 
interrupt was not received on a secondary processor within the allocated time 
interval.
  - On linux VMs I'm noticing hrtimer: interrupt took 2992229 ns messages 
  - On some proprietary virtual appliances I'm noticing crashes an due to 
missing timer interrupts

  QEMU version is:
  QEMU emulator version 1.7.91 (Debian 2.0.0~rc1+dfsg-0ubuntu3)

  Full command line:

  qemu-system-x86_64 -enable-kvm -name win7eval -S -machine pc-
  i440fx-1.7,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=4,threads=1 -uuid 05e5089a-
  4aa1-6bb2-ef06-ab4d020a -no-user-config -nodefaults -chardev
  
socket,id=charmonitor,path=/var/lib/libvirt/qemu/win7eval.monitor,server,nowait
  -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime
  -no-shutdown -boot strict=on -device piix3-usb-
  uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
  file=/var/vm/win7eval.qcow2,if=none,id=drive-virtio-disk0,format=qcow2
  -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-
  disk0,id=virtio-disk0,bootindex=1 -drive
  file=/home/damarion/iso/7600.16385.090713-1255_x86fre_enterprise_en-
  us_EVAL_Eval_Enterprise-GRMCENEVAL_EN_DVD.iso,if=none,id=drive-
  ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive
  =drive-ide0-0-0,id=ide0-0-0 -drive file=/home/damarion/iso/virtio-
  win-0.1-74.iso,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=24,id=hostnet0 -device
  e1000,netdev=hostnet0,id=net0,mac=52:54:00:38:31:0a,bus=pci.0,addr=0x3
  -chardev pty,id=charserial0 -device isa-
  serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0
  -vnc 127.0.0.1:1 -device VGA,id=video0,bus=pci.0,addr=0x2 -device
  virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1307473/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1326705] Re: Precise kvmhost ends in fsck when adding to a open vswitch on a trusty wirth

2014-06-06 Thread Jan Müller
Precise won't boot connected to Open vSwitch (und without i have no
network to install new kernels...)

** Tags added: kernel-unable-to-test-upstream

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

-- 
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:
  Confirmed

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   
amd64programs for the libvirt library
  ii  libvirt01.2.2-0ubuntu13.1   
amd64library for interfacing with different virtualization systems

  kvm:
  ii  qemu-kvm2.0.0+dfsg-2ubuntu1 
amd64QEMU Full virtualization on x86 hardware (transitional package)

  Log (/var/log/libvirt/qemu/precise-host:
  2014-06-05 08:36:42.862+: shutting down
  2014-06-05 08:37:40.917+: 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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1326705] [NEW] Precise kvmhost ends in fsck when adding to a open vswitch on a trusty wirth

2014-06-05 Thread Jan Müller
Public bug reported:

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   
amd64programs for the libvirt library
ii  libvirt01.2.2-0ubuntu13.1   
amd64library for interfacing with different virtualization systems

kvm:
ii  qemu-kvm2.0.0+dfsg-2ubuntu1 
amd64QEMU Full virtualization on x86 hardware (transitional package)

Log (/var/log/libvirt/qemu/precise-host:
2014-06-05 08:36:42.862+: shutting down
2014-06-05 08:37:40.917+: 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)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: kvm libvirt qemu trusty

** Attachment added: Fscking host after adder open vSwitch
   https://bugs.launchpad.net/bugs/1326705/+attachment/4125751/+files/fsck.png

-- 
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   
amd64programs for the libvirt library
  ii  libvirt01.2.2-0ubuntu13.1   
amd64library for interfacing with different virtualization systems

  kvm:
  ii  qemu-kvm2.0.0+dfsg-2ubuntu1 
amd64QEMU Full virtualization on x86 

[Kernel-packages] [Bug 1326705] Re: Precise kvmhost ends in fsck when adding to a open vswitch on a trusty wirth

2014-06-05 Thread Jan Müller
#1047531  =
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1047531

-- 
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   
amd64programs for the libvirt library
  ii  libvirt01.2.2-0ubuntu13.1   
amd64library for interfacing with different virtualization systems

  kvm:
  ii  qemu-kvm2.0.0+dfsg-2ubuntu1 
amd64QEMU Full virtualization on x86 hardware (transitional package)

  Log (/var/log/libvirt/qemu/precise-host:
  2014-06-05 08:36:42.862+: shutting down
  2014-06-05 08:37:40.917+: 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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1326705] Re: Precise kvmhost ends in fsck when adding to a open vswitch on a trusty wirth

2014-06-05 Thread Jan Müller
cannot

apport-collect 1326705

since precise host is hanging in fsck during bootup

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

-- 
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:
  Confirmed

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   
amd64programs for the libvirt library
  ii  libvirt01.2.2-0ubuntu13.1   
amd64library for interfacing with different virtualization systems

  kvm:
  ii  qemu-kvm2.0.0+dfsg-2ubuntu1 
amd64QEMU Full virtualization on x86 hardware (transitional package)

  Log (/var/log/libvirt/qemu/precise-host:
  2014-06-05 08:36:42.862+: shutting down
  2014-06-05 08:37:40.917+: 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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp