June 2009 - virt - Fedora mailing-lists

ANNOUNCE: Rawhide virt repo for F11 users
by Mark McLoughlin 30 Oct '09

30 Oct '09

Hey, The idea[1] was discussed here before, so I'll keep this short. We've set up a repository for people running Fedora 11 who would like to test the rawhide/F12 virt packages. To use it, do e.g. $> cat > /etc/yum.repos.d/fedora-virt-preview.repo << EOF [rawvirt] name=Virtualization Rawhide for Fedora 11 baseurl=http://markmc.fedorapeople.org/virt-preview/f11/$basearch/ enabled=1 gpgcheck=0 EOF $> yum update At the moment, it contains the F-12 versions of libvirt and qemu, but as F-12 development continues, it will contain more. I'll send periodic mails to the list detailing the latest updates. Also, this is very much a work-in-progress. The TODO list includes: - get createrepo installed on fedorapeople.org - include debuginfo packages in the repo (need more quota) - find a better location than markmc.fedorapeople.org - enable package builders to upload directly to the repo - automatically do preview build/upload for devel/ builds - allow building against preview packages; e.g. for language bindings Comments most welcome. Help with the TODO list is even more welcome :-) Thanks, Mark. [1] - https://www.redhat.com/archives/fedora-virt/2009-April/msg00154.html

9 76

Dom0 kernels
by M A Young 28 Aug '09

28 Aug '09

I have built a new set of kernel packages based on fedora rawhide kernels and the xen/dom0/hackery branch of Jeremy's git repository ( http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=summary ). This batch (kernel-2.6.29-0.114.2.6.rc6.fc11) is available via the koji build system at http://koji.fedoraproject.org/koji/taskinfo?taskID=1149500 These are really for development and debugging purposes only, as I am still having problems getting them to boot, but others have reported more success at getting kernels based on this git repository working, so you might be lucky. Note to install these packages on Fedora 10 you will need to have rpm-4.6.0-1.fc10 installed (currently in updates-testing but it should be available in updates soon) because of the change to SHA-256 file digest hashing in recent Fedora 11 builds. Michael Young

11 86

git tree for Fedora qemu patches
by Mark McLoughlin 28 Jul '09

28 Jul '09

Hey, Glauber and I are going to start using git to manage the patches for the qemu package. The idea is that we'll use git's magical powers to make it easier for us to fix problems in patches, cherry-pick patches from upstream, re-base our patches to a newer upstream, etc. Nothing is changing, really - patches should still go upstream first and we'll still include patches as individual files in the source RPM - this is purely about making managing those patches easier. Here's the tree: http://git.et.redhat.com/?p=qemu-fedora.git It might be useful to others who want to help with back-porting fixes etc. Cheers, Mark.

1 1

Success with Fedora 10 Xen pv_ops 2.6.29-rc8 dom0
by Pasi Kärkkäinen 27 Jul '09

27 Jul '09

Hello! I've used a lot of time trying to get my custom Xen pv_ops dom0 kernel working with virt-install and/or virt-manager on Fedora 10, and now it seems I got things working. If you want to play with this you need: 1) New enough pv_ops dom0 kernel (2.6.29-rc8 or newer) so it has /sys/hypervisor support included - Compile with CONFIG_HIGHPTE=n since it seems to be broken still 2) libvirt 0.6.1 and related packages from Fedora 10 updates-testing In addition to those I'm using Xen 3.3.1-9 packages from rawhide/F11 rebuilt for F10. With the older Fedora 10 libvirt packages libvirtd was crashing often for me, and I had some other issues with virt-install console window not opening but stalling etc.. Today I was able to run the following on Fedora 10 32bit PAE pv_ops dom0: - CentOS 5.3 32bit PAE PV domU - Fedora 10 32bit PAE PV domU - Use virt-install to install Fedora 10 32bit PAE PV domU (using custom kickstart to force PAE kernel installation to avoid the anaconda BUG which installs wrong non-PAE kernel as a default). Fedora 11 (rawhide) installation most probably works too. I'm using LVM volumes for domU disks (tap:aio is not yet supported by pv_ops dom0 kernel). Network seems to work after running "ifdown eth0 && ifup eth0" on the guest.. dunno why that's needed. That's something to figure out later:) Graphical domU console works with virt-viewer and virt-install during installation. Issues: - virt-manager complains about default network (virbr0) being inactive and asks if I want to start it. If I click Yes, then I get error: "libvirtError: cannot create bridge 'virbr0': File exists" virbr0 works just fine with virt-install. So dunno what's the problem with that.. have to look into that later. Thanks to everyone involved for helping me with this! -- Pasi

2 7

Re: febootstrap question
by Richard W.M. Jones 07 Jul '09

07 Jul '09

[CC'd to fedora-virt] On Wed, Jun 17, 2009 at 05:25:26PM -0400, Christopher Johnston wrote: > I had a question about febootstrap and a specific > use case of mine at my company where I am implementing a stateless solution > for our grid. I wanted to be able to take the initramfs image that is spun > up out of febootstrap and put a custom linuxrc in there which will > essentially take the contents of the initramfs and copy them directly into a > tmpfs filesystem thats mounted as /sysroot then do a pivot_root into it and > then do a full execution of init. I'm a bit confused why you'd want to do this, but maybe I'm missing something. Why copy the initramfs image into a tmpfs? The initramfs is already loaded into kernel memory at boot time and so it has all the same properties / benefits of tmpfs. > I have been using nash currently to do > this and I have ran into a few issue when the system boots up once init > forks off where it segfaults. Below is my custom linuxrc: I would tend to avoid using nash. If it's possible to add bash to the image, just use bash. You might find it helpful to look at what we do in libguestfs, here: http://git.et.redhat.com/?p=libguestfs.git;a=blob;f=appliance/make.sh.in;hb… > #!/sbin/nash > > mount -t proc /proc /proc > echo Mounting proc filesystem > echo Mounting sysfs filesystem > mount -t sysfs /sys /sys > echo Creating /dev > mount -o mode=0755 -t tmpfs /dev /dev > mkdir /dev/pts > mount -t devpts -o gid=5,mode=620 /dev/pts /dev/pts > mkdir /dev/shm > mkdir /dev/mapper > echo Creating initial device nodes > mknod /dev/null c 1 3 > mknod /dev/zero c 1 5 > mknod /dev/systty c 4 0 > mknod /dev/tty c 5 0 > mknod /dev/console c 5 1 > mknod /dev/ptmx c 5 2 > mknod /dev/fb c 29 0 > mknod /dev/tty0 c 4 0 > mknod /dev/tty1 c 4 1 > mknod /dev/tty12 c 4 12 > mknod /dev/ttyS0 c 4 64 > mknod /dev/ttyS1 c 4 65 > mknod /dev/ttyS2 c 4 66 > mknod /dev/ttyS3 c 4 67 > /lib/udev/console_init tty0 > mkchardevs > mkblkdevs > echo Creating tmpfs filesystem > mkdir -p /sysroot > mkrootdev -t tmpfs -o defaults,ro /dev/root > mount -o mode=0755 -t tmpfs /dev/root /sysroot > mkdir -p /sysroot/proc > mkdir -p /sysroot/sys > mkdir -p /sysroot/.oldroot > echo Copying rootfs->tmpfs > cp -a bin /sysroot > cp -a dev /sysroot > cp -a etc /sysroot > cp -a home /sysroot > cp -a lib /sysroot > cp -a lib64 /sysroot > cp -a mnt /sysroot > cp -a sbin /sysroot > cp -a tmp /sysroot > cp -a usr /sysroot > cp -a var /sysroot > cp -a root /sysroot > echo Setting up the new root tmpfs filesystem > setuproot > echo Switching from rootfs to tmpfs > switchroot > > -Chris Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/

2 5

Disk device performance in F11
by Jerry James 06 Jul '09

06 Jul '09

I'm having a problem with a virtual machine created on an F-11 host that I didn't have with an F-10 host, and I'm wondering if I've misconfigured something or missed a trick somewhere. I'm doing some custom Linux kernel work for my employer, and I'm using a small collection of virtual machines to test it. In the short time I've had F-11 on my host machine, I've seen that virtual disk performance is noticeably worse than it was with F-10. My virtual machines regularly spew soft lockup messages to the system log, always with backtraces that show the process is being starved of the disk. The tests put a lot of stress on the disk, because this custom kernel work is going to help some overloaded servers deal with the load. It's actually working pretty well on the real machines with real disks, but with the upgrade to F-11, my test VMs have become almost useless for testing further development work. Before I take the drastic step of rolling back to F-10, what factors affect the virtual disk performance? I created both the F-10 and F-11 machines with virt-manager, if that matters. Thanks, -- Jerry James http://www.jamezone.org/

7 15

F-11 libvirt no longer creating firewall/iptables rules for virtual network?
by Jonathan Underwood 03 Jul '09

03 Jul '09

Hi there, I've recently installed F-11 and am having a problem with networking between the host and guest with the default network configuration - specifically that the iptables rules for virbr0 are not being inserted by libvirt as they used to be under F-10. I am using the default configuration of the firewall as shipped with F-11. The guest instance is a windowsXP image created under F-10 - I simply recreated the cconfig files by "creating" a new guest under virt-manager and pointing it to the disk image file. The guest boots up fine, but no networking. The output of iptables -L doesn't contain any reference to virbr0 or vnet0 (the latter automatically created when starting the guest OS) - I have confirmed virbr0 and vnet0 are present using ifconfig.. In case it's relevant this machine is using NetworkManager and has a single wired ethernet adapter configured with a static IP. Any suggestions on how I can debug further ? Thanks, jonathan

3 3

[PATCH] Change libguestfs to use virtio block devices
by Richard W.M. Jones 01 Jul '09

01 Jul '09

The following set of patches changes libguestfs to use virtio block devices by default. Device names change from /dev/sd* to /dev/vd*, but device name translation should hide this change in most cases: http://libguestfs.org/guestfs.3.html#block_device_naming The change isn't totally straightforward. The CHS for virtio disks is different from the CHS for IDE disks (even where the disks have identical size). These caused sfdisk with explicit cylinder numbers to fail, so I had to change all these. This is the reasoning behind patch 2 and most of patch 3. Patch 1: Just changes the way some messages are displayed from the test suite. Patch 2: Changes the statvfs test so it doesn't get affected by the CHS change. Patch 3: (a) We change the list-devices and list-partitions functions so that they see and return /dev/vd* devices. (b) The udev fix previously posted to this list. (c) Change the partition sizes because of the CHS change - see above. (d) Add ,if=virtio to -drive parameters so that block devices are exported as virtio disks. Patch 4: The generated code, just shown for completeness. The tests all pass except one. A single test fails because pvremove from the previous test causes sfdisk to fail (apparently the previous pvremove is still happening, so sfdisk refuses to partition the device because it is in use). I believe this is an underlying failure revealed by this change to virtio, not caused by the change itself. There doesn't appear to be any noticable increase in speed when running the tests, but I didn't measure anything. The main reason to use virtio is that it's inherently simpler than emulating IDE or SCSI devices. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://et.redhat.com/~rjones/libguestfs/ See what it can do: http://et.redhat.com/~rjones/libguestfs/recipes.html

2 3

best Fedora virtualization
by Rich Mahn 01 Jul '09

01 Jul '09

I am planning on running several virtual machines on a single host. I will have two or three Linux baeed virtual machines and one or two Windoze. I plan on using a F11 host system. I need most of these to run automatically on boot-up of the host system. It would be really nice if I could use something like the Ctl-Alt-FN to be able to access and switch between virtual machines. This needs to be stable. The machines that these virtual machines are intended to replace are often running hundreds of days between reboots. My gut feel is that the virt-manager suite might be the way to go, editting the apropriate xml files as required. I also see there is a qemu launcher and it seems to work okay. I suspect there are others as well. What tends to be the consensus here on the various virtual machine managers? Are there white papers somewhere that could give some insight? Thanks Rich

5 10

Fedora virtualization -- comments and questions
by Gene Czarcinski 30 Jun '09

30 Jun '09

I am a newcomer to Fedora (linux) virtualization. However, I have been a long time user of VMware products running first on Red Hat Linux and then on Fedora. When I recently acquired a CPU with hardware virtualization support (AMD Phenom II 940), I decided to "change my problem set" and give Fedora Virtualization a try ... specifically qemu/kvm/etc. I use virtuals for three purposes: 1) To test software which might destroy a system or testing which requires a lot of re-booting. 2) For development environment to build rpm packages for various systems, i386/x86_64, etc. 3) To run windows. OK, install the virtualization packages and then install a simple Fedora 11 guest ... naturally it worked fine. Now lets get down to real business since I would be installing/running a number of virtual systems. The first thing I found was that configuration files, disk images, etc. were scattered but mostly under /etc/libvirt and /var/lib/libvirt. I looked for a runtime parameter which specified where things were to be stored but did not find anything. Furthermore, all of this stuff was in the root ("/") partition and, when I upgraded to the next release, a pain to bring across. I have three suggestions (I will put these in bugzilla as soon as someone says what package they should be filed against): 1. Put all files (disk images, configuration, etc.) under a single directory (easier to manage). 2. Provide a virtualization configuration parameter for setting the top directory to be used to store virtualization files (make it easier to get things out of root). 3. Do not require DVD/CD ISO images to be in the image directory and do not screw with SELinux settings on ISO files. For those unfamiliar with it, this is more or less how VMware stuff sets things up. So much for wishful thinking, how do I make things easier (and get the files out of root)? OK, what I have come up with is to create a separate partition for all of the files and then "bind mount" it to /var/lib/libvirt and /etc/libvirt. Does this make sense? Is this going to work? Any other suggestions? Gene

