Bugs item #2949622, was opened at 2010-02-11 11:12 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2949622&group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: qemu Group: None >Status: Closed >Resolution: Invalid Priority: 7 Private: No Submitted By: Peter B. (jden44) Assigned to: Nobody/Anonymous (nobody) Summary: kvm - dmi rembo error on guest Initial Comment: Hello kvm experts, * cpu model host = XEON E5420 8 core * kvm version = 0.12.2 * host kernel = 2.6.31.8-desktop (opensuse 11.2 64 bit) * guest OS = ubuntu 8.04 32 bit , kernel = 2.6.24-16-server * quemu command line (done by aqemu)= /usr/bin/qemu-kvm -smp 2 -k de -no-kvm-irqchip -kvm-shadow-memory 4 -m 1528 -localtime -cdrom "/home/iso/logodidact.iso" -hda "/home/vms/LogoDidact1_HDA" -boot c -net nic,vlan=0 -net user,vlan=0 -net nic,vlan=0 -net tap,vlan=0,script="/etc/qemu01-ifup" $* we are using logodidact sw, which consists of ubuntu 8.04 server with rembo5 sw and i want to migrate to a virtual machine with kvm. Host is opensuse 11.2 with kvm installed, and then using the gui aqemu to install VM's. Everthing is working fine with windows and linux systems as vm's, except with ubuntu 8.04/rembo. The guest ubuntu 8.04 is starting fine, until rembo (tivoli provisioning manager for os system 5.1) ist starting. We get the message, which blocks then the vm: starting rembo services.. loading rembo configuration into database.. ---> DMI 5.31 found at ef2c0 (17293 tables at a43c6, max 17350) In a xenserver 5.5 enviroment it works fine in a virtual machine. please help. May the bios (bios.bin) is not supporting this dmi or the max is to small. Peter ---------------------------------------------------------------------- >Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 13:13 Message: Sounds like it is trying to find something in the BIOS which isn't there, or something it thinks shouldn't be there. Looks like a bug in the rembo software, not a bug in KVM. Jes ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2949622&group_id=180599 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
