Thanks. Strange, after all the keywords I searched for today, after your email
I looked up 'kvm-qemu config' and found exactly the explanation I needed here:
"Converting from QEMU args to domain XML" http://libvirt.org/drvqemu.html
-Original Message-
From: libvirt-users-boun...@redhat.
On 03/04/2011 01:47 PM, Markiewicz, Patrick F (N-No Laurels) wrote:
Hi,
Can virsh be used to connect to a standalone KVM? I.e. I started a
KVM from the command line, and I wondered how to connect to it. Virsh
list shows no VMs. Thanks.
No. libvirt (and consequently virsh) only knows ab
Hi,
Can virsh be used to connect to a standalone KVM? I.e. I started a KVM from
the command line, and I wondered how to connect to it. Virsh list shows no
VMs. Thanks.
Patrick
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redh
Hi!
Is there any progress on issue mentioned in [1]? I mean the issue when
xml file has VM type as openvz but 'virsh dumpxml ' returns domain
type qemu. I still have issue in libvirt-0.8.8.
BR,
Nikolay.
[1] http://osdir.com/ml/libvir-list/2009-07/msg00635.html
_
Hi!
In [1] it's written that "Then a generic configuration file
/etc/vz/vznetctl.conf must be created containing [...]" whereas it has
to be /etc/vz/vznet.conf since /usr/sbin/vznetcfg script has the
following line
VZNETCFG='/etc/vz/vznet.conf'
vzctl version is 3.0.26-1.
Best regards,
Nikol
sorry, I forgot to mention a vzctl version which is 3.0.26-1.
kna...@gmail.com wrote on 04/03/11 21:10:
Hi!
Is there any way to specify ethernet device name to be created inside
the openvz container?
I could find such info at
http://libvirt.org/formatdomain.html#elementsNICS.
If I do as below I
Hi!
Is there any way to specify ethernet device name to be created inside
the openvz container?
I could find such info at http://libvirt.org/formatdomain.html#elementsNICS.
If I do as below I get br0 as ethernet device inside VM whereas I'd like
it to be eth0.
$ cat ovz.xml
144
0071c128
2011/3/4 Hereward Cooper :
> [...]
>> 400 means bad request. You probably have a character in you password
>> that needs to be escaped in XML: <, >, &, ', "
>>
>> libvirt currently doesn't escape the password properly when building
>> the SOAP request. You can manually workaround this by entering t
[...]
> 400 means bad request. You probably have a character in you password
> that needs to be escaped in XML: <, >, &, ', "
>
> libvirt currently doesn't escape the password properly when building
> the SOAP request. You can manually workaround this by entering the
> password in escaped form. Fo