search for: rbarry

...of the logs. >> I haven't tried EFI with 440fx, only with q35. I haven't found an option to enable EFI neither a secureboot anywhere in virt-manager. >> Using qemu-kvm directly (qemu-kvm -bios >> /usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd -m 1G -cdrom >> ~rbarry/Downloads/Fedora-Server-netinst-x86_64-22.iso) boots and loads >> successfully. > We don't use '-bios' but '-drive file,if=pflash' and that's done once for the OVMF code and second time for the efivars storage. What's the guest XML and full command line of qem...

...sults in successful EFI initialization, but the VM exits ungracefully after the bootloader (with F22 and CentOS 7 installer images). There's no really useful information in any of the logs. Using qemu-kvm directly (qemu-kvm -bios /usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd -m 1G -cdrom ~rbarry/Downloads/Fedora-Server-netinst-x86_64-22.iso) boots and loads successfully. What's the difference here? Where can I go for troubleshooting? libvirt XML is below: <domain type='kvm'> <name>fedora22</name> <uuid>7f363d28-881f-4240-97eb-9b8d49cfb282</uuid...

...since I was able to boot >with basically the generated command (see below) from a console, but >it's 100% reproducible. > >> >>>> Using qemu-kvm directly (qemu-kvm -bios >>>> /usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd -m 1G -cdrom >>>> ~rbarry/Downloads/Fedora-Server-netinst-x86_64-22.iso) boots >>>> and loads successfully. >>> >> >> We don't use '-bios' but '-drive file,if=pflash' and that's done >> once for the OVMF code and second time for the efivars storage. >> Wha...

...tand is why this matters, since I was able to boot with basically the generated command (see below) from a console, but it's 100% reproducible. > >>> Using qemu-kvm directly (qemu-kvm -bios >>> /usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd -m 1G -cdrom >>> ~rbarry/Downloads/Fedora-Server-netinst-x86_64-22.iso) boots >>> and loads successfully. >> > > We don't use '-bios' but '-drive file,if=pflash' and that's done > once for the OVMF code and second time for the efivars storage. > What's the guest XM...

...nerated command (see below) from a >> console, but it's 100% reproducible. >> >>> >>>>> Using qemu-kvm directly (qemu-kvm -bios >>>>> /usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd -m 1G >>>>> -cdrom >>>>> ~rbarry/Downloads/Fedora-Server-netinst-x86_64-22.iso) >>>>> boots and loads successfully. >>>> >>> >>> We don't use '-bios' but '-drive file,if=pflash' and that's >>> done once for the OVMF code and second time for the efivars...

...lization, but the VM exits ungracefully > after the bootloader (with F22 and CentOS 7 installer images). There's > no really useful information in any of the logs. > > Using qemu-kvm directly (qemu-kvm -bios > /usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd -m 1G -cdrom > ~rbarry/Downloads/Fedora-Server-netinst-x86_64-22.iso) boots and loads > successfully. Just to update -- This appears to be related to secureboot. Using a VM which has secure boot enabled is successful > > What's the difference here? Where can I go for troubleshooting? > > libvirt X...

I don't think C has a way to express 32b x 32b -> 64b multiply, even though there is (on x86 anyway) a hardware instruction that does it. The type of your expression (x * y) is still uint32_t. The implicit type coercion up to uint64_t as part of the return statement doesn't change this. On Jan 13, 2008, at 10:29 PM, Zhou Sheng wrote: > Hi, > > Here is C function: >

Started playing with LLVM this week, picking apart the examples to see how they work. So I think I understand the basic process of instantiating a program and getting LLVM to generate the runnable code, and then running it. What I have not seen an example of, and want to know if it's possible, is having LLVM generated code calling back out to plain C code during its run. What