7 12

default tftp root dir in virt-manager or qemu?
by Gianluca Cecchi 30 Jun '09

30 Jun '09

Hello, I'm on a x86_64 F11 host. I created with success CentOS 5.3 and Windows 2003 vms from iso images. If i try to create a VM from virt-manager with pxe, I see from ps that there is the -boot n option, but there aren't any -tftp dir and/or -bootp file options.... Is there any default for qemu and/or virt-manager? If this helps, I'm trying to create a qemu/kvm virtual machine. ps output is: root 3577 1 99 14:52 ? 02:37:30 /usr/bin/qemu-kvm -S -M pc -m 768 -smp 1 -name slackware64 -uuid 4e3c9c56-695a-b5a5-ff87-ab0807b19d63 -monitor pty -pidfile /var/run/libvirt/qemu//slackware64.pid -no-reboot -boot n -drive file=/dev/vg_qemu01/slack64,if=ide,index=0 -net nic,macaddr=54:52:00:56:19:31,vlan=0 -net tap,fd=19,script=,vlan=0,ifname=vnet3 -serial pty -parallel none -usb -vnc 127.0.0.1:3 -soundhw es1370 The installation remains in attemp to get the tftp file without success (it give "no filename") It seems that the guest gets one of the available ip provided by dhcpd, also it founds dhcpd and tftp server: both are set to 192.168.122.1 (the server itself with its virbro default interface). No configuration done by me. I see /etc/libvirt/qemu/networks/default.xml with some parameters but I don't know if and how I can put here also tftp settings.... Thanks for any pointer. Bye, Gianluca

6 7

[RFC/PATCH] libguestfs: build Debian based appliance
by Guido Günther 30 Jun '09

30 Jun '09

Hi Rich, attached patches allows to build the appliance based on Debian (or any Debian based distribution supported by debirf) by using e.g.: ./configure --with-repo=squeeze --with-mirror=http://apt:9999/debian Please note that the third patch isn't to be applied yet, it simply overwrites the contents of make/update.sh.in with the stuff we need for Debian. Also when building a fixed (#509381) debirf is needed which has just been uploded to unstable. Cheers, -- Guido

2 9

USB passthrough
by Mark McLoughlin 30 Jun '09

30 Jun '09

Hey, At FUDCon yesterday, Paul asked me about how to get KVM USB device passthrough working and I had to admit I'd never tried it. So, after some poking with F-11, here's what I found: 1) You need selinux-policy-targeted-3.6.12-55.fc11 or later 2) Make sure the virt_use_usb SELinux boolean is enabled, which it should be by default: $> getsebool virt_use_usb virt_use_usb --> on $> setsebool -P virt_use_usb on 3) Plug your device in, and if it's a USB mass storage device, make sure it's not mounted in the host 4) In virt-manager, open the VM window, go to the details tap, clock 'Add hardware', select 'Phyiscal host device', choose 'USB device', then the device you wish to passthrough 5) Take a peek at the device in the guest XML config $> virsh dumpxml xp ... <devices> ... <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x0dda'/> <product id='0x0001'/> </source> </hostdev> </devices> 6) Start the guest and check whether the guest can see it. If not, check /var/log/libvirt/qemu/$guest.log because qemu will happily start up even if the device cannot be assigned. 7) It sucks that the device has to be plugged in before you start the guest; qemu now has a "autoconnect" mode which probably makes sense for libvirt to use by default, see bug #508645 Cheers, Mark.

4 3

[PATCH] Add pipe support to guestfish
by Richard W.M. Jones 28 Jun '09

28 Jun '09

This patch adds support for pipes to guestfish, so you can pipe output from a guestfish command through a command on the host. The canonical example is: ><fs> hexdump /bin/ls | less Another example, looking for root backdoors in the password file: ><fs> cat /etc/passwd | awk -F: '$3 == 0 { print }' | grep -v ^root: Anything right of the first pipe symbol gets passed to the local shell, thus expansion, redirection and so on work on that. Rich. >From 57de1f4b17aba957ac18b64fccef66d2f21241d9 Mon Sep 17 00:00:00 2001 From: Richard W.M. Jones <rjones(a)redhat.com> Date: Sat, 27 Jun 2009 15:00:48 +0200 Subject: [PATCH] Guestfish pipes. --- fish/fish.c | 86 +++++++++++++++++++++++++++++++++++++++++++++++---------- fish/fish.h | 2 +- fish/glob.c | 2 +- guestfish.pod | 26 +++++++++++++++++ 4 files changed, 99 insertions(+), 17 deletions(-) diff --git a/fish/fish.c b/fish/fish.c index 5e8a6e9..5b0a065 100644 --- a/fish/fish.c +++ b/fish/fish.c @@ -29,6 +29,8 @@ #include <signal.h> #include <assert.h> #include <ctype.h> +#include <sys/types.h> +#include <sys/wait.h> #ifdef HAVE_LIBREADLINE #include <readline/readline.h> @@ -138,9 +140,15 @@ main (int argc, char *argv[]) struct mp *mp; char *p, *file = NULL; int c, inspector = 0; + struct sigaction sa; initialize_readline (); + memset (&sa, 0, sizeof sa); + sa.sa_handler = SIG_IGN; + sa.sa_flags = SA_RESTART; + sigaction (SIGPIPE, &sa, NULL); + /* guestfs_create is meant to be a lightweight operation, so * it's OK to do it early here. */ @@ -462,6 +470,8 @@ script (int prompt) "\n")); while (!quit) { + char *pipe = NULL; + exit_on_error = global_exit_on_error; buf = rl_gets (prompt); @@ -522,9 +532,8 @@ script (int prompt) /* Get the parameters. */ while (*p && i < sizeof argv / sizeof argv[0]) { - /* Parameters which start with quotes or square brackets - * are treated specially. Bare parameters are delimited - * by whitespace. + /* Parameters which start with quotes or pipes are treated + * specially. Bare parameters are delimited by whitespace. */ if (*p == '"') { p++; @@ -556,6 +565,10 @@ script (int prompt) } p[len] = '\0'; pend = p[len+1] ? &p[len+2] : &p[len+1]; + } else if (*p == '|') { + *p = '\0'; + pipe = p+1; + continue; /* } else if (*p == '[') { int c = 1; @@ -607,7 +620,7 @@ script (int prompt) argv[i] = NULL; got_command: - if (issue_command (cmd, argv) == -1) { + if (issue_command (cmd, argv, pipe) == -1) { if (exit_on_error) exit (1); } @@ -636,18 +649,51 @@ cmdline (char *argv[], int optind, int argc) optind++; if (optind == argc) { - if (issue_command (cmd, params) == -1) exit (1); + if (issue_command (cmd, params, NULL) == -1) exit (1); } else { argv[optind] = NULL; - if (issue_command (cmd, params) == -1) exit (1); + if (issue_command (cmd, params, NULL) == -1) exit (1); cmdline (argv, optind+1, argc); } } int -issue_command (const char *cmd, char *argv[]) +issue_command (const char *cmd, char *argv[], const char *pipecmd) { int argc; + int stdout_saved_fd = -1; + int pid = 0; + int r; + + /* For | ... commands. Annoyingly we can't use popen(3) here. */ + if (pipecmd) { + int fd[2]; + + fflush (stdout); + pipe (fd); + pid = fork (); + if (pid == -1) { + perror ("fork"); + return -1; + } + + if (pid == 0) { /* Child process. */ + close (fd[1]); + dup2 (fd[0], 0); + + r = system (pipecmd); + if (r == -1) { + perror (pipecmd); + _exit (1); + } + _exit (WEXITSTATUS (r)); + } + + stdout_saved_fd = dup (1); + close (fd[0]); + dup2 (fd[1], 1); + close (fd[1]); + } for (argc = 0; argv[argc] != NULL; ++argc) ; @@ -657,29 +703,39 @@ issue_command (const char *cmd, char *argv[]) list_commands (); else display_command (argv[0]); - return 0; + r = 0; } else if (strcasecmp (cmd, "quit") == 0 || strcasecmp (cmd, "exit") == 0 || strcasecmp (cmd, "q") == 0) { quit = 1; - return 0; + r = 0; } else if (strcasecmp (cmd, "alloc") == 0 || strcasecmp (cmd, "allocate") == 0) - return do_alloc (cmd, argc, argv); + r = do_alloc (cmd, argc, argv); else if (strcasecmp (cmd, "echo") == 0) - return do_echo (cmd, argc, argv); + r = do_echo (cmd, argc, argv); else if (strcasecmp (cmd, "edit") == 0 || strcasecmp (cmd, "vi") == 0 || strcasecmp (cmd, "emacs") == 0) - return do_edit (cmd, argc, argv); + r = do_edit (cmd, argc, argv); else if (strcasecmp (cmd, "lcd") == 0) - return do_lcd (cmd, argc, argv); + r = do_lcd (cmd, argc, argv); else if (strcasecmp (cmd, "glob") == 0) - return do_glob (cmd, argc, argv); + r = do_glob (cmd, argc, argv); else - return run_action (cmd, argc, argv); + r = run_action (cmd, argc, argv); + + if (pipecmd) { + fflush (stdout); + close (1); + dup2 (stdout_saved_fd, 1); + close (stdout_saved_fd); + waitpid (pid, NULL, 0); + } + + return r; } void diff --git a/fish/fish.h b/fish/fish.h index 8815807..8f57595 100644 --- a/fish/fish.h +++ b/fish/fish.h @@ -34,7 +34,7 @@ extern guestfs_h *g; extern int quit; extern int verbose; -extern int issue_command (const char *cmd, char *argv[]); +extern int issue_command (const char *cmd, char *argv[], const char *pipe); extern void pod2text (const char *heading, const char *body); extern void list_builtin_commands (void); extern void display_builtin_command (const char *cmd); diff --git a/fish/glob.c b/fish/glob.c index f20da84..a8ac58a 100644 --- a/fish/glob.c +++ b/fish/glob.c @@ -147,7 +147,7 @@ glob_issue (char *cmd, int argc, } printf ("\n"); - if (issue_command (argv[0], &argv[1]) == -1) + if (issue_command (argv[0], &argv[1], NULL) == -1) *r = -1; /* ... but don't exit */ for (i = argc-1; i >= 1; --i) { diff --git a/guestfish.pod b/guestfish.pod index 0870b9e..26312fe 100644 --- a/guestfish.pod +++ b/guestfish.pod @@ -282,6 +282,32 @@ will create a directory C<local> on the host, and then export the contents of C</remote> on the mounted filesystem to C<local/remote-data.tar.gz>. (See C<tgz-out>). +=head1 PIPES + +Use C<command E<lt>spaceE<gt> | command> to pipe the output of the +first command (a guestfish command) to the second command (any host +command). For example: + + cat /etc/passwd | awk -F: '$3 == 0 { print }' + +(where C<cat> is the guestfish cat command, but C<awk> is the host awk +program). The above command would list all accounts in the guest +filesystem which have UID 0, ie. root accounts including backdoors. +Other examples: + + hexdump /bin/ls | head + list-devices | tail -1 + +The space before the pipe symbol is required, any space after the pipe +symbol is optional. Everything after the pipe symbol is just passed +straight to the host shell, so it can contain redirections, globs and +anything else that makes sense on the host side. + +To use a literal argument which begins with a pipe symbol, you have +to quote it, eg: + + echo "|" + =head1 EXIT ON ERROR BEHAVIOUR By default, guestfish will ignore any errors when in interactive mode -- 1.6.2.2 -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/

