Skip to main content

utilisation de virsh et virt-install

Mon utilisation

Cette entrée me sert plutot de bloc-note pour ne pas perdre de vue mes commandes usuelles de manipulation de machines virtuelles

Voir si une machine virtuelle existe

 sudo virsh --connect qemu:///system list --all 

Définir une machine virtuelle à partir d'un xml

 sudo virsh --connect qemu:///system define le-fichier.xml 

Dump XML de la conf d'une machine virtuelle

 sudo virsh --connect qemu:///system dumpxml centos6-01 

Démarrer une machine virtuelle

 sudo virsh --connect qemu:///system start centos6-01 

Installer une machine virtuelle

 sudo virt-install --connect qemu:///system --name fedora-16-64-01 \
--ram 1024 --keymap=fr \
--cdrom=/media/500G/ISO/Fedora-16/Fedora-16-x86_64-Live-LXDE.iso --os-type=linux \
--os-variant=fedora16 --network=network:default --vnc --accelerate \
--force --disk path=/mnt/big/mihamina/Virtual/fedora-16-64-01,size=10G

Se connecter à une machine virtuelle en VNC

 sudo virt-viewer --connect qemu:///system fedora-16-64-01 

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo&

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: https://issues.jenkins-ci.org/browse/JENKINS-57495 Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM

Emacs TypeScript Development

Emacs Configuration for Typescript In order to comfortably develop on Node, React or Angular projects with Emacs, TIDE is a good solution. We have TypeScript code highlight (that is the minimum!) and code completion based on the codebase (not only on locally defined and builtins) In order to achieve that: Install Emacs (24+) Install Node Install Typescript (which will provide "tsserver") Install TIDE and some usefull dependencies Configure Emacs to use all those Node is then installed in " /home/mihamina/Apps/node-v12.18.0-linux-x64/bin ": you should add it to your PATH. Installing Typescript is done with: npm install --save typescript @types/browserify After that, "tsserver" will be in " /home/mihamina/node_modules/.bin " Then comes the installation of TIDE: With the Emacs package manager, M-x package-install , install "tide". Do the same for "web-mode", "flycheck", "company" "js2-mode" and "