Hi,
Thank you for your comment.
On Fri, 11 May 2007 19:29:48 +0100 "Daniel P. Berrange" wrote:
> On Fri, May 11, 2007 at 07:15:33PM +0100, Daniel P. Berrange wrote:
> >
> > If the guest was created by libvirt, then I consider it a bug if the XML
> > dump does not allow re-creation in exact same
Hi
This patch adds virsh attach-device/detach-device.
Currently it supports a definition of a device by XML(proposal 2).
I plan to submit command option version (proposal 1) later.
Any comments are welcome!
Signed-off-by: Masayuki Sunou <[EMAIL PROTECTED]>
Thanks,
Masayuki Sunou.
-
On Fri, 11 May 2007 14:06:07 -0400 Daniel Veillard wrote:
> > Can I ask something ? That means adding xmlDomainPtr to virDomainPtr,
> > like this ?
> >
> > struct _virDomain {
> > unsigned int magic; /* specific value to check */
> > int uses;/*
"If QEMU fails during startup" ... please tell me how to start QEMU as a
service!
Thanks, smoyer
-Original Message-
From: [EMAIL PROTECTED] on behalf of Daniel P. Berrange
Sent: Tue 5/15/2007 6:27 PM
To: Mark McLoughlin
Cc: libvir-list@redhat.com
Subject: Re: [Libvir] PATCH: Create a lo
On Tue, May 15, 2007 at 06:37:40PM +0100, Daniel P. Berrange wrote:
> On Tue, May 15, 2007 at 05:15:04PM +0100, Daniel P. Berrange wrote:
> > On Tue, May 15, 2007 at 05:09:56PM +0100, Mark McLoughlin wrote:
> > > On Tue, 2007-05-15 at 17:04 +0100, Daniel P. Berrange wrote:
> > >
> > > > For every
The problem I'm having with respect to QEMU is that qemu:///system doesn't form
a connection. What has to be running before I start the virsh command below?
I know my images are okay, I just can't manage them with
virt-manager/virt-install/virsh->libvirt.
Thanks, smoyer
On Tuesday 15 May 200
On Tue, May 15, 2007 at 05:15:04PM +0100, Daniel P. Berrange wrote:
> On Tue, May 15, 2007 at 05:09:56PM +0100, Mark McLoughlin wrote:
> > On Tue, 2007-05-15 at 17:04 +0100, Daniel P. Berrange wrote:
> >
> > > For every VM we start it will create a logfile
> > >
> > > /etc/libvirt/qemu/logs/[vm
On Tue, May 15, 2007 at 05:09:56PM +0100, Mark McLoughlin wrote:
> On Tue, 2007-05-15 at 17:04 +0100, Daniel P. Berrange wrote:
>
> > For every VM we start it will create a logfile
> >
> > /etc/libvirt/qemu/logs/[vmname].log
>
> Why not /var/log? /etc/ isn't the place for this kind of st
On Tue, 2007-05-15 at 17:04 +0100, Daniel P. Berrange wrote:
> For every VM we start it will create a logfile
>
> /etc/libvirt/qemu/logs/[vmname].log
Why not /var/log? /etc/ isn't the place for this kind of stuff, surely.
(Putting them in their own directory is nice, though -
Most of the error reporting the QEMU daemon is focused on sending errors
wrt to RPC ops to the client. There is no provision currently for getting
info about the QEMU vm itself when problems occur. The most common problem
is some mis-configurable in the XML causes qemu to fail to start up. This
res
Hi Richard,
On 14.05.2007, at 18:00, Richard W.M. Jones wrote:
Jan Michael wrote:
32266 stat64("/var/run/xenstored/socket", {st_mode=S_IFSOCK|
0600,st_size=0, ...}) = 0
32266 socket(PF_FILE, SOCK_STREAM, 0) = 4
32266 fcntl64(4, F_GETFD) = 0
32266 fcntl64(4, F_SETFD, FD_CLO
Hi,
I made the patch which output debug messages and error messages
of virsh to the log file.
I think that it is necessary to leave logs to the file for the
investigation at the failure.
Debug messages can take appointed optional information,
and error messages will make it easy to specify a cause
12 matches
Mail list logo