1 1

[PATCH] Cleanup XML output of virt-inspector
by Matthew Booth 27 Jun '09

27 Jun '09

The attached patch makes some changes to the XML output of virt-inspector. Firstly, it changes the output code to use XML:Writer. This changes: * Single quotes for attributes become double quotes * All data is properly escaped * Indentation In practise, these should be invisible. It also changes the output semantically in 2 ways: * /operatingsystems/operatingsystem/os is renamed to /operatingsystems/operatingsystem/name * /operatingsystems/kernels/version becomes an attribute of /operatingsystems/kernel for consistency with initrds Are these changes likely to cause problems? Matt -- Matthew Booth, RHCA, RHCSS Red Hat Engineering, Virtualisation Team M: +44 (0)7977 267231 GPG ID: D33C3490 GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490

2 1

20% cpu usage spikes with idle centos 5.3 guest on F11
by Dennis Jacobfeuerborn 25 Jun '09

25 Jun '09

Hi, When I run a centos 5.3 x86_64 guest on my F11 x86_64 system with kvm I see the qemu-kvm process cpu usage jump to ~20% every few seconds even though the guest is completely idle (I even disabled the HAL polling for /dev/hdc). Does anyone have an idea what could be the cause of this or how find the reason for this behavior? Regards, Dennis

3 2

Re: [fedora-virt] 20% cpu usage spikes with idle centos 5.3 guest on F11
by Dennis Jacobfeuerborn 25 Jun '09

25 Jun '09

On 06/25/2009 03:55 PM, Don Dutile wrote: > Dennis J. wrote: >> Hi, >> When I run a centos 5.3 x86_64 guest on my F11 x86_64 system with kvm I >> see the qemu-kvm process cpu usage jump to ~20% every few seconds even >> though the guest is completely idle (I even disabled the HAL polling for >> /dev/hdc). Does anyone have an idea what could be the cause of this or >> how find the reason for this behavior? >> >> Regards, >> Dennis >> >> _______________________________________________ >> Fedora-virt mailing list >> Fedora-virt(a)redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-virt > > Try turning off the network (ifcfg eth0 down) in the guest& > see if the cpu usage goes away. if so, it's probably network > polling mis-behaving. if not, then send details > (kernel revs; #pcpu's, #vcpu's in guest, etc. I shut down the interface using "ifdown eth0" but that didn't change anything. I filed a bug here: https://bugzilla.redhat.com/show_bug.cgi?id=508109 It contains additional information about the environment and an attached screenshot showing the peaks in virtual-machine-manager in more detail. Regards, Dennis

1 0

libvirt and iptables rules added
by philippe.marcovici＠free.fr 25 Jun '09

25 Jun '09

Hi, My iptables rules are not permissives. For exemple, my default iptables's rules are DROP. libvirt inserts some iptables's rules. But, because my rules are not permissives, some DROP are generated. I fix it with a script, but i am looking for an automatization. I saw an directory named iptables with sub-directories named nat and filter in /var/lib/libvirt (all empty) : # ls -r /var/lib/libvirt/iptables nat filter My questions, in this context, are : - Can i use this directories to put some iptables rules who will be loaded and unloaded with libvirtd ? - If yes, how i must set them ? - If no, any others solutions ? Thanks.

1 0

Meet us at Berlin FUDCon / LinuxTAG, Friday - Sunday (26-28 June)
by Richard W.M. Jones 24 Jun '09

24 Jun '09

Mark McLoughlin and myself will be at LinuxTag and FUDCon in Berlin this week. There's a talk on virtualization, Saturday 11am. And, subject to demand, hackfests on libguestfs and the Windows cross-compiler (Fedora MinGW project) on Sunday. https://fedoraproject.org/wiki/FUDCon:Berlin_and_LinuxTag_2009_talks If you'll be at LinuxTag or FUDCon, please come along and say hello. We're also meeting up with a few people, so if you need my mobile number, email me. More information here: https://fedoraproject.org/wiki/LinuxTag_2009 Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/

1 0

Fedora virt status
by Mark McLoughlin 24 Jun '09

24 Jun '09

F-12 Schedule ============= Phew, Fedora 11 has just been released and Fedora 12 is already coming at us hard: http://fedoraproject.org/wiki/Releases/12/Schedule 2009-07-28 Feature Freeze (36 days) 2009-09-22 Beta (Final Development) Free (92 days) 2009-10-20 Final Release Compose (120 days) F-12 Features ============= We've prepared a good bunch of feature pages so far for F-12: http://fedoraproject.org/wiki/Category:F12_Virt_Features In the kernel related space we have: - SR-IOV - KSM - Huge pages For QEMU, we have: - Stable PCI Addresses - Stable Guest ABI - KVM NIC hotplug - VNC resource tunnel In the libvirt space we have: - VirtPrivileges - VirtAuthorization - Host network interface APIs - Storage management APIs - TCK General virt tools related features include: - Hostinfo - VirtAppliances Also, of note is the feature describing NetworkManager's forthcoming support for bridged networking: http://fedoraproject.org/wiki/Features/NetworkManagerBridging Please do jump in and give help or feedback where you can! F-12 Release Engineering ======================== Some of the Fedora release engineering folks held a Fedora Activity Day (FAD) at Red Hat's offices in Raleigh recently: http://fedoraproject.org/wiki/Fedora_Activity_Day_Fedora_Development_Cycle_… They came away from the meeting with a bunch of proposals intended to improve the Fedora development process: http://fedoraproject.org/wiki/Milestone_Adjustment_Proposal What was called the Preview release is now called Beta, what was Beta is now called Alpha and what was called Alpha is no more. http://fedoraproject.org/wiki/Israwhidebroken.com_Proposal The goal is to have a place where people can go to find the "last known good" rawhide tree. http://fedoraproject.org/wiki/Koji_Build_Autosign_Proposal All packages coming from Koji will be signed - i.e. rawhide packages will be signed. http://fedoraproject.org/wiki/Critical_Path_Packages_Proposal A core set of packages will receive special attention when they are being updated to try and reduce the chance of major regressions. http://fedoraproject.org/wiki/No_Frozen_Rawhide_Proposal Rawhide will no longer freeze when we hit the Beta Freeze, instead rawhide will continue to be published from the devel/ CVS branch and there will be new install trees immediately available for the new CVS branch (e.g. the F-12/ branch). Fedora Community Portal ======================= A new web interface for Fedora community members is no available: https://admin.fedoraproject.org/community/ Fedora Community provides a window into the Fedora distribution, leveraging the power of Fedora's Account System, Bodhi, Bugzilla, Koji, and PackageDB into a single user-friendly website. ... Fedora Community is designed to simplify Fedora workflows and bring transparency to Fedora processes. qemu-0.11 ========= Anthony Liguori posted his plans for QEMU's 0.11 release: http://lists.gnu.org/archive/html/qemu-devel/2009-06/msg01575.html 0.10.0 was released on March 2nd so following with the 6 month release cycle, that would put 0.11.0 at September 2nd. Based on the experiences with the stable releases, here's what I'd recommend: o On July 15th, fork master -> stable-0.11 o Change version to 0.10.90 o Release qemu-0.11.0-rc1 o Release additional -rcN releases every 1-2 weeks o Introduce a new maintainer for stable-0.10 (via git pulls) o At least 1 week before release, hopefully we'll have the final -rcN that we can then declare 0.11.0. Avi confirmed that he plans to mirror these releases with matching qemu-kvm releases. For Fedora 12, we already have a 0.11 snapshot (0.10.50-6.kvm86.fc12) and as new snapshots become available we will pull them in. This means we should have a feature frozen qemu in time for the F-12 feature freeze and a final 0.11 release in time for the final F-12 freeze. libguestfs ========== Rich Jones continues rocking with his libguestfs working, with a whole load of interesting stuff on the fedora-virt list and his blog. Rich always does his best to assure us that he really is crazy, but his libguestfs "supermin appliance" work takes the biscuit: http://www.redhat.com/archives/fedora-virt/2009-June/msg00118.html The supermin appliance removes the kernel and all the executable libraries and programs from the appliance. That just leaves a skeleton of config files and some data files, which is obviously massively smaller than the normal appliance. At runtime we rebuild the appliance on-the-fly from the libraries and programs on the host (eg. pulling in the real /lib/libc.so, the real /bin/bash etc.) The new appliance is a mere 500K, so libguestfs RPMs will be a lot smaller. libosinfo ========= Cole Robinson posted an RFC detailing his plans to create a libosinfo library replacing python-virtinst's OS_TYPES dictionary which contains valuable information on the preferred configuration for different guest OSes: http://www.redhat.com/archives/fedora-virt/2009-June/msg00100.html I've done the initial work for a new library, libosinfo (better name recommendations appreciated). This library will provide OS meta data for use in virt applications, replacing the dictionary we currently keep in virtinst. FWN === Another couple of Fedora Weekly News virt roundups from Dale Bewley: http://fedoraproject.org/wiki/FWN/Issue179#Virtualization http://fedoraproject.org/wiki/FWN/Issue180#Virtualization Xen === Gerd is planning on pushing a xen-3.4.0 update to F-11: http://www.redhat.com/archives/fedora-virt/2009-June/msg00032.html Not yet. I wanna give it a bit more testing in rawhide. Also it looks like xensource wants to release 3.4.1 quickly to fix a bunch of important bugs. I think it is a good idea to wait until that one is out, then update F11 straight to xen-3.4.1. Also xen 3.4 bumps the shared library major for some libraries from 3.2 to 3.4, so I'll have to figure what breaks due to that and coordinate the update. I know xenner is affected. Libvirts seems to do fine as it needs libxenstore only which is still at 3.0. Didn't investigate yet what else might need a rebuild. Also, Michael Young continues to push new Dom0 kernel builds: http://www.redhat.com/archives/fedora-virt/2009-June/msg00097.html Unfortunately, Dom0 seems to have missed the 2.6.31 boat, so Dom0 support in Fedora 12 looks highly unlikely. Bugs ==== = New Bugs = == kvm == https://bugzilla.redhat.com/504376 F-11 guest takes 45 minutes in mke2fs for 8gb fs on virtio disk with a sparse backing file A report of mke2fs taking forever during an anaconda install of an F-11 guest when using a virtio disk with a sparse backed file. Apparently, SLES-11 doesn't appear to suffer from the problem. https://bugzilla.redhat.com/505695 Poor KVM guest performance doing kernel builds (100+% overhead, w/ 8vcpu and virtio) Another report from Erik highlighting performance problems with KVM and disk I/O. https://bugzilla.redhat.com/507500 "MAX_LOCK_DEPTH too low!" warning during kvm guest startup https://bugzilla.redhat.com/507535 GPF in nf_conntrack_alloc() with KVM guests (2.6.31) An oops in core networking code as a result of routing packets back and forth between two guests. == qemu == https://bugzilla.redhat.com/506170 removing virtualization packages leaves qemu-system-x86 'yum groupinstall Virtualization' installs qemu-system-x86 via the qemu-kvm meta-package, but 'yum groupremove Virtualization' only removes qemu-kvm. Looks like expected behaviour for yum. https://bugzilla.redhat.com/507626 qemu-kvm VNC :: major display tearing garbage with windows guest and scrolling windows This looks like a similar issue to xterm getting garbled in a Fedora guest (bug #503156) https://bugzilla.redhat.com/506585 qemu-nbd dies with 'nbd.c:nbd_receive_request():L465: read failed' Looks like qemu-nbd dies when a client closes its end. https://bugzilla.redhat.com/505109 qemu ppc/ppc64 boot says "Boot failure! No secondary bootloader specified" Yet another bug with the ppc target. This time only in rawhide. == libvirt == https://bugzilla.redhat.com/507271 libvirt always places IDE disks before virtio/scsi disks If you attach an IDE disk to a guest booting from a virtio disk, libvirt ends up sorting the disks such that the guest will try and boot from the IDE disk. https://bugzilla.redhat.com/468384 RFE: use virt-manager to create network bridges A bugzilla basically requesting the 'Shared Network Interface' F-12 feature. https://bugzilla.redhat.com/505625 libvirtd segfault during virsh dominfo on security model 'virsh dominfo' was causing libvirtd to segfault because the selinux was blown away by virGetCapabilities(). Fixed upstream, needs to be pulled into F-11. https://bugzilla.redhat.com/506590 libvirt should ignore NUMA cells with missing topology It turns out some NUMA cells can be missing topology information, and libvirt should ignore these. Dan has come up with a patch which works well for the reporter. https://bugzilla.redhat.com/507405 virsh: renaming of guests creates a copy https://bugzilla.redhat.com/507555 libvirt starting a guest with ISO on NFS mount fails when unnecessarily setting SELinux file context Tim Waugh supplied a patch for this one. == svirt == https://bugzilla.redhat.com/506250 svirt prevents symlinks to be used in disk image paths If any part of a disk image path is a symlink, svirt denies qemu access to it. This will be fixed in a selinux-policy update soon. == virtinst == https://bugzilla.redhat.com/504604 virtinst ignores VirtualDisk(sparse = False) and doesn't pre-allocate the disk image Pre-allocation of disk images was disabled until it could be done without blocking libvirtd. This was fixed in libvirt-0.6.3, so to enable nonsparse disks in F-11 we would need to first backport the change from 0.6.3. https://bugzilla.redhat.com/505317 virtinst: make SLES11 guests use virtio by default Looks like SLES11 guests work well with virtio, should make virtinst enable it by default. == virt-manager == https://bugzilla.redhat.com/504605 virt-manager gets sparse/nosparse mixed up in New VM dialog virt-manager currently gets confused between sparse/nonsparse. Not that it matters since virtinst currently ignores it. https://bugzilla.redhat.com/504326 virt-manager's new VM dialog does not use storage pool interface https://bugzilla.redhat.com/502204 virt-manager's dialog to connect an existing CD-ROM to an ISO does not use storage pool interface A couple of places where we should be using the storage poll interface in virt-manager. Cole has now fixed these upstream. == virt-mem == https://bugzilla.redhat.com/505072 virt-mem "invalid argument in virDomainLookupByUUIDString" error A known error with the virt-mem tools on F-11, Rich has a patch somewhere. = Resolved Bugs = == qemu == https://bugzilla.redhat.com/506435 kvm: -kernel option seems broken Re-basing our qemu-roms-more-room.patch onto 0.10.5 introduced this regression. Fixed in qemu-0.10.5-3.fc11 https://bugzilla.redhat.com/499060 vgabios regression - 1440x900 resolution no longer available Glauber has cherry-picked the code to fix this from 0.6c and pushed a vgabios-0.6b-2.fc11 update to F-11. https://bugzilla.redhat.com/501545 "qemu-kvm -vga std" broken with vgabios 0.6c Tom London bisected the problem down to a specific upstream commit. It turns out the qemu is missing some code (which is in latest boch, but not qemu) in order for 0.6c to work. We've reverted to 0.6b (with some changes cherry-picked from 0.6c) in F-12 for now. == kvm == https://bugzilla.redhat.com/504374 kvm: hw DR_* watchpoint registers are ignored KVM in 2.6.29 does not virtualization the x86 debug registers so GDB watchpoints do not work. However, this is implemented in 2.6.30. == etherboot == https://bugzilla.redhat.com/506616 [qemu netboot] Eliminate 3 second delay on PXE boot Request to simply rebuild etherboot with ASK_BOOT=-1 in order to eliminate a pointless 3 second delay that most people don't ever see. https://bugzilla.redhat.com/507391 qemu-kvm PXE boot with e1000 results in bogus packets Several people have reported PXE using a virtio NIC doesn't work in F-11. It turned out to be an issue with gcc re-ordering writes and was fixed simply by appropriately using the 'volatile' keyword for the packet header. Fix available in etherboot-5.4.4-16.fc11 == svirt == https://bugzilla.redhat.com/499259 svirt denials breaks KVM PCI device assignment The virt_manage_sysfs SELinux boolean was added quite some time ago which is enough to use PCI device assignment with SELinux in enforcing mode. https://bugzilla.redhat.com/504444 svirt denials break USB device passthrough Similar to bug #499259 where svirt breaks PCI passthrough, svirt is denying qemu access to /proc, breaking USB passthrough. Dan Walsh has added a virt_use_usb boolean to selinux-policy which, if enabled, fixes the problem. == libvirt == https://bugzilla.redhat.com/506737 virt-manager should allow VM names with spaces in them Apparently this is a 'feature', so WONTFIX. == virtinst == https://bugzilla.redhat.com/484099 virt-install SASL authentication support virt-install doesn't currently have support for authenticating using SASL. Cole has fixed this upstream now. https://bugzilla.redhat.com/506319 virtinst errors finding default bridge: upsets virt-manager Cole fixed this upstream. = Ongoing Bugs = == qemu == https://bugzilla.redhat.com/473154 Virtual machine fails to start without cdom - qemu: could not open disk image /dev/sr0 Eduardo has posted a variant of Cole's patch upstream; Anthony has requested further changes. https://bugzilla.redhat.com/501131 qemu segfault when VNC client disconnects Gerd has fixed this upstream, just need to back-port the patch to F-11 now. https://bugzilla.redhat.com/504273 qemu-system-ppc on ppc host fails with "no opcode defined" It looks like this bug should be fixed by a change upstream to disable gcc optimizations for translate.c. Pavel still sees "invalid opcode" errors, though. A qemu-0.10.5-3.fc11 update has been pushed which might help. == virt-manager == https://bugzilla.redhat.com/503784 memory/vcpus changes in virt-manager do not persist across libvirtd restart Erik Jacobson points out that this issue affects CPU changes as well as memory. virt-manager needs to explicitly make these config changes persistent. https://bugzilla.redhat.com/503786 virt-manager refuses to increase guest memory until max memory change is first applied Cole has fixed this upstream. == koan == https://bugzilla.redhat.com/493414 Windows installs require manual reboot in the middle koan needs to acquire the ability to re-start a guest once the first stage of the install has completed.

