On Thu, May 31, 2007 at 05:38:02PM +0900, Saori Fukuta wrote:
Hi,
The definition of (type ioemu) is *not* required by Xen3.1.
So I cut out it when xendConfigVersion is 4 or later.
okay, the patch looks fine, but what happens when you leave
(type ioemu) in 3.1 expressions ? Does it fail ?
On Fri, 1 Jun 2007 05:47:51 -0400 Daniel Veillard wrote:
okay, the patch looks fine, but what happens when you leave
(type ioemu) in 3.1 expressions ? Does it fail ? If it doesn't
fail, maybe we can avoid the complexity added by this patch, right ?
It does not fail on 3.1 even if I remove
Hi, Daniel
Thank you for your comment.
My experience with systematic logging at command line level is that
you end up polluting your file system with (hidden) log files, and while it
may be fine for a developper it's not something you want to inflict to
your customers. Also the fixed name
Hi
Would you give me a comment on this patch?
Thanks,
Masayuki Sunou.
In message [EMAIL PROTECTED]
[Libvir] [PATCH] Device attach/detach on virsh (command optionversion)
Masayuki Sunou [EMAIL PROTECTED] wrote:
Hi
This patch adds virsh attach-device/detach-device.
This supports a
On Do, Mai 31, 2007 at 05:49:41 -0400, Glen Deem wrote:
Hi all,
Hello, Glen.
I've created an HVM guest under RHES 5 (Xen 3.0.3) using xm create
but I cannot access it with vncviewer.
The Virtual Machine Manager also informs about graphics console
unavailability.
What am I doing
On Fri, Jun 01, 2007 at 07:35:00PM +0900, Nobuhiro Itou wrote:
Hi, Daniel
Hi Nobuhiro,
But since the patch is relatively simple based on existing virsh logging
code, I think this could go as a command line option for virsh, for example
--log filename
where the detailed logs can
On Fri, May 25, 2007 at 07:42:12PM +0900, Masayuki Sunou wrote:
Hi
Now, virsh attach-device displays the following messages when device
attribute of disk element is floppy in XML.
# virsh attach-device HVM_RH4_file floppy.xml
libvir: Xen Daemon error : POST operation failed: (xend.err
On Fri, Jun 01, 2007 at 07:29:25PM +0900, Saori Fukuta wrote:
On Fri, 1 Jun 2007 05:47:51 -0400 Daniel Veillard wrote:
okay, the patch looks fine, but what happens when you leave
(type ioemu) in 3.1 expressions ? Does it fail ? If it doesn't
fail, maybe we can avoid the complexity added
Thanks to Igor Chubin (spasibo) and Richard Jones, the qemu vnc server
was listening but I did not connect to its proper port (why libvirt
doesn't use IP:domU id kind of vnc connection and restricts the
server to local host only by default?).
Regards,
Glen
On 5/31/07, Glen Deem [EMAIL
On Fri, Jun 01, 2007 at 11:03:36AM -0400, Glen Deem wrote:
Thanks to Igor Chubin (spasibo) and Richard Jones, the qemu vnc server
was listening but I did not connect to its proper port (why libvirt
doesn't use IP:domU id kind of vnc connection and restricts the
server to local host only by
On Fr, Jun 01, 2007 at 06:11:22 +0300, Igor Chubin wrote:
On Fr, Jun 01, 2007 at 11:03:36 -0400, Glen Deem wrote:
Thanks to Igor Chubin (spasibo) and Richard Jones, the qemu vnc server
was listening but I did not connect to its proper port (why libvirt
doesn't use IP:domU id kind of vnc
Hi Dan,
I'm with you about the VNC authentication.
But I still don't understand the logic behind assigning HVM displays.
Instead of clear domU ID is the display number (vncunused 0), the
Virtual Machine Manager assigns vncunused to 1 and then calculates the
5900+ port, I suppose depending on
On Fri, Jun 01, 2007 at 02:13:15PM -0400, Glen Deem wrote:
Hi Dan,
I'm with you about the VNC authentication.
But I still don't understand the logic behind assigning HVM displays.
Instead of clear domU ID is the display number (vncunused 0), the
Virtual Machine Manager assigns vncunused
13 matches
Mail list logo
