search for: jolimont

...xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org Reporter: jerome at jolimont.fr QA Contact: xorg-team at lists.x.org Hi. Sometimes, my system freezes. No keyboard, no CTRL+Fx, altough I can REISUB. The mouse moves but the screen is frozen so it can't click anywhere. I tried to wait two or three minutes but nothing happens so I generally REISUB. Is there a po...

Le 2015-10-14 13:27, Jérôme a écrit : >> TRIM is needed to indicate that space is reclaimable. This needs file >> system support (no fat32, e.g.), and support by QEMU('s I/O driver). >> Once Qemu is set up to accept TRIM, you can either enable the discard >> mount option, or set up an fstrim cron job. Thanks. I read stuff about that and it's becoming clearer now.

Hi all. I'm having issues while creating snapshots. I posted on Stack Exchange [1], but figured I might get more success here. My VM backup script fails while creating the snapshot. virsh snapshot-create-as --domain machine_1 snap --diskspec vda,file=/srv/test/test-snap.qcow2 --disk-only --atomic --no-metadata --quiesce error: Requested operation is not valid: domain is

Le Thu, 24 Sep 2015 05:32:45 +0800, Bill Kenworthy <billk@iinet.net.au> a écrit : > Look into the "panic" option to ntpd - once the gap gets to big (such > as when the VM is suspended for a few hours) it goes into freewheel > and doesn't sync - its in the ntp docs. My use case is when rebooting the host (after a kernel update, for instance). The gap is about 2

Hi. Thanks for answering. Le 2015-09-23 17:34, Dominique Ramaekers a écrit : > Linux has two methods to use ntp: > > ntpdate: > It will run once at boot time to sync time. (This is probably > installed on your system) > It will not run after suspend and resume... => no correction Nope. This is not installed on my system. > ntpd: > Continuously adjusts time. The

Le 2015-10-14 12:09, Sven Schwedas a écrit : > On 2015-10-14 11:34, Jérôme wrote: > >> In other words, can I have this on a 60Go drive? >> total 53G >> 7,4G -rw------- 1 root root 11G oct. 8 06:34 prod_151008.qcow2 >> 7,4G -rw------- 1 root root 11G oct. 9 06:37 prod_151009.qcow2 >> 7,5G -rw------- 1 root root 11G oct. 10 06:41 prod_151010.qcow2 >>

Hi all. When resuming guest after suspend, the time is wrong (because the guest doesn't know it has been suspended). Apparently, ntp running on the guest doesn't solve this. At least on Linux system. I read it works on Windows guests. I don't understand why, so I'd appreciate a link to an explanation, but I understand it is out of scope for this list. The HW clock is correct and

Hi Eric. Thank you so much for your quick and relieving answer. Le 2015-09-11 17:05, Eric Blake a écrit : > Yes, using active block-commit is the ideal way to perform a live backup. Great. > Yep, that about covers it. Note that the --quiesce step in snapshot > creation requires qemu-guest-agent running in the guest, and that you > trust interaction with your guest. Yes, I think

Hi. I'm following here a conversation that was initiated on Kashyap's website [1]. We have a server we use as a host for virtual machines using KVM (virt-manager used for VM creation) and we would like to setup VM backups. Basically, we're thinking of a backup schedule like "keep 7 daily and 4 weekly backups". We'd rather not shutdown the VM every day so live backups

Hi all. I have a few questions regarding the qcow2 format. 1/ Allocated size vs. file size When creating a VM, I indicated a size of 10 G. $ls -lsh 7,7G -rw------- 1 libvirt-qemu libvirt-qemu 11G oct. 14 10:04 prod.qcow2 The allocated size is lesser than max size. Alright. I think I more or less grab the difference between allocated size and file size, but I'm not sure I get the point