similar to: RHEL 7.x Guests Unable to Detect Any Storage Disks

Hi, I am trying to provide virtual USB disk devices to guests but without success. With QEMU is simple to plug the virtual USB disk with the command: (qemu) drive_add 0 id=my_usb_disk,if=none,file=usbdisk.img OK (qemu) device_add usb-storage,id=my_usb_disk,drive=my_usb_dis I can do this with libvirt? PK PS: sorry for my poor english -------------- next part -------------- An HTML

I'm wondering under what circumstances the kvm-clock source is exposed to a guest. I've got a bunch of KVM servers running Centos 5.5 and some of the guests have are defaulting to jiffies or apic whilst some are picking up kvm-clock. These guests are a mix of 32bit and 64bit Centos 5.5. Looking at the virtual machine definition file there doesn't appear to be a difference between the

Hi, I created an HVM type virtual machine and installed RHEL5U7 guest in it. I have assigned 7 scsi disks to the virtual machine in physical mode (using phy:), however, I see those disks are xvd and not as scsi. Is anyone aware what the problem might be ? Please let me know what kind of information do I need to post in order to narrow down to the problem. Thanks, K

Hello, Is it possible to share a single host's Logical Volume among multiple local KVM guests which mount it read-only? I'm asking this because I have an idea to run multiple idential KVM guests (they all have exactly the same software installed on them), booting them from a shared local Logical Volume read-only root file system, or alternatively let them share the bulk of the software

Does anyone know if 4k sectors will be handled better by the kernel in Centos6? I'd like to copy backups to a 750Gb laptop type drive for offsite storage but the best write speed I can get is about 8MB/sec even with dd to the raw disk which shouldn't have an issue with partition alignment. -- Les Mikesell lesmikesell at gmail.com

Currently virt-inspector takes ages to run on RHEL 3 guests. I tracked this down to processing the old-style initrd images in these guests. These initrd images are compressed ext2 filesystems. 'cpio' tries to parse them as cpio files, and takes a very long time to fail (and spews out a lot of errors in the process). These two patches fix the problem: Firstly we introduce a new command

RHEL 3 doesn't have a dynamic /dev. kmod-virtio creates devices nodes for vdX block devices based on what the major number of virtblk was at the time it was installed. This is, in turn, based on the order the modules were loaded in initrd. To try to preserve this precarious state of affairs, when adding virtio drivers to a new initrd we always load the same drivers as kmod-virtio in the same

-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -------------- next part -------------- >From c1a227a960066fb9552e0c225bc473be365b67b0 Mon Sep 17 00:00:00 2001 From: Richard W.M. Jones

On Mon, 2020-08-17 at 12:05 +0530, Anoop C S via samba wrote: > Hi all, > > This is to announce the availability of Samba(and CTDB) rpms from > Storage SIG[1] on CentOS 7 and 8. Visit Samba's CentOS wiki page[2] > for > more details on installation steps. > > [1] https://wiki.centos.org/SpecialInterestGroup/Storage > [2]

On Thu, 2020-08-20 at 20:04 +1200, Andrew Bartlett via samba wrote: > On Mon, 2020-08-17 at 12:05 +0530, Anoop C S via samba wrote: > > Hi all, > > > > This is to announce the availability of Samba(and CTDB) rpms from > > Storage SIG[1] on CentOS 7 and 8. Visit Samba's CentOS wiki page[2] > > for > > more details on installation steps. > > >

I have RHEL 7 Beta installed in dual boot with CentOS 6.x. Since RHEL 7 installed GRUB2, I had problem that RHEL 7 is default boot. My personal solution was to go to /etc/grub.d and run command: mv 10_linux 31_linux grub2-mkconfig -o /boot/grub2/grub.cfg Explanation: - /etc/grub.d is where grub2 writes down config files used to create boot menu. - OS-prober creates 30_os-prober file in

On Sat, Aug 15, 2020 at 15:38:19 -0700, Vjaceslavs Klimovs wrote: > Hey all, > With libvirt 6.5.0 and qemu 5.1.0 migration of non shared disks in > tunneled mode does not work for me: > > virsh # migrate alpinelinux3.8 qemu+tls://ratchet.lan/system --live > --persistent --undefinesource --copy-storage-all --tunneled --p2p > error: internal error: qemu unexpectedly closed the

On Mon, Aug 17, 2020 at 3:24 AM Peter Krempa <pkrempa@redhat.com> wrote: > > On Sat, Aug 15, 2020 at 15:38:19 -0700, Vjaceslavs Klimovs wrote: > > Hey all, > > With libvirt 6.5.0 and qemu 5.1.0 migration of non shared disks in > > tunneled mode does not work for me: > > > > virsh # migrate alpinelinux3.8 qemu+tls://ratchet.lan/system --live > >

On 12/10/2014 11:40 PM, Payes Anand wrote: > Hi, > Is it possible to freeze windows guests for a consistent storage level > snapshot. Yes, if you install qemu-guest-agent in the guest, and wire up your libvirt XML to have the guest-agent channel available. Once you have done that, use the --quiesce flag as part of creating your snapshots. > I was able to freeze Centos guests by

Hello, I'm managing smaller private virtualization infrastructure, currently based on CentOS 7.x. In the past we were running mostly on Debian 7 (kernel 3.2.x) and CentOS 6.x without problems. After we have upgraded to CentOS 7.x, I have experienced occasional physical host crashes when I did e.g. suspend or resume more virtual machines OR random virtual machine checkpoint was invalid and VM

Hi all, I have a strange problem when I use lvm disks to expose to virtual guests (host is CentOS 6.5 x86_64). If I remove a kvm guest and all lvm disks attached to it, and I create a new kvm with another lvm disks that use the same disk space previously assigned to the previous kvm guest, this new guest sees all partitions and data. Creating new lvm volumes with different names to this new kvm

Hi all, Recently I have acquired a supermicro e200-8d micro server to use it as my homelab. It is equipped with two ssd disks. My idea is to install several kvm guests on it, but I have some doubts about what type of filesystem (ext4 or xfs?) or block to use (lvm). Recommendations? Do I need to accomplish some type of running if I choose to use ext4 or xfs?? Thanks.

This series fixes an issue where disks of 1 TiB or more cannot be added to a xen guest. The problem lies in the xen backend driver using a 32 bit integer xenstore interface to write the number of sectors corresponding to the file or device that represents the virtual disk. The first patch adds 64 bit integer write functions to the xenstore interface. The second patch fixes the xen backend driver

-- Richard Jones, Virtualization Group, Red Hat http://people.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 -------------- next part -------------- >From f7806322c5173d392e1f22b99ea00d45083f3f42 Mon Sep 17

Hi, Is it possible to freeze windows guests for a consistent storage level snapshot. I am using openstack icehouse on centos 6.6 Hypervisor: KVM Libvirt: 0.10.2 Qemu: 0.10.2 Guest OS: Windows 7 and Windows Server 2008 I was able to freeze Centos guests by issuing the command: virsh qemu-agent-command <guest_ID> '{"execute":"guest-fsfreeze-freeze"}' For CentOS