- openSUSE Virtual

[opensuse-virtual] iSCSI en Virtualbox
by marcelo 19 May '14

19 May '14

Hi! I was trying to use iSCSI on Virtualbox. This is the configuration of my /etc/ietd.conf Target iqn.test.2014:3a4408cc-9918-4904-8cd2-00d307f03bdf Lun 0 Path=/varios/01/discotest,Type=fileio Lun 1 Path=/varios/01/otrotest,Type=fileio and the I added this lines to attach de iSCSI to my vm. VBoxManage storageattach iSCSI-test --storagectl "SATA" --port 1 --device 0 --type hdd --medium iscsi --server 10.202.10.18 --target "iqn.test.2014:3a4408cc-9918-4904-8cd2-00d307f03bdf" --tport 3260 --lun 0 VBoxManage storageattach iSCSI-test --storagectl "SATA" --port 2 --device 0 --type hdd --medium iscsi --server 10.202.10.18 --target "iqn.test.2014:3a4408cc-9918-4904-8cd2-00d307f03bdf" --tport 3260 --lun 1 when I start the vm I try to format the disk /dev/sdb (one of the iSCSI). in the vm nothing happens but in the iSCSI server (arlene) 2014-05-16T21:22:59.169220-03:00 arlene kernel: [ 5123.066498] iscsi_trgt: check_segment_length(1896) data too long 2 65536 8192 then the iSCSI get's readonly... what can I do or where can I find some info about it? regards -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

3 2

[opensuse-virtual] VirtualBox windows-7 guest?
by Thomas Taylor 14 Apr '14

14 Apr '14

I need to re-install Windows-7 (Professional) due to changing the motherboard/CPU on my desktop system. I currently dual boot with OS 13.1 & Win-7. This creates a difficulty as currently I have windows installed on sdb and re-map using Grub. If I let windows install itself it will use sda which is where openSUSE is loaded thereby over-writing it. What type of guest container would make a good choice for installing windows and why? This will be my first use of VB so don't know if a physical partition or a virtual one would work better. I've read the VB users guide but don't understand some of the methods regarding guest accounts. Would the type of guest affect things like internet access or port (serial/USB) utilization? This is for my personal computer and has no vital programs or data involved. The current OS 13.1 is backed up to 2 different devices and could be restored if problems develop. Thanks, Tom -- The foolish man seeks happiness in the distance. The wise man grows it under his feet. - James Oppenheim ^^ --... ...-- / -.- --. --... -.-. ..-. -.-. ^^^^ Tom Taylor KG7CFC openSUSE 13.1 (64-bit), Kernel 3.11.6-4-default, KDE 4.11.2, AMD Phenom X4 955, GeForce GTX 550 Ti (Nvidia 325.15) 16GB RAM -- 3x1.5TB sata2 -- 128GB-SSD FF 27.0, claws-mail 3.9.2 registered linux user 263467 -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

3 2

[opensuse-virtual] libvirtd, qemu+ssh and polkit: internal error: received hangup / error event on socket?
by Johannes Kastl 01 Apr '14

