similar to: Specify hard disk type (immutable) in the domain.xml file

Displaying 20 results from an estimated 90 matches similar to: "Specify hard disk type (immutable) in the domain.xml file"

2014 Oct 30
1
libvirt with VirtualBox - possible to specify path to snapshot folder in domain.xml?
Hi! I'm using libvirt withVirtual Box. I have installed libvirt 0.10.2 and Virtual Box 4.1.Is possible to spesify the pat to the folder I want my differencing image created in in my domain.xml file? When I define my vm (virsh domain.xml) with my domain.xml and use the readonly tag, Virual Box creates a differencing image (default in users Vitual Box VMs folder). I want to specify in my
2002 Feb 08
1
If the .journal file is marked 'immutable' how is data written to it
man chattr mentions the following [on RH 7.2] A file with the `i' attribute cannot be modified: it cannot be deleted or renamed, no link can be created to this file and no data can be written to the file. Only the superuser can set or clear this attribute The .journal file has the following properties ---i-d------- ../.journal As such, I am confused as to how data to the journal can
2011 Apr 26
0
Immutable ticks using ts.plot?
Hello all- ? What I'm going for here is a stack of four time series plots that use a common X axis on the bottom plot. And setting up customized tick marks on each plot that help illustrate the respective trends. Here's my code: ? #### Start #### fig_data <- ts(read.csv("F:/mydata.csv"), start=2000, end=2010, freq=1) opar = par() plot(fig_data, ann = FALSE, plot.type =
2017 Oct 01
0
Is ArrayRef supposed to be immutable?
It seems like ArrayRefs are supposed to be immutable ( However, as far as i can tell, the iterators are defined wrong to make this true. While ArrayRef<int> Foo(Something); Foo[0] = 5; will give a compile time error. something like: ArrayRef<int> Foo(Something); std::sort(Foo.begin(), Foo.end()); Will work fine. Is this expected? (FWIW: I expected this to only work with a
2012 Dec 05
1
[LLVMdev] Non-immutable alias analysis
Hi, I wrote a module pass that uses Alias Analysis. For this reason I added AU.addRequired<AliasAnalysis>() to function getAnalysisUsage and used getAnalysis<AliasAnalysis>() in my pass. I tried a few types of alias analyses and I discovered that only alias analyses which are ImmutablePasses are returned using getAnalysis<AliasAnalysis>(). Moreover, when I added both
2013 Jul 03
2
[LLVMdev] CallGraph in immutable pass
Hello, is there any way I can access CallGraph from immutable pass via getAnalysis? As I understand it, this may not be possible, because immutable pass don't have runOn method and is never actually planned. But I'm not 100% sure how this works, so I don't know if there is some other way. Thanks, Robert Barucak
2013 Jul 03
0
[LLVMdev] CallGraph in immutable pass
Your understanding is correct -- this is impossible. What are you really trying to do? On Jul 3, 2013 9:15 AM, "Robert Baručák" <xbaruc00 at stud.fit.vutbr.cz> wrote: > Hello, > is there any way I can access CallGraph from immutable pass via > getAnalysis? > As I understand it, this may not be possible, because immutable pass don't > have runOn method and is
2013 Jul 04
1
[LLVMdev] CallGraph in immutable pass
On 07/03/2013 06:18 PM, Chandler Carruth wrote: > > Your understanding is correct -- this is impossible. What are you > really trying to do? > I'm working on implementation of some fancier alias analysis algorithm. I have experienced strange behavior when I registered my AA (as module pass) into AA group. Somehow I was unable to get correct DataLayout from AA interface. So I
2013 Oct 09
0
[LLVMdev] Immutable Pass in Analysis Group
Hi The LLVM online document says that "There must be exactly one default implementation available at all times for an Analysis Group to be used. Only default implementation can derive from ImmutablePass. " http://llvm.org/docs/WritingAnLLVMPass.html#implementing-analysis-groups Is it still true that only the default implementation can derive from ImmutablePass, it does not seem to be
2016 Mar 11
1
virt-sysprep and immutable files
Greetings, I attempted to use virt-sysprep however it failed because the .ssh/authorized_keys file of a user had been (purposely) set immutable. Would this be considered a bug? An obvious work around would be not to clone vms with such files of course. Many thanks, Nick
2018 Sep 03
2
Immutable backing files
Hi list, suppose I have an immutable (ie: due to a read-only snapshot) backing file. After creating an overlay file with "qemu-img create -f qcow2 -o backing_file=/path/to/immutable/file.img current.qcow2", libvirt refuse to start the virtual machine and exits with an error stating "Could not open backing file /path/to/immutable/file.img: Permission denied". From my
2018 Sep 04
0
Re: Immutable backing files
Il 03-09-2018 13:14 Gionatan Danti ha scritto: > Hi list, > suppose I have an immutable (ie: due to a read-only snapshot) backing > file. > > After creating an overlay file with "qemu-img create -f qcow2 -o > backing_file=/path/to/immutable/file.img current.qcow2", libvirt > refuse to start the virtual machine and exits with an error stating > "Could not
2018 Sep 06
0
Re: Immutable backing files
Il 06-09-2018 12:54 Peter Krempa ha scritto: > You forgot to specify the format of the backing file into the overlay > file (qemu-img option -F). Libvirt treats any unspecified format as raw > since it's not secure to do probing of the format. Hi, the immutable base file *was* a raw image. Then a qcow2 overlay was added, but the vm (which accesses the overlay file) only boot if the
2018 Sep 07
1
Re: Immutable backing files
On Thu, Sep 06, 2018 at 18:23:46 +0200, Gionatan Danti wrote: > Il 06-09-2018 12:54 Peter Krempa ha scritto: > > You forgot to specify the format of the backing file into the overlay > > file (qemu-img option -F). Libvirt treats any unspecified format as raw > > since it's not secure to do probing of the format. > > Hi, the immutable base file *was* a raw image.
2006 Jan 31
1
Immutable Maildir (or: "I know drag&drop")
Hi, I'm 'constantly' (every odd month) faced with users happily dragging around or (un)subscribing folders in our shared IMAP account. Is there a "clean" way to prevent users from doing that when having a Maildir? Unix permissions probably won't cut the slack since setting any Maildir (sub)directory to readonly (immutable or chmod u-w ) will probably cause dovecot to
2013 Dec 15
0
[Bug 10325] New: Links to files marked schg (system immutable) fail
https://bugzilla.samba.org/show_bug.cgi?id=10325 Summary: Links to files marked schg (system immutable) fail Product: rsync Version: 3.1.0 Platform: x64 OS/Version: FreeBSD Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: rkoberman at
2018 Oct 24
0
Suggestion: Make CRAN source URLs immutable
>>>>> Kurt Wheeler writes: Try e.g. https://cran.r-project.org/package=httr&version=1.3.1 https://cran.r-project.org/package=httr&version=1.3.0 -k > Hello, I hope the is the right list to send this suggestion to. > I was wondering if it might be possible to have CRAN store the most current > version of a package's source tarball at a location that does not
2018 Nov 03
0
Suggestion: Make CRAN source URLs immutable
FWIW, you can get the URL and extract the link with extension from there. Archived packages are always tarballs, so that makes the following possible: url <- "https://cran.r-project.org/package=httr&version=1.3.0" library(RCurl) pkgurl <- gsub(".*(https://cran.+\\.tar.gz).*", "\\1", getURL(url)) install.packages(pkgurl, type
2018 Nov 03
1
Suggestion: Make CRAN source URLs immutable
On Sat, 3 Nov 2018 at 11:54, Joris Meys <jorismeys at gmail.com> wrote: > > FWIW, you can get the URL and extract the link with extension from there. Archived packages are always tarballs, so that makes the following possible: > > url <- "https://cran.r-project.org/package=httr&version=1.3.0" > > library(RCurl) > > pkgurl <-
2018 Sep 06
2
Re: Immutable backing files
On Tue, Sep 04, 2018 at 17:32:49 +0200, Gionatan Danti wrote: > Il 03-09-2018 13:14 Gionatan Danti ha scritto: > > Hi list, > > suppose I have an immutable (ie: due to a read-only snapshot) backing > > file. > > > > After creating an overlay file with "qemu-img create -f qcow2 -o > > backing_file=/path/to/immutable/file.img current.qcow2", libvirt