2 2

Fix supermin when kernel arch != arch (x86)
by Matthew Booth 23 Jun '09

23 Jun '09

I have a non-PAE kernel installed (arch=i586) on a machine which reports arch=i686. This breaks the supermin helper. The attached patch makes it look for any x86 kernel. Matt -- Matthew Booth, RHCA, RHCSS Red Hat, Global Professional Services M: +44 (0)7977 267231 GPG ID: D33C3490 GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490

2 1

F-11 experience installing a CentOS guest
by Jerry James 22 Jun '09

22 Jun '09

I just upgraded to F-11 and have been trying out the new virt-manager. I have had a few "Huh?" moments that I'd like to share in case they help anyone else out. The release notes say that F-11 guests now get higher screen resolutions and absolute mouse coordinates via a USB tablet, out of the box. I need to make a CentOS 5.3 guest, and decided to see if I could get those same benefits. I knew the higher screen resolution was possible, because I have been running a CentOS 5.3 guest in F-10 using explicit invocation of qemu-kvm with the -std-vga switch. I hoped that the absolute mouse coordinates would also be possible, as the lack of them was probably the most annoying part of using that guest machine in F-10. My first attempt was to lie to virt-manager about what kind of guest I was installing. I told it that I was installing an F-11 guest, in hopes that things would Just Work. They didn't. Still, I was able to mostly patch things together as described below. When I created the virtual machine, I took a look at the hardware list. Even though I had specified an F-11 guest, there was no USB tablet on the hardware list. I thought I was supposed to get that automatically, just by specifying the F-11 guest. No matter; I added it manually. Now I don't need the PS/2 mouse, so let's get rid of it. I can't. The "Remove" button is grayed out. What's up with that? So I installed CentOS 5.3 in the guest. For the record, if you have SELinux on in your host machine, the CD images have to have type virt_content_t. Something (virt-manager?) apparently set the type correctly for me for CD #1, but I got an AVC denial and no CD visible to the guest when I tried to change to CD #2. So I changed all the CD image types to virt_content_t by hand and everything went okay after that. Installation finished. I rebooted the machine and got an 800x600 resolution screen. Darn. I looked through Xorg.0.log and found that virt-manager gave me the Cirrus video card. I thought specifying an F-11 guest was supposed to give me a generic VESA card. By adding a Monitor section to my xorg.conf and playing with HorizSync and VertRefresh, I can manage to get a 1280x800 window, but I really want 1280x1024. It doesn't appear to be possible to achieve that, though, as the emulated Cirrus card is reporting a dot clock that can't manage that resolution. How do I get virt-manager to give me the VESA card? It doesn't appear to be possible to get that through the interface it provides. Why not? The absolute mouse coordinates did NOT work when I first installed the machine. Once I added the Monitor section, they started working. I don't know why, though, as Xorg.0.log says that it is using the ExplorerPS/2 protocol, which suggests that X is using the PS/2 mouse that virt-manager won't let me remove instead of the USB tablet that I added manually. Thanks for all the work that has gone into improving the F-11 virtualization technology. -- Jerry James http://www.jamezone.org/

3 2

Fedora-virt
by Gerry Maddock 19 Jun '09

19 Jun '09

Hey all, just wanted to send a big THANKS to all developers involved in RH/FC virtulization. I have been using it since F10 and have 3 production W2k3 servers running rock solid on it (qemu-kvm) and I'm about to add 1 more W2k3 and 2 F11 virt servers. Keep up the good work!

2 2

F12 feature: Host information
by Richard W.M. Jones 17 Jun '09

17 Jun '09

I posted this page on the wiki last week, which is a feature we intend to implement for Fedora 12: http://fedoraproject.org/wiki/Features/Hostinfo Any comments? Rich. "Allow a virtual machine to see information and statistics from the host operating system, under narrow and strictly controlled conditions and only at the discretion of the host administrator. Detailed Description Allow a virtual machine to look at host information (such as number of physical, not just virtual CPUs), and statistics like the load on the host. Users have asked for this primarily as a diagnostic tool -- for example, poor performance of a virtual machine might be caused by excessive load on the host. Normally we try to isolate virtual machines from accessing any such details from the host, and there are very good reasons for that too, such as security of the host, commercial confidentiality, and the privacy of other virtual machines running on the host. As a result, at the moment there is no mechanism for accessing host information. We propose to add a feature which allows the host administrator, at their discretion, and only of limited data to limited virtual machines, to export host information and statistics to virtual machines. Administrators will need to: * explicitly enable this feature, * select the virtual machines and/or data they wish to be seen in guests, * select the frequency that guests can ask for data. The mechanism will be a daemon running on the host which collects the statistics (see below for what). The information will be exported to guests over a spare (virtual) serial port or through the qemu/kvm vmchannel feature, whichever is available. Guests will request information by sending a plain text command to the serial port, and will receive information in the form of a simple, plain text message. No special drivers or software are required by the guest. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones New in Fedora 11: Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 70 libraries supprt'd http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw

6 10

libguestfs experimental build with supermin appliance
by Richard W.M. Jones 16 Jun '09

16 Jun '09