01 Apr '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, maybe this is an old issue, but I am just starting to set up my machines with libvirt and qemu-kvm, and tried using a remote connection. I already changed the following lines in libvirtd.conf: unix_sock_group = "libvirt" unix_sock_rw_perms = "0770" auth_unix_rw = "none" I made my user a member of said group 'libvirt'. And I restarted both libvirtd and polkit. I can connect as local user via virsh -c qemu:///sytem without a password prompt. I can also ssh into the remote host with my ssh key without problems. Trying from another machine (say hostname HOSTX, username testuser) with virsh -c qemu+ssh://testusers@HOSTX/system always results in > error: failed to connect to the hypervisor error: internal error: > received hangup / error event on socket I found not much information on this error, so I need your help. /var/log/messages says: > 2014-03-24T21:25:55.023525+01:00 HOSTX sshd[3509]: Accepted > publickey for testuser from 192.168.79.8 port 54176 ssh2 > 2014-03-24T21:25:55.024744+01:00 HOSTX sshd[3509]: > pam_unix(sshd:session): session opened for user testuser by > (uid=0) 2014-03-24T21:25:55.025717+01:00 HOSTX kernel: [ > 3162.225673] type=1006 audit(1395692755.024:69): pid=3509 uid=0 old > auid=4294967295 new auid=1000 old ses=4294967295 new ses=24 res=1 > 2014-03-24T21:25:55.027501+01:00 HOSTX systemd[1]: Starting Session > 24 of user testuser. 2014-03-24T21:25:55.027918+01:00 HOSTX > systemd-logind[703]: New session 24 of user testuser. > 2014-03-24T21:25:55.028213+01:00 HOSTX systemd[1]: Started Session > 24 of user testuser. 2014-03-24T21:25:55.081719+01:00 HOSTX > sshd[3511]: Received disconnect from 192.168.79.8: 11: disconnected > by user 2014-03-24T21:25:55.082095+01:00 HOSTX sshd[3509]: > pam_unix(sshd:session): session closed for user testuser > 2014-03-24T21:25:55.086268+01:00 HOSTX systemd-logind[703]: Removed > session 24. I am curious about the "disconnected by user" line, but I could not figure out what causes this line. I tried adding the libvirt rules to /etc/polkit-default-privs.local and all kinds of javascript stuff to /etc/polkit-1/rules.d/, but to no avail. Is configuring polkit necessary anymore? I am using Tumbleweed, which means libvirt* is 1.1.2-2.18.3.x86_64 and polkit is polkit-0.112-2.1.x86_64. Regards, Johannes - -- Osama bin Laden might wish to destroy America, but America is too big for him; he cannot do it. Bush may really do it. (Richard M. Stallman) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlMwmlcACgkQzi3gQ/xETbJrggCffwnL4SvZeTWKqMXKX5/wiq9a +SgAnRAJogyyyA2equDI6EyRz0GPwIW/ =9WvP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 3

[opensuse-virtual] Win-7 in VirtualBox guest
by Thomas Taylor 29 Mar '14

29 Mar '14

I have windows-7 installed on a physical partition on one of my hard drives. How mat I run this under VirtualBox version 4.3.8-110.9? How is the physical partition mounted in VB? System info below. Thanks, Tom -- The foolish man seeks happiness in the distance. The wise man grows it under his feet. - James Oppenheim ^^ --... ...-- / -.- --. --... -.-. ..-. -.-. ^^^^ Tom Taylor KG7CFC openSUSE 13.1 (64-bit), Kernel 3.11.6-4-default, KDE 4.11.2, AMD Phenom X4 955, GeForce GTX 550 Ti (Nvidia 325.15) 16GB RAM -- 3x1.5TB sata2 -- 128GB-SSD FF 27.0, claws-mail 3.9.2 registered linux user 263467 -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 1

[opensuse-virtual] Opensuse xen kernel not working on IBM x3550M4 7914
by Jeroen Groenewegen van der Weyden 27 Mar '14

27 Mar '14

