May 2009 - Devel - libvirt List Archives

[libvirt] [PATCH 0/1] Added Networking API to change/create/etc. hostonly/internal network in VirtualBox
by Pritesh Kothari 06 May '09

06 May '09

Hi All: [PATCH 0/1]: Contains sample xml file showing features supported so far. [PATCH 1/1]: Contains the patch for adding Networking API to change/create/etc. hostonly/internal network in VirtualBox Regards, Pritesh

2 2

[libvirt] [PATCH 1/2] Support for 'hostonly' and 'internal' network in VirtualBox
by Pritesh Kothari 06 May '09

06 May '09

Hi All, I have added the support for hostonly and internal network as suggested on irc and list and am attaching the patch for same. PATCH 1/2: contains changes in the xml parsing/formatting on libvirt side namely adding a mode attribute to <source> tag in domain/interface xml PATCH 2/2: contains changes in the vbox driver itself. Regards, Pritesh

2 1

[libvirt] [PATCH 1/1] Added Networking API to change/create/etc. hostonly/internal network in VirtualBox
by Pritesh Kothari 06 May '09

06 May '09

Hi All: [PATCH 0/1]: Contains sample xml file showing features supported so far. [PATCH 1/1]: Contains the patch for adding Networking API to change/create/etc. hostonly/internal network in VirtualBox Regards, Pritesh

2 1

[libvirt] USB pass-through only works after many disconnects at the beginning
by Felix Schwarz 06 May '09

06 May '09

Hi, I want to pass through a USB device to a KVM guest (Windows 2000). My host OS is a standard Fedora 10, 64 bit. However, the device is only passed to the guest when I use qemu monitor directly and only after several tries... The device has no Linux drivers ('AVM GmbH ISDN-Controller FRITZ!Card v2.0') so I think I don't have to tell the kernel not to use it. I have KVM 74 and tried initially with libvirt 0.5.1 so from what I read this should be ok. At first I added this to my domain xml via virsh: <hostdev mode='subsystem' type='usb'> <source> <vendor id='0x....'/> <product id='0x....'/> </source> </hostdev> However, the device did not turn up in the guest. Therefore I updated libvirt/-python 0.6.1 and python-virtinst from updates-testing and recompiled virt-manager 0.7 from F11 because I read that virt-manager 0.7 had some support for USB pass-through. Now I had some new UI, but it turned out that using that did not produce better results... After that I called qemu-kvm directly with '-usb -usbdevice host:...:...'. qemu produced this output on my terminal: husb: open device 2.9 husb: config #1 need -1 husb: 1 interfaces claimed for configuration -1 husb: grabbed usb device 2.9 husb: config #1 need 1 USBDEVFS_DISCONNECT: No such device husb: device 2.9 disconnected When I used qemu monitor to re-attach the device, something liek that happened (re-attached multiple times): husb: open device 2.11 husb: config #1 need -1 husb: 1 interfaces claimed for configuration -1 husb: grabbed usb device 2.11 husb: config #1 need 1 husb: 1 interfaces claimed for configuration 1 husb: config #1 need 1 USBDEVFS_DISCONNECT: No such device husb: config #1 need 1 USBDEVFS_DISCONNECT: No such device husb: config #1 need 1 USBDEVFS_DISCONNECT: No such device husb: device 2.11 disconnected ... Eventually (after several tries), the device was attached and no more disconnects happened. After that I could use the device as expected. However plain qemu is not what I would like to have. I read about 'virsh attach-device' so I tried to use my usb hostdev snippet but to no avail (even after 10s of tries). So how can I use USB pass through? Could this be Windows-related? Judging from all the other threads (like [1]) it should be really easy to use. fs [1] https://www.redhat.com/archives/libvir-list/2009-February/msg00387.html

3 4

[libvirt] (no subject)
by mike.hinz＠yr20.com 05 May '09

05 May '09

