Peter Viskup wrote:
> Hello Jonathan,
> thanks for taking care. I was not experiencing this issue since
> then.
Interesting. Thanks for the update.
[...]
> I am still using the system and going to update it to squeeze within
> next two weeks.
Best of luck. :)
--
To UNSUBSCRIBE, email to de
Peter Viskup writes:
> 'xm block-attach phy:data/disk /dev/xvda6 w'
I can attach a block device
$ sudo xm block-attach 27 file:/local/xen/lindi-exp1/disk.img /dev/xvda w
$ sudo xm block-list 27
Vdev BE handle state evt-ch ring-ref BE-path
51712 00 4 9 770 /local/domain/0/
Hello Timo,
for some reason I didn't received your question and I found it just now
on bugs.debian.org pages.
I didn't record my previous commands but I used standard xm block-attach
syntax from vhost config like:
'xm block-attach phy:data/disk /dev/xvda6 w'
I am mapping LVM LV's from VG n
Peter Viskup writes:
> Execution of xm block-attach to PV domU failed and I have got Ooops
> kernel messages in attachment.
Can you tell me the exact block-attach command so that I can at least
test that it works with squeeze? (I doubt it can be fixed for lenny.)
--
To UNSUBSCRIBE, email to
Package: linux-image-2.6-xen-amd64
Version: 2.6.26-26lenny1
Severity: critical
Tags: lenny
Execution of xm block-attach to PV domU failed and I have got Ooops
kernel messages in attachment.
After that domU wasn't manageable from dom0 - all xm commands were not
successful and I had to shutdown
5 matches
Mail list logo
