;t really sure how to put
together a Maven repo and rely on the community to help us out. If you
have instructions on how to generate the pom correctly then we would
appreciate that and could incorporate that into future releases.
--
Doug Goldstein
___
l
gt; 5. Try to start your guest with virsh
>>
>>
>> Now send us the much more verbose logfile that was created
>
> Dennis has already knew what's wrong with his environment,
> his kernel doesn't support securityfs. libvirt should handle this problem.
>
Its 6807238d that made securityfs required on the host kernel when
userns isn't used.
--
Doug Goldstein
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
ake sure that you have all the necessary
kernel options enabled. You can check with: ebuild
/usr/portage/app-emulation/libvirt/libvirt-1.1.2-r1.ebuild setup clean
--
Doug Goldstein
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
; Note: I am not a government employee and have no authority to obligate
> any federal, state or local government to perform any action or
> payment.FC949ES
>
> _______
> libvirt-users mailing list
> libvirt-users@redhat.com
> https://www.redhat.com/m
__
> libvirt-users mailing list
> libvirt-users@redhat.com
> https://www.redhat.com/**mailman/listinfo/libvirt-users<https://www.redhat.com/mailman/listinfo/libvirt-users>
>
You'll get the same error with all drivers connecting to 'session' on Mac
OS X for some reason.
t) implementation. It does not support
UNIX sockets which is a requirement of libvirt when using the
qemu+ssh:// scheme to connect.
I'd suggest looking into generating some certificates and using
qemu+tls:// (the default when using qemu:// to a remote system). If
you don't care about an
stara ~ # virsh --version
> 1.0.3
virsh version --daemon would check that the daemon is 1.0.3 as well
and not just the client.
>
> ostara ~ # uname -a
> Linux ostara 3.7.10-gentoo #1 SMP PREEMPT Tue Mar 5 15:23:39 CST 2013
> x86_64 Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz Ge
kvm_intel loaded? Best place to start is checking
/var/log/libvirt/libvirtd.log
--
Doug Goldstein
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
>
> It looks like I have been bitten by the above bug.
>
> What version of libvirt will these patches appear in? eg, is there a
> way to map a git commit to a future release?
>
Its worth noting that the commit you referenced was par
e issue and I already asked him to
try the patch you mentioned. I was going to do my best to try and
follow up soon with another idea but for reference the bug is here:
https://bugs.gentoo.org/show_bug.cgi?id=451584
--
Doug Goldstein
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
On Wed, Jan 30, 2013 at 1:21 AM, Wayne Sun wrote:
> On 01/30/2013 01:25 PM, Doug Goldstein wrote:
>>
>> On Mon, Jan 28, 2013 at 10:23 AM, Osier Yang wrote:
>>>
>>> On 2013年01月29日 00:17, Doug Goldstein wrote:
>>>>
>>>> On Sun, Jan 27, 2013
On Mon, Jan 28, 2013 at 10:23 AM, Osier Yang wrote:
> On 2013年01月29日 00:17, Doug Goldstein wrote:
>>
>> On Sun, Jan 27, 2013 at 10:46 PM, Osier Yang wrote:
>>>
>>> On 2013年01月28日 11:47, Osier Yang wrote:
>>>>
>>>>
>>>> On 201
On Sun, Jan 27, 2013 at 10:46 PM, Osier Yang wrote:
> On 2013年01月28日 11:47, Osier Yang wrote:
>>
>> On 2013年01月28日 11:44, Osier Yang wrote:
>>>
>>> On 2013年01月26日 01:07, Doug Goldstein wrote:
>>>>
>>>> On Thu, Jan 24, 2013 at 12:58 AM,
On Thu, Jan 24, 2013 at 12:58 AM, Osier Yang wrote:
> On 2013年01月24日 14:26, Doug Goldstein wrote:
>>
>> On Wed, Jan 23, 2013 at 11:02 PM, Osier Yang wrote:
>>>
>>> On 2013年01月24日 12:11, Doug Goldstein wrote:
>>>>
>>>>
>&g
On Wed, Jan 23, 2013 at 11:02 PM, Osier Yang wrote:
> On 2013年01月24日 12:11, Doug Goldstein wrote:
>>
>> On Wed, Jan 23, 2013 at 3:45 PM, Doug Goldstein wrote:
>>>
>>> I am using libvirt 0.10.2.2 and qemu-kvm 1.2.2 (qemu-kvm 1.2.0 + qemu
>>> 1.2.2 applied
On Wed, Jan 23, 2013 at 3:45 PM, Doug Goldstein wrote:
> I am using libvirt 0.10.2.2 and qemu-kvm 1.2.2 (qemu-kvm 1.2.0 + qemu
> 1.2.2 applied on top plus a number of stability patches). Having issue
> where my VMs fail to start with the following message:
>
> kvm_init_vcpu
pc-0.13
pc-0.12
pc-0.11
pc-0.10
isapc
none
Any suggestions are appreciated.
--
Doug Goldstein
___
libvirt-users mailing list
libvirt-users@redhat.com
ht
t; _______
> libvirt-users mailing list
> libvirt-users@redhat.com
> https://www.redhat.com/mailman/listinfo/libvirt-users
Your /usr/bin/kvm symlink is bad. It's pointing to
/usr/bin/qemu-x86_64, instead of /usr/bin/qemu-system-x86_64.
--
Doug Goldstein
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
roup CPU pinning patch caused problems for some people.
--
Doug Goldstein
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
#x27;ve commented on the bug. But for what its worth, I see this as well
but the delay comes from the fact that I have a number of storage
pools marked as autostart. The solution^H^H^H^Hhack was to unmark them
from autostart and make an init script which started up all of my
storage pools. Now I can restart libvirt as often as I like with a
fairly linear with relation to VMs delay.
--
Doug Goldstein
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
On Jun 15, 2012, at 10:35 PM, "Xing.x.Gao" wrote:
> 2012/6/15 Xing.x.Gao :
>> 2012/6/15 Anthony Bourguignon :
>>> Le vendredi 15 juin 2012 à 14:29 +0800, Xing.x.Gao a écrit :
Hello,
when i use virsh to reboot a guest,it report a "unsupported
configuration: Reboot is not supported
takes a
virDomain object while libvirt.virConnect.createXML() takes an xmldesc.
$ python
>>> import libvirt
>>> conn = libvirt.open("qemu:///system")
>>> dom = conn.lookupByName("my-machine")
>>> dom.create()
Should do the trick.
--
Doug
nality that I had
configured, while still having a tty available to connect through via
virsh console. Basically does libvirt have the ability to multiplex
the output from qemu's serial port in any way?
--
Doug Goldstein
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
them debug an issue.
However, if you need to connect to the console of the VM its
impossible (e.g. it needs the root password for a fsck).
Any suggestions to allow logging but allow it to be usable via "virsh
console" as well?
Thanks.
--
end ?no_tty=1 to the end of your URI that you pass
to open() or openReadOnly().
For more info see the docs here:
http://libvirt.org/remote.html#Remote_URI_parameters
--
Doug Goldstein
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
he VM let's say. This requires a full privilege
connection, rather than opening a new connection I was hoping to
upgrade the existing one to a full privilege connection.
Just confirming that's not possible.
--
Doug Goldstein
___
libvirt-u
omainPtr
> i am not sure on how to print the domain object features in python, such as
> name, disk size, etc
Use python's built in help.
$ python
>>> import libvirt
>>> help (libvirt.virDomain)
--
Doug Goldstein
___
27 matches
Mail list logo