I had originally posted a plea for help on the virt-manager related list, but the same issue exists with virsh and this list seems to have higher traffic. I'd been chatting on the irc channel with various people about this, but wanted to put this on the mail list for the record and to also raise a philosophical question. First, we've confirmed that Fedora 11 preview (fully updated) has an issue with properly mounting NFS shares without the noacl option. Fedora 10 works fine with regard to mounting NFS shares. That issue causes problems when attempting to write files to an NFS share and more importantly, for this group, causes problems when attempting to create an NFS based storage pool and then subsequently creating volumes on said NFS share. That bug is 499178. This was all figured out with Openfiler support and with the support of the fine folks working on libvirt and virt-manager. There is a somewhat ugly workaround for this and I can describe it in case anyone is interested. Now comes the philosophy piece: It seems like that the way that libvirt and virt-manager want to handle storage is to be able to fully control the mounting process. That seems to me to be a very nice thing as you have a single way to manage storage along with your VMs. However, at least with respect to NFS, there are a number of parameters that people might need to give to the mount command for things like performance optimization and who knows what else. Note that this is a consideration completely aside from the bug issue above. It seems to me that either you have to just use the user created mount points, either manually or by fstab OR you have to allow all the possible options to be passed if you want to fully control the process. Right now, it's tricky to do, if you want to get paras passed for tuning or whatever and requires some tricky handwork to get it done. One way to accomplish this from the user input perspective would be to add an 'options' input field that could take multiple parameters on the step 2 of 2 page of the 'add storage pool' function. So, is my thinking all screwed up about this or is there merit to this concept? I tend to think, at least right now, that the logical thing is to either have the user create the mount points through the normal mechanisms that have in place roughly forever and then you just ask for what these are with respect to the NFS pools or you have to allow for user to pass the required parameters via your mechanism, although there are certainly many, many options when it comes to NFS. Thanks for all the help to date! I hope the above is helpful! Regards, Mike Hinz President YR20 1718 Fry Road, Suite 440 Houston, TX 77084 mike.hinz(a)yr20.com 832-225-1293 (o) 713-594-3095 (m) 832-550-2657 (f)

1 0

[libvirt] pool default not starting on f10
by Jason Guiditta 05 May '09

05 May '09

Hello, hopefully this is something simple I just don't understand how to debug, but right now, it is keeping me from creating any new VMs. As stated in the subject, I am running F10, on x86_64 arch. Libvirt version is 0.6.1-5.fc10. Using virt-manager to create a new vm, when I get to the step to create a disk image, I get the error: 'Storage parameter error. internal error storage pool is not active'. Running virsh pool-start default gets me: error: Failed to start pool default error: out of memory Note there is no reason my machine would be out of memory, is has 6GB and nothing else running (and tried this right after booting) virsh pool-list --all shows default is inactive and 'yes' for autostart I would be happy to file a bug if needed, but thought I would throw this out to the list first to see if I was just unaware of some simple fix. Let me know if there are other details I can provide to make this easier to solve. Thanks, -j

2 6

[libvirt] [PATCH v2] Don't throw away QEMU startup errors when migrating.
by Cole Robinson 05 May '09

05 May '09

The attached patch removes the error message squashing that can take place in the qemu driver when launching a new VM via restore or migrate. Thanks, Cole

2 2

[libvirt] [PATCH] Test driver VolCreate cleanups
by Cole Robinson 05 May '09

05 May '09

The attached patch fixes some small issues with VolCreateXML implementation in the test driver. Thanks, Cole

2 2

[libvirt] [PATCH] Remove some old debugging code
by Cole Robinson 05 May '09

05 May '09

The attached patch removes some debugging code accidentally applied with my async vol creation patches. Thanks, Cole

2 2

[libvirt] [PATCH] Use correct error code in public VolCreateXML
by Cole Robinson 05 May '09

05 May '09

The attached patch fixes a use of an incorrect error code in libvirt.c VolCreateXML. Thanks, Cole

2 2

[libvirt] [PATCH 0/1] NPIV node device backend
by David Allan 05 May '09

05 May '09

Here is an initial implementation of the NPIV support backend using the node device API. It only implements create. Destroy should be fairly straightforward, but I want to get the patch out to the list for comment while I continue to work. The code currently requires the device name and host number to be specified in the XML, but it does not use those values. I will clean that up. The user will not be able to specify either of those values, as they are created by the system when it discovers the newly created device. <device> <name>foo</name> <parent>pci_10df_fe00_scsi_host_0</parent> <capability type='scsi_host'> <host>99999</host> <capability type='fc_host'> <wwnn>c0001b0000000018</wwnn> <wwpn>c0001b1000000018</wwpn> </capability> </capability> </device>

2 2

[libvirt] Patch: Fix build with -Werror=format-security cflag
by Frederik Himpe 05 May '09

05 May '09

This patch is needed to build libvirt with -Werror=format-security gcc cflag, which is used by default on Mandriva diff -ur libvirt-0.6.3.orig/src/virsh.c libvirt-0.6.3/src/virsh.c --- libvirt-0.6.3.orig/src/virsh.c 2009-04-15 21:43:26.000000000 +0200 +++ libvirt-0.6.3/src/virsh.c 2009-05-02 13:56:11.000000000 +0200 @@ -4463,7 +4463,7 @@ } /* Print this device */ - vshPrint(ctl, indentBuf); + vshPrint(ctl, "%s", indentBuf); vshPrint(ctl, "%s\n", devices[devid]); @@ -4487,7 +4487,7 @@ /* If there is a child device, then print another blank line */ if (nextlastdev != -1) { - vshPrint(ctl, indentBuf); + vshPrint(ctl, "%s", indentBuf); vshPrint(ctl, " |\n"); } @@ -4511,7 +4511,7 @@ /* If there was no child device, and we're the last in * a list of devices, then print another blank line */ if (nextlastdev == -1 && devid == lastdev) { - vshPrint(ctl, indentBuf); + vshPrint(ctl, "%s", indentBuf); vshPrint(ctl, "\n"); } }

2 1

[libvirt] [PATCH 0/7] Improve QEMU process startup error reporting
by Cole Robinson 04 May '09

04 May '09