This is an experimental rebuild of libguestfs with the supermin appliance: http://koji.fedoraproject.org/koji/taskinfo?taskID=1418138 Make sure you install libguestfs >= 1.0.48-2. Earlier versions were broken in various different ways. I've tested it locally on i586 & x86-64 and it seems to work for me. You'll get warning messages like this: ><fs> alloc /tmp/test.img 10M ><fs> run cpio: ./usr/sbin/glibc_post_upgrade.i686: Cannot open: Permission denied cpio: ./usr/sbin/groupadd: Cannot open: Permission denied cpio: ./usr/sbin/groupdel: Cannot open: Permission denied cpio: ./usr/sbin/groupmems: Cannot open: Permission denied cpio: ./usr/sbin/groupmod: Cannot open: Permission denied cpio: ./usr/sbin/tzdata-update: Cannot open: Permission denied [etc.] This is a known problem (it tries to pull some files from the host filesystem which are not readable) and shouldn't affect any operations and it still passes the test suite even without those programs. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen guests. http://et.redhat.com/~rjones/virt-p2v

1 0

libguestfs 'supermin appliance'
by Richard W.M. Jones 16 Jun '09

16 Jun '09

I just checked in a very experimental[1] set of patches to libguestfs git repo which allow you to build a so-called 'supermin (super- minimized) appliance'. The fact that it passes many of the API tests is nothing short of remarkable. To explain what this all means, read this: http://git.et.redhat.com/?p=libguestfs.git;a=commitdiff;h=14ec52d3dc332a02d… Rich. [1] With any luck, nothing will be broken _unless_ you do: ./configure --enable-supermin -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://et.redhat.com/~rjones/libguestfs/ See what it can do: http://et.redhat.com/~rjones/libguestfs/recipes.html

2 3

handling guest-service dependencies at boot time elegantly?
by Bill McGonigle 16 Jun '09

16 Jun '09

Hi, all, Before I start hacking up my own poor solution, I'd like to run this by the list and see if there's a good way to handle this. I have a host (5.3 Xen Dom0) that has three guests: Fedora 10 Fedora 11 Nexenta 2 The Nexenta (opensolaris) guest's job is to provide storage services to the Fedora DomU's, via iSCSI and NFS (ZFS storage). My goal is to automate system startup. My dependency tree looks like: Dom0 -> nexenta-DomU -> 'service iscsi'@Dom0 -> fedora-DomU's Currently I have xendomains and iscsi set to 'chkconfig off' and the fedora DomU's set for 'auto', and do: xm create nexenta [watch xentop to see when it's running] service iscsi start service xendomains start Which works find and requires me to do it. I can write some scripts to do the same thing, but if there was a more general-purpose way to express these kinds of boot-time dependencies, I'd rather do it right. I was thinking perhaps upstart could be co-opted for this purpose, if I can make it not cobbler init (it would have to run alongside on 5.3). Are there any libvirt event hooks into upstart? Thanks, -Bill -- Bill McGonigle, Owner Work: 603.448.4440 BFC Computing, LLC Home: 603.448.1668 http://www.bfccomputing.com/ Cell: 603.252.2606 Twitter, etc.: bill_mcgonigle Page: 603.442.1833 Email, IM, VOIP: bill(a)bfccomputing.com Blog: http://blog.bfccomputing.com/ VCard: http://bfccomputing.com/vcard/bill.vcf

3 5

RFC: libosinfo: Library for virt OS/distro metadata 3
by Cole Robinson 15 Jun '09

15 Jun '09

Hi all, I've done the initial work for a new library, libosinfo (better name recommendations appreciated). This library will provide OS meta data for use in virt applications, replacing the dictionary we currently keep in virtinst. This is based off of a post by Dan Berrange: https://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00028.html The code can be fetched with: git clone http://fedorapeople.org/~crobinso/osinfo/.git Check out the TODO list for a simple roadmap. http://fedorapeople.org/~crobinso/osinfo/TODO The public API looks like: /** * Values stored in the OS dictionary */ enum _os_value_type { OS_VALUE_NAME = 1, /** Human readable family/distro... name */ OS_VALUE_MEDIA_INSTALL_URL, /** URL to an install tree */ }; typedef enum _os_value_type os_value_t; int os_init(); void os_close(); int os_find_families (char ***list); int os_find_distros (const char *parent_id, char ***list); int os_find_releases (const char *parent_id, char ***list); int os_find_updates (const char *parent_id, char ***list); int os_lookup_value (os_value_t value_type, const char *os_id, char **value); The unique identifier for each distro is its 'id', which is a simple human readable string, similar to values we use for virt-install --os-variant today. The user will ask the API for available families/distros/releases/updates, which will return a list of ids. We then pass an id to os_lookup_value to actually retrieve data. The family/distro/... separation will likely be removed pretty soon, in favor of an arbitrary hierarchy, where every OS can have child OSes: no doubt hardcoding the family/distro/... split would come back to bite us in the ass. As an example, the following code will list the 'Name' of every id at the'family' level, where name is full name of the OS (id = rhel5.3, name = Red Hat Enterprise Linux 5.3): char *value = NULL; char **namelist = NULL; int i, num_fams; if (os_init() < 0) goto error; if ((num_fams = os_list_families(&namelist)) < 0) goto error; for (i = 0; i < num_fams; ++i) { if (os_lookup_value(OS_VALUE_NAME, namelist[i], &value) < 0) goto error; printf("%s\n", value); free(value); } error: free(namelist); free(value); os_close(); There is a simple tool called 'osinfo-tool' which allows listing an ASCII repr of the OS hierarchy, and listing all values for an individual id (which is pretty sparse at the moment since most of these values haven't been filled in yet). So, things that I'm interested in feedback on: - How do we expect apps to list OS choices? Currently, virt-manager lists type (linux, windows, unix, etc.) and associated distros (Fedora 8, RHEL4, Debian Lenny, etc.). The linux/windows/unix info isn't represented in the xml (should it be?) so the best way seems to be: Distro | --> Release | --> Update Ex. RHEL | -> RHEL5 | -> 5.0 5.1 5.2 If we do away with the family/distro/... distinction, the user won't have much choice in the matter, but the 'family' concept (e.g. value of 'Red Hat') isn't very useful to expose to a user. - How should we handle derivatives like Scientific Linux + CentOS: should we expect users to understand they are based on RHEL, or give them explicit IDs? - Querying for device values (supported buses, models, etc.). Dan's original proposal talks about this; to recommend a default with the best chance of actually working, we need to know: - OS being installed - Virt type ('hvm' vs. 'xen') - Guest Architecture (i386, x86_64, ...) - Hypervisor (kvm, qemu, xen, vbox, ...) - Hypervisor version - Libvirt version We would need to find the intersection of what the OS, the hypervisor, and libvirt support, and return what we decide is the best choice. How to expose this in the API? We could simply have one long function os_lookup_device_value(char *os_id, char *virt_type, char *arch, ...) It works, but its pretty tedious, and I'm afraid that we would need even more info to make a correct choice in the future, and the above isn't flexible. We may also need some of the above info for other values (ACPI/APIC settings, returning a proper install url may depend on arch). Any suggestions? - os_init and os_close: Any better ideas for this? os_init just parses the xml document, os_close frees it. We could run os_init with the first API call, but I think that makes it less clear that the user would then need to call os_close(). Any feedback appreciated. Thanks, Cole

4 18

iPod Touch + Fedora 11 + KVM + WinXP guest + iTunes?
by Laine Stump 14 Jun '09

14 Jun '09

I want a Win XP guest (running under a fresh F11 install) to talk to my shiny new iPod Touch. I tried adding the "Apple Inc. iPod" USB device to the guest's hardware list with virt-manager, but even after restarting everything it isn't recognized (it's still picked up by the host OS - which doesn't know what to do with it - and not seen at all by the guest). Has anybody done this? Any hints? (a better solution would be if RhythmBox or some other program figured out how to talk to the Touch (and/or iPhone), but as far as I've found, that hasn't happened yet).

2 1

Is this normal?
by Tom Horsley 13 Jun '09

13 Jun '09

I have my newly installed fedora 11 x86_64 system on an Intel Core 2 Duo with virtualization hardware support, so I thought I'd give KVM a whirl. I started virt-manager as root, defined a new machine which I made be an i686 and pointed at the Fedora 11 i386 DVD iso image. I also told it to allocate space immediately for a 12GB image file. It has now been running anaconda's cylon eyeball format progress bar for about an hour. How long should it take to format the silly disk image? Other points: I can't believe virt-manager insists on placing image files under /var. They take lots of space. I'd expect to be able to pick a place to put the disk image. This fedora-virt mailing list doesn't have a pointer in the list of mailing lists on the fedora mailing list web page at: http://fedoraproject.org/wiki/Communicate

4 5

libguestfs under Debian / Ubuntu
by Tim Tassonis 13 Jun '09

13 Jun '09

Hi all Just came across libguestfs and, as a qemu user, this project really sound fantastic to me. However, when I tried to compile the latest tarball, I failed, mainly because of the inavalability of febootstrap, which obviously does not exist under ubuntu, and cannot be installed due to the lack of yum under ubuntu at least. Is debian support planned, or is libguestfs designed to be a fedora-only project? Bye Tim

5 24

Error using Virtual Machine Manager to create new Windows XP VM
by Colin Coates 12 Jun '09

12 Jun '09

Dear All, I was previously successful in using KVM/Qemu to create and run a Windows XP virtual machine hosted on Fedora 10. I have now upgraded to Fedora 11 x86_64 (using Live distribution), but I get an error whilst using the Virtual Machine Manager to create a Windows XP virtual machine. The virtual machine is configured to install from a local CD (containing the Windows XP Pro install CD), OS type is "Windows", Version is "Microsoft Windows XP (x86)", memory is 1536MB, CPU set to 1, disk is 50GB (allocate entire disk now). My host PC is a Lenovo T60p (Intel Core 2 Duo with 4GB physical memory), and I have enable Intel Virtualization in the BIOS. The message displayed in the Error dialog is: "Unable to complete install: 'internal error unable to start guest: char device redirected to /dev/pts/0 char device redirected to /dev/pts/1" The details are: "Unable to complete install '<class 'libvirt.libvirtError'> internal error unable to start guest: char device redirected to /dev/pts/0 char device redirected to /dev/pts/1 Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/create.py", line 1501, in do_install dom = guest.start_install(False, meter = meter) File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 541, in start_install return self._do_install(consolecb, meter, removeOld, wait) File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 633, in _do_install self.domain = self.conn.createLinux(install_xml, 0). File "/usr/lib64/python2.6/site-packages/libvirt.py", line 974, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error unable to start guest: char device redirected to /dev/pts/0 char device redirected to /dev/pts/1" Can anyone offer any suggestions about what I might be doing wrong? Kind Regards, Colin Coates

2 1

Fedora 11 - Networking fails in KVM VMs
by Scott Dowdle 11 Jun '09

11 Jun '09

Greetings, I have used KVM in Fedora now since Fedora 9 and it has always done quite well and I've been very happy with it. Today I did a fresh Fedora 11 install (retaining my /home and /vm directories where my .img files were stored) and copied my Fedora 10 /etc/libvirt/qemu/*.xml from backup. My machines started fine. The one Windows VM I had noticed a lot of new hardware. Everything seems to work fine and be very fast... but networking does NOT work in any of my VMs. Thinking that perhaps something had changed in the .xml files, I deleted all of the VMs (but retained their storage) and created all new VMs using the existing storage. I don't have any fancy networking going on. My physical machine has a public IP address. It has NATing turned on and ip_foward = 1. The VMs are default ones with privates that are gotten via DHCP with the internal DHCP server and I have not messed with any of the DHCP settings in virt-manager. In the past, the VMs would get a 192.168.122.x address and they just worked. Now they can't seem to get an IP. I'm guessing it is something funky with my iptables settings but I can't seem to see anything out of the ordinary. Anyone else run into problems or have some suggestions for troubleshooting this? So far I haven't seen anything on the mailing list that applies. I've installed Fedora 11 on about 6 machines now and a few VMs for building remix images and it has been great. Good job. TYL, -- Scott Dowdle CS Department SysAdmin EPS 262 406-994-3931 [work] 406-388-0827 [home]

2 2

Fedora 11 and Virtual Machine Manager
by Gerry Maddock 10 Jun '09

10 Jun '09

Hello all, I have been using qemu-kvm via the virtual machine manger on Fedora 10 and have had no problems (works great & love it!). I just downloaded and installed Fedora 11 64 bit on a new server and logged in as a normal user and started the virtual machine manager. I'm able to connect to the virtual machine manager, but cant setup any new VM's as I'm connected as Read-Only (This must be a new feature). How should I go about connecting to VMM READ-WRITE? Do I need to setup this user in /etc/sudoers to use VMM? Any help would be appreciated!

