Creating a F14 VM on a F13 host crashes host

[Fred Brier]

When I try to install an F14 VM on on an up-to-date F13 host using virt-manager.  It
crashes the host.  I have tried this twice and it happened in exactly the same spot. 
After you specify the ISO medium and the VM OS type, version, and an LVM volume, it starts
to boot, you select the Install option and then it crashes.  Has anyone else seen this?  I
might expect a failure to create a VM, but not to crash the entire host OS.  The host has
had over 5 VMs and never had a problem.

I did try creating an F11 VM using virt-manager on the same F13 host is going fine.  It
looked like it was going to succeed, but then crashed the host after it had installed all
the packages for the new VM and was in the process of rebooting.  So now I feel something
is corrupted.  I have created F11 hosts under F11 previously.  Thank you for any
information on resolving this.

[Justin Forbes]

On Sat, 2011-01-15 at 06:22 -0500, Frederick N. Brier wrote:
>  When I try to install an F14 VM on on an up-to-date F13 host using
> virt-manager.  It crashes the host.  I have tried this twice and it happened in exactly
> the same spot.  After you specify the ISO medium and the VM OS type, version, and an LVM
> volume, it starts to boot, you select the Install option and then it crashes.  Has anyone
> else seen this?  I might expect a failure to create a VM, but not to crash the entire host
> OS.  The host has had over 5 VMs and never had a problem.
>  
>  I did try creating an F11 VM using virt-manager on the same F13 host is going fine.  It
> looked like it was going to succeed, but then crashed the host after it had installed all
> the packages for the new VM and was in the process of rebooting.  So now I feel something
> is corrupted.  I have created F11 hosts under F11 previously.  Thank you for any
> information on resolving this. 
A bit unclear here, did the F11 VM also crash the host, just further
into the installation?  Can you please tell us which version of qemu and
kernel you are running on the host?

Justin

[Fred Brier]

On 01/15/2011 08:57 AM, Justin M. Forbes wrote:
>  On Sat, 2011-01-15 at 06:22 -0500, Frederick N. Brier wrote:
> > When I try to install an F14 VM on on an up-to-date F13 host using virt-manager.  It
> crashes the host.  I have tried this twice and it happened in exactly the same spot. 
> After you specify the ISO medium and the VM OS type, version, and an LVM volume, it starts
> to boot, you select the Install option and then it crashes.  Has anyone else seen this?  I
> might expect a failure to create a VM, but not to crash the entire host OS.  The host has
> had over 5 VMs and never had a problem.
> >
> > I did try creating an F11 VM using virt-manager on the same F13 host is going fine. 
> It looked like it was going to succeed, but then crashed the host after it had installed
> all the packages for the new VM and was in the process of rebooting.  So now I feel
> something is corrupted.  I have created F11 hosts under F11 previously.  Thank you for any
> information on resolving this.
>  A bit unclear here, did the F11 VM also crash the host, just further
>  into the installation? 
Yes.  The F11 install crashed which looked like it was going
to work and had previously worked under F11 (prior to upgrading the host).
>     Can you please tell us which version of qemu and
>  kernel you are running on the host? 
The kernel is 2.6.34.7-66.fc13.x86_64
The qemu.x86_64 package is at 2:0.12.5-1.fc13

Thank you for the help.

Fred
>  Justin
>
>

[Richard W.M. Jones]

On Sat, Jan 15, 2011 at 06:22:51AM -0500, Frederick N. Brier wrote:
>  When I try to install an F14 VM on on an up-to-date F13 host using
>  virt-manager.  It crashes the host.  I have tried this twice and it
>  happened in exactly the same spot.  After you specify the ISO medium
>  and the VM OS type, version, and an LVM volume, it starts to boot,
>  you select the Install option and then it crashes.  Has anyone else
>  seen this?  I might expect a failure to create a VM, but not to
>  crash the entire host OS.  The host has had over 5 VMs and never had
>  a problem. 
As Justin said, give us the precise versions of all relevant host
components: kernel, qemu-kvm, libvirt.

What is the libvirt XML for the guest?

What sort of hardware is this?  (KVM capable?)

Is there any console message when it crashes?

Is the host filesystem running ext4?

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://et.redhat.com/~rjones/virt-df/

[Tom Horsley]

On Sat, 15 Jan 2011 14:28:14 +0000
Richard W.M. Jones wrote:

>  What sort of hardware is this?  (KVM capable?) 
Is it an AMD host? I had big problems with newer
kernels on an AMD host machine:

https://bugzilla.redhat.com/show_bug.cgi?id=637821

[Fred Brier]

