"Cole Robinson wrote:"
> 
> On 11/14/2013 11:33 PM, David Highley wrote:
> > First off I'm not very experienced setting up and running virtual guest
> > systems. I install Fedora 20 Beta using virt-manager. It is hosted on a
> > Fedora 19 system.
> > 
> > 1) Reocurring issue with the pointer not being visible in the guest
> >    window. Some times cleared by stopping and restarting the guest
> >    system. Most of the time need to force stop.
> 
> Please provide the guest config: sudo virsh dumpxml $vmname

<domain type='kvm'>
  <name>BetaFedora20-x64</name>
  <uuid>56527a8f-d3c9-054c-6882-16ce154ca811</uuid>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <vcpu placement='static'>4</vcpu>
  <os>
    <type arch='x86_64' machine='pc-i440fx-1.4'>hvm</type>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-kvm</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/var/lib/libvirt/images/BetaFedora20-x64.img'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' 
function='0x0'/>
    </disk>
    <disk type='block' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <target dev='hdc' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='1' target='0' unit='0'/>
    </disk>
    <controller type='usb' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' 
function='0x2'/>
    </controller>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' 
function='0x1'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' 
function='0x0'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'/>
    <interface type='direct'>
      <mac address='52:54:00:1b:4b:94'/>
      <source dev='p57p1' mode='bridge'/>
      <model type='rtl8139'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' 
function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='spicevmc'>
      <target type='virtio' name='com.redhat.spice.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'/>
    <input type='mouse' bus='ps2'/>
    <graphics type='spice' autoport='yes'/>
    <sound model='ich6'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 
function='0x0'/>
    </sound>
    <video>
      <model type='qxl' ram='65536' vram='65536' heads='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 
function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' 
function='0x0'/>
    </memballoon>
  </devices>
</domain>

> > 2) During initial install I did not seem to beable to create a network
> >    bridge. I was able to add a network bridge after the install.
> 
> Do you mean that macvtap is not an option in the New VM->Advanced
> Options->Network list in virt-manager? You can do 'customize before install'
> to setup macvtap. We only didn't promote it in the 'new vm' wizard since
> macvtap has some operational caveats that would need some explanation.
> 
> If you mean something else, please be more specific: is this virt-manager,
> inside the guest installer, did you see an error message, etc.

Then from this explaination it is expected behavior.

> > 3) I shutdown the guest and when I went to bring it up it failed trying
> >    to create the network bridge again. I then looked at configuration
> >    and found two network bridge devices. I deleted one but it still
> >    failed. So I deleted the other one and then added a new network
> >    bridge which worked.
> > 
> Error messages please.

This only happened the one time. We have no idea why. Since we are not
able to recreate it we can only say that it was complaining that it
could not create the network device even though it did not exist in the
host network configuration.

> 
> Thanks,
> Cole
> 
_______________________________________________
virt mailing list
virt@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/virt

Reply via email to