2 1

Minimum Host for Virt-Manager?
by Frank Murphy 10 Jun '09

10 Jun '09

What is the Minimum Host I can install to rum Virt-Manager? AOS? XFCE? Frank

2 2

Install Guest\HD Q?
by Frank Murphy 06 Jun '09

06 Jun '09

Is it possible to assign a full *physical drive* to each guest. If I need one for F11, F11, Rawide the first two being update in line with releases. Do I set this up while installing the host OS? Best Recommended? -- msn: frankly3d skype: frankly3d Mailing-List Reply to: Mailing-List Still Learning, Unicode where possible

3 6

Some new features of virt-inspector
by Richard W.M. Jones 06 Jun '09

06 Jun '09

I've added a few extra features to virt-inspector (in libguestfs >= 1.0.42). First up is a new 'query mode', documented in the manpage: http://et.redhat.com/~rjones/libguestfs/virt-inspector.1.html#query_mode Just run: virt-inspector --query [some virtual machine] and it'll print out some useful facts about the virtual machine such as whether it's fully virtualized or needs a Xen hypervisor, and whether it has various paravirt drivers installed. Secondly (not covered in the manpage), virt-inspector will try to discover whether a VM contains the right initrd drivers and module configuration to boot under various hypervisors. So for example it can tell you whether a guest has the virtio drivers available at boot time to boot from a virtio disk. As usual, to find out more about virt-inspector, see the manual page or the libguestfs home page: http://et.redhat.com/~rjones/libguestfs/virt-inspector.1.html http://et.redhat.com/~rjones/libguestfs/ libguestfs and virt-inspector are available in Fedora 11 updates- testing, or Rawhide, or as RPMs from Koji here: http://koji.fedoraproject.org/koji/buildinfo?buildID=105088 Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 75 OCaml packages (the OPEN alternative to F#) http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora

1 0

Too much ram for F10
by Thomas S Hatch 06 Jun '09

06 Jun '09

I already posted about this in the cobbler list and they sent me over here. It seems that whenever I try to install a new virtual machine(kvm) with koan, and the ram for the machine is higher than 2 gigs the machine fails to install. The domain and hard drive image are created, but they won't start up to do the install. My guess was that the arch was being set to i686 in the libvirt xml file, and that that was causing issues, but the vms with 2 gigs of ram and arch="i686" in the libvirt config install just fine with a 64 bit version of Fedora. I then decided to track down where the arch assignment was being made in the code, koan uses the default arch supplied by virtinst.FullVirtGuest. In that code the 2 lines that detect the host arch are commented out, I uncommented them, and tried again. The arch in the libvirt xml files became x86_64, but they still failled to install for vms with 4 gigs of ram! So I am stumpted! Anyone have any suggestions? Host machine: Fedora 10 64 bit, 8 3Ghz core, 32 Gigs of ram 1TB hdd It is also running on a node in a red hat cluster suite 2.99 Here is the log from one of my systems: LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/bin/qemu-kvm -S -M pc -m 4096 -smp 2 -name broker -uuid 60cec202-99dd-0f63-e198-f708c90a288b -monitor pty -no-reboot -boot c -kernel /var/lib/libvirt/boot/virtinst-vmlinuz.kmgRaG -initrd /var/lib/libvirt/boot/virtinst-initrd.img.W2X9jX -append ks= http://192.168.46.234/cblr/svc/op/ks/system/broker ksdevice=link kssendmac lang= text method=http://192.168.46.234:80/cblr/links/F10-x86_64/<http://192.168.46.234/cblr/links/F10-x86_64/>-drive file=/vm/images/broker-disk0,if=virtio,index=0,boot=on -net nic,macaddr=00:16:3e:38:81:65,vlan=0,model=virtio -net tap,fd=22,script=,vlan=0,ifname=vnet1 -serial pty -parallel none -usb -vnc 0.0.0.0:1 -k en-us char device redirected to /dev/pts/4 char device redirected to /dev/pts/5 i^[[K^[[Din^[[K^[[D^[[Dinf^[[K^[[D^[[D^[[Dinfo^[[K^[[D^[[D^[[D^[[Dinfo ^[[K^[[D^[[D^[[D^[[D^[[Dinfo c^[[K^[[D^[[D^[[D^[[D^[[D^[[Dinfo cp^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo cpu^[[K^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[Dinfo cpus^[[K^M * CPU #0: pc=0x00000000000ffff0 thread_id=17984^M CPU #1: pc=0x00000000000ffff0 thread_id=17985^Mc^[[K^[[Dco^[[K^[[D^[[Dcon^[[K^[[D^[[D^[[Dcont^[[K^Mqemu: loading initrd (0x10efde0 bytes) at 0x000000007ef10000 kvm_cpu_register_physical_memory: failed create_userspace_phys_mem: Invalid argument And here is some host system info: /proc/cpuinfo: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5450 @ 3.00GHz stepping : 6 cpu MHz : 3000.092 cache size : 6144 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 lahf_lm bogomips : 6000.18 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5450 @ 3.00GHz stepping : 6 cpu MHz : 3000.092 cache size : 6144 KB physical id : 1 siblings : 4 core id : 0 cpu cores : 4 apicid : 4 initial apicid : 4 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 lahf_lm bogomips : 6000.31 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5450 @ 3.00GHz stepping : 6 cpu MHz : 3000.092 cache size : 6144 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 4 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 lahf_lm bogomips : 6000.29 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5450 @ 3.00GHz stepping : 6 cpu MHz : 3000.092 cache size : 6144 KB physical id : 0 siblings : 4 core id : 2 cpu cores : 4 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 lahf_lm bogomips : 6000.27 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: processor : 4 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5450 @ 3.00GHz stepping : 6 cpu MHz : 3000.092 cache size : 6144 KB physical id : 0 siblings : 4 core id : 3 cpu cores : 4 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 lahf_lm bogomips : 6000.26 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: processor : 5 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5450 @ 3.00GHz stepping : 6 cpu MHz : 3000.092 cache size : 6144 KB physical id : 1 siblings : 4 core id : 1 cpu cores : 4 apicid : 5 initial apicid : 5 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 lahf_lm bogomips : 6000.31 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: processor : 6 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5450 @ 3.00GHz stepping : 6 cpu MHz : 3000.092 cache size : 6144 KB physical id : 1 siblings : 4 core id : 2 cpu cores : 4 apicid : 6 initial apicid : 6 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 lahf_lm bogomips : 6000.32 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5450 @ 3.00GHz stepping : 6 cpu MHz : 3000.092 cache size : 6144 KB physical id : 1 siblings : 4 core id : 3 cpu cores : 4 apicid : 7 initial apicid : 7 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 lahf_lm bogomips : 6000.29 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: /proc/meminfo: MemTotal: 23452656 kB MemFree: 19856416 kB Buffers: 11308 kB Cached: 92944 kB SwapCached: 236 kB Active: 3073996 kB Inactive: 29244 kB SwapTotal: 10256376 kB SwapFree: 10256016 kB Dirty: 180 kB Writeback: 0 kB AnonPages: 2998556 kB Mapped: 16820 kB Slab: 189048 kB SReclaimable: 61812 kB SUnreclaim: 127236 kB PageTables: 10352 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 21982704 kB Committed_AS: 3661632 kB VmallocTotal: 34359738367 kB VmallocUsed: 150160 kB VmallocChunk: 34359587191 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB DirectMap4k: 7920 kB DirectMap2M: 23846912 kB

2 1

intel vt versus amd-v?
by Robert P. J. Day 06 Jun '09

06 Jun '09

a friend wants to buy a server (probably dell) with HW virt support, and is wondering if there are any current clear advantages of intel over amd. the only observation i had time to make was that, if one checks out entry-level servers from dell (ballpark $1000 cdn), the amd opteron systems appear to be somewhat less expensive than equivalent intel-based systems. further thoughts? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Annoying Kernel Pedantry. Web page: http://crashcourse.ca Linked In: http://www.linkedin.com/in/rpjday Twitter: http://twitter.com/rpjday ========================================================================

5 7

Fedora virt status
by Mark McLoughlin 05 Jun '09

05 Jun '09

