I was digging around KVM trunk before leaving the office and it looked like the old vmport code (couldn't see anyone having used this with open-vm-tools though) has been scratched for some kind of qemu fw_cfg framework. Trunk does have a --uuid option, and it looks like with libvirt integration this at least will put the uuid of the guest somewhere on the guest where you can get to it.
If there's no decent way to interact with the vmport code that is there now (to mimic vmware's setguestinfo), I'll wait for the next release of KVM. Bryan -----Original Message----- From: Kevin O'Connor <[EMAIL PROTECTED]> Sent: Friday, October 24, 2008 5:49 PM To: Bryan McLellan <[EMAIL PROTECTED]> Subject: Re: [coreboot] Providing an identifier to a virtualization guest via SMBIOS Hi Bryan, On Fri, Oct 24, 2008 at 03:33:02PM -0700, Bryan McLellan wrote: > Ultimately I want a KVM/libvirt guest booting using the > Coreboot/LinuxBIOS code to be able to figure out something unique > about it's host (like hostname) to script inventory management type > stuff (like iClassify). Yes - the latest QEMU supports setting a UUID for the guest. However, it doesn't use the code currently found in the bochs bios. The new code (using something called vmport) just got checked into qemu. I suspect it's also in the tip of kvm (or about to added). You probably want to ask on the qemu or kvm mailing lists. -Kevin -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
