[vfio-users] Virt-manager setup issues - CPU "host-passthrough" - can't boot media using edk2 EFI - no bridge available

[Eddie Yen]

You don't have to set IP in XML file if you want to bridging VM network
into eth. Unless eth network isn't DHCP.
Even so, you can type IP address in guest OS.

Anyway, it's better to check problems if you can paste XML information.

2016-03-09 8:55 GMT+08:00 Garland Key <david.garland.key at gmail.com>:

> 1. I'm using the kernel 4.4.3-1
>
> 2. I'm pretty sure that I'm pressing a key.  When I do it just cycles back
> to the EFI Shell and nothing loads.  I'll try it again just to make sure.
>
> 3. I'll try this.  Do I need to do anything with ip to enable it once I've
> entered it into the XML with virsh?
>
> On Tue, Mar 8, 2016 at 7:30 PM Eddie Yen <missile0407 at gmail.com> wrote:
>
>> My 2 cents:
>>
>> 1. I feel it happened about Kernel version, which version you use on Arch
>> Linux?
>>
>> 2. When you see "press any key to boot from cd rom", you need to press
>> any key on time, or it will skip CD-ROM option.
>> You can try EFI Shell command to boot up Windows 10 installation.
>>
>> 3. Try edit network to Bridge by using virsh.
>>
>> <interface type='bridge'>
>>       <mac address='XX:XX:XX:XX:XX:XX'/>
>>       <source bridge='br-ex'/>
>>       <model type='e1000'/>
>>       <address type='pci' domain='0x0000' bus='0x00' slot='0x03'
>> function='0x0'/>
>>     </interface>
>>
>> 2016-03-09 4:00 GMT+08:00 Garland Key <david.garland.key at gmail.com>:
>>
>>>
>>> *Specs*OS: Arch Linux x86_64
>>> Mobo: ASUS Sabertooth X99
>>> CPU: i7-5930K
>>> RAM: 32G DDR4
>>> GPU: Gigabyte Nvidia GTX 970
>>>
>>> I've successfully installed qemu, libvirt, edk2.git-ovmf-x64 and
>>> vfio-linux.  I have successfully dedicated one gpu to vfio and the other to
>>> the nvidia driver.  Each of my gpus are listed in different groups, so I
>>> don't need the ACS over ride patch.  As such, I'm using the standard kernel.
>>>
>>> I'm following the following guide
>>> <http://vfio.blogspot.com/2015/05/vfio-gpu-how-to-series-part-4-our-first.html>
>>> in an attempt to setup the initial VM but I'm running into various problems.
>>>
>>>
>>>    1. If I manually enter "host-pass-through" in
>>>    Processor>CPUs>Configuration>Model:, my host will lock up when I click
>>>    "Begin Installation".  My only option is to hard reset the host.  I've been
>>>    using Haswell-noTSX instead.  Will this be okay?  What would cause
>>>    "host-passthrough" to freeze my host like that?
>>>
>>>    2. When booting to the EFI shell, I'm unable to load the linked
>>>    virtio drivers
>>>    <https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.113-1/>
>>>    or the Windows 10 install iso, even though I've selected them as IDE CDROM
>>>    1 & 2.  When I select CDROM 1 in the boot options of the EFI shell, it says
>>>    to press any key to boot from cd rom, but when I do nothing happens and it
>>>    goes back to the EFI shell.  Is this likely a problem with my isos or is it
>>>    possible that I'm doing something wrong?
>>>
>>>    3. I don't have the Bridge option available as a network source.  Is
>>>    this something I can create through virt-manager or do I need to look
>>>    elsewhere.  If you know of a link, it would be very helpful - I'm don't
>>>    know enough about how this works to google the right keywords.
>>>
>>> Any help that you can provide is greatly appreciated.
>>>
>>> Best,
>>> Garland
>>>
>>> _______________________________________________
>>> vfio-users mailing list
>>> vfio-users at redhat.com
>>> https://www.redhat.com/mailman/listinfo/vfio-users
>>>
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/vfio-users/attachments/20160309/7a1c7bae/attachment.htm>