Hi Dustin,
Yes, the disks are definitely there... it seems to be some issue with
accessing them with the new release:
r...@defiant:~$ sudo ls -alF /dev/volume-a/ubuntu_8.10_server
/dev/volume-a/windows_xp_kvm
[sudo] password for russ:
lrwxrwxrwx 1 root root 40 2009-06-22 23:13 /dev/volume-a/ubu
Dustin,
Yep, they are there:
r...@defiant:/dev/volume-a# ls -al /dev/mapper
total 0
drwxr-xr-x 2 root root 300 2009-06-22 23:13 .
drwxr-xr-x 19 root root5060 2009-06-23 06:48 ..
crw-rw 1 root root 10, 61 2009-06-22 23:13 control
brw-rw 1 root disk 252, 0 2009-06-22 23:13 isw_
Public bug reported:
Binary package hint: kvm
I have two KVM guests which I installed while running Intrepid:
- Ubuntu Intrepid Server x86
- Windows XP Home Edition
These two guests ran fine, however, since I performed a dist-upgrade to
Jaunty neither of them will boot. Intrepid server boot fa
Did I report this in the wrong place or do I need to provide further
information?
--
Guest's built with Intrepid will not boot after upgrade to Jaunty
https://bugs.launchpad.net/bugs/371475
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Dustin,
I tend to use virt-manager to create my guests and then either start
them through there or using virsh. Anyhow, here is the process output
for the two intrepid created guests I'm having the issues with:
r...@defiant:~$ ps -ef | grep kvm
root 27112 1 21 18:18 ?00:00:
I can confirm the same issue with Jaunty. I believe it is due to the
fact that flash for linux is only compatible with V4L devices and not
V4L2.
--
webcam does not work with flash
https://bugs.launchpad.net/bugs/332377
You received this bug notification because you are a member of Ubuntu
Bugs, w
I had some free time today and did some 'destructive' debugging on this
problem, here's what I discovered:
I closed down firefox and performed 'rm -rf .mozilla' in my home
directory, effectively blowing away the entire firefox configuration. I
restarted firefox and went through preferences, setti
-
Your issue looks like its gmarks that was causing it. this may not be the same
for everyone but either way we are unable to support extensions we dont package.
-
I certainly agree with that. I'm more concerned that my experience with
add-ons here is likely to be the cause of everyone e
I too can confirm that the hardy-proposed kernel for 32bit systems isn't
fixing the issue here also. I can see RX/TX packets on the vif1.0
interface in Dom0, however, still no reply to pings / traffic from
inside or outside DomU.
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6
Thanks for the responses, Hirano & janevirt.
I tried Hirano's 32bit kernel and had no luck, now I'm on the hardy-
proposed kernel and still have no luck.
To answer your question, janevirt, I'm using 2.6.24-17-xen. I'm
installing via xen-tools, which seems (to my surprise) to be booting
using dom
Ok,
The good news here is that I'm an idiot!!! :)
I'm very, very new to xen and had accepted pretty much the defaults for
the xend configuration.
I was setting up my DomU to use routed traffic, however, my xend config
was configured to use bridging.
I switched from:
(network-script network-brid
11 matches
Mail list logo