On 01/15/2011 11:12 AM, Tom Horsley wrote:
>  On Sat, 15 Jan 2011 14:28:14 +0000
>  Richard W.M. Jones wrote:
>
> > What sort of hardware is this?  (KVM capable?)
>  Is it an AMD host? I had big problems with newer
>  kernels on an AMD host machine:
>
>  https://bugzilla.redhat.com/show_bug.cgi?id=637821 
Read the bug.  Wow.  Bummer. 
Well, my VMs actually launch and run.  I have Asterisk running in VM as I write this. 
Works great <hand swipe across forehead>.  Answered a phone call.  It is creating
new VMs that seem to crash the system.  I am using a slightly newer kernel than shown in
the bug report.  Perhaps a developer fixed the complete failure, but there are still
remaining issues?  Thank you for the heads up.

Fred

[Fred Brier]

On 01/15/2011 09:28 AM, Richard W.M. Jones wrote:
>  On Sat, Jan 15, 2011 at 06:22:51AM -0500, Frederick N. Brier wrote:
> > When I try to install an F14 VM on on an up-to-date F13 host using
> > virt-manager.  It crashes the host.  I have tried this twice and it
> > happened in exactly the same spot.  After you specify the ISO medium
> > and the VM OS type, version, and an LVM volume, it starts to boot,
> > you select the Install option and then it crashes.  Has anyone else
> > seen this?  I might expect a failure to create a VM, but not to
> > crash the entire host OS.  The host has had over 5 VMs and never had
> > a problem.
>  As Justin said, give us the precise versions of all relevant host
>  components: kernel, qemu-kvm, libvirt. 
The kernel is 2.6.34.7-66.fc13.x86_64
The qemu-kvm.x86_64 package is at 2:0.12.5-1.fc13
The libvirt.x86_64 package is 0.8.2-1.fc13
>  What is the libvirt XML for the guest? 
The Fedora 11 install
crashed the system, but the XML was generated and the VM is showing in virt-manager.  I
have appended that XML file from /etc/libvirt/qemu at the end of this email.
>  What sort of hardware is this?  (KVM capable?) 
Yes. KVM capable
and configured in BIOS.  It is an AMD Pnenom II X4 955 processor with 8GB of RAM.
>  Is there any console message when it crashes? 
No Console.
>  Is the host filesystem running ext4? 
The host file system where
the OS resides is running Ext4.  However, the system has a 3ware 9650SE-8LPML with 3 RAID
1 pairs.  So a couple of the older data volumes are Ext3, but the majority are Ext4.  The
VMs are setup in their own 20GB host LVM volume, in which they use LVM, which I believe
are all Ext4.
>  Rich. 
Thank you for the help.

Fred
-------------------------fedora.xml------------------------
<domain type='kvm'>
<name>fedora</name>
<uuid>9a301260-fbe7-56a2-be7b-214c6fe4c0e3</uuid>
<memory>524288</memory>
<currentMemory>524288</currentMemory>
<vcpu>1</vcpu>
<os>
<type arch='x86_64' machine='fedora-13'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/bin/qemu-kvm</emulator>
<disk type='block' device='disk'>
<driver name='qemu' type='raw'/>
<source dev='/dev/VolGroup02/fedora'/>
<target dev='vda' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x04' function='0x0'/>
</disk>
<disk type='block' device='cdrom'>
<driver name='qemu' type='raw'/>
<target dev='hdc' bus='ide'/>
<readonly/>
<address type='drive' controller='0' bus='1'
unit='0'/>
</disk>
<controller type='ide' index='0'>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x01' function='0x1'/>
</controller>
<interface type='bridge'>
<mac address='52:54:00:d5:40:5c'/>
<source bridge='br0'/>
<model type='virtio'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x05' function='0x0'/>
</interface>
<serial type='pty'>
<target port='0'/>
</serial>
<console type='pty'>
<target port='0'/>
</console>
<input type='tablet' bus='usb'/>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='-1' autoport='yes'/>
<sound model='ac97'>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x06' function='0x0'/>
</sound>
<video>
<model type='cirrus' vram='9216' heads='1'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x02' function='0x0'/>
</video>
</devices>
</domain>

[Richard W.M. Jones]

On Sat, Jan 15, 2011 at 12:58:35PM -0500, Frederick N. Brier wrote:
>  On 01/15/2011 09:28 AM, Richard W.M. Jones wrote:
>  > Is there any console message when it crashes?
>  No Console. 
If there's a way to "reliably" crash the host, might be worth
switching to the console before doing that and seeing if there are any
messages.  The kernel usually prints something before it goes down,
but those messages don't make it to a log file.

The closest bug I could find to the description is this one (a bug in
ext4, provoked somehow by installing a KVM guest):

https://bugzilla.redhat.com/show_bug.cgi?id=627371

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
New in Fedora 11: Fedora Windows cross-compiler. Compile Windows
programs, test, and build Windows installers. Over 70 libraries supprt'd
http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw