f20 guest on centos5 xen host
by Bruno Postle
Hi, I'm having trouble installing a fedora f20 guest on a centos5
host, I previously had a working f16 guest, so I guess I want to
know if this is possible or not.
virt-install seems to work ok as before, but then the reboot fails
with this error:
Error starting domain: POST operation failed: xend_post: error from
xen daemon: (xend.err "Error creating domain: Boot loader didn't
return any data!")
I've tried formatting /boot as ext2 and ext3 with the same result,
now I'm out of ideas. Here is my virt-install command:
virt-install --paravirt --name honk --ram 2048 --disk \
path=/dev/VolGroup02/LogVol12 --vnc --location \
http://dl.fedoraproject.org/pub/fedora/linux/releases/20/Fedora/x86_64/os/
--
Bruno
9 years, 7 months
"You Are Here" on Snapshots
by Jorge Fábregas
Hello again,
Another question with internal snapshots. I can see the snapshot tree with:
virsh snapshot-list Win7vm --tree
However, I would like to know from what previous snapshot I'm currently
running off. Something like the "You are here" that VMware shows. Is
there a way to find that out?
Thanks,
Jorge
9 years, 7 months
Network issue between host server and libvirt client
by David Highley
I was some what confused as the libvirt client was able to talk on the
internet but then seemed not to be able to talk to a host on the local
net. After more investigation it seems it can talk to all hosts except
the one it is being hosted on. I'm sure it is something simple, but I
have very little experience with libvirt. Here is the client
configuration:
<domain type='kvm' id='3'>
<name>Fedora20-x64</name>
<uuid>56527a8f-d3c9-054c-6882-16ce154ca811</uuid>
<memory unit='KiB'>4194304</memory>
<currentMemory unit='KiB'>4194304</currentMemory>
<vcpu placement='static'>4</vcpu>
<resource>
<partition>/machine</partition>
</resource>
<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/Fedora20-x64.img'/>
<target dev='vda' bus='virtio'/>
<alias name='virtio-disk0'/>
<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/>
<alias name='ide0-1-0'/>
<address type='drive' controller='0' bus='1' target='0' unit='0'/>
</disk>
<controller type='usb' index='0'>
<alias name='usb0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
</controller>
<controller type='ide' index='0'>
<alias name='ide0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
</controller>
<controller type='virtio-serial' index='0'>
<alias name='virtio-serial0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</controller>
<controller type='pci' index='0' model='pci-root'>
<alias name='pci.0'/>
</controller>
<interface type='direct'>
<mac address='52:54:00:1b:4b:94'/>
<source dev='p57p1' mode='bridge'/>
<target dev='macvtap0'/>
<model type='rtl8139'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
</interface>
<serial type='pty'>
<source path='/dev/pts/3'/>
<target port='0'/>
<alias name='serial0'/>
</serial>
<console type='pty' tty='/dev/pts/3'>
<source path='/dev/pts/3'/>
<target type='serial' port='0'/>
<alias name='serial0'/>
</console>
<channel type='spicevmc'>
<target type='virtio' name='com.redhat.spice.0'/>
<alias name='channel0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
<input type='tablet' bus='usb'>
<alias name='input0'/>
</input>
<input type='mouse' bus='ps2'/>
<graphics type='spice' port='5900' autoport='yes' listen='127.0.0.1'>
<listen type='address' address='127.0.0.1'/>
</graphics>
<sound model='ich6'>
<alias name='sound0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</sound>
<video>
<model type='qxl' ram='65536' vram='65536' heads='1'/>
<alias name='video0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</video>
<memballoon model='virtio'>
<alias name='balloon0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</memballoon>
</devices>
<seclabel type='dynamic' model='selinux' relabel='yes'>
<label>system_u:system_r:svirt_t:s0:c367,c464</label>
<imagelabel>system_u:object_r:svirt_image_t:s0:c367,c464</imagelabel>
</seclabel>
</domain>
9 years, 8 months
Fedora virt status December 2013
by Cole Robinson
Here are some Fedora virt happenings for December.
Fedora 20 released!
===================
Fedora 20 was officially released on December 17th:
https://fedoraproject.org/wiki/F20_release_announcement
http://fedoraproject.org/wiki/Common_F20_bugs
There was some last minute issues with the 'fedup' update tool, but they
should be resolved now. Just make sure you fully update F19 before trying to
upgrade to F20!
Since F20 is out, virt-preview for F19 will no longer be receiving new builds.
FWIW, no F21 schedule has been posted yet.
Libvirt 1.2.0, separate python bindings
=======================================
libvirt 1.2.0 was released on Monday December 2nd 2013. Major changes:
- Add support for gluster pool (Eric Blake)
- Split out python binding (Daniel P. Berrange)
- vbox: add support for 4.3 APIs (Ryota Ozaki)
Per the second item there, the libvirt python bindings are now a standalone
project. This was mainly done to simplify distributing these bindings via pip
which was of interest to Openstack.
https://www.redhat.com/archives/libvirt-announce/2013-December/msg00000.html
https://www.redhat.com/archives/libvirt-announce/2013-December/msg00001.html
seabios-1.7.4
=============
seabios 1.7.4 was released on December 23rd. Highlights from the changelog:
- Support for obtaining ACPI tables directly from QEMU.
- Initial support for XHCI USB controllers (initially for QEMU only).
- Support for booting from "pvscsi" devices on QEMU.
This will soon be heading to rawhide.
Bug stats
=========
Total bugs on 2013-12-02 : 190
Total bugs on 2014-01-05 : 166
note: I dropped gnome-boxes from the stats. There isn't much perceptible bug
triaging happening with that component, so the numbers pretty much grow
without bound until Fedora goes end of life. Which makes it not all that
interesting to track here. 'spice' was added, it should have been there the
whole time.
I also did a lot of F18 bug closing/confirming/deferring in preparation of F18
end-of-life on
By release:
* Fedora 18 : 7
* Fedora 19 : 75
* Fedora 20 : 66
* Fedora rawhide : 18
By package:
* edk2 : 1
* gtk-vnc : 1
* ipxe : 4
* libguestfs : 7
* libosinfo : 1
* libvirt : 42
* libvirt-sandbox : 9
* netcf : 6
* openbios : 1
* qemu : 24
* seabios : 2
* spice : 11
* spice-gtk : 3
* virt-dmesg : 1
* virt-manager : 20
* virt-viewer : 7
* virt-what : 2
* virtio-win : 1
* xen : 10
* xorg-x11-drv-qxl : 13
By status:
* ASSIGNED : 11
* NEW : 142
* ON_QA : 1
* POST : 12
Bugs of note
============
https://bugzilla.redhat.com/show_bug.cgi?id=1031696
libvirt-guests.service is broken in F20
Still waiting for some guidance from systemd folks, no solution yet.
Thanks,
Cole
9 years, 8 months
Proper way to migrate (F19 to F20)
by Jorge Fábregas
Hello everyone,
I have a F19 that I'm wiping out in order to perform a clean intall of
F20. Is it ok to simply tar /etc/libvirt and /var/lib/libvirt/ and
untar them on the new installation? Or is it better to grab the VM
definition files & their disks and import them with vish on the new setup?
The first option seems very straightforward but don't know if there are
new config files or changes in syntax that I may be overriding by
extracting the previous version.
Thanks,
Jorge
9 years, 8 months
USB devices get reset a few seconds after attaching them to guest and then get binded to host
by Stewart Adam
Hi,
I have been attempting to attach a USB keyboard & mouse from the host to a
Windows 7 guest using QEMU's USB2 controller. The keyboard seems to attach
correctly, however I have trouble with certain mice and devices. When
starting the guest, the devices remain attached for a second or two, then
they disconnect. the libvirt logs show that it no longer sees the USB
device, and I see this in dmesg:
[ 10.876071] usb 3-13: reset full-speed USB device number 2 using xhci_hcd
[ 10.888206] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with
disabled ep ffff88041917f740
[ 10.888209] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with
disabled ep ffff88041917f800
[ 10.888210] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with
disabled ep ffff88041917f7c0
[ 11.041209] usb 3-14: reset full-speed USB device number 3 using xhci_hcd
[ 11.054379] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with
disabled ep ffff8800c8d559c0
[ 11.054383] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with
disabled ep ffff8800c8d55440
<repeats for some time>
[ 87.476806] usb 3-14: new full-speed USB device number 4 using xhci_hcd
[ 87.491908] usb 3-14: New USB device found, idVendor=046d, idProduct=c066
[ 87.491911] usb 3-14: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 87.491912] usb 3-14: Product: G9x Laser Mouse
[ 87.491914] usb 3-14: Manufacturer: Logitech
[ 87.491914] usb 3-14: SerialNumber: 081BB92CA70018
[ 87.494697] input: Logitech G9x Laser Mouse as
/devices/pci0000:00/0000:00:14.0/usb3/3-14/3-14:1.0/input/input16
[ 87.494994] hid-generic 0003:046D:C066.0008: input,hidraw0: USB HID v1.11
Mouse [Logitech G9x Laser Mouse] on usb-0000:00:14.0-14/input0
[ 87.498834] input: Logitech G9x Laser Mouse as
/devices/pci0000:00/0000:00:14.0/usb3/3-14/3-14:1.1/input/input17
[ 87.499078] hid-generic 0003:046D:C066.0009: input,hiddev0,hidraw1: USB
HID v1.11 Keyboard [Logitech G9x Laser Mouse] on usb-0000:00:14.0-14/input1
As you can see the device re-attaches to the host. The device is plugged
into a USB2 port, but it appears to be controlled by Intel's XHCI controller:
00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series
Chipset Family USB xHCI [8086:8c31] (rev 04)
I'm running 3.12.5-303.fc20.x86_64, which is Fedora 20's
kernel-3.12.5-302.fc20.x86_64 with the i915 VGA arbitration patches applied.
Should I report a bug against the kernel?
Regards,
Stewart
9 years, 8 months
