On 01.06.2015 15:47, Cole Robinson wrote:
> On 06/01/2015 07:00 AM, poma wrote:
>>
>> Applicability of the changes in configuration is broken, at least to some
>> extent.
>>
>> e.g.
>> Controller USB - USB2 to USB3 and vice versa,
>> etc.
>>
>> $ rpm -q virt-manager
>> virt-manager-1.2.0-1.fc22.no
On 06/01/2015 07:00 AM, poma wrote:
>
> Applicability of the changes in configuration is broken, at least to some
> extent.
>
> e.g.
> Controller USB - USB2 to USB3 and vice versa,
> etc.
>
> $ rpm -q virt-manager
> virt-manager-1.2.0-1.fc22.noarch
> $ rpm -q virt-manager
> virt-manager-1.2.0-1
Applicability of the changes in configuration is broken, at least to some
extent.
e.g.
Controller USB - USB2 to USB3 and vice versa,
etc.
$ rpm -q virt-manager
virt-manager-1.2.0-1.fc22.noarch
$ rpm -q virt-manager
virt-manager-1.2.0-1.fc23.noarch
However it is resolved upstream.
Tested with
Hi,
I am working on resolving an issue with virt-manager on FreeBSD. A
contributor recently worked on getting spice-gtk ported to FreeBSD,
however I am working on this error when launching console.py.
[helfman@its-helfman03 ~/workspace/ports/deskutils/virt-manager]$ python
/usr/local/share/virt-
On 08/19/2011 01:27 PM, Jason Helfman wrote:
Hi,
I am getting this error when I run virt-manager in FreeBSD:
[Fri, 19 Aug 2011 09:32:14 virt-manager 24762] DEBUG (engine:555) No
inspection thread because libguestfs is too old, not available, or libvirt
is not thread safe.
libguestfs isn't port
Hi,
I am getting this error when I run virt-manager in FreeBSD:
[Fri, 19 Aug 2011 09:32:14 virt-manager 24762] DEBUG (engine:555) No
inspection thread because libguestfs is too old, not available, or libvirt
is not thread safe.
libguestfs isn't ported to FreeBSD, however I was wondering about t
On Mon, 2010-01-25 at 15:33 -0800, C.J. Adams-Collier wrote:
> On Mon, 2010-01-18 at 13:46 -0800, C.J. Adams-Collier wrote:
> > Hey Dan, list,
> >
> > It seems to me that virt-manager could do with more information about
> > the virtual network devices, the DHCP leases on them, maybe a view of
>
On Mon, 2010-01-18 at 13:46 -0800, C.J. Adams-Collier wrote:
> Hey Dan, list,
>
> It seems to me that virt-manager could do with more information about
> the virtual network devices, the DHCP leases on them, maybe a view of
> the arp table, etc.
>
> To this end, I've abused Dan's .glade file a
Hey Dan, list,
It seems to me that virt-manager could do with more information about
the virtual network devices, the DHCP leases on them, maybe a view of
the arp table, etc.
To this end, I've abused Dan's .glade file a bit and put some stub code
in virtManger/host.py
Could I get some comments a
Apologies if this has been already discussed.
While using virt-manager to create a vm-guest we see the following errors being
logged in /var/log/messages.
libvirtd: 22:40:57.675: error : Domain not found: no domain with matching name
'guest1'
libvirtd: 22:42:22.039: error : invalid storage volu
On Sat, Aug 01, 2009 at 12:13:42PM -0400, Michael Zeller wrote:
> okay so using virt-manager it only lists my root partition as storage, or
> atleast thats what it appears
> So it says I can only make a vm the size of 9G when my home partition has
> 800+G
> is there a way to change that?
You'll pr
okay so using virt-manager it only lists my root partition as storage, or
atleast thats what it appears
So it says I can only make a vm the size of 9G when my home partition has
800+G
is there a way to change that?
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/li
On Tue, May 05, 2009 at 02:40:54PM -0500, mike.h...@yr20.com wrote:
>
> Now comes the philosophy piece: It seems like that the way that
> libvirt and virt-manager want to handle storage is to be able to
> fully control the mounting process. That seems to me to be a
> very nice thing as you ha
I had originally posted a plea for help on the virt-manager related list, but
the same issue exists with virsh and this list seems to have higher traffic.
I'd been chatting on the irc channel with various people about this, but wanted
to put this on the mail list for the record and to also rais
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel P. Berrange wrote:
> On Mon, Feb 23, 2009 at 05:46:36PM -0500, Daniel J Walsh wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Daniel P. Berrange wrote:
>>> On Tue, Feb 17, 2009 at 04:52:08PM -0500, Daniel J Walsh wrote:
---
On Mon, Feb 23, 2009 at 05:46:36PM -0500, Daniel J Walsh wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Daniel P. Berrange wrote:
> > On Tue, Feb 17, 2009 at 04:52:08PM -0500, Daniel J Walsh wrote:
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA1
> >>
> >> Looks like qemu laun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel P. Berrange wrote:
> On Tue, Feb 17, 2009 at 04:52:08PM -0500, Daniel J Walsh wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Looks like qemu launched from libvirt wants to create pulseaudito files
>> under /root/.pulse director
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel P. Berrange wrote:
> On Tue, Feb 17, 2009 at 04:52:08PM -0500, Daniel J Walsh wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Looks like qemu launched from libvirt wants to create pulseaudito files
>> under /root/.pulse director
On Tue, Feb 17, 2009 at 04:52:08PM -0500, Daniel J Walsh wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Looks like qemu launched from libvirt wants to create pulseaudito files
> under /root/.pulse directory.
Hmm, that sounds bad - it should not do this.
> Seems strange, and we migh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Looks like qemu launched from libvirt wants to create pulseaudito files
under /root/.pulse directory.
Seems strange, and we might want to consider changing the homedir for
each qemu launched by libvirt.
/var/run/libvirt/qemu/DOMAIN
for example.
It
Hi!
This is my first post to either of these list, I have been lurking, (sorry to
cross post but I don't know if this is a virt-manager or libvirt question). So
first off thank you to everyone for all your efforts. I think libvirt and
virt-manager are excellent! I've built a pair of server
Hi Claes
It should be posted on virt-manager mailing list.
"et-mgmt-tools at redhat.com"
Thanks
Atsushi SAKAI
ClaesBas <[EMAIL PROTECTED]> wrote:
> If you have ssh moved/hidden somewhere else then port 22 this patch
> makes it possible to open the vnc/console.
> I have to add the entry from co
If you have ssh moved/hidden somewhere else then port 22 this patch
makes it possible to open the vnc/console.
I have to add the entry from commandline like this:
virt-manager -c qemu+ssh://[EMAIL PROTECTED]:2/system
If ssh is running on port 2.
I've also submitet this on bugzilla:
https:/
On Mon, 2007-02-26 at 00:07 +0100, Karel Zak wrote:
> On Sun, Feb 25, 2007 at 08:48:12PM +, Daniel P. Berrange wrote:
> > See this thread on kvm-devel for a question about link time dependancies
> > in libvirt. I'm not sure what the optimal approach is for us to deal with
> > this is - just som
On Sun, 2007-02-25 at 20:48 +, Daniel P. Berrange wrote:
> See this thread on kvm-devel for a question about link time dependancies
> in libvirt. I'm not sure what the optimal approach is for us to deal with
> this is - just something we should think about in an idle moment...
The driv
On Sun, Feb 25, 2007 at 08:48:12PM +, Daniel P. Berrange wrote:
> See this thread on kvm-devel for a question about link time dependancies
> in libvirt. I'm not sure what the optimal approach is for us to deal with
> this is - just something we should think about in an idle moment...
Definite
Date: Sun, 25 Feb 2007 18:48:44 +0200
> From: Avi Kivity <[EMAIL PROTECTED]>
> To: "Daniel P. Berrange" <[EMAIL PROTECTED]>
> CC: kvm-devel@lists.sourceforge.net
> Subject: Re: [kvm-devel] QEMU / KVM support in libvirt & virt-manager
>
> Daniel P. Be
27 matches
Mail list logo