Hello, Currently we are trying to install a xen machine on a IBM x 3550M4 7914 machine Without any succes. We try to get xen running with opensuse 12.3 or opensuse 13.1 Installing opensuse is no problem, the default ( desktop ) kernel is working ok. when we install the xen-kernel and xen packages openSuse 13.1 -> booting the xen kernel makes the machine freeze and does not react at all. openSuse 12.3 -> booting the xen kernel makes - the keyboard/mouse inresponsive - the video also seems to hang ( only distorted bitmap can be seen on screen ) - However with openSuse 12.3 networking is working and console login is possible - I can not identify from the logs the specific error. - additionally lsusb gives the output "unable to initialize libusb: -99" Anybody any idea where to start trouble shooting? BR, Jeroen xm dmesg __ __ _ _ ____ _____ ___ _ _ ____ ____ _ _ \ \/ /___ _ __ | || | |___ \ |___ / / _ \/ | / | |___ \|___ \ | || | \ // _ \ '_ \ | || |_ __) | |_ \ | | | | |__| | __) | __) || || |_ / \ __/ | | | |__ _| / __/ _ ___) | | |_| | |__| |_ / __/ / __/ |__ _| /_/\_\___|_| |_| |_|(_)_____(_)____/___\___/|_| |_(_)_____|_____(_) |_| |_____| (XEN) Xen version 4.2.3_01-1.22.4 (abuild@) (gcc (SUSE Linux) 4.7.2 20130108 [gcc-4_7-branch revision 195012]) Mon Dec 2 12:22:01 UTC 2013 (XEN) Latest ChangeSet: 26064 (XEN) Bootloader: GRUB2 2.00 (XEN) Command line: (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) Disc information: (XEN) Found 0 MBR signatures (XEN) Found 0 EDD information structures (XEN) Multiboot-e820 RAM map: (XEN) 0000000000000000 - 000000000006c000 (usable) (XEN) 000000000006c000 - 000000000006d000 (ACPI NVS) (XEN) 000000000006d000 - 000000000009f000 (usable) (XEN) 000000000009f000 - 00000000000a0000 (ACPI NVS) (XEN) 0000000000100000 - 000000006895f000 (usable) (XEN) 000000006895f000 - 0000000068960000 (ACPI data) (XEN) 0000000068960000 - 000000006a15f000 (usable) (XEN) 000000006a15f000 - 000000006a164000 (reserved) (XEN) 000000006a164000 - 000000006a641000 (usable) (XEN) 000000006a641000 - 000000006a645000 (ACPI data) (XEN) 000000006a645000 - 000000006a647000 (usable) (XEN) 000000006a647000 - 000000006a648000 (ACPI data) (XEN) 000000006a648000 - 000000006a662000 (usable) (XEN) 000000006a662000 - 000000006a66a000 (ACPI data) (XEN) 000000006a66a000 - 000000006a672000 (usable) (XEN) 000000006a672000 - 000000006a674000 (ACPI data) (XEN) 000000006a674000 - 000000006a675000 (usable) (XEN) 000000006a675000 - 000000006a679000 (ACPI data) (XEN) 000000006a679000 - 000000006a81c000 (usable) (XEN) 000000006a81c000 - 000000006a821000 (ACPI data) (XEN) 000000006a821000 - 000000006a822000 (reserved) (XEN) 000000006a822000 - 000000006a999000 (usable) (XEN) 000000006a999000 - 000000006a99a000 (reserved) (XEN) 000000006a99a000 - 000000006a99c000 (ACPI data) (XEN) 000000006a99c000 - 000000006b1f9000 (usable) (XEN) 000000006b1f9000 - 000000006b1fa000 (ACPI data) (XEN) 000000006b1fa000 - 000000006b44f000 (usable) (XEN) 000000006b44f000 - 000000006b450000 (ACPI data) (XEN) 000000006b450000 - 000000007d971000 (usable) (XEN) 000000007d971000 - 000000007d97e000 (reserved) (XEN) 000000007d97e000 - 000000007e395000 (usable) (XEN) 000000007e395000 - 000000007e751000 (reserved) (XEN) 000000007e751000 - 000000007ebb4000 (ACPI NVS) (XEN) 000000007ebb4000 - 000000007ec02000 (usable) (XEN) 0000000080000000 - 0000000090000000 (reserved) (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) (XEN) 00000000ff800000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000280000000 (usable) (XEN) ACPI Error (tbxfroot-0218): A valid RSDP was not found [20070126] (XEN) System RAM: 8163MB (8359232kB) (XEN) Domain heap initialised (XEN) Found and enabled local APIC! (XEN) Not enabling x2APIC: depends on iommu_supports_eim. (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2100.028 MHz processor. (XEN) Initing memory sharing. (XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7 (XEN) I/O virtualisation disabled (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) Platform timer is 1.193MHz PIT (XEN) Allocated console ring of 16 KiB. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) - Unrestricted Guest (XEN) - APIC Register Virtualization (XEN) - Virtual Interrupt Delivery (XEN) - Posted Interrupt Processing (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB (XEN) Brought up 1 CPUs (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0x2000 -> 0xa65000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000274000000->0000000275000000 (2013714 pages to be allocated) (XEN) Init. ramdisk: 000000027c1cb000->000000027ffff200 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff80002000->ffffffff80a65000 (XEN) Init. ramdisk: 0000000000000000->0000000000000000 (XEN) Phys-Mach map: ffffea0000000000->ffffea0000f84238 (XEN) Start info: ffffffff80a65000->ffffffff80a654b4 (XEN) Page tables: ffffffff80a66000->ffffffff80a6f000 (XEN) Boot stack: ffffffff80a6f000->ffffffff80a70000 (XEN) TOTAL: ffffffff80000000->ffffffff80c00000 (XEN) ENTRY ADDRESS: ffffffff80002000 (XEN) Dom0 has maximum 1 VCPUs (XEN) Platform timer appears to have unexpectedly wrapped 1 times. (XEN) Scrubbing Free RAM: .done. (XEN) Initial low memory virq threshold set at 0x4000 pages. (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) Freed 252kB init memory.

2 3

[opensuse-virtual] Xl usb-attach in opensuse 13.1
by Jeroen Groenewegen van der Weyden 12 Feb '14

12 Feb '14

