similar to: Re: VM running with storage image file deleted

On 10.01.19 11:19, Roosen, Nicolas wrote: > Hello, I have a strange issue I'd like to have some insights on. > > > We have 2 running VM, the storage pool is over NFS. Unfortunately, the backend storage folder has been deleted (so the image file in it as well, obviously) ... > > > Yet, the 2 VM are still up and running, with their root filesystem being mounted

Hi! I need to convert a KVM virtual machine from LVM to a qcow2 image, and wonder if this is the best way to do it (*1): [$] qemu-img convert -O qcow2 /dev/vg_name/lv_name/ /var/lib/libvirt/images/image_name.qcow2 If this is the best way to do this, will this keep the information on: /dev/vg_name/lv_name/ untouched? Thanks, and please point me towards another mailing list if this it not right

Dear all, I'm having a problem with debugger() in both R 2.8.0 and R 2.12.0. Probably also versions in-between. I don't see it logged in the bug database, but it's hard for me to imagine that no-one else has encountered it. So my question is whether it's a known problem with a workaround, or do I log it as a new problem? The situation is that if I use

Hi, Is there someone on this mailing list who could/want help me figure out this issue? We do not know where to look to solve this. --- Description --- This is a brand new server, which has been tested for days with FreeBSD in our office, and a few days with Windows on the site of our hardware distributor. Now customer wants CentOS, which we installed, but after few days we get a kernel panic.

Dear R-users, I've enhanced the "xtable" package, adding numerous features that have been requested by users. The changes are listed below. The objective throughout has been to avoid any breaking changes. However, as "xtable" is widely used and is a dependency of many packages I'd like to have others try it out before I post it to CRAN. Both bug reports and design

BaselR - The new R meeting We are pleased to announce the new R meeting to be held in Basel, Switzerland. BaselR will be held from 6:30-9:30pm on Tues, Apr 27 at TransBARent: http://transbarent.business.sv-group.ch Doors open at 6:30,pm with the presentations starting at 7:00pm Introduction: What is Basel R? Andreas Krause:... Graphing Pharma Data Yann Abraham: Graphics Charles Roosen: Web

I am searching for directions for using live block migration to copy running vm's to a different storage pool. Example: VM1 running on Host1, the image(s) for VM1 are stored in /var/lib/libvirt/images. I'd like to copy the disk image(s) that VM1 is using to /nfs/images. Without stopping/pausing/powering down the VM. Do you have any examples or documentation of how to accomplish this

I created a new LVM type storage pool on my server and would like to move my VM disk volumes in a directory-based pool into this new pool. But I cannot figure out how that is done. I find plenty of information on how to migrate live VM images from one host to another, but not on how to just move one live from one storage pool to another on the same host. If it cannot be done live, how an I

My fame package has a function that checks to see if a FAME SERVER process is already running. On Linux, I can do this in one of two ways: pid <- Sys.getpid() user <- Sys.info()["user"] cmd <- paste("pgrep -fU", user, "-P", pid, "'FAME SERVER'") fameRunning <- as.logical(length(system(cmd, intern = T))) or I can use cmd

My question is this: If you have an ongoing blockcopy (drive-mirror) of a running transient VM, and the VM kernel panics, can you restart the VM without interrupting the ongoing blockcopy? A virsh reboot won't work since if the VM is kernel panicked, its not going to respond to ACPI requests.

Hello, I'm seeking the solution to live storage migration using blockcopy. Previously, the "virsh undefine" is required before blockcopy. https://www.redhat.com/archives/libvirt-users/2015-October/msg00027.html QEMU has "block-dirty-bitmap-*" operations now, are there steps for the live storage migration using blockcopy without undefine? By the way, why's the purpose

Thank you Eric, On 2014-02-05 17:23, Eric Blake wrote: > Yes, live storage migration is possible; although at the moment, qemu is > lacking a way to restart the operation if it fails midstream, so libvirt > only allows the operation if you are willing to temporarily make your > guest transient. What does this mean? Will I loose anything if - for example - there is not enough space on

Hello, I have two servers where I can push VMs from one to the other by issuing the command virsh migrate --live --persistent --copy-storage-all --verbose \ test6 qemu+ssh://kvmhost2/system on kvmhost1. I can get the VM back by issuing the equivalent command on kvmhost2: virsh migrate --live --persistent --copy-storage-all --verbose \ test6 qemu+ssh://kvmhost1/system virsh

I have a script that runs as a cron job every minute (on Ubuntu 10.10 and R 2.11.1), querying a database for new data. Most of the time it takes a few seconds to run, but once in while it takes more than a minute and the next run starts (on the same data) before the previous one has finished. In extreme cases this will fill up memory with a large number of runs of the same script on the same data.

On 2015-04-08, Leon Fauster <leonfauster at googlemail.com> wrote: > Am 08.04.2015 um 16:22 schrieb Liam O'Toole > <liam.p.otoole at gmail.com>: >> On 2015-04-08, David Both >> <dboth at millennium-technology.com> >> wrote: >>> The easy way to restart gdm is when you are on the login screen >>> itself or the desktop simply press

Hi, I've recently taken over maintenance for the "xtable" package, and have set it up on R-Forge. At the moment I'm pondering what the best way is to handle submitted patches. Basically, is it better to: 1) Be non-restrictive regarding committer status, let individuals change the code with minimal pre-commit review, and figure changes can be reviewed before

We are using following dtrace script to analyze an application. However we see different number of lwp_yield and yield calls reported depending on whether we trace mutex_lock or mutex_unlock or not. The number reported when we are not tracing mutex_lock or mutex_unlock is higher. What could be going on here and which one is the correct number. This is on S10 U2. Thanks, Rao.

Hello, I am running qemu-kvm 1.4.0 and libvirt 1.0.2 on Ubuntu 12.04. I have two NFS mountpoints configured as two separate pools in virsh: <pool type='dir'> <name>nfs1</name> <uuid>419d799c-2493-6ebc-6848-53b0919e7bad</uuid> <capacity unit='bytes'>6836057014272</capacity> <allocation unit='bytes'>0</allocation>

On 02/20/2017 09:10 PM, Michal Privoznik wrote: > On 17.02.2017 17:18, Yunchih Chen wrote: >> `virsh list` hangs on my server that hosts a bunch of VMs. >> This might be due to the Debian upgrade I did on Feb 15, which upgrades >> `libvirt` from 2.4.0-1 to 3.0.0-2. >> I have tried restarting libvirtd for a few times, without luck. >> >> Attached below are