Error reporting for failed QEMU processes isn't too great at the moment. A couple cases I have hit: - Trying to start a VM with a cdrom pointing to a nonexistent file. The svirt hook function choked on this and indicated as much in the domain log, but I still had to wait for the pidfile timeout (10 seconds), and the only error reported was 'Domain did not show up'. - QEMU dies quickly at startup. Happened with the pulse audio issue, or if we build cli args incorrectly. The reporting here varies: if QEMU dies before writing out the pidfile, the above case applies. If the pidfile is written, we timeout in ReadLogOutput, and it's hit or miss whether we even report the logfile output to the user. The following patches improve the above cases by ensuring we never have to wait for a timeout, and that the logfile output is always reported in the error message. Cole Robinson (7): Add documentation for __virExec and virExec virExec: Delay daemonizing as long as possible. Add helper function virExecDaemonize Report qemu log data if we fail to daemonize the process. Add pidfile argument to __virExec Check that QEMU is still alive while reading startup output. Don't throw away QEMU startup errors when migrating. src/libvirt_private.syms | 2 +- src/proxy_internal.c | 16 +-- src/qemu_conf.c | 7 - src/qemu_driver.c | 105 +++++++---- src/remote_internal.c | 15 +-- src/uml_driver.c | 11 +- src/util.c | 186 +++++++++++++++----- src/util.h | 15 ++- .../qemuxml2argvdata/qemuxml2argv-boot-cdrom.args | 2 +- .../qemuxml2argvdata/qemuxml2argv-boot-floppy.args | 2 +- .../qemuxml2argv-boot-network.args | 2 +- .../qemuxml2argvdata/qemuxml2argv-bootloader.args | 2 +- .../qemuxml2argv-clock-localtime.args | 2 +- tests/qemuxml2argvdata/qemuxml2argv-clock-utc.args | 2 +- .../qemuxml2argv-console-compat.args | 2 +- .../qemuxml2argv-disk-cdrom-empty.args | 2 +- .../qemuxml2argvdata/qemuxml2argv-disk-cdrom.args | 2 +- .../qemuxml2argv-disk-drive-boot-cdrom.args | 2 +- .../qemuxml2argv-disk-drive-boot-disk.args | 2 +- .../qemuxml2argv-disk-drive-cache-v1-none.args | 2 +- .../qemuxml2argv-disk-drive-cache-v1-wb.args | 2 +- .../qemuxml2argv-disk-drive-cache-v1-wt.args | 2 +- .../qemuxml2argv-disk-drive-cache-v2-none.args | 2 +- .../qemuxml2argv-disk-drive-cache-v2-wb.args | 2 +- .../qemuxml2argv-disk-drive-cache-v2-wt.args | 2 +- .../qemuxml2argv-disk-drive-fmt-qcow.args | 2 +- .../qemuxml2argv-disk-drive-shared.args | 2 +- .../qemuxml2argvdata/qemuxml2argv-disk-floppy.args | 2 +- tests/qemuxml2argvdata/qemuxml2argv-disk-many.args | 2 +- tests/qemuxml2argvdata/qemuxml2argv-disk-usb.args | 2 +- .../qemuxml2argvdata/qemuxml2argv-disk-virtio.args | 2 +- .../qemuxml2argvdata/qemuxml2argv-disk-xenvbd.args | 2 +- .../qemuxml2argv-graphics-sdl-fullscreen.args | 2 +- .../qemuxml2argv-graphics-sdl.args | 2 +- .../qemuxml2argv-graphics-vnc-sasl.args | 2 +- .../qemuxml2argv-graphics-vnc-tls.args | 2 +- .../qemuxml2argv-graphics-vnc.args | 2 +- .../qemuxml2argv-hostdev-pci-address.args | 2 +- .../qemuxml2argv-hostdev-usb-address.args | 2 +- .../qemuxml2argv-hostdev-usb-product.args | 2 +- .../qemuxml2argv-input-usbmouse.args | 2 +- .../qemuxml2argv-input-usbtablet.args | 2 +- tests/qemuxml2argvdata/qemuxml2argv-input-xen.args | 2 +- tests/qemuxml2argvdata/qemuxml2argv-migrate.args | 2 +- tests/qemuxml2argvdata/qemuxml2argv-minimal.args | 2 +- tests/qemuxml2argvdata/qemuxml2argv-misc-acpi.args | 2 +- .../qemuxml2argv-misc-no-reboot.args | 2 +- tests/qemuxml2argvdata/qemuxml2argv-misc-uuid.args | 2 +- .../qemuxml2argv-net-eth-ifname.args | 2 +- tests/qemuxml2argvdata/qemuxml2argv-net-eth.args | 2 +- tests/qemuxml2argvdata/qemuxml2argv-net-user.args | 2 +- .../qemuxml2argvdata/qemuxml2argv-net-virtio.args | 2 +- .../qemuxml2argv-parallel-tcp.args | 2 +- .../qemuxml2argvdata/qemuxml2argv-restore-v1.args | 2 +- .../qemuxml2argvdata/qemuxml2argv-restore-v2.args | 2 +- .../qemuxml2argvdata/qemuxml2argv-serial-dev.args | 2 +- .../qemuxml2argvdata/qemuxml2argv-serial-file.args | 2 +- .../qemuxml2argvdata/qemuxml2argv-serial-many.args | 2 +- .../qemuxml2argvdata/qemuxml2argv-serial-pty.args | 2 +- .../qemuxml2argv-serial-tcp-telnet.args | 2 +- .../qemuxml2argvdata/qemuxml2argv-serial-tcp.args | 2 +- .../qemuxml2argvdata/qemuxml2argv-serial-udp.args | 2 +- .../qemuxml2argvdata/qemuxml2argv-serial-unix.args | 2 +- tests/qemuxml2argvdata/qemuxml2argv-serial-vc.args | 2 +- tests/qemuxml2argvdata/qemuxml2argv-sound.args | 2 +- 65 files changed, 288 insertions(+), 183 deletions(-)

2 18

[libvirt] Virtio Disk Drivers and Windows
by Aaron Clausen 04 May '09

04 May '09

I've imported a Windows Server 2003 as a guest using the IDE drivers. When I try to use the virtio drivers instead, Windows just blue screens. Am I stuck with the IDE drivers under Windows? -- Aaron Clausen mightymartianca(a)gmail.com

1 1

[libvirt] [PATCH] Fix a comment typo in storage_backend_fs.c
by Cole Robinson 04 May '09

04 May '09

This comment hid from my attempt to 'grep FILE_BOCHS', which is the actual name of the constant. Thanks, Cole

2 2