Okay, so F-11 is done and dusted. Onwards to F-12! Here's what the schedule looks like: 2009-07-28 Feature Freeze (53 days) 2009-08-04 Beta Freeze (60 days) 2009-09-22 Final Development Freeze (109 days) 2009-10-20 Compose & Stage Release Candidate (137 days) F11 Release =========== Another one week slip for the F11 release, this because of a late breaking anaconda storage problem: http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02159.html A late discovered and just potentially fixed anaconda storage bug[1] has necessitated another week slip of our schedule. The change is important but invasive enough to require re-validating our storage tests. We were already late in producing the Release Candidate and there is not enough time to produce another one and validate it in time for next Tuesday's release date. However, the release is now complete and being queued up on the mirrors. Expect the release early next week! F11 Virt Interview ================== Dan Berrange was interviewed about virtualization in Fedora 11. Read the full interview here: http://jaboutboul.blogspot.com/2009/05/fedora-11-virtualization-reality.html F11 Updates =========== A number of zero-day updates are available for F-11 users. The following are available in stable: https://admin.fedoraproject.org/updates/qemu-0.10.5-2.fc11 https://admin.fedoraproject.org/updates/libvirt-0.6.2-11.fc11 https://admin.fedoraproject.org/updates/virt-manager-0.7.0-5.fc11 https://admin.fedoraproject.org/updates/libguestfs-1.0.21-3.fc11 https://admin.fedoraproject.org/updates/openbios-1.0-1.fc11 and these are in updates-testing: https://admin.fedoraproject.org/updates/libvirt-0.6.2-12.fc11 https://admin.fedoraproject.org/updates/virt-viewer-0.0.3-5.fc11 https://admin.fedoraproject.org/updates/libguestfs-1.0.41-1.fc11 https://admin.fedoraproject.org/updates/etherboot-5.4.4-14.fc11 Please help out with testing these latest updates and report any issues. Virt Preview Repository ======================= Updates are being pushed regularily to the virt-preview repository: http://markmc.fedorapeople.org/virt-preview/README Below are the updates which have been pushed lately - obviously these are also available in rawhide: == qemu == * Fri Jun 5 2009 Mark McLoughlin <markmc(a)redhat.com> - 2:0.10.50-6.kvm86 - Fix 'kernel requires an x86-64 CPU' error - BuildRequires ncurses-devel to enable '-curses' option (#504226) * Wed Jun 3 2009 Mark McLoughlin <markmc(a)redhat.com> - 2:0.10.50-5.kvm86 - Prevent locked cdrom eject - fixes hang at end of anaconda installs (#501412) - Avoid harmless 'unhandled wrmsr' warnings (#499712) * Thu May 21 2009 Mark McLoughlin <markmc(a)redhat.com> - 2:0.10.50-4.kvm86 - Update to kvm-86 release - ChangeLog here: http://marc.info/?l=kvm&m=124282885729710 == libvirt == * Fri Jun 5 2009 Mark McLoughlin <markmc(a)redhat.com> - 0.6.4-2.fc12 - Remove the qemu BuildRequires * Fri May 29 2009 Daniel Veillard <veillard(a)redhat.com> - 0.6.4-1.fc12 - Upstream release of 0.6.4 - new APIs - fixes for latests QEmu/KVM versions - various assorted fixes * Mon May 25 2009 Mark McLoughlin <markmc(a)redhat.com> - 0.6.3-11.fc12 - Bring up the bridge, even if it doesn't have an IP address (bug #501912) * Thu May 21 2009 Mark McLoughlin <markmc(a)redhat.com> - 0.6.3-10.fc12 - Fix XML attribute escaping (bug #499791) - Fix serious event handling issues causing guests to be destroyed (bug #499698) * Thu May 21 2009 Mark McLoughlin <markmc(a)redhat.com> - 0.6.3-9.fc12 - Fix qemu argv detection with latest qemu (bug #501923) Some discussion has also begun on how to sign the packages in the preview repo: http://www.redhat.com/archives/fedora-virt/2009-June/msg00024.html Xen Dom0 ======== Jeremy Fitzhardinge's latest submission of the Xen Dom0 patches for 2.6.31 has caused the kernel community to get themselves into a bit of a flap. LWN has a nice article on the 'discussion': http://lwn.net/Articles/335812/ But the stronger voice looks to be the one saying that the problems need to be fixed first. The deciding factors seem to be (1) the user-space ABI, and (2) the intrusion into the core x86 code; those issues make Xen different from yet another driver or filesystem. That, in turn, suggests that the Dom0 code is not destined for the mainline anytime soon. Instead, the Xen developers will be expected to go back and fix a list of problems - a lot of work with an uncertain result at the end. Will we have Dom0 support in the F-12 kernel? It's looking increasingly unlikely, isn't it? On a positive note, reading LKML threads like this are a good way of putting the supposed dire state of fedora-devel-list in perspective ;-) In other news Michael Young continues to push out RPM builds of the latest Dom0 patch set: http://www.redhat.com/archives/fedora-virt/2009-June/msg00023.html Oh yes - Gerd Hoffman has pushed a xen-3.4.0 update to F-11: Bugs ==== DOOM-O-METER: 236 open bugs 3 weeks ago, 238 now. It looks like 103 of these are F-11/F-12 bugs which aren't fixed by pending updates. The "short" list of particularily interesting F-11 bugs is here: https://bugzilla.redhat.com/showdependencytree.cgi?id=F11VirtTarget&hide_re… = New Bugs = == qemu == https://bugzilla.redhat.com/503236 qemu/tcg - boot hangs intermittently on cryptomgr_test at doublefault_fn Rich Jones discovered this TCG issue with libguestfs tests. There has been some discussion upstream analyzing the issue. https://bugzilla.redhat.com/503184 Add system_reboot to qemu Currently there is no way for libvirt to request qemu to reboot a guest. We really should get this done for F12. https://bugzilla.redhat.com/503156 qemu VNC :: xterm inside VM shows garbled text Looks like our vnc server has some issues with framebuffer updates. https://bugzilla.redhat.com/504273 qemu-system-ppc on ppc host fails with "no opcode defined" It looks like qemu-system-ppc on a ppc host is failing to initialize its opcode table. https://bugzilla.redhat.com/504294 qemu-system-ppc fails to boot ISO image Looks like qemu's ppc target can't currently boot from a cdrom. == libvirt == https://bugzilla.redhat.com/500968 virt-manager traceback on shutdown of qemu-kvm -no-acpi guest A guest with ACPI disabled will exit immediately when issued with the "system_powerdown" command and libvirt isn't handling this gracefully. == virtinst == https://bugzilla.redhat.com/502627 virtinst should always specify the disk image format in guest configuration This is a long standing known issue, which has been fixed upstream bu we should really pull the fix into F-11. == virt-manager == https://bugzilla.redhat.com/502110 virt-manager does not re-connect after libvirtd restart It seems that if you restart libvirtd while virt-manager is running, then virt-manager doesn't know how to re-connect to libvirtd. https://bugzilla.redhat.com/499547 virt-manager should restart linux guests after they have finished installing Discussion about the fact that virt-manager does not re-start a guest after it has been installed. https://bugzilla.redhat.com/502777 virt-manager does not recalculate free disk space on new VM creation In the 'New VM' wizard, we don't currently update the 'XXXGb available on the host' message if people go and delete files when they realize they don't have enough space. https://bugzilla.redhat.com/503001 RFE virt-manager: allow desktop switch with ctrl+alt+arrow_key Someone finally filed a bug on it :-) When you go to switch workspaces with Ctrl-Alt-Arrow, virt-manager grabs the keyboard, which is pretty annoying. https://bugzilla.redhat.com/503150 virt-manager window size bigger after returning from fullscreen It seems that going back and forth between fullscreen can cause the virt-manager window to be resized such that it is partially off-screen. https://bugzilla.redhat.com/503784 memory changes in virt-manager do not persist across libvirtd restart virt-manager is using a non-persistent libvirt API to adjust the guest memory configuration. https://bugzilla.redhat.com/503786 virt-manager refuses to increase guest memory until max memory change is first applied An annoying little problem where virt-manager appears to want to pick a fight with the user. == gnome-applet-vm == https://bugzilla.redhat.com/502748 gnome-applet-vm should use PolicyKit The applet currently uses consolehelper, it should use PolicyKit instead. = Resolved Bugs = == qemu == https://bugzilla.redhat.com/501412 f11 kvm guest install exits after package install completes qemu wasn't properly implementing cdrom door locking allowing anaconda to eject the cdrom while it was locked, killing the install. Fixed in qemu-0.10.5-2.fc11. https://bugzilla.redhat.com/501264 qemu segfaults for -net socket,listen=localhost:4567 Simple fix cherry-picked from upstream and included in qemu-0.10.5-2.fc11. https://bugzilla.redhat.com/499712 qemu-kvm: avoid harmless unhandled wrmsr 0xc0010117 messages These warnings were causing quite a bit of confusion so we've cherry-picked a fix from Marcelo to make them go away. Also in qemu-0.10.5-2.fc11. https://bugzilla.redhat.com/503575 LiveCD Installer hangs during guest VM install-to-virt-drive Apparently this has been fixed by the qemu-0.10.5 update. https://bugzilla.redhat.com/503807 kqemu is disabled in qemu Glauber lays down the law, we're not supporting kqemu. https://bugzilla.redhat.com/504226 qemu-kvm binary should support the '-curses' option A simple missing ncurses-devel BuildRequires was causing the '-curses' option to not be supported in qemu. Fixed in F-12. == libvirt == https://bugzilla.redhat.com/502862 libvirt runs qemu-system-ppc with wrong machine type - should be g3beige, not g3bw The ppc machine types have changed in upstream qemu; fixed in the libvirt-0.6.2-12.fc11 update. https://bugzilla.redhat.com/503066 libvirtd crashes on tls connection danpb fixed this upstream and the fix was included in libvirt-0.6.2-12.fc11. https://bugzilla.redhat.com/503406 F11: libvirt: cannot shutdown virtual machines booted to a console prompt It turns out that if acpid is not running in the guest, the qemu 'system_powerdown' command used by libvirt doesn't do anything. == virt-viewer == https://bugzilla.redhat.com/499362 virt-viewer prevents key combinations like alt-f from being sent to the guest https://bugzilla.redhat.com/499595 virt-viewer mixes up password and username credentials for VNC https://bugzilla.redhat.com/499594 virt-viewer doesn't know how to provide a username/password to libvirt connections danpb pushed a virt-viewer-0.0.3-5.fc11 update with fixes for all these issues. == libguestfs == https://bugzilla.redhat.com/503133 "mkdir-p" should not throw errors on preexisting directories https://bugzilla.redhat.com/503135 cramfs and squashfs modules should be available in libguestfs appliances https://bugzilla.redhat.com/503169 libguestfs /dev is too sparse for kernel installation/upgrade Rich Jones and Charles Duffy have been busily fixing libguestfs bugs. = Ongoing Bugs = == qemu == https://bugzilla.redhat.com/501935 qemu-kvm -kernel should parse "vga=" cmdline option Someone posted an implementation for this upstream. https://bugzilla.redhat.com/501131 qemu segfault when VNC client disconnects Enrico tried the test patch and it didn't help, but that could be down to the fact that there are many failure cases. A cleaner fix is required.

2 1

