Re: [Xen-devel] Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG

[Valtteri Kiviniemi <kiviniemi.valtteri@xxxxxxxxx>]

Hi,

Yes, I understood for what the parameters were for. I'ts been a long time since I last had major problems with Xen (maybe 3.1 or something, been using Xen since version 2) and I had a shady recollection that Xen was required to be build debugging enabled in order to get any usable debugging data.

But anyway, I cant reproduce that kernel crash everytime, it just happens sometimes. Major problem is the black screen on VNC and second problem seems to be that everytime i try to run Linux in HVM mode it somehow breaks the hotplug scripts.

- Valtteri

2012/10/2 Pasi Kärkkäinen <pasik@xxxxxx>

On Tue, Oct 02, 2012 at 05:37:08PM +0300, Valtteri Kiviniemi wrote:
>    Hi,
>
>    Tried boogin with vif-parameters commented out, result is the same:
>
>    Error: Device 768 (vbd) could not be connected. Hotplug scripts not
>    working.
>
>    But what is more troubling with these issues I'm having is the fact that
>    this "hotpluf scripts not working" came out of nowhere. I was able to boot
>    my Windows domU just fine earlier with only problem being that the VNC
>    output was just black screen after Windows installer had started. Then I
>    tried to create a Linux HVM (debian squeeze) and then I got that "Hotplug
>    scripts not working" error. And after trying to start Windows domU again
>    it says that same "Hotplug scripts not working" error.
>
>    If I reboot the machine and start my Windows domU it will start again just
>    fine, but the VNC output is just black screen. Then again, if I start the
>    Linux HVM domU I will again get that "Hotplug scripts not working" error
>    and then the Windows domU wont start either again and tells the same
>    "Hotplug scripts not working" error.
>
>    So this is pretty confusing and troubling indeed.
>
>    I will reboot the machine later and put those boot parameters that Pasi
>    mentioned.
>

My parameters were meant for the case where your server crashes,
to be able to get a proper boot and crash logs to analyze it.

-- Pasi


>    - Valtteri
>
>    2012/10/2 Konrad Rzeszutek Wilk <[1]konrad@xxxxxxxxxx>

>
>      On Tue, Oct 2, 2012 at 9:01 AM, Valtteri Kiviniemi

>      <[2]kiviniemi.valtteri@xxxxxxxxx> wrote:
>      > Hi,
>      >
>      > I already tried 3.2, 3.5, 3.5.0, 3.6.0-rc7 and 3.6.0, same problem all
>      of
>      > those. My dom0 config is the same config that I'am using on other
>      server
>      > where HVM is working, so I dont think that it is a config problem. I
>      have
>      > triple checked everything and all should be ok. dom0 dmesg shows the
>      same
>      > crash that I have previously posted here. /var/log/xen/ does not
>      contain any
>      > specific errors.
>      >
>      > Could this be some kind of broblem with my motherboard bios being
>      buggy or
>      > CPU not supported? I'm using the new intel Ivy Bridge processor which
>      has
>      > integrated GPU, but that should not probably cause these kind of
>      problems.
>      > Or maybe some ACPI problem? xm dmesg is showing some notices about
>      ACPI. Is
>      > there any ACPI kernel parameters that I should try booting? This has
>      to be
>      > somekind of problem with my hardware, or then maybe it could be a
>      kernel
>      > problem too. I just really cant figure this out myself, I have tried
>      > everything.
>      >
>      > Lets take a quick summary of what has been tested, what hardware I'm
>      using
>      > etc.
>      >
>      > Xen-versions tested: 4.2.0, 4.0.4
>      > Kernel-versions tested: 3.2.0, 3.5.0, 3.5.4, 3.6.0-rc7, 3.6.0
>      >
>      > Host OS: Debian testing/wheezy, udev version 175-7, 2.13-35, python
>      version
>      > 2.7.3~rc2-2.1
>      >
>      > Hardware:
>      >
>      > CPU: Intel Core i7-3770 3.4GHz
>      > MB: Intel DQ77MK (latest bios updated)
>      > Memory: 32GB (4 x 8GB DDR3-1600MHz)
>      >
>      > All relevant log files and configs:
>      >

>      > dom0 dmesg: [3]http://nago.fi/dmesg.txt
>      > qemu-dm log: [4]http://nago.fi/qemu-dm.txt
>      > xm dmesg log: [5]http://nago.fi/xm-dmesg.txt
>      > domU config: [6]http://nago.fi/domu-config.txt
>      > dom0 kernel config: [7]http://nago.fi/dom0-config.txt

>      >
>      > I have also tried playing with every setting on that domU that I can
>      think
>      > of and tried different configs etc.
>
>      This is troubling. You seem to trigger the QEMU closing the tunX (your
>      Windows's guest network interface) which then crashes somehow.
>      Just to make sure that this is the case - can you try launching your
>      guest without network and seeing what happens?
>

> References
>
>    Visible links
>    1. mailto:konrad@xxxxxxxxxx
>    2. mailto:kiviniemi.valtteri@xxxxxxxxx
>    3. http://nago.fi/dmesg.txt
>    4. http://nago.fi/qemu-dm.txt
>    5. http://nago.fi/xm-dmesg.txt
>    6. http://nago.fi/domu-config.txt
>    7. http://nago.fi/dom0-config.txt

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel