search for: testvm2

...hat i don''t have any file in the location "/var/lib/xen" [root@globushead xen]# pwd /var/lib/xen [root@globushead xen]# ls -ll total 0 Further i tested the command "xm save " and results as follows Terminal 1: xm save -c TestVM1 TestVM1.chkpt Terminal 2 : xm save -c TestVM2 TestVM2.chkpt & issued command simultaneously.. I could able to get those checkpoint files as follows & no error has occured.. [root@globushead ~]# ls -ll TestVM* -rwxr-xr-x 1 root root 134508135 Jul 29 09:05 TestVM1.chkpt -rwxr-xr-x 1 root root 134508135 Jul 29 09:05 TestVM2.chkpt I h...

...ose file-based image for storage of the VM, it seems to be set up to use file: backend/driver with loopback-mounted image file: > > <disk type='file' device='disk'> > <driver name='file'/> > <source file='/var/lib/libvirt/images/testvm2.img'/> > <backingStore/> > <target dev='hda' bus='ide'/> > </disk> > > # losetup -a > /dev/loop0: [fd00]:1709109 (/var/lib/libvirt/images/testvm2.img) > > With earlier versions of rpms similar setup used blktap2 backen...

...for storage of the VM, it seems to be set up to use file: backend/driver with loopback-mounted image file: > > > > <disk type='file' device='disk'> > > <driver name='file'/> > > <source file='/var/lib/libvirt/images/testvm2.img'/> > > <backingStore/> > > <target dev='hda' bus='ide'/> > > </disk> > > > > # losetup -a > > /dev/loop0: [fd00]:1709109 (/var/lib/libvirt/images/testvm2.img) > > > > With earlier versions o...

...arts prompting me for all the things I already have specified in the kickstart. Any idea what I could be doing wrong? Here is the command im using to get things started: virt-install --hvm --location=http://mirrors.liquidweb.com/CentOS/5.2/os/x86_64 --noautoconsole --file=/dev/XenVol/XenVE2 --name=testvm2 --ram=512 --network bridge:xenbr1 --vnc -x "ks=http://blah.com/client_work/kickstart.txt ip=67.xx.xx.xx netmask=255.255.xxx.0 dns=208.67.222.222 gateway=67.xxx.xxx.x" Note: I did modify the kickstart to use "hda" for partitioning versus "xvda". Thanks, Mark _______...

...rt-manager, and choose file-based image for storage of the VM, it seems to be set up to use file: backend/driver with loopback-mounted image file: <disk type='file' device='disk'> <driver name='file'/> <source file='/var/lib/libvirt/images/testvm2.img'/> <backingStore/> <target dev='hda' bus='ide'/> </disk> # losetup -a /dev/loop0: [fd00]:1709109 (/var/lib/libvirt/images/testvm2.img) With earlier versions of rpms similar setup used blktap2 backend.. (and yes, I do have blktap module...

...of the VM, it seems to be set up to use file: backend/driver with loopback-mounted image file: >>> >>> <disk type='file' device='disk'> >>> <driver name='file'/> >>> <source file='/var/lib/libvirt/images/testvm2.img'/> >>> <backingStore/> >>> <target dev='hda' bus='ide'/> >>> </disk> >>> >>> # losetup -a >>> /dev/loop0: [fd00]:1709109 (/var/lib/libvirt/images/testvm2.img) >>> >>>...

...snap1.qcow2 [. . .] ><fs> run ><fs> mount /dev/sda1 / ><fs> ls / bar baz jazz lost+found ><fs> Now, let's do a live blockcopy (with a '--finish' to graecully finish the mirroring): $ virsh blockcopy --domain testvm2 vda \ /export/dst/copy.qcow2 \ --wait --verbose --finish Examine the contents of the above 'copy': $ guestfish --ro -a copy.qcow2 [. . .] ><fs> run ><fs> mount /dev/sda1 / ><fs> ls / bar baz jazz lost+found...

Hello, I just upgraded some of my el6xen boxes to latest CentOS 6.7, Xen 4.4.3 and dom0 3.18.17 rpms, and noticed these new problems: 1) virt-manager fails to start with an error: "D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory" And indeed.. there was no such file. Running

...;fs> mount /dev/sda1 / > ><fs> ls / > bar > baz > jazz > lost+found > ><fs> > > Now, let's do a live blockcopy (with a '--finish' to graecully finish > the mirroring): > > $ virsh blockcopy --domain testvm2 vda \ > /export/dst/copy.qcow2 \ > --wait --verbose --finish > > > Examine the contents of the above 'copy': > > $ guestfish --ro -a copy.qcow2 > [. . .] > ><fs> run > ><fs> mount /dev/sda1 / > &gt...

...Forgot to note: Before blockcopy, the current block device is snap1.qcow2 (after too, it's the same, since we didn't `--pivot` to the copy. > Now, let's do a live blockcopy (with a '--finish' to graecully finish > the mirroring): > > $ virsh blockcopy --domain testvm2 vda \ > /export/dst/copy.qcow2 \ > --wait --verbose --finish > > > Examine the contents of the above 'copy': > > $ guestfish --ro -a copy.qcow2 > [. . .] > ><fs> run > ><fs> mount /dev/sda1 / > >&l...

...simple chain: > > base <- snap1 > > Let's quickly examine the contents of 'base' and 'snap1' images: > > Now, let's do a live blockcopy (with a '--finish' to graecully finish > the mirroring): > > $ virsh blockcopy --domain testvm2 vda \ > /export/dst/copy.qcow2 \ > --wait --verbose --finish This defaults to a full copy (copy.qcow2 will contain everything in the latest state of the original chain, but with no backing file). > > If I'm reading the man page of 'blockcopy' correctly, s...