Hello, I updated my machines recently from opensuse 12.3 to 13.1. Which made us switch from xm to xl. However there is no command available for xl to attach on usb device to a running domain. In other words, does anyone know what the xl variant is of the old xm usb-add/usb-del command? BR, Jeroen. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

3 6

[opensuse-virtual] Proposed KVM related packaging changes
by Bruce Rogers 10 Feb '14

10 Feb '14

All, I proposed making some KVM related packaging changes. Motivation: Certain aspects of KVM support have changed over time, and we should adjust to better align to the current state of affairs. Among these are: - the KVM modules have been included with the base kernel for quite some time - there is no longer a qemu / qemu-kvm code split upstream qemu handles KVM completely - on x86, since v3.7 the KVM kernel modules are auto loaded based on detection of the required hardware virtualization features Our current kvm package originally included the KVM kernel modules, as well as the QEMU binaries which supported KVM acceleration. As noted above conditions have changed to where a kvm package has little of its original purpose. The qemu package now has the basic support for using KVM, and about the only meaningful use of a kvm package would be for KVM related configuration or deliverables which would not be appropriate (for whatever reason) in the qemu package. The current content of the kvm package in OBS Virtualization includes: - dependency on qemu package - a recommends for virt-utils - the legacy qemu-kvm executable, which is simply a wrapper for the QEMU provided executable with the parameter added that enables KVM acceleration. I believe this wrapper still provides the useful feature of having an executable name, compatible with prior kvm enabled usage. - man page for qemu-kvm (which maps to qemu) - a udev rule to change permissions and group ownership of /dev/kvm to be compatible with current libvirt usage as well as non-libvirt based (ie QEMU command line) kvm group administration. - a qemu-ifup script which I find useful for testing and creating simple usage scenarios - a kvm_stat tool which allows for monitoring of the lower level KVM module activities of the running KVM guests - in the case of the SLES version of the kvm package, a place for additional modprobing, and support documentation, which in effect, rounds out the complete base support for KVM. I propose that we rename (essentially) the kvm package to be qemu-kvm. This is partly to reduce the number of maintained packages, as I envision this simply being a subpackage of qemu. This will also make versioning simpler to maintain. This package will maintain a dependency on qemu. I propose that the permissions and group ownership udev rule be moved from qemu-kvm to the base qemu package so that libvirt and etc. can function without the qemu-kvm package, providing for a slightly smaller package set and simpler configuration. I propose that the recommends dependency for virt-utils be removed. If the additional features and documentation still remaining in qemu-kvm (the qemu-kvm wrapper and man page, the sample qemu-ifup script, the kvm_stat debug utility, possible scripts for modprobing of additional kernel modules which enhance qemu-kvm usage (eg vhost-net), and the support documentation) are desired, then that package may be installed, but it is not considered essential for basic KVM support. The virt-utils package currently provides little value. It was envisioned as a place to collect generic utilities useful for either KVM or Xen virtualization, but to date very little has been done there. QEMU based utilities are now in qemu-tools, and the only utility in virt-utils is the unmaintained vm-snapshot-disk. I propose that we eliminate this package, but if there is objection, and someone relies on the vm-snapshot-disk feature, we can keep it, but not have it be part of the default set of rpms installed by KVM Host Server pattern. If there are dependencies on the kvm package name which will take time to remove, we could have that stripped down package simply require qemu-kvm in the interim. Comments on these proposed changes are of course welcome. Thanks, Bruce Rogers

1 0

Re: [opensuse-virtual] Status of USB redirection in Qemu-KVM?
by Wilfred van Velzen 10 Feb '14

10 Feb '14

Is this: http://forums.opensuse.org/showthread.php/494758-VM-won-t-start-when-added-… The same problem? >>>On 2014-02-07 at 15:26, Bjoern Voigt <bjoernv(a)arcor.de> wrote: > Hello all, > > I like know, how is the status of USB redirection for Qemu-KVM in > openSUSE (Virtualization repository)? > > For me and probably for many other users it is a nice feature to > give virtualization guests direct access to USB devices of the > host system. > > I did some tests with the following results: > > * USB redirection does not work at all using Qemu-KVM 1.7.0 from > Virtualization repository > * After building my own version of Qemu-KVM 1.7.0 with libusb >= > 1.0.18 from "hardware" repository and activation of libusb > using "configure --enable-libusb" in qemu.spec I had some success. > > The following worked: > > * USB redirection with static assignment of an USB device worked > with Windows XP as a guest. I tested with an USB mass storage > device. From my "windowsxp" libvirt configuration: > <hostdev mode='subsystem' type='usb' managed='yes'> > <source> > <vendor id='0x2237'/> > <product id='0x4193'/> > </source> > </hostdev> > > But I also had some problems: > > * The same configuration did not worked with a Windows 8 guest. > The error in Windows 8.1 device manager was, that the USB > device could not be started. > * USB redirection at runtime with "Spicy" didn't worked with > Windows XP and Windows 8. Spicy offered the redirection in a > dialog, but the guests did not see the redirected devices. > Permission problems can not be the reason, because I also > tried Spicy with root access. Windows XP also has the Spice > driver installed. > > My questions: > > Are there plans to add USB redirection support for Qemu-KVM? For > reference and testing I made a repository here: > > http://download.opensuse.org/repositories/home:/bjoernv:/branches:/Virtualiz > ation/openSUSE_13.1/home: bjoernv:branches:Virtualization.repo > > Are there ideas how to resolve the remaining problems? > > Greetings, > Björn -- Met vriendelijke groet / Best regards, Wilfred van Velzen -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 0

[opensuse-virtual] QCOW2 resizing magic explained
by Rob Verduijn 07 Feb '14

07 Feb '14

QCOW2 resizing magic explained Hello all, I don't know about you but Ipersonally have been rather irritated about the fact that in the past you could not shrink a qcow2 image online while the virtual machine was running. I've found that this is already possible for some time and actually rather simple to do. Now don't get your hopes up to high there's still a few drawbacks that you will have to deal and live with (for now). The first drawback being that unless you already use a (virtio-)scsi device you will need to reinstall your vm or migrate your vm-images to (virtio-)scsi, depending on your config you should decide which is the least hassle. >From now on to keep the virt-install commands readable I will use a couple variables containing values that are always the same and of no influence on the resizing of the images. Another requirement is that you have a running kvm setup with a bridge. BRIDGE=br0 CDISO=/path/to/installation.iso STORAGEDIR=/var/lib/libvirt/images DISKIMAGE=$STORAGEDIR/disk.qcow2 STDOPTS="--name=testmachine --ram=1024 --vcpus=1 --os-type=linux --os-variant=opensuse12" STDOPTS="$STDOPTS --network bridge=$BRIDGE --disk $CDISO,device=cdrom" So the first requirement is to create a virtual machine with a scsi or virtio-scsi controller. Issue the following commandto create a vm using a scsi disk image virt-install $STDOPTS \ --disk $DISKIMAGE,bus=scsi Issue the following command to creat a vm with a virtio-scsi disk. (add the Virtualization repo if you want this in opensuse) virt-install $STDOPTS \ --disk $DISKIMAGE,format=qcow2,size=16,bus=scsi \ --controller scsi,model=virtio-scsi Now choose the installation of your personal liking and wait for it to complete. Once the machine is done you need to change a few entries in the fstab. In my example I have created an installation using an lvm partition schema. My opensuse installation produced the following fstab: /dev/system/swap swap swap defaults 0 0 /dev/system/root / ext4 acl,user_xattr 1 1 /dev/disk/by-id/scsi-0QEMU_QEMU_HARDDISK_drive-scsi0-0-0-0-part1 /boot ext4 acl,user_xattr 1 2 /dev/system/home /home ext4 acl,user_xattr 1 2 The discard option must be added to all filesystems that support it. /dev/system/swap swap swap defaults 0 0 /dev/system/root / ext4 discard,acl,user_xattr 1 1 /dev/disk/by-id/scsi-0QEMU_QEMU_HARDDISK_drive-scsi0-0-0-0-part1 /boot ext4 discard,acl,user_xattr 1 2 /dev/system/home /home ext4 discard,acl,user_xattr 1 2 Save and close the fstab Now since I've used an lvm based partition schema I need to explain to lvm to use the discard option. Edit /etc/lvm/lvm.conf find the line that says : issue_discards = 0 and change it to : issue_discards = 1 save and close the file We have almost reached our goal. Shut down the vm Edit the virtual machine settings with virsh. virsh edit testmachine and find the entry for your harddisk. Mine looks like this : <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/var/lib/libvirt/images/disk.qcow2'/> <target dev='sda' bus='scsi'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> add the discard=unmap option to line 2 : <disk type='file' device='disk'> <driver name='qemu' type='qcow2' discard='unmap'/> <source file='/var/lib/libvirt/images/disk.qcow2'/> <target dev='sda' bus='scsi'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> save and close the file check the file size of the disk image ls -als /var/lib/libvirt/images/disk.qcow2 1222792 -rw------- 1 root root 1252261888 Feb 7 15:14 /var/lib/libvirt/images/disk.qcow2 start the vm log in as root on the vm and create a big file dd if=/dev/urandom of=/bigfile count=1024k bs=1k sync check the file size of the disk image ls -als /var/lib/libvirt/images/disk.qcow2 2271560 -rw------- 1 qemu qemu 2327248896 Feb 7 15:24 /var/lib/libvirt/images/disk.qcow2 delete the bigfile from the vm rm /bigfile sync and check the file of the disk image again ls -als /var/lib/libvirt/images/disk.qcow2 1222984 -rw------- 1 qemu qemu 2327248896 Feb 7 15:27 /var/lib/libvirt/images/disk.qcow2 Notice the first number has shrunk back to a smaller size, the second is still big. This is normal behaviour, the image is sparse therefore it claims to be already 2.2G while it only consumes 1.2G on the hd. You now have a virtual disk image that automatically shrinks and grows depending on the usage. But wait, I said there were multiple drawbacks and I've named only one yet. So here are the others. You might have already deduced that this causes fragmentation of the images on your drive. This is one of the drawbacks that you will have to live with. Next there is the performance impact from doing this, but there is a solution to this. You can do the discarding manually, or in a cronjob at a time that pleases you. To do the manual discards, remove the discard option from the /etc/fstab. If you use lvm leave it in /etc/lvm/lvm.conf. Now simply issue in the vm: fstrim <mountpoint> In my example this would be fstrim / fstrim /home fstrim /boot And for the last catch, older kernels do not pass the discard option properly when using qcow2 images. rhel6.5 and lower don't support this, I haven't tested this in sles11 yet. However they do support it on raw images (as do the newer kernels). You will just have to live with the fact that your snapshots of those systems do not support discarding. Well that is all there is to it Oh p.s. on a side note and completely unrelated to this subject. Did you know there has been a new qcow release ? Probably not since it has been done rather quietly. Check http://wiki.qemu.org/Features/Qcow3 But what would you care, and I would say performance. So to add a nice finishing touch to the vm creation using qcow3...errr I mean qcow2 compat=1.1 mode (I'm so happy they took care not to confuse people) issue the following two commands : qemu-img create -f qcow2 -o preallocation=metadata,lazy_refcounts=on,compat=1.1 \ $DISKIMAGE 16G virt-install $STDOPTS \ --disk $DISKIMAGE,bus=scsi --controller scsi,model=virtio-scsi If you want to check what qcow version an image is, you will need a hex editor to look at the first eight bytes of the qcow image. Byte number eight will be a three when using qcow3 and a two for qcow2. Glad to see they made it easy to tell the difference....<cough> <cough> Enjoy your new fully dynamic qcow image resizing. Rob Verduijn -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