F-11 xen-3.4.0 update ? [was Re: [fedora-virt-maint] rpms/xen/F-11 dom0-kernel.repo, NONE, 1.1 init.blktapctrl, NONE, 1.1 init.xenconsoled, NONE, 1.1 init.xend, NONE, 1.1 init.xenstored, NONE, 1.1 sysconfig.blktapctrl, NONE, 1.1 sysconfig.xenconsoled, NONE, 1.1 sysconfig.xenstored, NONE, 1.1 xen-configure-xend.patch, NONE, 1.1 .cvsignore, 1.39, 1.40 sources, 1.54, 1.55 xen-dumpdir.patch, 1.4, 1.5 xen-initscript.patch, 1.11, 1.12 xen-net-disable-iptables-on-bridge.patch, 1.3, 1.4 xen.spec, 1.2
by Mark McLoughlin 05 Jun '09

05 Jun '09

Hi Gerd, On Wed, 2009-05-27 at 20:06 +0000, Gerd Hoffmann wrote: > Author: kraxel > > Update of /cvs/pkgs/rpms/xen/F-11 > In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv16320 > ... > %changelog > +* Wed May 27 2009 Gerd Hoffmann <kraxel(a)redhat.com> - 3.4.0-1 > +- update to version 3.4.0. Are you planning on pushing this to F-11 updates? Cheers, Mark.

1 1

Adding VM to virt-manager
by Dennis Jacobfeuerborn 05 Jun '09

05 Jun '09

Hi, How do I add a custom-built vm to virt-manager? I basically created an empty image, untarred a template setup into it and made it boot using qemu-kvm from the shell. Now I'd like to make this vm visible in virt-manager so that I can manage it from there. I tried creating a domain xml file in /etc/libvirt/qemu but that doesn't seem to be enough. Regards, Dennis

2 2

GPG signatures for Rawhide virt repo
by Ján ONDREJ (SAL) 05 Jun '09

05 Jun '09

Hello, Mark, can you please add signatures to vire-preview packages? Installation of totally unsigned packages on my machine is not a good idea, because I don't know, if they was changed by an attacker on internet. Installation works with root privileges, so everything is possible. To add signatures, you can be inspired by my scripts. You can run "rpm --sign" command before createrepo on all packages safely. My script uses libskippass.so to do not require password for singning key. You need to create .rpmmacros, where signing key is defined: %_signature gpg %_gpg_path /home/YOURLOGIN/.gnupg %_gpg_name YOUR_KEY_NAME My libskippass.c, if you need it: ---------------------------- // compile with: gcc -shared -o libskippass.so skippass.c #include <stdio.h> char *getpass(const char *prompt) { char *p = ""; printf("%s <<< SKIPPED! >>>\n", prompt); return p; } ---------------------------- And finally signing command: LD_PRELOAD=/lib/libskippass.so rpm --addsign /path/to/your/packages/*/*.rpm \ 2>&1 | grep -v -e 'was already signed by key' -e ':$' Output of this command is filtered to do not show already signed packages. Now you only need to create your new GPG key, distribute public key and start to sign with private key. I think signed packages with potentially insecure key is much better, like totally unsigned, but you also can use a key for your signing key. SAL

2 2

ANNOUNCE: libguestfs 1.0.41 released
by Richard W.M. Jones 04 Jun '09

04 Jun '09

[This is the only time I'll send this announcement to qemu-devel] I'm pleased to announce the release of a new stable version of libguestfs, the library for accessing and modifying virtual machine disk images. Based on around qemu and Linux kernel code, this can be used as a library or from scripts to make batch configuration changes to guests, view and edit config files inside guests, and much more. http://et.redhat.com/~rjones/libguestfs/ Source: http://et.redhat.com/~rjones/libguestfs/files/libguestfs-1.0.41.tar.gz Fedora 11+ packages: (Available soon in F11 updates-testing or directly from Koji: http://koji.fedoraproject.org/koji/buildinfo?buildID=104824) RHEL/CentOS 5 packages: (Being uploaded to EPEL now, available soon) Debian packages: http://www.annexia.org/tmp/debian/ Since the last announcement, many bugs have been fixed and features added. The main highlights are: - squashfs and cramfs support - better support for read-only access to drives - many problems with string handling in different language bindings have been fixed - internationalization support - ext4 support improved on RHEL 5 - improved support for running commands in the guest - support for skipping tests - lvresize and ext2/3 resize support - pvremove, vgremove, lvremove commands - sleep command - IRC channel #libguestfs on FreeNode Bugs fixed: 501761 - libguestfs requires qemu, not qemu-system-x86 or qemu-system-ppc 501878 - guestfish built-in commands like 'alloc' and 'help' don't autocomplete 501883 - javadoc messed up in libguestfs java documentation 501885 - Doesn't detect missing Java, --with-java-home=no should not be needed 501892 - OptString parameters not handled properly in bindings 502309 - libguestfs build failure - tests occasionally fail with 'ranlib: './libmlguestfs.a': No such file' 502533 - Polish translation of libguestfs 503133 - "mkdir-p" should not throw errors on preexisting directories 503135 - cramfs and squashfs modules should be available in libguestfs appliances 503169 - libguestfs /dev is too sparse for kernel installation/upgrade Thanks to Charles Duffy for a number of patches and suggestions. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://et.redhat.com/~rjones/libguestfs/ See what it can do: http://et.redhat.com/~rjones/libguestfs/recipes.html

1 0

Installing kernel packages under libguestfs
by Charles Duffy 04 Jun '09

04 Jun '09

I'm trying to upgrade kernel packages via libguestfs -- but grubby and mkinitrd don't deal well at all with having a less-than-fully-populated /dev, either failing to operate at all or producing an initrd with LVM support omitted. Before I spend too much more time on this one -- any hints or recipes? Thanks!

2 3

Problem installing KVM gueast on LMV
by Leonid Flaks 02 Jun '09

02 Jun '09

Hi! I am trying to install KVM guest on fedora 10 host system using virt-install command: virt-install \ --connect qemu:///system \ --accelerate \ --vnc \ --ram 512 \ --name test \ --mac 00:16:3E:70:8C:D0 \ --network bridge:br0 \ --disk path=/dev/vg-virt/LV1 \ --os-type=linux \ --os-variant=fedora10 \ --location http://mycompany.local.mirror/fedora/releases/10/Fedora/x86_64/os \ -x "ip=dhcp kssendmac ksdevice=bootif noipv6 ks=http://myweb.server/ks/virt-system/ks-test-bnl-f10-64.cfg" All goes well to the point when anaconda is trying to do partitioning. At this moment I see error on the screen - "Error allocating requested partitions. Partitioning failed. Could not allocate partitions as primary partitions. Not enough space left to create partition /boot. Press OK to exit the installer." kickstart has the following partitions information: part /boot --asprimary --fstype="ext3" --size=100 part / --fstype="ext3" --size=2000 part swap --fstype="swap" --size=500 part /var/log --fstype="ext3" --size=250 part /usr --fstype="ext3" --size=1 --grow /dev/vg-virt/LV1 is 9G - should be plenty of space. I think the LVM information is not being passed to anaconda for some reason. I had very similar setup on fedora 8 with Xen and it works fine. Is there anything specific to KVM on fedora 10 that I missed? Thanks, Leon

4 6

virt-inspector calling guestfs_umount_all() before launch()?
by Charles Duffy 02 Jun '09

02 Jun '09

This is virt-inspector-1.0.34-1.3 on CentOS 5: $ virt-inspector --ro-fish --xml da.qcow2 qemu: loading initrd (0x33a576d bytes) at 0x0000000014c4a000 umount_all: guestfs_umount_all: call launch() before using this function at /usr/bin/virt-inspector line 375.

2 18

[Fwd: Re: [fedora-virt] Hostdev XML Not Working (Libvirt)]
by Robert L Cochran 02 Jun '09

02 Jun '09

Well, I do understand that virt-install and libguestfs are very important, but I hope there can be some attention focused on my tiny problem. Or perhaps I should file a bug? Bob -------- Original Message -------- Subject: Re: [fedora-virt] Hostdev XML Not Working (Libvirt) Date: Wed, 27 May 2009 17:28:36 -0400 From: Robert L Cochran <cochranb(a)speakeasy.net> To: Cole Robinson <crobinso(a)redhat.com> CC: fedora-virt(a)redhat.com On 05/27/2009 10:23 AM, Cole Robinson wrote: > Robert L Cochran wrote: > >> Why doesn't the hostdev xml shown below for a USB device work? I've >> shown the entire<devices> block for context. >> >> <devices> >> <emulator>/usr/bin/qemu-kvm</emulator> >> <disk type='file' device='cdrom'> >> <target dev='hdc' bus='ide'/> >> <readonly/> >> </disk> >> <disk type='file' device='disk'> >> <source file='/var/lib/libvirt/images/Ubuntu9.img'/> >> <target dev='vda' bus='virtio'/> >> </disk> >> <interface type='network'> >> <mac address='54:52:00:74:32:2f'/> >> <source network='default'/> >> <model type='virtio'/> >> </interface> >> <serial type='pty'> >> <target port='0'/> >> </serial> >> <console type='pty'> >> <target port='0'/> >> </console> >> <hostdev mode='subsystem' type='usb'> >> <source> >> <vendor id='0403'/> >> <product id='6001'/> >> </source> >> </hostdev> >> <input type='mouse' bus='ps2'/> >> <graphics type='vnc' port='-1' autoport='yes'/> >> <sound model='es1370'/> >> </devices> >> >> The USB device of interest to me is an FTDI FT232RL chip. When I plug >> the board into a USB port on the host, I want it to be passed through to >> my Ubuntu guest so that it can be seen as /dev/ttyUSB0. The guest >> doesn't see it. I took the product and vendor id numbers from the >> /var/log/messages output, and these might be in hexadecimal (and I >> should be writing e.g.<vendorid=0x0403'/>. I might also be getting the >> physical handling of the device wrong: maybe it needs to be already >> plugged in at the time the Ubuntu guest is started up, or maybe I should >> start the guest first and then plug in the device? >> >> Advice appreciated. >> >> Bob Cochran >> >> > > For future reference, easiest way to get device product + vendor info is > to use 'lsusb'. > > I think you need to use the hex format you mention above to get this to > work correctly (<vendor id='0x0403'/> ...). Also, make sure that the > <hostdev> device is still listed in the domain xml when you use 'virsh > dumpxml<domname>': this will guarantee that libvirt is at least > recognizing the new xml. > > You can also check /var/log/libvirt/qemu/<domname>.log to see what QEMU > command line libvirt is generating, which helps debugging these issues. > > - Cole > > > Cole, Thanks for your response. I modified the file /etc/libvirt/qemu/Ubuntu9.xml so that it looks like this: <domain type='kvm'> <name>Ubuntu9</name> <uuid>cb8c3d15-fe92-1bf2-5676-03370743e815</uuid> <memory>1572864</memory> <currentMemory>1572864</currentMemory> <vcpu>1</vcpu> <os> <type arch='x86_64' machine='pc'>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='cdrom'> <target dev='hdc' bus='ide'/> <readonly/> </disk> <disk type='file' device='disk'> <source file='/var/lib/libvirt/images/Ubuntu9.img'/> <target dev='vda' bus='virtio'/> </disk> <interface type='network'> <mac address='54:52:00:74:32:2f'/> <source network='default'/> <model type='virtio'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target port='0'/> </console> <hostdev mode='subsystem' type='usb'> <source> <vendor id='0x0403'/> <product id='0x6001'/> </source> </hostdev> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes'/> <sound model='es1370'/> </devices> </domain> My interest is getting the Ubuntu machine to recognize the FTDI device indicated in the <hostdev> entry you see above. I did not start the virtual machine or actually plug the USB device of interest into an available port at this point. Instead I ran 'virsh' as you suggested above. Here is the output: [root@deafeng3 qemu]# virsh dumpxml Ubuntu9 <domain type='kvm'> <name>Ubuntu9</name> <uuid>cb8c3d15-fe92-1bf2-5676-03370743e815</uuid> <memory>1572864</memory> <currentMemory>1572864</currentMemory> <vcpu>1</vcpu> <os> <type arch='x86_64' machine='pc'>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='cdrom'> <target dev='hdc' bus='ide'/> <readonly/> </disk> <disk type='file' device='disk'> <source file='/var/lib/libvirt/images/Ubuntu9.img'/> <target dev='vda' bus='virtio'/> </disk> <interface type='network'> <mac address='54:52:00:74:32:2f'/> <source network='default'/> <model type='virtio'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target port='0'/> </console> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes'/> <sound model='es1370'/> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0103'/> <product id='0x1771'/> </source> </hostdev> </devices> </domain> At this point, I plugged in the USB device I am interested in and again ran 'virsh', repeating the command above. Here is the output: [root@deafeng3 qemu]# virsh dumpxml Ubuntu9 <domain type='kvm'> <name>Ubuntu9</name> <uuid>cb8c3d15-fe92-1bf2-5676-03370743e815</uuid> <memory>1572864</memory> <currentMemory>1572864</currentMemory> <vcpu>1</vcpu> <os> <type arch='x86_64' machine='pc'>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='cdrom'> <target dev='hdc' bus='ide'/> <readonly/> </disk> <disk type='file' device='disk'> <source file='/var/lib/libvirt/images/Ubuntu9.img'/> <target dev='vda' bus='virtio'/> </disk> <interface type='network'> <mac address='54:52:00:74:32:2f'/> <source network='default'/> <model type='virtio'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target port='0'/> </console> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes'/> <sound model='es1370'/> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0103'/> <product id='0x1771'/> </source> </hostdev> </devices> </domain> I'm not sure what device 0103:1771 is. Here is the output of lsusb. Notice the device on bus 007 device 003. This is what I want the Ubuntu machine to see and manage. [root@deafeng3 qemu]# lsusb Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 006: ID 0c45:63f8 Microdia Bus 001 Device 011: ID 045e:0084 Microsoft Corp. Basic Optical Mouse Bus 001 Device 010: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard Bus 001 Device 009: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 012: ID 413c:8153 Dell Computer Corp. Bus 001 Device 013: ID 413c:8154 Dell Computer Corp. Bus 001 Device 003: ID 413c:2513 Dell Computer Corp. Bus 001 Device 008: ID 0a5c:4500 Broadcom Corp. Bus 001 Device 007: ID 413c:8149 Dell Computer Corp. Bus 001 Device 004: ID 413c:2513 Dell Computer Corp. Bus 001 Device 002: ID 0424:2512 Standard Microsystems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lastly, you wondered what command line qemu is using. I checked /var/log/libvirt/qemu and at the very start of the file I see this: LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/bin/qemu-kvm -S -M pc -m 1536 -smp 1 -name Ubuntu9 -uuid cb8c3d15-fe92-1bf2-5676-03370743e815 -monitor pty -pidfile /var/run/libvirt/qemu//Ubuntu9.pid -no-reboot -boot d -drive file=/home/rlc/Download/ubuntu-9.04-desktop-i386.iso,if=ide,media=cdrom,index=2 -drive file=/var/lib/libvirt/images/Ubuntu9.img,if=virtio,index=0 -net nic,macaddr=54:52:00:74:32:2f,vlan=0,model=virtio -net tap,fd=18,script=,vlan=0,ifname=vnet0 -serial pty -parallel none -usb -vnc 127.0.0.1:0 char device redirected to /dev/pts/1 char device redirected to /dev/pts/2 info cpus * CPU #0: pc=0x00000000000ffff0 thread_id=3476 cont balloon 1536 info balloon balloon: actual=1536 info balloon balloon: actual=1536 info balloon balloon: actual=1536 info balloon balloon: actual=1536 info balloon balloon: actual=1536 [above two lines repeat for a few thousand lines] Advice appreciated. How can I get the USB device to work? By the way, I thought I have an installed virtual machine on my hard drive, so I'm a little puzzled that the reference -drive file=/home/rlc/Download/ubuntu-9.04-desktop-i386.iso still exists in the qemu-kvm command line. Am I still starting up from the iso image? I'm confused. Bob

2 1

how to build iso from virt-p2v
by Arthur Wang 01 Jun '09

01 Jun '09

Hello, I have a trouble when build virt-p2v-0.9.9.tar.gz to generate an iso file. Search for help I have install all the packet that virt-p2v depend on, and i run the follow commands successfully configure make rpm But when i enter "make build" command, wait minutes, i got the follow error: Setting maximal mount count to -1 Setting interval between checks to 0 seconds Error creating Live CD : Unable to download from repo : Cannot retrieve repository metadata (repomd.xml) for repository: released. Please verify its path and try again make: *** [build] error 1 Could anyone tell me where it want to get repository metadata , and which tools or command it use to get? Arthur Wang Research Department, CPD Huawei Technologies Co., Ltd. Phone: 86-755-28976096 Email: wangjihai(a)huawei.com 2009-05-25

2 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

virt June 2009