[Users] Panic on FreeBSD guest with >1 CPU

[Karli Sjöberg]

27 nov 2012 kl. 15.51 skrev Laszlo Hornyak:

> Does that PHY refer to the ethernet card in the Vm?

I don´t know for sure but I don´t think so. Standard ethernet is just called "em" with Intel, or "vtnet" with VirtIO, besides it´s waaay to early in the boot process.

/Karli

> 
> Thx,
> Laszlo
> 
> ----- Original Message -----
>> From: "Karli Sjöberg" <Karli.Sjoberg at slu.se>
>> To: "users" <users at ovirt.org>
>> Sent: Tuesday, November 27, 2012 2:28:26 PM
>> Subject: [Users] Panic on FreeBSD guest with >1 CPU
>> 
>> Hey all!
>> 
>> Since recently patching our hosts, I´ve been having trouble running
>> FreeBSD guests with more than one virtual core or socket. I have
>> managed take a screenshot of how it looks like when it panics when
>> booting kernel, right after ACPI:
>> http://i47.tinypic.com/2u90qrr.png
>> 
>> I´ve tried this with similar results using 8.2-RELEASE, 8.3-RELEASE,
>> 9.0-RELEASE and 9-STABLE.
>> 
>> If I edit the guest to have only one virtual core or socket, it boots
>> up without issue.
>> 
>> Since noticing this, I´ve tried updating the packages one more time,
>> thinking maybe it had already been fixed but no, it remains. These
>> are the package versions I´m using:
>> # rpm -qa | egrep '(kernel|libvirt|qemu|vdsm|seabios)' | sort -d
>> ipxe-roms-qemu-20120328-1.gitaac9718.fc17.noarch
>> kernel-3.6.2-4.fc17.x86_64
>> kernel-3.6.3-1.fc17.x86_64
>> kernel-3.6.7-4.fc17.x86_64 << This is the one that´s running
>> libvirt-0.9.11.7-1.fc17.x86_64
>> libvirt-client-0.9.11.7-1.fc17.x86_64
>> libvirt-daemon-0.9.11.7-1.fc17.x86_64
>> libvirt-daemon-config-network-0.9.11.7-1.fc17.x86_64
>> libvirt-daemon-config-nwfilter-0.9.11.7-1.fc17.x86_64
>> libvirt-lock-sanlock-0.9.11.7-1.fc17.x86_64
>> libvirt-python-0.9.11.7-1.fc17.x86_64
>> qemu-common-1.0.1-2.fc17.x86_64
>> qemu-img-1.0.1-2.fc17.x86_64
>> qemu-kvm-1.0.1-2.fc17.x86_64
>> qemu-kvm-tools-1.0.1-2.fc17.x86_64
>> qemu-system-x86-1.0.1-2.fc17.x86_64
>> seabios-1.7.1-1.fc17.x86_64
>> seabios-bin-1.7.1-1.fc17.noarch
>> vdsm-4.10.0-10.fc17.x86_64
>> vdsm-cli-4.10.0-10.fc17.noarch
>> vdsm-python-4.10.0-10.fc17.x86_64
>> vdsm-xmlrpc-4.10.0-10.fc17.noarch
>> 
>> Do you have any insights as to what the problem might be?
>> 
>> Best Regards
>> Karli Sjöberg
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>