similar to: How to device port on the controller

Hi, Look under examples: http://builder.virt-tools.org/artifacts/libvirt-virshcmdref/html/sect-attach-disk.html (root at h2)-(/)# virsh attach-disk vps_99 /dev/nbd2 vdb --address pci:0000.00.11.0 --persistent *error: command 'attach-disk' doesn't support option --address* (root at h2)-(/)# virsh --version 0.7.5 Is someone playing a trick on me? Regards, Daniele -------------- next

On 01/08/2015 12:44 PM, Gary R Hook wrote: > I've learned how to use the blockcopy command to create a local copy in > a simple disk file: > > virsh dumpxml my_domain > my_domain.xml > virsh undefine my_domain > virsh blockcopy --domain my_domain vda $PWD/dsk.copy.qcow2 --wait > --verbose --finish > virsh define my_domain.xml > > and the resulting copy in

On Wed, Mar 01, 2017 at 07:28:46PM +0100, Viktor Mihajlovski wrote: > On 01.03.2017 16:58, Daniel P. Berrange wrote: > > given a basic Fedora 25 guest, with a virtio-mmio disk added as per the > > guide above... > > > > looking at device '/devices/platform/a003e00.virtio_mmio/virtio3/block/vda': > > KERNEL=="vda" > >

On Wed, Mar 01, 2017 at 07:28:46PM +0100, Viktor Mihajlovski wrote: > On 01.03.2017 16:58, Daniel P. Berrange wrote: > > given a basic Fedora 25 guest, with a virtio-mmio disk added as per the > > guide above... > > > > looking at device '/devices/platform/a003e00.virtio_mmio/virtio3/block/vda': > > KERNEL=="vda" > >

On Sun, Sep 28, 2014 at 6:48 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Sun, Sep 28, 2014 at 06:33:53PM +0800, Zhi Yong Wu wrote: >> On Sun, Sep 28, 2014 at 6:26 PM, Richard W.M. Jones <rjones@redhat.com> wrote: >> > Which version of libguestfs is this? I think you'll have no hope of >> #rpm -qa | grep libguestfs >> libguestfs-1.20.8-1

On Wed, Mar 01, 2017 at 04:02:53PM +0100, Viktor Mihajlovski wrote: > On 01.03.2017 04:30, Zbigniew J?drzejewski-Szmek wrote: > > On Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote: > >>>>>> One could argue about back-level compatibility, but virtio by-path > >>>>>> naming has changed multiple times. We have seen

On Wed, Mar 01, 2017 at 04:02:53PM +0100, Viktor Mihajlovski wrote: > On 01.03.2017 04:30, Zbigniew J?drzejewski-Szmek wrote: > > On Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote: > >>>>>> One could argue about back-level compatibility, but virtio by-path > >>>>>> naming has changed multiple times. We have seen

On 01.03.2017 19:44, Daniel P. Berrange wrote: [...] replying on the list, a bit lengthy > > Ok, my guest has 4 disks > > - sda - virtio-scsi, over virtio-pci transport > - sdb - virtio-scsi, over virtio-mmio transport > - vda - virtio-scsi, over virtio-pci transport > - vdb - virtio-scsi, over virtio-mmio transport > > with systemd 231 I get these links >

On Thu, Jan 08, 2015 at 01:44:58PM -0600, Gary R Hook wrote: > On 12/24/14 4:42 AM, Kashyap Chamarthy wrote: > >On Tue, Dec 23, 2014 at 12:38:57PM -0600, Gary R Hook wrote: > > > >[. . .] > > > >In my case, the block device is a QCOW2 disk image file. If I boot > >without using the disk image file which has the operating system, the > >domain will fail

On Sun, Sep 28, 2014 at 11:04:11PM +0800, Zhi Yong Wu wrote: > On Sun, Sep 28, 2014 at 6:48 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > > On Sun, Sep 28, 2014 at 06:33:53PM +0800, Zhi Yong Wu wrote: > >> On Sun, Sep 28, 2014 at 6:26 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > >> > Which version of libguestfs is this? I think you'll

Thank you for your help! 1, i used vda as install disk and vdb as target disk, because i boot from the first. After setup boot order flag i was able change install disk to vdb and target disk to vda. With this configuration when i boot from vdb i can install OS with grub and after it redefine XML without vdb without problem. Thanks a lot. 2, maybe i have something wrong, but still not working:

Hi, I'm trying to create a snapshot on a specific disk by using diskspec option. However, libvirt/virsh seems to ignore it and takes a snapshot of all disks. Am I using this option incorrectly? In below examples, I'm trying to snapshot only vdb. However even vda is getting snapshotted regardless of diskspec. Is this a known issue? I'm on CentOS 7.1, libvirtd (libvirt) 1.2.8, virsh

On Sun, Sep 28, 2014 at 11:31 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Sun, Sep 28, 2014 at 11:04:11PM +0800, Zhi Yong Wu wrote: >> On Sun, Sep 28, 2014 at 6:48 PM, Richard W.M. Jones <rjones@redhat.com> wrote: >> > On Sun, Sep 28, 2014 at 06:33:53PM +0800, Zhi Yong Wu wrote: >> >> On Sun, Sep 28, 2014 at 6:26 PM, Richard W.M. Jones

Dear all, Please let me start by indicating that I am not from a technical background, so please be gentle and patient with me. I am trying to get a snapshot from my virtual machines (vm) and the following command works for all of them bar one: # virsh snapshot-create-as --quiesce --no-metadata --domain myvm myvm-state --diskspec vda,file=overlay.qcow2 --disk-only --atomic The only exception is

REPRODUCIBLE EXAMPLE: With the R.rsp package installed, the following search, which gives a hit: options(help_type = "html") help.search("rsp") generates: Error in if (nchar(Outfile)) Outfile else File : argument is not interpretable as logical in the browser (e.g. http://127.0.0.1:30410/doc/html/Search?results=1). Another example is

Hi, I am having 2 issues with disks and KVM. ISSUE 1: I am unable to detach a disk from a running KVM. (root at h2)-(/tmp)# virsh dumpxml vps_99 <domain type='kvm' id='224'> <name>vps_99</name> <uuid>5e24e17c-f0e4-1030-ac57-0050560018a2</uuid> <memory>524288</memory> <currentMemory>524288</currentMemory>

I hate intermittent problems ... Most of the time, my domUs launch just fine. But, occasionally I get a failure to connect a vdb or vif and the domU fails to completely launch ("xm list" shows it is present but no console activity either through "xm create -c" or through "xm console"). The log shows a stack trace in DevController.py in the area of waiting for

I hate intermittent problems ... Most of the time, my domUs launch just fine. But, occasionally I get a failure to connect a vdb or vif and the domU fails to completely launch ("xm list" shows it is present but no console activity either through "xm create -c" or through "xm console"). The log shows a stack trace in DevController.py in the area of waiting for

This commit documents the limits on export name, encoding, etc. --- generator/generator | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/generator/generator b/generator/generator index a72f36c..87a8cdf 100755 --- a/generator/generator +++ b/generator/generator @@ -1066,10 +1066,16 @@ C<\"nbd2\">, etc."; longdesc = "\ For servers

I''ve had a go at determining exactly what happens when you create a filesystem without enough devices to meet the requested replication strategy: # mkfs.btrfs -m raid1 -d raid1 /dev/vdb # mount /dev/vdb /mnt # btrfs fi df /mnt Data: total=8.00MB, used=0.00 System, DUP: total=8.00MB, used=4.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=153.56MB, used=24.00KB Metadata: