On Apr 01, Russell Coker <[EMAIL PROTECTED]> wrote:
> # xm create -c ha1
> Using config file "/etc/xen/ha1".
> Error: Device 768 (vbd) could not be connected. Hotplug scripts not working.
>
> The above is all I get from the Xen console.
Which could mean anything, but usually means that your xen
On Sunday 01 April 2007 21:59, "Marco d'Itri" <[EMAIL PROTECTED]> wrote:
> What about you look at the xen console while the guest boots and then
> copy and paste the messages?
# xm create -c ha1
Using config file "/etc/xen/ha1".
Error: Device 768 (vbd) could not be connected. Hotplug scripts not w
On Apr 01, Russell Coker <[EMAIL PROTECTED]> wrote:
> What is the default location for the log messages that you desire?
What about you look at the xen console while the guest boots and then
copy and paste the messages?
--
ciao,
Marco
signature.asc
Description: Digital signature
On Sunday 01 April 2007 19:09, "Marco d'Itri" <[EMAIL PROTECTED]> wrote:
> On Apr 01, Russell Coker <[EMAIL PROTECTED]> wrote:
> > The messages from the udev init script, where do they end up? What log
> > entries would you like me to send you?
>
> To the boot log? I can't tell how your system is
On Apr 01, Russell Coker <[EMAIL PROTECTED]> wrote:
> The messages from the udev init script, where do they end up? What log
> entries would you like me to send you?
To the boot log? I can't tell how your system is configured, and "not
enabled" is not an useful bug report.
--
ciao,
Marco
sig
reopen 401673
stop
This bug occurs on a freshly installed Etch system with all the updates
applied.
The messages from the udev init script, where do they end up? What log
entries would you like me to send you?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Tr
6 matches
Mail list logo