1 0

[opensuse-virtual] Status of USB redirection in Qemu-KVM?
by Bjoern Voigt 07 Feb '14

07 Feb '14

Hello all, I like know, how is the status of USB redirection for Qemu-KVM in openSUSE (Virtualization repository)? For me and probably for many other users it is a nice feature to give virtualization guests direct access to USB devices of the host system. I did some tests with the following results: * USB redirection does not work at all using Qemu-KVM 1.7.0 from Virtualization repository * After building my own version of Qemu-KVM 1.7.0 with libusb >= 1.0.18 from "hardware" repository and activation of libusb using "configure --enable-libusb" in qemu.spec I had some success. The following worked: * USB redirection with static assignment of an USB device worked with Windows XP as a guest. I tested with an USB mass storage device. From my "windowsxp" libvirt configuration: <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x2237'/> <product id='0x4193'/> </source> </hostdev> But I also had some problems: * The same configuration did not worked with a Windows 8 guest. The error in Windows 8.1 device manager was, that the USB device could not be started. * USB redirection at runtime with "Spicy" didn't worked with Windows XP and Windows 8. Spicy offered the redirection in a dialog, but the guests did not see the redirected devices. Permission problems can not be the reason, because I also tried Spicy with root access. Windows XP also has the Spice driver installed. My questions: Are there plans to add USB redirection support for Qemu-KVM? For reference and testing I made a repository here: http://download.opensuse.org/repositories/home:/bjoernv:/branches:/Virtuali… Are there ideas how to resolve the remaining problems? Greetings, Björn -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-virtual+owner(a)opensuse.org

2 1