search for: noonian

Package: xen-hypervisor-4.0-amd64 Version: 4.0.0-1 Severity: grave The only thing I can read is: ERROR: Unable to locate IOAPIC for GSI 2 ERROR: Unable to locate IOAPIC for GSI 9 ERROR: Unable to locate IOAPIC for GSI 9 cannot read /etc/fstab: no such file or directory mounting [...] failed: no such file or directory I boot with: moltiboot [xen] module [kernel] root=[uuid or device] ro quiet

I''m trying to get ceph working with decent performance (currently getting kb/second write performance!) and it seems that maybe the Debian wheezy kernel is just a bit too ancient. The 3.8 kernel from experimental works on bare metal, but when booting as dom0 under the xen hypervisor it crashes. I just figured out how to redirect xen output to my IPMI/BMC serial port and I see this:

...ing socket access. Because the daemon now may get relative paths, it changed to make it absolute on its own[1]. This means that a current libxenstore is not compatible with older xenstored. Bastian [1]: Changeset f1b435507f34 -- Suffocating together ... would create heroic camaraderie. -- Khan Noonian Singh, "Space Seed", stardate 3142.8 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/201105...

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: important After installing Xen and setting up (network-script 'network-bridge netdev=eth0') I no longer have a sane IPv6 address in the dom0: inet6 2001:700:300:d03f:fcff:ffff:feff:ffff/64 scope global dynamic valid_lft 2591977sec preferred_lft 604777sec This is probably since xenbr0 has a MAC address of fe:ff:ff:ff:ff:ff;

Hey all, I was watching some logs on a domU today and i suddenly noticed that the timestamps were off by something on the order of 47 seconds. I was surprised because *I don''t* run independent wall clocks. I checked some other domUs and the "drift" was also very close to that of the first domU. I also checked another dom0, Here the domUs were "only" out of sync by