Confirming because it happens to several users.
** Changed in: xen-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/205450
Title:
xend fails to connect g
I have had this problem for a while too. (swap.img failed error)?
I looked where Andrew Shugg said in here;
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/199533/comments/41
and sure enough none of those files exist. the whole directory of xen is
missing indeed?!
So whats the cure?
where c
Thanks, fortunately it was just a "kept back" packages issue:
1) I installed hardy heron when it was devel
2) During subsequent upgrades, the 2.6...*-15* kernel was kept not upgrading to
*-16*
3) apt-get dist-upgrade did the trick
4) tap:aio fixed the remaining vbd issue :)
Thanks !
--
xend fa
another workaround:
//understand losetup -f and -a
$ sudo losetup -f
$ sudo losetup -a
//actually do the mount and check that it worked and which device it picked
$ sudo losetup `sudo losetup -f`
$ sudo losetup -a
//then use phy:/dev/loop in your xen config file
I wouldn't recommend this f
I can confirm the bug and I've tried every single workaround/fix/variant
of domU config files with no success (waiting to mount root
filesystem)... is there a unified/unique way to deal with this issue ?
--
xend fails to connect guest to dom0 block device or loopback file
https://bugs.launchpad.n
Todd Deshane wrote:
> I don't the file:/ is a high priority. I am surprised that it doesn't
> work, I bet it is just a module not loading or something similar.
>
> deti: Did you notice that in the network bug that someone posted a patch
> and some links to custom packages, you might want to try th
I don't the file:/ is a high priority. I am surprised that it doesn't
work, I bet it is just a module not loading or something similar.
deti: Did you notice that in the network bug that someone posted a patch
and some links to custom packages, you might want to try those.
--
xend fails to connec
The "tap:aio:" and "xvda" workaround still seems to work - but should
this be the solution for upcoming 8.04 LTS version? Still networking
does not work either... this is depressing!
--
xend fails to connect guest to dom0 block device or loopback file
https://bugs.launchpad.net/bugs/205450
You re
Same here. Is there any known fix or workaround?
--
xend fails to connect guest to dom0 block device or loopback file
https://bugs.launchpad.net/bugs/205450
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
In linux-image-2.6.24-16-xen (2.6.24-16.30) I am back to the old
problem:
[EMAIL PROTECTED]:~$ sudo xm create -c /etc/xen/gutsy.cfg
Using config file "/etc/xen/gutsy.cfg".
Error: Device 51713 (vbd) could not be connected. losetup /dev/loop4
/xen/domains/gutsy/swap.img failed
[EMAIL PROTECTED]:~$
I can confirm this.
I added this to my initramfs modules:
sd_mod
scsi_mod
blkbk
xenblk
netloop
netbk
xennet
After i build by initramfs and uses hda1 in my dom0.cfg the guest starts
and the network works
--
xend fails to connect guest to dom0 block device or loopback file
https://bugs.launchpad
I've a problem similar to what Todd found in:
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/205450/comments/3
I've filed a separate bug report here:
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/214821
I'm using lvm instead of loopback image, and I've tried to change to hda
with
Todd Deshane said:
> It is actually fixed for me, but with the workarounds listed above:
>
> sda --> hda
>
> file:/ --> tap:aio/
You're right, with the following config I have a working domU - as far
as the block devices are concerned anyway. (I did not have the hda/sda
problem: strange.)
kern
It is actually fixed for me, but with the workarounds listed above:
sda --> hda
file:/ --> tap:aio/
a way to get the console:
adding extra='xencons=tty' to domU config
OR
adding xvc0 to /etc/inittab in domU file system
The bugs above could be fixed by fixing xen-tools and
deti said:
> The new kernel package 2.6.24-14 fixed this problem for me. Can anyone
> confirm this?
> The networking bug #204010 seems not to be fixed by now.
Not fixed for me by this package, no. =/
Andrew.
--
Andrew Shugg <[EMAIL PROTECTED]> http://www.neep.com.au/
"Just
The new kernel package 2.6.24-14 fixed this problem for me. Can anyone confirm
this?
The networking bug #204010 seems not to be fixed by now.
--
xend fails to connect guest to dom0 block device or loopback file
https://bugs.launchpad.net/bugs/205450
You received this bug notification because you
ok so a modprobe xennet gives me an eth0...
no connectivity yet though.
There are several strange bugs documented here, but I will move to
bug # 204010 to see if we can figure out the network stuff
--
xend fails to connect guest to dom0 block device or loopback file
https://bugs.launchpad.net/
UPDATE:
changing sda to hda in the guest config
gets a little farther into the boot:
[1.252536] thermal: Unknown symbol acpi_processor_set_thermal_limit
Done.
Begin: Running /scripts/init-premount ...
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
B
My best guess is that it is a problem with the xen initrd
(/boot/initrd.img-2.6.24-12-xen).
It seems to be only loading the fuse module and not the SCSI modules or
any of the xen modules.
The following are loaded by xend:
blktap
blkbk
xenblk
netloop
netbk
Do any of these and possible also SCSI
attaching xenguest1.cfg
** Attachment added: "guest config file (created by xen-tools) replaced file:/
with tap:aio"
http://launchpadlibrarian.net/12834466/xenguest1.cfg
--
xend fails to connect guest to dom0 block device or loopback file
https://bugs.launchpad.net/bugs/205450
You received t
Additional information:
Attaching bootup process that dies at:
0.242383]
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/rtc/hctosys.c:
unable to open rtc device (rtc0)
[0.242392] Freeing unused kernel memory: 216k freed
Loading, please wait...
Begin: Loading essential d
I can confirm this behavior.
I think that it is *also* a bug with xen-tools since it should use
tap:aio by default instead of file:/
changing to tap:aio lets the guest boot, but brings me back to this bug:
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/144631
** Changed in: xen-3.2 (Ubu
Did you try tap:aio instead of file: in the guest config file?
Also, there have been a number of problems fixed, but a couple lingering
issues with the latest packages.
see:
https://bugs.launchpad.net/ubuntu/+source/xen-3.2
also, make sure that the modules (loaded by /etc/init.d/xend are being l
23 matches
Mail list logo
